Merge branch 'main' into content/1168-energisers

README.md

@@ -78,7 +78,7 @@ Then add the common theme and content modules as hugo modules to hugo.toml:
 
 Look at the [org-cyf](/org-cyf/) and [org-cyf-tracks](/org-cyf-tracks/) examples for more details and options.
 
-To customise the css, make a dir `assets/custom-theme` and throw any scss in there. It will be compiled and added last.
+To customise the CSS, make a dir `assets/custom-theme` and throw any SCSS in there. It will be compiled and added last.
 
 To add site logo/s, make a dir and add svgs to `assets/custom-images/site-logo/`. They will be added to the site header.
 

common-content/en/energisers/confident-presenting/index.md

@@ -0,0 +1,29 @@
++++
+title="Confident Presenting!"
+time=15
+[objectives]
+    1="Trainee can strike a power pose"
+    2="Trainee has experience with confidently introducing themselves"
+[build]
+  render = 'never'
+  list = 'local'
+  publishResources = false
++++
+
+# The Setup
+
+Get everyone standing for this exercise!
+
+1. Start by everyone demonstrating unconfident poses
+2. Get everyone moving with a quick stretch or power pose to break the ice and release tension. 
+ - Superman pose – feet shoulder-width apart, hands on hips, chest out.
+ - The victor - hands up in the air in a V and feet apart
+ - Any others?
+3. In a power pose of your choosing go around the room and ask everyone to say their name in the most exaggerated, enthusiastic way possible, like they’re introducing themselves to a stadium of people. 
+
+> [!WARNING]  
+> This is not proven science. This is just a fun game to get everyone up and moving around!
+
+# Resources on Confident Presenting
+- [Make Body Language Your Superpower](https://www.youtube.com/watch?v=cFLjudWTuGQ&ab_channel=StanfordGraduateSchoolofBusiness)
+- [Alter Ego: How having an alter ego empowers you](https://www.bbc.com/worklife/article/20200817-the-batman-effect-how-having-an-alter-ego-empowers-you)

common-content/en/module/js1/install-node/index.md

@@ -25,7 +25,7 @@ Check if you already have NodeJS installed by running `node -v` in a terminal. T
 1. Install nvm by running the following commands in your terminal:
 
 ```terminal
-curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.3/install.sh | bash
+curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.40.1/install.sh | bash
 ```
 
 2. After the installation is complete, you'll need to source the nvm script by running:
@@ -46,51 +46,65 @@ nvm install --lts
 node -v
 ```
 
-You should see a version number like `v20.16.0`.
+You should see a version number like `v22.11.0`.
 
 5. Check that you have successfully installed npm by running:
 
 ```terminal
 npm -v
 ```
 
-You should see a version number like `10.5.0`.
+You should see a version number like `10.9.0`.
 
 ##  On Mac
 
-1. Install nvm by running the following command in your terminal:
+1. Install the the Xcode Command Line Developer Tools by running the following command in your terminal:
 
 ```terminal
-curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.3/install.sh | bash
+xcode-select --install
 ```
 
-2. After the installation is complete, you'll need to source the nvm script by running:
+These may already be installed, in which case you will see "xcode-select: note: Command line tools are already installed." and can continue to the next step.
+
+2. Create a (Non-Login Interactive) Shell Configuration File:
+
+```terminal
+touch ~/.zshrc
+```
+
+3. Install nvm:
+
+```terminal
+curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.40.1/install.sh | bash
+```
+
+4. After the installation is complete, you'll need to source the nvm script by running:
 
 ```terminal
 source ~/.zshrc
 ```
 
-3. Install the latest LTS version of Node.js by running:
+5. Install the latest LTS version of Node.js by running:
 
 ```terminal
 nvm install --lts
 ```
 
-4. Check that you have successfully installed Node.js by running:
+6. Check that you have successfully installed Node.js by running:
 
 ```terminal
 node -v
 ```
 
-You should see a version number like `v20.16.0`.
+You should see a version number like `v22.11.0`.
 
-5. Check that you have successfully installed npm by running:
+7. Check that you have successfully installed npm by running:
 
 ```terminal
 npm -v
 ```
 
-You should see a version number like `10.5.0`.
+You should see a version number like `10.9.0`.
 
 {{<note type="tip" title="Protip">}}
 Using nvm allows you to easily install and manage multiple versions of Node.js on your system. This will help you access projects that use older versions of Node.js.

common-content/en/module/the-launch/presentation/index.md

@@ -10,4 +10,7 @@ hide_from_overview=true
   publishResources = false
 +++
 
-<iframe src="https://docs.google.com/presentation/d/e/2PACX-1vQLfMfy30P8RVJcxKlbZX4ElfgAFBDJz_AeOCJFLlshZjifnJqCktuBX4MmZl8qn4PfmoloNvUxI3tw/embed?start=false&loop=false&delayms=3000" frameborder="0" width="100%" height="540" allowfullscreen="true" mozallowfullscreen="true" webkitallowfullscreen="true"></iframe>
+On the demo day the Launch Module teams will present their products. Each team has 10 minutes to present. You must ensure that you can present within the allocated time.
+_Suggestion of split: 7 minutes for the presentation itself and 3 minutes for questions._
+
+Use our [presenting guide](/guides/presenting/) to understand what you should consider when building your demo.

common-theme/layouts/shortcodes/objectives.html

@@ -0,0 +1,11 @@
+{{ $items := slice }}
+{{ $objectives := split .Inner "\n" }}
+{{ range $objectives }}
+  {{ $objective := replace . "- [ ] " "" }}
+  {{ if ne (trim $objective " ") "" }}
+    {{ $items = $items | append $objective }}
+  {{ end }}
+{{ end }}
+{{ with $items }}
+  {{ partial "objectives/block" . }}
+{{ end }}

common-theme/layouts/shortcodes/tasks.html

@@ -0,0 +1,12 @@
+{{ $items := slice }}
+{{ $objectives := split .Inner "\n" }}
+{{ range $objectives }}
+  {{ $objective := replace . "- [ ] " "" }}
+  {{ if ne (trim $objective " ") "" }}
+    {{ $items = $items | append $objective }}
+  {{ end }}
+{{ end }}
+{{ with $items }}
+  {{ partial "objectives/block" . }}
+{{ end }}
+<!-- Compare this snippet from common-theme/layouts/shortcodes/objectives.html: -->

org-cyf-guides/content/contributing/minutes/index.md

@@ -17,6 +17,67 @@ Attendees:
 
 ---
 
+## 2024-11-19
+
+Attendees: Ali Smith, Daniel Wagner-Hall, Sally McGrath
+
+### ❗Actions from last time
+
+- [x] Ali (Carry-over): Check in with the Dashboard team about Piscine reqs (write up a ticket for this)
+- [ ] All (Carry-over): Think about useful resources for SDC
+- [x] All: File tickets about requirements for the curriculum platform in https://github.com/orgs/CodeYourFuture/projects/105/views/17
+
+### 📝 Agenda points
+
+#### Helping ITP team reboot the first module for ITP iteration 2 which starts in about 6 weeks
+
+We should start thinking about reworking the first module as slightly more fundamentals-style "try this out and enroll as a trainee or drop out".
+
+We may want to do with on behalf of the ITP syllabus team and hand it over, as they are bandwidth-constrained.
+
+We would probably want this to happen before we rely on people having access to their own computers.
+
+Would probably want to keep git, which you can do on GitHub, but without Codespaces that doesn't let you _run_ code. These are cheap enough that we can probably pay for it. Probably ditching the terminal completely though.
+
+Sally has acquired a poor quality trainee laptop and will experiment with it.
+
+##### Do we want to time-limit the module?
+
+Pros:
+* Encourages people to focus and pushes them to actually enroll as trainees
+* Sets the expectation of: You have to show up, put the work in, and make progress
+
+Cons:
+* Extra pressure
+* Makes a paperwork spike of enrollment applications
+* Mismatched expectations around introducing artificial time pressure for module 1 vs trying to relieve time pressure for ITP
+
+We probably want to set a target guideline of 4 weeks, but not enforce this. Maybe we "enforce" this by telling cohort leaders that week 5 must be working on module 2 not module 1.
+
+##### Actions
+
+* Collaboratively put together learning objectives.
+* Rebranding the module.
+* Go through moving/removing things we think need to be removed.
+* Frame sprint 1 with specific energisers/introductions.
+
+#### Renaming SDC
+
+Daniel would quite like to rename SDC to Software Engineering for two reasons:
+1. To not need to disambiguate between "old SDC" and "new SDC"
+2. "Software engineering" contrasts nicely with "Learning programming"
+
+#### Piscine dashboard requirements
+
+Worked out in comments on https://docs.google.com/document/d/1KOl4eWF0XWS34esrkWvCE5d4ESgMrjeFWQFao404UPY/edit
+
+### ❗Actions
+
+- [ ] All: Collaboratively put together LOs and name for ITP Introduction Module.
+- [ ] Daniel: Sync with Karen on Piscine dashboard requirements
+
+---
+
 ## 2024-11-05
 
 Attendees: Daniel Wagner-Hall, Mitch Lloyd, Sally McGrath

org-cyf-guides/content/presenting/_index.md

@@ -0,0 +1,50 @@
++++
+title = 'Presenting'
+description = "Sharing information with people"
+emoji = '📢'
++++
+
+## Types of presentation
+
+When presenting to people, it's important to know what style of presentation you're giving. Some common presentation styles are:
+* **[Demos](demoing)**: Presenting something you've done (maybe a working product, maybe a new feature, maybe just a mock-up).
+* **Lectures**: Teaching information that you know, that the people you're presenting to don't already know.
+
+This page contains general advice for all presentations. There are also links to specific information for some of these kinds of presentation.
+
+## Time
+
+Know how much time you have for your presentation. Make sure you stick to it. Practice your presentation to ensure you can do it within that time.
+
+Make sure you know if any time for questions is included in your time, or if there is extra time afterwards for questions.
+
+If you're using slides, you should aim for about one slide per minute of your presentation. If you have more slides than this it will be hard for the audience to take in your presentation.
+
+## Audience
+
+Make sure you know about your audience. Think about:
+
+**What do they _already_ know?**
+* Are there things you need to explain so that they can follow what you actually want to talk about?
+* Can you skip some things because everyone in the audience already knows them?
+* Do you need to _check_ in your presentation to make sure they actually know what you think?
+
+**What do they _want_ to know?** What are they excited about? e.g. Talking about a cool way of achieving a code problem probably isn't interesting to someone who doesn't know how to code.
+
+**What do you want _them_ to know?** Do you want them to take some action based on your presentation? Do you want them to use something you're explaining?
+
+**What do your audience care about?** An audience of non-developers may be more interested in your UI. An audience of developers may be more interested in your code. Target your presentation to your audience.
+
+## Focus
+
+Pick a focused message - one or two things you want people to take away.
+
+If you just say everything that you know/did, it's hard to pick out what was important.
+
+Explain **what** as well as **why**. If you're talking about something you did, explain why you did it the way you did it.
+
+## Ordering
+
+Try to introduce things in the order they're needed. Avoid needing to say "I'll explain that later" or "You'll understand this later".
+
+## Guidance for specific presentation types

org-cyf-guides/content/presenting/demoing/index.md

@@ -0,0 +1,62 @@
++++
+title = 'Demos'
+description = "Sharing something you've done with people"
+emoji = '📢'
++++
+
+Make sure you've read all of [the general presentation guidance](../presenting). This page adds to that information.
+
+## Purpose
+
+Think about the purpose of your demo.
+
+Are you **pitching** - trying to get someone to use/buy/support your product?\
+If so, you probably want to focus on features, value, and why your product is unique.
+
+Are you **seeking feedback** - asking people for suggestions or ideas?\
+If so, you probably want to tell the audience what feedback you want, and make sure they know how to give it.
+
+Are you **teaching** - trying to help someone understand something they don't know?\
+If so you probably want to be checking understanding as you go.
+
+Are you **celebrating** - showing off something you're proud of?
+
+Make sure you think about this when you prepare your demo. Make sure the audience know what you're expecting from them too.
+
+## Pick what you show
+
+If you need to log into your product, the audience probably don't care about watching you log in. Set up a tab which is already logged in so you can jump straight to the interesting stuff.
+
+If your project requires you to add some data, but what you want to demo is how the data is presented, add the data _before_ your demo so you can jump straight to the interesting stuff.
+
+You don't need to show the audience everything in your app. Focus on what matters.
+
+## Pick what you tell
+
+You should have already picked a focused message. Only tell your audience what they need to understand that message.
+
+If you're demoing a product experience, you probably don't need to talk about creating a git repo. It's something you needed to do, but it doesn't contribute to your focused message.
+
+## Preparing for a demo
+
+Know the scenarios you are going to demo. Practice them!
+
+Make sure your product/code is already up and running. No one wants to watch you start your project. No one wants to watch you try to open a project and find it's not working.
+
+Have tabs already open and prepared for each scenario you want to demo.
+
+If you need to be logged in as multiple users (e.g. as a buyer and a seller) log in to one in your regular browser and use incognito mode to log in as the other one.
+
+Consider pre-recording anything that could go wrong - that way you can switch to a video if you need.
+
+Anticipate questions your audience are likely to ask you. Think about answers to them!
+
+## Demoing as a group
+
+Make sure you know how you're splitting up the demo between the people.
+
+Make sure everyone is talking for about the same amount of time. Don't let one person take over.
+
+If you're handling questions, make sure everyone answers similar numbers of questions. One person shouldn't answer most of them.
+
+**Don't ever swap laptops**. Have everyone present from the same laptop.

org-cyf-itd/content/blocks/step-1/instructions/index.md

@@ -54,7 +54,7 @@ Software for Lawyers Ltd makes case management software. Their software helps la
 2. Ask the AI to help you write a cover letter. Give it the description of Jane and the job description provided. It may take some experimentation to get the right prompt. That’s OK: getting AI to do what you want is all about trial and error.
 3. Think about [the goals of a cover letter](https://hbr.org/2014/02/how-to-write-a-cover-letter). Read and reflect on the cover letter. Has the AI provided good links between Jane's experience and the job's requirements (e.g. does it note that she has experience in the legal sector)? How has the AI demonstrated that Jane has the right skills for the job? Has the AI added anything that wasn’t in the description of Jane? Could you do better?
 4. Think about your own future job hunt. What have you learned that will help you apply for jobs in the future? Will you use ChatGPT to help you generate a cover letter? If so, how will you make sure it's a good cover letter? If not, why not?
-5. Create a Google doc with the text of the cover letter you generated
+5. Create a Google doc with the text of the cover letter you generated. If this platform is new to you, there is this [guide on what Google docs is and how to use it](https://support.google.com/docs/answer/7068618?hl=en-GB&co=GENIE.Platform%3DDesktop) available.
 6. Please put your name in the title of the Google doc and **make it public**. You can add just your given name or your family name if you prefer.
 7. Add the link to the Google doc to this platform
 8. Add a comment with at least three comments (positive or negative) on the AI’s work

org-cyf-itd/content/blocks/step-3/instructions/index.md

@@ -12,6 +12,7 @@ time= 300
 This course teaches you HTML and CSS by helping you make five great projects. You'll also get to do over 75 coding tasks. You don't need to know anything about coding to start - it's good for complete beginners.
 
 1. Create an [account on Scrimba](https://v2.scrimba.com/home)
+1. Learn [what to do and what to avoid when taking the Scrimba course](https://docs.google.com/presentation/d/1Z10grrFWQcKeEb2iD84ljhq9vzLMPWL5ny6oaotpb8E/edit?usp=sharing)
 1. Go to the course: [Learn HTML and CSS](https://v2.scrimba.com/learn-html-and-css-c0p) on Scrimba
 1. Follow along and build the first five projects
 1. Make a public Google doc to collect the links to all your deployed projects on Netlify

org-cyf-itp/content/data-groups/sprints/1/day-plan/index.md

@@ -15,6 +15,18 @@ time=15
 name="Workshop"
 src="blocks/workshop"
 time="140"
+[[blocks.nested.blocks]]
+    name="Giving Feedback [PD] (60 Mins)"
+    src="https://github.com/CodeYourFuture/CYF-Workshops/tree/main/feedback"
+    time=0
+  [[blocks.nested.blocks]]
+    name="Arrays [Tech] (60 Mins)"
+    src="https://github.com/CodeYourFuture/CYF-Workshops/tree/main/arrays"
+    time=0
+  [[blocks.nested.blocks]]
+    name="Testing [Tech] (60 Mins)"
+    src="https://github.com/CodeYourFuture/CYF-Workshops/tree/main/testing"
+    time=0
 [[blocks]]
 name="lunch"
 src="blocks/lunch"

org-cyf-itp/content/data-groups/sprints/2/day-plan/index.md

@@ -15,6 +15,14 @@ time=15
 name="Workshop"
 src="blocks/workshop"
 time="140"
+  [[blocks.nested.blocks]]
+    name="Objects [Tech] (60 Mins)"
+    src="https://github.com/CodeYourFuture/CYF-Workshops/tree/main/objects"
+    time=0
+  [[blocks.nested.blocks]]
+    name="Debugging 2 [Tech] (60 Mins)"
+    src="https://github.com/CodeYourFuture/CYF-Workshops/tree/main/debugging-2"
+    time=0
 [[blocks]]
 name="lunch"
 src="blocks/lunch"