Skip to content

Conversation

@adamblanchard
Copy link
Contributor

@adamblanchard adamblanchard commented Jan 15, 2026

The idea here is to:

  1. Document how the final projects will/can run
  2. Capture the learning goals for all final projects
  3. Capture the specific requirements for each specialism

I have written these requirements from a mix of staff conversations, the old final project repo, and the new learning goals overviews. They are 100% up for discussion, I am only writing these down as a starting point.

This PR now contains an initial outline of the final projects for both frontend and backend. Frontend is "done" in that i have an initial version of the requirements here. Backend still has todos for those, might need some help there.

We will also add session plans later.

But i'd like to merge this in it's current state, and keep adding content iteratively.

The easiest way to view it:

  1. Final project (frontend)
  2. Final project (backend)


## Organisation Requirements
## Organisational Requirements

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Based on our talk at HYF 2.0, Here the bullet points for the final P (from Soheib and me) regarding the project presentations.

Please feel free to suggest changes if needed, and add your ideas! 🙃

🎮 Final Project Presentation Guidelines
When: 3rd week of the Foundation project
Duration: 7–10 minutes per team

Presentation structure:

Start with your Trello board → Explain your workflow, task organization, and process.

Show your project → Demonstrate the working game/application.

Talk about contributions → Each team member should briefly explain what they worked on.

Requirements before presentation day:
✅ Project must be fully deployed and live.(did we decide which platform for deployment?)
✅ Prepare a QR code linking to your live project.

During the session:

Share the QR code so other teams can test your game on their devices.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it would also be good to have consistent steps for the Specialization final project.
That way, trainees would know what to expect in advance, and we don’t have to wait until two days before the presentation to tell them.

Would you like me to draft a similar set of guidelines for the Specialization phase as well?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@saloumeh-67 The guidelines sound good. The default deployment for the projects is render right now, since we have instructions for those.

Yes, would be great to get similar guidelines for the specialism so we can just get them in here already!

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@saloumeh-67 and I decided to merge this pr first, then iterate with the session plans for each final project after.

@adamblanchard adamblanchard changed the title WIP: Specialism final projects Specialism final projects Jan 20, 2026
@adamblanchard adamblanchard marked this pull request as ready for review January 20, 2026 11:52
@adamblanchard adamblanchard requested a review from a team as a code owner January 20, 2026 11:52
@adamblanchard
Copy link
Contributor Author

Since there are only structural changes since the last approve, i'm merging it.

@adamblanchard adamblanchard merged commit ac0be21 into main Jan 20, 2026
3 checks passed
@adamblanchard adamblanchard deleted the specialism-final-projects branch January 20, 2026 11:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Backlog

Development

Successfully merging this pull request may close these issues.

3 participants