HTML CSS coursework review

docs/contributing/minutes.md

@@ -16,6 +16,53 @@ Attendees:
 
 ---
 
+## 2022-11-24
+
+Attendees:
+
+### ❗Actions from last time
+
+- Open a ticket to add the Bandit to the terminal lesson (Sally) []
+
+### 📝 Agenda points
+
+#### Feedback from flipped classroom Q & A
+
+- [Here's a link to the notes from the Q&A session](https://docs.google.com/document/d/122t689Qpe_UbrrhW1xvpN88arM_I8ZGcoIAE9hd7ESs/edit) with Shaun and Zacheé re flipped classroom in S Africa
+- Greg likes to think of flipped classroom more as having really well thought out prep work that makes the Saturday class run more smoothly
+
+#### Brief talk through Saturday flipped classroom presentation
+
+- Some discussion around the grouping of trainees on a Saturday:
+
+  - Ask trainees how long they've spent on the prep work in a given week
+  - May need to say in advance that someone in their group is going to be slightly/considerably more advanced than them
+  - Very important to normalise the differentiation
+  - Alternatively leave it vague who is strong/weak before grouping up trainees
+  - If 2 people are trying to learn the same thing, say `useEffect`, then it makes sense for the `useEffect` people to work together
+  - In general, the less they know specifically -> more mixed ability becomes possible
+  - Could potentially get more frustration with people working at different levels
+  - If we assume people are learning different things then groups don't matter massively
+
+- Peer-2-peer collaboration will work better if trainees provide verbal explanations of how their code works
+
+#### Video recording volunteers
+
+- Lo-fi recordings done with volunteers
+- Greg, very interested in helping with recordings - at some point in the future making some videos when he gains capacity
+- Will to observe something beforehand to see how it works
+
+#### Welcome to Will
+
+- Welcome to Will who's joining on syllabus! 🎉
+- Will was previously a mentor in 2nd LDN class in 2018
+
+### ❗Actions
+
+- [] Mitch and Will to catch up on a module PR later this week
+
+---
+
 ## 2022-11-10
 
 ### ❗ Actions from last time

docs/contributing/react/minutes.md

@@ -4,14 +4,43 @@ title: React Module Syllabus Team Minutes
 sidebar_label: Team Minutes
 ---
 
+## 2022-11-07
+
+Present: Ali, Tom
+
+## Agenda Items
+- Ali leaving the React module team (@Ali)
+  - Ali is planning to leave the React module syllabus team (as he originally planned), though will still be around in CYF to help
+	- His role was to set up the team and get the ball rolling, which has been successful
+	- All of the team are free to join the Global Syllabus team meeting
+- Team time/task progress - something's not working (@Tom)
+  - Not everyone in attendance at regular meetings, and often rescheduled
+	- Few agenda points and not much work in progress on the board
+	- This not a problem with the individuals in the team! It is a symptom of the team's setup
+	- The Global Syllabus team generally has enough work on so that everyone has a task assigned, meaning there are always agenda point for the regular meeting
+	- The React module is generally complete and only needs a few improvements, with no specific deadlines, so tickets are not always in progress
+	- No specific feedback from module coordinators to update the module - does this mean the module is good, or is there just no feedback?
+	- Even if there was enough work (i.e. feedback to re-write the whole module, which is unlikely), would it take 4 people more than 1 month?
+	- Maybe the team needs restructuring & re-focussing. Current 'TODO' work could be completed in less than 1 month, will the team have no purpose after this?
+- How can we get feedback for the module?
+	- Cape Town towards end of module instruction, Birmingham and Manchester starting in November, London in March
+  - A good opportunity to get feedback from module coordinators
+
+### Action Items
+- Ali: reach out/refer us to city coordinators who can tell us who the most recent module instructor was, to get feedback
+- Ali: discuss with Global Syllabus team re above agenda items
+- Tom: create ticket to update module coordinator page to 'keep notes on questions & feedback and submit tickets at end of teaching'
+
+---
+
 ## 2022-10-17 - React Syllabus
 
 Attendees:
 - Ali
 - Alex
 - Zach
 - Tom
--
+
 ### 3 => 4 Week
 - Alex introduced the concept  of separating course into 4
 - Presentational components -> state -> syncronosity ->  forms
@@ -58,6 +87,7 @@ Attendees:
 - Internal push for more testing - open call for TDD
 	-	Alex to join call on 1st of November
 
+---
 
 ## 2022-09-12
 
@@ -94,7 +124,7 @@ Present: Ali, Alex, Tom, Sharlu
 - Alex: convert lessons into a single .md file to find 'splitting points'
 - All: discuss sync/async suitable 'splitting points' in the 3 week course for updating to a 4 week course (#468)
 
-
+---
 
 ## 2022-08-01
 

docs/finalproject/intro.md

@@ -37,21 +37,21 @@ The final projects form the final module of the course, comprising four weeks fo
 
 Ideally, the project team would consist of the following:
 
-- Four CYF trainees;
-- Three volunteer mentors, forming a [balanced team](https://www.youtube.com/watch?v=Z_Q4Q8rCVpU); and
-- A product owner.
+- Three or four CYF trainees;
+- Two volunteer mentors ([Tech Lead](https://docs.codeyourfuture.io/volunteers/teams-1/cyf-products-final-projects/roles/tech-lead) and [Product Manager](https://docs.codeyourfuture.io/volunteers/teams-1/cyf-products-final-projects/roles/product-manager), forming a [balanced team](https://www.youtube.com/watch?v=Z_Q4Q8rCVpU); and
+- A [product owner](https://docs.codeyourfuture.io/volunteers/teams-1/cyf-products-final-projects/roles/product-owner).
 
 The mentor group would include an engineer (responsible for unblocking technical/architectural issues, _not_ an extra developer), designer (responsible for user research and UI/UX) and product manager (responsible for prioritisation and alignment with the product owner’s goals). This gives an opportunity to bring in volunteers from the broader tech community, and exposes the trainees to the roles they could be collaborating with in employment.
 
-For more information on roles [click here](./roles.md)
+[More information on volunteer roles](https://docs.codeyourfuture.io/volunteers/teams-1/cyf-products-final-projects/roles)
 
 The product owner would either be a representative from the partner organisation or someone at CYF, depending on the project. It’s important that they are able to engage at least twice a week with the team, and have the authority to make decisions that let the team keep moving.
 
 ## Weekly plan
 
 We’re going to run the final projects in weekly “sprints”, planning out what we’re going to do as teams and as individuals. Each week will therefore look something like:
 
-- **Daily standup**: post a daily message in the team Slack channel to let the rest of the team know what you’re working on, what progress you’ve made (even, and perhaps _especially_, if it’s none so far) and share anything that’s blocking you. Set a time for this and stick to it. Afterwards, post a team summary in the main class channel.
+- **Daily standup**: post a daily message in the team Slack channel to let the rest of the team know what you’re working on, what progress you’ve made (even, and perhaps _especially_, if it’s none so far) and share anything that’s blocking you. Set a time for this and stick to it. Don't forget to also read your team members updates and try to help them when they are blocked. Afterwards, post a team summary in the main class channel. 
 
 - **Mid-week check-in**: you should have at least one Slack call with the whole team and a mentor during the week to sync on progress, escalate any blockers and make sure that you’re still heading in the right direction.
 - **Classes**: we’ll continue to meet on class days where we will be spending time on:

docs/finalproject/prep.md

@@ -4,9 +4,35 @@ title: Final Project Preparation
 sidebar_label: Preparation
 ---
 
+## Checklist to organise Final Projects
+Getting the Final Projects ready is not a task that can be done a week before the module. A lot of decisions have to be made beforehand, so this high-level list of the steps Volunteers and PROM (Programme Managers) should do in order to get everything ready for Final Projects. It also has the main links of important documents. 
+
+**When you are on the React Module**
+- [ ] Must review the trainee’s performance and make [readiness for Final Projects decision](https://docs.google.com/document/d/1jMxqI0L7IKFENCQ8Lw-D1lhnj3c3RZI_WK808wG4YJM/edit?usp=sharing)
+- [ ] If you haven't yet, make sure you identify trainees that will be filling in roles such as UI/UX Designer, Tester or Product Delivery
+- [ ] Ask internally and externally for possible ideas of charities that could be part of Final Projects. The form used should be the [Final Project Proposals form](https://forms.gle/Gn85Kdna6QB2Qfcp9). 
+- [ ] Start recruiting Tech Lead, Product Managers and UI/UX Designer for Final Projects. See the [role descriptions](https://docs.codeyourfuture.io/volunteers/teams-1/cyf-products-final-projects/roles). 
+
+**When you are on the NodeJS Module**
+- [ ] Review the project ideas with Tech Leads and Product Managers defining technical feasibility and scope size. You might have to have volunteers clarify some information with the charities
+- [ ] Identify which of the Ideas will be used as a final project. 
+	Send feedback to all charities if they have been chosen or not. 
+	For the chosen ones, clarify the [role](https://docs.codeyourfuture.io/volunteers/teams-1/cyf-products-final-projects/roles/product-owner) and who will be the Product Owner from their Charity. 
+- [ ] Onboard the volunteers with the standard process
+- [ ] Use [this template](https://docs.google.com/spreadsheets/d/16vSSJgzCZJKF-2pwuBTkKjJJJ9i1CGRqMbYB-HEO5mo/edit?usp=sharing) to identify the projects that will be used and who will be on which team
+- [ ] Let volunteers choose which project they would like to be on
+
+**When you are on SQL Module**
+- [ ] Trainees must have completed up to Level 300 of the [Full Stack Assessment](https://github.com/CodeYourFuture/Table-of-Contents) by week 3 of the module before Final Projects.
+- [ ] Must review the trainees' performance and identify the ones going to Final Projects
+- [ ] Identify trainees that are close in performance and allocate them to the same project. We encourage trainees to work with different people, so try to mix the teams up. Don’t forget to update the spreadsheet.
+- [ ] Have a meeting with all volunteers and trainees to go through the details of the final project (presentation to be created with expectation, escalation process, type of support, overview of the trainees per team, etc). Don't forget to record it and share the recording with all the participants, with their consent.
+- [ ] Introduce all teams and people in it and create all Slack groups
+- [ ] A day before the first Saturday of Final Projects, send the project briefing to the team
+
 ## Project Submissions
 
-Some trainees may have some ideas about projects that they would like to complete for their Final Project. Before the Final Project starts, ideas should be gathered and fully specified before the start of the first week.
+As mentioned above, before the Final Project starts ideas should be gathered and fully specified before the start of the first week. The form used to receive these ideas is [this](https://forms.gle/Gn85Kdna6QB2Qfcp9). 
 
 A good project should
 
@@ -22,18 +48,15 @@ All code should be done _in public on the trainees' Githubs_, unless there is a
 
 Before class starts volunteer and trainee teams should have been assigned.
 
-You can find a template for organising the teams [here](https://docs.google.com/spreadsheets/d/13WGRmeUZoCZfPV3joO4q69GLIaAiYFnrh9WmZ51FrE8/edit#gid=0)
+Please make a copy of this [template spreadsheet](https://docs.google.com/spreadsheets/d/16vSSJgzCZJKF-2pwuBTkKjJJJ9i1CGRqMbYB-HEO5mo/edit?usp=sharing) to organise the teams and track the progress of the projects.
 **Repos must be logged on this spreadsheet so everyone can see what is happening during the module.**
-All trainees should make sure that they are comfortable with their roles and what they will be required to do. More information about roles can be found [here](./roles)
+All trainees should make sure that they are comfortable with their roles and what they will be required to do. More [information about roles](https://docs.codeyourfuture.io/volunteers/teams-1/cyf-products-final-projects/roles).
 
 ## Starter Projects
 
-Here is a starter project that trainees can fork to get started:
-
-- Starter project for [Mongo/Express/React/Node](https://github.com/CodeYourFuture/cyf-final-project-starter-kit)
-- Starter project for [Postgres/Express/React/Node](https://github.com/CodeYourFuture/cyf-final-project-starter-kit/tree/postgres) (this is a branch of the above project)
+Here is a [starter project for Postgres/Express/React/Node](https://github.com/CodeYourFuture/cyf-final-project-starter-kit/).
 
-Documentation can be found [here](https://github.com/textbook/starter-kit/wiki) for both of the above projects
+Documentation can be found [here](https://github.com/textbook/starter-kit/wiki).
 
 If you need help for any of these projects, you can find help in this Slack channel: [`#cyf-full-stack-starter-kit`](https://codeyourfuture.slack.com/archives/C021ATWS9A5)
 

docs/finalproject/roles.md

@@ -10,40 +10,34 @@ These roles should in total create a [balanced team](https://www.youtube.com/wat
 
 ## Volunteer Roles
 
-### Product Manager // Scrum Master
-
-**Time Commitment**: One day a week plus 2-4 hours during the week
-
-Scrum Masters are expected to coordinate the team and make sure everyone knows what they are working on. They can provide support in
+### Product Manager / Scrum Master
+Full [role description of roles](https://docs.codeyourfuture.io/volunteers/teams-1/cyf-products-final-projects/roles/product-manager)
 
+Your main role is to coordinate the team and make sure everyone knows what they are working on. They can provide support in:
 - Scheduling meetings
-- Working with the team to create and update tasks on Trello
+- Working with the team to create and update tasks on Github Projects
 - Introducing and enforcing Agile practices (e.g. sprint planning, retros)
 
-### Technical Assistant
-
-**Time Commitment**: One day a week plus 2-4 hours during the week
-
-Teaching assistant provide technical support to the trainees as they are developing their projects. They can provide support in
+### Technical Lead
+Full [role description for Tech Lead](https://docs.codeyourfuture.io/volunteers/teams-1/cyf-products-final-projects/roles/tech-lead) (TL)
 
+The TL provides technical support to the trainees as they are developing their projects. They can provide support in:
 - Architecture of the application
 - Helping to solve specific implementation problems
 - Helping to solve specific bugs or errors
 - Providing overview of the entire project
 
-### UI/UX Designer
-
+### User Interface/ User Experience (UI/UX) Designer
 _UI/UX Designers are spread across multiple teams_
+Full [role description for UI/UX designer](https://docs.codeyourfuture.io/volunteers/teams-1/cyf-products-final-projects/roles/ui-ux-designer).
 
-UI/UX'ers will provide their expertise in supporting the UI/UX trainees in each team. The can provide support in
-
+UI/UXers will provide their expertise in supporting the UI/UX trainees in each team. For example:
 - Developing simple UI for the applications
 - Providing support on answering UX issues
 - Giving advice on how to better design an application to our teams
 
 
 ## Trainee Roles
-
 Trainees join Final Projects in their graduation role and stay with one team. These are updated in [Graduation Roles](https://docs.google.com/document/d/1HHjftKmMqAT8zaxQubj5ixBrJqVcwLLNrAFLXGcn4N4/edit?usp=sharing) but usually include:
 
 - Full Stack Developer

docs/finalproject/week-1/lesson.md

@@ -72,7 +72,7 @@ _A note for PMs_ - don't forget to create your own copy of the presentation and
 
 _Led by trainees_
 
-Project Management boards are a tool that you can use to help you organise how you work.
+Project Management boards are a tool that you can use to help you organise how you work. There are many tools in the market, but we use Github Projects.
 
 Create a copy of this Project Board to manage your work - [Project Board](https://github.com/orgs/CodeYourFuture/projects/13)
 
@@ -88,7 +88,9 @@ _Facilitated by Tech Assistants_
 
 Every day you should post a message in the team's Slack channel to let the rest of the team know what you’re working on, what progress you’ve made (even, and perhaps _especially_, if it’s none so far) and share anything that’s blocking you.
 
-Set a time for this and stick to it.
+Don't forget to also read your teammates updates. This way you can understand what is happening in the team and support each other.
+
+Set a time for this and stick to it. Put it in your calendar.
 
 Afterwards, post a team summary in the main class channel.
 

docs/finalproject/week-3/lesson.md

@@ -4,9 +4,9 @@ title: Final Project - Week 3
 sidebar_label: Lesson
 ---
 
-See [Week 2](../week-2/lesson) for instructions for this week
+See [Week 2](../week-2/lesson) for instructions for this week. You are working as a team to deliver a product, so will continue using that format through the Final Projects
 
-### Check In
+### Check In: how are the contributions of all team members so far?
 
 It's important to evaluate our contributions to the group. Here's what we expect:
 

docs/finalproject/week-4/lesson.md

@@ -4,4 +4,6 @@ title: Final Project - Week 4
 sidebar_label: Lesson
 ---
 
-See [Week 2](../week-2/lesson) for instructions for this week
+See [Week 2](../week-2/lesson) for instructions for this week. 
+
+Make sure to check in again on the contributions per team members, as detailed on [Week 3](../week-3/lesson)

docs/html-css/week-1/homework.md

@@ -14,12 +14,35 @@ Is your Google Classroom, not here! Teachers and trainees, make sure you check y
 
 Fork then clone the [HTML/CSS week 1 coursework](https://github.com/CodeYourFuture/HTML-CSS-Coursework-Week1), and follow the instructions in the `README.md` file.
 
-### 2) Complete Flexbox Froggy game (3 hours)
+### 2) Begin the module project (6 hours)
 
-Complete the [Flexbox Froggy game](https://flexboxfroggy.com) to get practise on flexbox.
+The module project spans the whole module. Your task is to re-create a design from scratch, using your HTML and CSS skills, and improve it over this module. You have four weeks to develop this project, so plan your time wisely.
+
+You'll find all instructions in this repository:
+[https://github.com/CodeYourFuture/HTML-CSS-Module-Project](https://github.com/CodeYourFuture/HTML-CSS-Module-Project)
+
+Before you start, make sure you **fork** the repository to your Github account. Open a pull request to submit your coursework.
+
+### 3) CSS Grid (3 hours)
+
+1. Complete this [Scrimba course on CSS Grid](https://scrimba.com/learn/cssgrid)
+2. Don't just watch the videos! You won't really learn anything that way. Interact with the code and type it out.
+3. Take a screenshot of your progress on your dashboard https://scrimba.com/dashboard?tab=enrolled and submit this
+
+### 4) Prepare for the next class (1 hour)
+
+You need to prepare for every class.
+
+The syllabus is a sample/guide lesson, so you might do something different in class, but the broad learning objectives will be similar. Read the learning objectives. What other reading can you do to prepare for class? Is there any code to checkout from github?
+
+CYF trainees must always come to class **with questions**.
 
 ## Stretch coursework
 
-### 3) CSS Diner game (3 hours)
+### 1) Complete Flexbox Froggy game
+
+Complete the [Flexbox Froggy game](https://flexboxfroggy.com) to practise using flexbox.
+
+### 2) CSS Diner game
 
-Complete the [CSS Diner game](https://flukeout.github.io) to get practise on advanced CSS selectors.
+Complete the [CSS Diner game](https://flukeout.github.io) to practise using advanced CSS selectors.