Frontend :: Advanced JS, weeks 3 and 4#284
Merged
adamblanchard merged 4 commits intomainfrom Mar 29, 2026
Merged
Conversation
…into team33-frontend-advancedjs
markitosha
changed the title
adamblanchard
approved these changes
Mar 29, 2026
Contributor
adamblanchard
left a comment
adamblanchard
left a comment
There was a problem hiding this comment.
Looks good to me. I checked it on gitbook too and looks good.
Thanks @markitosha!
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
As usual -- this updates the frontend Advanced JavaScript module so trainees and mentors treat the browser as the main place to see results, not only the console. It adds runnable session demos (worksheet, solution, light styling) and reorganises week 4 around a clearer story for classes and errors.
Week 4
There was a longer discussion in pull request 248. This change takes a lighter path than that full proposal: render-focused classes plus
Error-s only for explainingextends. That mirrors how you think about UI in real apps and lines up reasonably with what comes later in React, without teaching React here.