Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 15 additions & 3 deletions courses/foundation/final-project/project-brief.md
Original file line number Diff line number Diff line change
Expand Up @@ -57,8 +57,6 @@ Tips:

1. Revealing a card is not the same as a click! Your counter should incrememt with reveals.

### Week 2 Milestone

#### Storing and Retrieving Your Cards

Up until now, your cards have been hardcoded in your app code. Instead, these should be stored in a database and fetched via an API which the frontend can use to retrieve and display them.
Expand All @@ -73,6 +71,8 @@ Tips:
1. After these changes, your game should appear to the player to function just as it did before.
2. Refer to your exercises from previous modules if you need a reminder on creating databases and APIs.

### Week 2 Milestone

#### The Game Logic

The final step is to add the game logic, so it becomes a playable game!
Expand All @@ -82,7 +82,7 @@ The final step is to add the game logic, so it becomes a playable game!
- [ ] Once all cards have disappeared, the player wins and the game is over
- [ ] After winning, the player should be able to restart the game and play again

### Week 3 Milestone - Your own ideas!
#### Your Own Ideas!

Now your game is working, it's time to introduce your own features! Think of some improvements or changes to the game and implement it.

Expand All @@ -99,3 +99,15 @@ Some ideas for inspiration:
- [ ] Let the player choose a name, and save their score in the database
- [ ] Implement a leaderboard for the top 10 scores
- [ ] ... and many more!

### Week 3 Milestone

At the third session you'll be sharing a presentation. Read the [Session Plan](./session-plan.md) for more info.

Make sure you have all of the final details of your project working, as well as tidying up your deliverables such as your Trello board ready to present.

#### Deploy your app!

Part of the reward of building a web app is putting it live on the web! By completing this step you can experience the joy of showcasing your app on a public URL.

Follow the guide at [Deployment Quick Start](https://program.hackyourfuture.dk/trainee/technical-guides/deployment-quick-start) and give it a go.
8 changes: 7 additions & 1 deletion courses/foundation/final-project/session-plan.md
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ Note: Trainees will work in pairs to compelete the project. These pairs will hav
- Actively work your way around the pairs, making sure everyone is making progress as they should.
- If multiple people are facing similar challenges, take the opportunity to "pause" the session and walk through something together out loud (e.g. creating a new github repo).

### The following sessions
### The second session

- Progress update: Check in on what people have completed since last week, what they found hard, questions to answer, and encourage some people to demo their progress in front of the team.
- Teaching moment: If there were any significant issues or confusions that came up, spend some time diving into them in detail.
Expand Down Expand Up @@ -48,3 +48,9 @@ During the session:

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

### The final assignment

After the presentation, trainees will have recently lots of feedback and some ideas for improving the app. Each trainee should choose 1 (or more) improvement to implement as a follow up assignment. The size of the change is not so important, since a small code change could have a big improvement on the app or to fix a bug. The important part is that they choose a valuable change from the feedback and implement it.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
After the presentation, trainees will have recently lots of feedback and some ideas for improving the app. Each trainee should choose 1 (or more) improvement to implement as a follow up assignment. The size of the change is not so important, since a small code change could have a big improvement on the app or to fix a bug. The important part is that they choose a valuable change from the feedback and implement it.
After the presentation, trainees will have recently received lots of feedback and ideas for improving the app. Each trainee should choose 1 (or more) improvement to implement as a follow up assignment. The size of the change is not so important, since a small code change can significantly improve the app or fix a bug. The important part is that they choose a valuable change from the feedback and implement it.


This helps close the feedback loop from the last session, and provides closure for the final state of the project before completing the course.