feature; stage 2: mounting this repo as modules

common-content/en/blocks/requirements/index.md

@@ -37,3 +37,46 @@ To make great software, we need to think about people, not just code.
 We can discover requirements with something called 'User Stories'. The simplest user story looks like this:
 
 > As a [type of user], I can [achieve some goal].
+
+#### Imagine a coursework tracker
+
+As trainees, you have coursework to do. Imagine a website which tracks how coursework is going for you all. Thinking about that website, some user stories could be:
+
+- As a trainee, I can ask for help with a topic or task.
+- As a mentor, I can see who needs extra support.
+- As a trainee, I can see what coursework I need to complete and when.
+- As a mentor, I can see what coursework has not been completed.
+
+These each take the form "As [who], I can [what]". They don't say why yet.
+
+{{<note type="activity" title="Exercise 10 Minutes" >}}
+In groups of about 5.
+
+Talk about why the "who" is useful. What would we be missing if we didn't think about the "Who"?
+
+Now think about the "why" for each of the listed user stories. Why are they important?
+
+{{</note>}}
+
+> As a [who], I can [what] so that **[why]**
+
+{{<note type="activity" title="Exercise 10 Minutes" >}}
+
+Write some user stories for our coursework tracker on a Jamboard.
+
+Think about the "who", "what", and "why" for each.
+
+You can think of new "who"s (e.g. the people who write the coursework questions), and as many "what"s as you want - but make sure you remember the "why".
+{{</note>}}
+
+### Reflecting
+
+{{<note type="glossary" title="Key Term" >}}
+A user story is a short sentence stating some goal a user can expect to achieve when using the product we are implementing.
+{{</note>}}
+
+{{<note type="activity" title="10 Minutes" >}}
+Why is thinking about user stories useful?
+
+What's useful about thinking about the "who" and the "why"? What could go wrong if you don't think about them?
+{{</note>}}

org-cyf/content/js1/sprints/1/prep/index.md

@@ -42,7 +42,7 @@ name="Wrapping up"
 src="blocks/wrapping-up"
 [[blocks]]
 name= "Critical Thinking"
-src= "TEMPURL-/blocks/prep-critical-thinking/readme/"
+src= "https://cyf-pd.netlify.app/blocks/prep-critical-thinking/readme/"
 +++
 
 ## Interacting with computers.

org-cyf/content/js1/sprints/4/day-plan/index.md

@@ -11,7 +11,7 @@ name="Energiser"
 src="blocks/energiser"
 [[blocks]]
 name= "Asking good technical questions"
-src= "TEMPURL-/blocks/asking-good-technical-questions/readme/"
+src= "https://cyf-pd.netlify.app/blocks/asking-good-technical-questions/readme/"
 [[blocks]]
 name="Progress check-in"
 src="https://github.com/CodeYourFuture/Module-JS1/issues/124"

org-cyf/content/js1/sprints/4/prep/index.md

@@ -35,5 +35,5 @@ src="module/js1/generalise"
 name="generalise"
 [[blocks]]
 name= "Asking good questions"
-src= "TEMPURL-/blocks/prep-asking-good-questions/readme/"
+src= "https://cyf-pd.netlify.app/blocks/prep-asking-good-questions/readme/"
 +++

org-cyf/content/js3/sprints/1/prep/index.md

@@ -35,5 +35,5 @@ name="using-map"
 src="module/js3/using-map"
 [[blocks]]
 name= "Prep Teamwork Project"
-src= "TEMPURL-/blocks/prep-teamwork-project/readme/"
+src= "https://cyf-pd.netlify.app/blocks/prep-teamwork-project/readme/"
 +++