Open
Conversation
adamblanchard
requested changes
Mar 9, 2026
| @@ -0,0 +1,135 @@ | |||
| <!doctype html> | |||
Contributor
There was a problem hiding this comment.
So as you said this code is for the trainee exercises? If they will run it, the code should live here https://github.com/HackYourFuture-CPH/hyf-assignment-template under the module name/week somewhere.
If we add changes here, trainees will have to follow the sync instructions so it would be helpful if you communicate that with them if they are missing anything as you add stuff there.
Contributor
Author
There was a problem hiding this comment.
Removed examples from this repo and added here: HackYourFuture-CPH/hyf-assignment-template#205
| # Assignment | ||
|
|
||
| <!-- The type of assignment you write will vary a lot depending on the module. But either way, all of the set up, instructions and tips should be captured in here. --> | ||
| Only **task 3** (movies) requires a frontend: HTML + CSS + JavaScript that runs in the browser, with the result visible in the page. **Tasks 1 and 2** do not: for task 1 submit the JavaScript (map/filter) solution (an HTML page is optional though); for task 2 just complete the Katas. |
Contributor
There was a problem hiding this comment.
great to be clear here
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.