📅 Day plan

A scheduled plan of activities for a class day with times and breaks.

🔖
  1. Energiser
  2. Placeholder Workshop
  3. Lunch
  4. Study Group 2
  5. Code Review
  6. Afternoon break
  7. Study Group 2
  8. Retro

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.

  1. Traffic Jam: re-order the cars to unblock yourself
  2. Telephone: draw the words and write the pictures
  3. 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 🔗

Learning Objectives

Workshop Name

Replace this readme with the requirements for your workshop

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.

Ensure every site configures markup 🔗

This avoids needing to notice and play whack-a-mole when things aren’t configured as we expect.

Also, add a –fix mode which will try to fix things for you.

Start a review
rm emojis from label filter on how this works 🔗
Some of these emojis exist on github but not Hugo so the perfect match filter fails and the backlog is empty. I have removed the emojis for safety in this case. Start a review
Content 1125 Add Class Planner to the 'How it works' info setup/onboarding module 🔗

What does this change?

Describes classplanner and the point of it for teams Links to planner

Fixes #1125

Common Content?

htw/classplanner

Org Content?

HTW | Self coordinate | Prep

Checklist

Who needs to know about this?

@NJ-G

Start a review
1211 details tags don't show up inside note 🔗

What does this change?

adds goldmark config to tracks because this cannot be inherited from theme

without configuring goldmark anything which does complex mixes of md and html goes wrong. You can tell it’s goldmark, or a markdown rendering problem mixing in HTML, because in the rendered view it says <!--raw HTML omitted -->

Fixes #1211

Org Content?

Tracks | hugo.toml

Checklist

Who needs to know about this?

Start a review
Content: STAD day plans update 🔗

What does this change?

  • slowly fade onboarding “blockers” and “wrap” into standups and retros
  • assign workshops they have context for
  • add structured activities to introduce coursework tasks

Fixes #1182 Fixes #1168

Common Content?

  • standup block
  • tweaked some energisers

Org Content?

STAD | 123 | Day Plans

Checklist

Who needs to know about this?

Start a review
See more pull requests

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>

A retro is a chance to reflect. You can do this on RetroTool (create a free anonymous retro and share the link with the class) or on sticky notes on a wall.

  1. Set a timer for 5 minutes. There’s one on the RetroTool too.
  2. Write down as many things as you can think of that you’d like to start, stop, and continue doing next sprint.
  3. Write one point per note and keep it short.
  4. When the timer goes off, one person should set a timer for 1 minute and group the notes into themes.
  5. 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.
  6. Finally, set a timer for 8 minutes and all discuss the top three themes.