Hi!
I've noticed this random hash at the end of the curriculum readme
Is there any purpose for this?

https://frontendmasters.com/books/front-end-handbook/2018/

HTML/CSS week0 has outdated links

Description

Update some modules (specifically JS)to use more project-driven homework instead of independent exercises. The idea is to help people build more meaningful projects that they are more engaged with, have more scope for developing their skills, and have something more useful to show at the end of it in e.g. interviews.

It's already been tried out in Aarhus with great feedback, and now with team28. More info here https://github.com/HackYourFuture-CPH/js-projects

Steps:

1. Evaluate appropriate approach
2. Choose modules to update
3. Test them as projects

Notes:

• This is already in progress
• Find "real life" examples of software development, both in teams but also in interviews. Tech interviews are usually mini projects in themselves. We could use that format at some points in the program.

Todo:

• Need to make it clear in modules where the homework has been replaced with projects or not (it's confusing right now)

Saw this at least on git and node.js (all weeks).

Example: https://github.com/HackYourFuture-CPH/node.js/blob/main/week1/homework/readme.md
"this resource" page 404s.

Some .md files don't follow the same structure as others.

I haven't spotted any major issues so far other than inconsistency, hard to follow, some good sections in some are missing in others.

I propose we put a template together for each, so when we review the modules we can fix them as best we can to towards matching the template.

Outcomes of this task:
A template .md for each of the following:

1. readme.md (module dir)
2. readme.md (weekX dir)
3. homework.md
4. lesson-plan.md
5. preparation.md

WIP