📅 Day plan
A scheduled plan of activities for a class day with times and breaks.
This view builds an agenda for class days. We built this because we used to spend a lot of time making spreadsheets every single week and class days could get chaotic and disruptive to learning. Now everyone knows what to do when. Learners can plan things like prayers or medication. Volunteers can see when they’re needed. Everyone can see when they can take a break.
The day plan will create a schedule from the time (in minutes) stored on each block using the time-stamper web component. You can override this time on your day plan by adding a time parameter as shown in the front matter.
This view doesn’t expect any content in the .Content section, but it exists in case you need to put a temporary notice up that everyone will see. It’s for temporary content only. If you just want to add a description of the day, add it to a .Description parameter in the front matter.
We also now can find out who is in class with a simple register. By default, a register will show at the top of the agenda. This register is an auto-detected Netlify form. If you don’t want this, add noRegister=true to the front matter, as this example does.
Energiser
Every session begins with an energiser. Usually there’s a rota showing who will lead the energiser. We have some favourite games you can play if you are stuck.
- Traffic Jam: re-order the cars to unblock yourself
- Telephone: draw the words and write the pictures
- Popcorn show and tell: popcorn around the room and show one nearby object or something in your pocket or bag and explain what it means to you.
Placeholder Workshop 🔗
Workshop Name
Replace this readme with the requirements for your workshop
Learning Objectives
Requirements
Explain the requirements of the workshop. You might want to talk about goals here. You might want to use formal specifications like Given/When/Then. It’s ok for requirements to be in different formats. We want trainees to learn to interpret requirements in many settings and expressions. Just make sure your workshop is active and not a lecture.
Always write your workshop in a readme.md in a folder with the same name as the workshop. This makes it easy to find and easy to show on the curriculum website.
Acceptance Criteria
- I have provided clear success criteria
- These might be related to the objectives and the requirements
- I have given some simple, clear ways for trainees to evaluate their work
- I have run Lighthouse and my Accessibility score is 100
Community Lunch
Every Saturday we cook and eat together. We share our food and our stories. We learn about each other and the world. We build community.
This is everyone’s responsibility, so help with what is needed to make this happen, for example, organising the food, setting up the table, washing up, tidying up, etc. You can do something different every week. You don’t need to be constantly responsible for the same task.
Study Group
Learning Objectives
What are we doing now?
You’re going to use this time to work through coursework. Your cohort will collectively self-organise to work through the coursework together in your own way. Sort yourselves into groups that work for you.
Use this time wisely
You will have study time in almost every class day. Don’t waste it. Use it to:
- work through the coursework
- ask questions and get unblocked
- give and receive code review
- work on your portfolio
- develop your own projects
🛎️ Code waiting for review 🔗
Below are trainee coursework Pull Requests that need to be reviewed by volunteers.
Move React to be an ITP track 🔗
What does this change?
This is re-organising it based on what prereq knowledge you need to do it, rather than how prepared you’ll be for a job having done it.
I’m not sure that’s correct. But it felt maybe useful. Thoughts welcome!
Org Content?
Moves a track.
Checklist
- I have read the contributing guidelines
- I have checked my spelling and grammar with an automated tool
- I have previewed my changes to check the markdown renders as I intend
- I have run my code to check it works
- My changes follow our Style Guide
Rework DOM to better separate elements from events 🔗
What does this change?
Fixes https://github.com/CodeYourFuture/curriculum/issues/332
This way, we:
- Fully handle accessing and setting DOM element properties in one chunk, then introduce events, rather than muddling the two together.
- Identify that there are two common actions to do, and talk through identifying and addressing this.
- Pull out the “what is the character limit” to be defined by the HTML attribute, rather than duplicated in the script.
- Practice breaking down the “remaining characters” problem into sub-problems.
- Generally solve things more incrementally.
- Explicitly call out “do a clean-up refactoring” at the end.
Also some misc copy edits.
Common Content?
Yes - changes, reorders, and adds blocks to much of JS2.
Org Content?
Data Groups Sprint 3
Checklist
- I have read the contributing guidelines
- I have checked my spelling and grammar with an automated tool
- I have previewed my changes to check the markdown renders as I intend
- I have run my code to check it works
- My changes follow our Style Guide
Afternoon Break
Please feel comfortable and welcome to pray at this time if this is part of your religion.
If you are breastfeeding and would like a private space, please let us know.
Study Group
Learning Objectives
What are we doing now?
You’re going to use this time to work through coursework. Your cohort will collectively self-organise to work through the coursework together in your own way. Sort yourselves into groups that work for you.
Use this time wisely
You will have study time in almost every class day. Don’t waste it. Use it to:
- work through the coursework
- ask questions and get unblocked
- give and receive code review
- work on your portfolio
- develop your own projects
Retro: Start / Stop / Continue
Retro (20 minutes)</span>
Retro (20 minutes)</span>
A retro is a chance to reflect. You can do this on a FigJam (make sure someone makes a copy of the template before you start) or on sticky notes on a wall.
- Set a timer for 5 minutes. There’s one on the FigJam too.
- Write down as many things as you can think of that you’d like to start, stop, and continue doing next sprint.
- Write one point per note and keep it short.
- When the timer goes off, one person should set a timer for 1 minute and group the notes into themes.
- Next, set a timer for 2 minutes and all vote on the most important themes by adding a dot or a +1 to the note.
- Finally, set a timer for 8 minutes and all discuss the top three themes.