Iterate HTML-CSS Sprint 1 timings from NW6

[JayMayer]

What does this change?

Module: HTML-CSS
Week(s): 1

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

Description

Changes timings of the "Transferable skills", "Feedback", and "Pairs for next week" sections of HTML-CSS / Sprint 1 / Day-Plan

Fixes #308

Who needs to know about this?

@Dedekind561

Rendered Pages

[netlify]

✅ Deploy Preview for cyf-curriculum ready!

Name	Link
🔨 Latest commit	5c3c79f
🔍 Latest deploy log	https://app.netlify.com/sites/cyf-curriculum/deploys/65b6848661075f00089b273b
😎 Deploy Preview	https://deploy-preview-306--cyf-curriculum.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 100 (no change from production) Accessibility: 100 (no change from production) Best Practices: 100 (no change from production) SEO: 91 (no change from production) PWA: 60 (no change from production) View the detailed breakdown and full score reports

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[kfklein15]

On the day plan for HTML S1, lunch shows 11.20 am. Is that because we need to adjust the hours of the morning exercise (it's a tech ed one)?

[varuna-v]

Yes, you're right, the hours of the morning exercise need updating too. #308

I've pushed a change so the day plan will be:

Energiser 10:00 - 10:20
DevTools Workshop 10:20 - 12:20
Lunch 12:20 - 13:20
Study Groups 13:20 - 15:00
Break 15:00 - 15:15
Transferable Skills 15:15 - 16:00
Feedback 16:00 - 16:30
Retro From 16:30

This removes one study group - does that work? Or should we try to fit less in the day so we have more study group time?

[SallyMcGrath]

@varuna-v I think we need more study group time.

[40thieves]

I've taken this off the tech ed board as we think it's in PD's court at the moment.

[LaraHuzjan]

@kfklein15 not sure what the situation is here...I saw there was a problem with timing on the tech side, with PD I think the timings are a bit longer than the content says/requires. For ex 'Feedback' was to be 15 min long but there is a 30-minute slot.
If that were corrected there'd be more time. I hope I understood the issue

[kfklein15]

@varuna-v and @JayMayer , any reason why our feedback session for PD in the afternoon was increased to 30 min, please? Maybe because 15 min wasn't enough when you tried doing the exercise in class?

[JayMayer]

@kfklein15 my memory is that 30 minutes was the time taken to introduce the task, run through the 15 minute role play, then have a group discussion on what was learned.

I appreciate not all of those activities are documented as part of the workshop, but it’s always nice to have time to reflect on the activity with the trainees, and it often leads to interesting discussions.

[kfklein15]

This is super helpful, thank you @JayMayer . We should try as much as possible to document things properly as per how it will be run, so very good input.

@LaraHuzjan , let's take a look at this and see what/how we can change this, please? Please raise a ticket on our board linking to this and explaining what needs to be checked (total time of all activities). I will approve this PR in the meantime.

[kfklein15]

Approving this, although the day is using more than the 1h for PD. We will review this in the near future in a separate ticket - these changes can be done directly via our PD CMS.

[kfklein15]

@JayMayer , is this ready to be merged?

[JayMayer]

@kfklein15 ready to merge 👍

[kfklein15]

It's showing conflicts. Can work on them and then merge it, please? :)

[JayMayer]

@kfklein15 the branch is now up-to-date

[LaraHuzjan]

@kfklein15 have created the ticket