Merged
Conversation
adamblanchard
requested changes
Mar 9, 2026
courses/frontend/advanced-javascript/week1/session-materials/listings-demo/index.html
Outdated
Show resolved
Hide resolved
adamblanchard
approved these changes
Mar 10, 2026
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
Task content is unchanged (learning goals, code snippets, Katas links, movies list, etc.). This PR updates format, structure, and framing across Week 1 so the frontend team consistently connects JavaScript with the frontend—JS driving a visible, interactive UI.
What changed
Week 1 README – A short paragraph states that the module encourages building a real frontend (not just writing JS in isolation), and that the exercises are set up so JS drives the page.
Assignment – The frontend requirement is introduced and spelled out: only the movies task (task 3) must have a page.
Session plan – A Mentors demo section is added and wired into the outline. For each topic (forEach, map, filter, and then chaining) the plan points to the demo and specifies which TODO to implement in class (FOREACH, MAP, FILTER, CHAINING).
Exercises – The exercises doc is rewritten for trainees to have more instructions and include work with Listing demo. Each exercise has a “What should happen” so trainees know the goal before coding. The old “Listing project” story is replaced by a concrete Task 4 (advanced filters) that matches the demo.
Session materials – Two runnable demos are added:
Mentors demo – A page with mentor cards and buttons. Mentors can use it live: the code file has TODOs (forEach, map, filter, chaining) to fill in during the session. There is a solution file and a README that explain the files and how to find the TODOs.
Listings demo – A page with exercises trainees work in.