Merge remote-tracking branch 'upstream/main'

Author: hash-noob

.github/workflows/nightly-deploy.yml

@@ -10,10 +10,37 @@ jobs:
     steps:
     - uses: actions/checkout@master
     - name: Publish curriculum
-      run: curl --fail -X POST ${{ secrets.CURRICULUM_NETLIFY_DEPLOY_HOOK_URL }}
+      env:
+        DEPLOY_HOOK_URL: ${{ secrets.CURRICULUM_NETLIFY_DEPLOY_HOOK_URL }}
+      if: ${{ env.DEPLOY_HOOK_URL != '' }}
+      run: curl --fail -X POST ${{ env.DEPLOY_HOOK_URL }}
+    - name: Publish ITD
+      env:
+        DEPLOY_HOOK_URL: ${{ secrets.ITD_NETLIFY_DEPLOY_HOOK_URL }}
+      if: ${{ env.DEPLOY_HOOK_URL != '' }}
+      run: curl --fail -X POST ${{ env.DEPLOY_HOOK_URL }}
     - name: Publish ITP
-      run: curl --fail -X POST ${{ secrets.ITP_NETLIFY_DEPLOY_HOOK_URL }}
+      env:
+        DEPLOY_HOOK_URL: ${{ secrets.ITP_NETLIFY_DEPLOY_HOOK_URL }}
+      if: ${{ env.DEPLOY_HOOK_URL != '' }}
+      run: curl --fail -X POST ${{ env.DEPLOY_HOOK_URL }}
     - name: Publish SDC
-      run: curl --fail -X POST ${{ secrets.SDC_NETLIFY_DEPLOY_HOOK_URL }}
+      env:
+        DEPLOY_HOOK_URL: ${{ secrets.SDC_NETLIFY_DEPLOY_HOOK_URL }}
+      if: ${{ env.DEPLOY_HOOK_URL != '' }}
+      run: curl --fail -X POST ${{ env.DEPLOY_HOOK_URL }}
     - name: Publish Piscine
-      run: curl --fail -X POST ${{ secrets.PISCINE_NETLIFY_DEPLOY_HOOK_URL }}
+      env:
+        DEPLOY_HOOK_URL: ${{ secrets.PISCINE_NETLIFY_DEPLOY_HOOK_URL }}
+      if: ${{ env.DEPLOY_HOOK_URL != '' }}
+      run: curl --fail -X POST ${{ env.DEPLOY_HOOK_URL }}
+    - name: Publish Tracks
+      env:
+        DEPLOY_HOOK_URL: ${{ secrets.TRACKS_NETLIFY_DEPLOY_HOOK_URL }}
+      if: ${{ env.DEPLOY_HOOK_URL != '' }}
+      run: curl --fail -X POST ${{ env.DEPLOY_HOOK_URL }}
+    - name: Publish Launch
+      env:
+        DEPLOY_HOOK_URL: ${{ secrets.LAUNCH_NETLIFY_DEPLOY_HOOK_URL }}
+      if: ${{ env.DEPLOY_HOOK_URL != '' }}
+      run: curl --fail -X POST ${{ env.DEPLOY_HOOK_URL }}

common-content/en/module/business-analysis/new-use-case/index.md

@@ -15,10 +15,15 @@ objectives = [
 
 As a group, work together to create and submit these key documents for a new business scenario. Each person should understand all parts of the submission:
 
-1. A Problem Statement (what the problem is) & Stakeholder Map (who is involved).
-2. 2-3 User Personas (descriptions of typical users).
-3. An "As-Is" Process or User Journey Diagram (how things currently work).
-4. 8-10 Requirements (what the solution needs to do, functional, non-functional).
-5. 5 User Stories with acceptance criteria.
-6. A high-level Solution Design (how you'd solve the problem).
-7. What's "In-Scope" (what you will do) and "Out-of-Scope" (what you won't do for this project)?
+1. Present the problem 
+   - Include a Problem Statement, Market overview (example of a similar product), goals 
+2. Present your approach 
+   - Include Stakeholder Map, 2-3 User Personas (descriptions of typical users) and User Journeys 
+3. Understand the product
+    - Scope Description and/or Context Diagram
+    - Business Process and/or Use Cases
+    - Prioritised Backlog (Epics/Features/Stories)
+    - MVP and Roadmap on Epic or Feature level
+4. Mock-up / High-level Solution Design
+5. Data model
+6. Rollout proposal

common-content/en/module/tools/process-spelunking/index.md

@@ -275,7 +275,7 @@ Use what you learned in the previous exercise, to find the *PID* of this program
 Now run `lsof -p 1234` (replace 1234 with the *PID* of the program).
 The `-p` flag tells `lsof` that we're only interested in the files opened by that process; without that option `lsof` will show everything that it can show.
 
-Can you find the FD of the `exercise_2.py` file?
+Can you find the FD of the `exercise_2_file.txt` file?
 
 ===[[Answer]]===
 If I run `lsof` on the program, I see this.
@@ -306,6 +306,8 @@ python3 65262 ariane    3r   REG  253,0        0  262147 /home/ariane/programmin
 The *FD* column says `3r`.
 This means the file is on *FD* 3.
 (The `r` suffix, means it is opened for reading.)
+
+Note that the file `exercise_2.py` does not appear in the list because, by the time lsof is executed, Python has already read its contents into memory and no longer holds an open file descriptor.
 {{</tabs>}}
 
 ### Standard Input, Output, and Error

common-theme/layouts/partials/block/readme.html

@@ -8,9 +8,11 @@
   {{ errorf "Couldn't find readme at %s" $blockData.api }}
 {{ end }}
 
+{{ $pageTitle := .Page.Title }}
+
 {{ with $response }}
   {{ with .Err }}
-    {{ errorf "Failed %s on %s. Error: %s" $blockData.api .Page.Title .Err }}
+    {{ errorf "Failed %s on %s. Error: %s" $blockData.api $pageTitle . }}
   {{ end }}
 
   {{ $response := .Content | unmarshal }}

common-theme/layouts/partials/card.html

@@ -1,5 +1,9 @@
-{{ $BaseURL := .Page.Parent.Permalink }}
-<a class="c-card" href="{{ relURL .Page.RelPermalink }}">
+{{ $url := relURL .Page.RelPermalink }}
+{{ if .Page.Params.external_url }}
+{{ $url = .Page.Params.external_url }}
+{{ end }}
+
+<a class="c-card" href="{{ $url }}">
   <h3 class="c-card__title">{{ .Name }}</h3>
   {{ with .Page.Description }}
     <p class="c-card__description">{{ . }}</p>

org-cyf-guides/content/employability/cvs/_index.md

@@ -4,3 +4,9 @@ title: CVs
 description: Learn how to tailor your CV to the right employer
 weight: 2
 ---
+
+The purpose of a CV is to show an employer that you would be a good person to work with.
+
+Your CV should tell a story about who you are and why you are a good person to work with.
+
+A recruiter will typically skim through your CV for 5-10 seconds. You must stand out with your CV. Most people will not read all of it.

org-cyf-guides/content/employability/cvs/applicant-tracking-system/index.md

@@ -2,7 +2,7 @@
 title: Applicant Tracking systems
 description: Make sure your CV stands out from the crowd
 emoji: 🖲️
-weight: 4
+weight: 3
 ---
 
 Many employers (especially larger companies) use **A**pplicant **T**racking **S**ystems (ATSs) to manage the huge amount of candidates that apply for roles online. An ATS is a system that scans resumes and matches them against criteria (mostly keywords) defined by the employer.  

org-cyf-guides/content/employability/cvs/common-mistakes/index.md

@@ -0,0 +1,44 @@
+---
+title: Common CV Mistakes
+description: Mistakes people often make in CVs
+emoji: ⚠️
+weight: 2
+---
+
+Lots of people make similar mistakes when making their CV. Look through your CV and see if you've done any of the things listed below.
+
+## Saying what you did and not what impact it had
+
+Compare the following pairs of statements on a CV. In each pair, the first just describes what was done, and doesn't say why it was useful. The second shows _value_ and is much more compelling.
+
+1. "Rewrote core logic in TypeScript"
+2. "Rewrote core logic in TypeScript, reducing bugs shipped to production by 30%"
+
+[//]: # (Break up list)
+
+1. "Automated manual tasks"
+2. "Automated manual tasks, saving 3 hours of paperwork per week"
+
+[//]: # (Break up list)
+
+1. "Built feature to better target potential customers"
+2. "Built features to better target potential customers, increasing sales by 10%"
+
+[//]: # (Break up list)
+
+1. "Mentored an intern"
+2. "Mentored an intern, helping them successfully deliver their project on time, leading to a job offer at the end of their internship"
+
+## Columns
+
+CVs should be a single column. Two-column layouts often waste space, are hard to read, and can get messed up by Application Tracking Systems.
+
+## Complicated designs
+
+It's ok to make your CV stand out - it can be beautiful and interesting. But never at the expensive of ease of reading and understanding. Make sure someone can quickly read your CV and understand everything in it.
+
+## Previous careers
+
+Often career-changers will skip previous jobs/careers from their CV. Other times, people will fill their CV with irrelevant experience. Both are mistakes.
+
+If you have an older unrelated career, focus on the transferrable skills from it. But think carefully about what these may be! If you were a journalist, you may have used skills in storytelling, explaining things, attention to detail, or focusing on the user. If you worked in a shop, perhaps you have great experience working in a team and supporting colleagues. Most jobs have transferrable skills - think about them and include them - but focus on what's relevant.

org-cyf-guides/content/employability/cvs/cv-layout/index.md

@@ -1,9 +1,10 @@
 ---
-title: Profile sections
+title: Sections of a CV
 description: Work through different sections in your CV
-emoji: 🖼️
-weight: 4
+emoji: 📄
+weight: 1
 ---
+
 ## Basic Information
 
 Your CV should clearly mention your name, email address and phone number. It is a good practice to include your LinkedIn and GitHub links as well. 
@@ -43,4 +44,4 @@ Everything you have delivered in a role can be explained as an achievement. Each
 
 Add the most recent experience first. The most recent or most important information appears above the older or less important information. If education is more important than experience for this job advert, then put the education section above experience. Focus on the experience that is relevant to the job you want.
 
-If have an older unrelated career, de-focus its importance by writing less about it. However, you can extract and use the important aspects that are transferable. For example, if your previous experience was working in a pub then only write one line about it with no achievements, but you can include transferable skills such as working as part of a team and supporting colleagues.
+If you have an older unrelated career, focus on the transferrable skills from it. But think carefully about what these may be! If you were a journalist, you probably have skills in storytelling, explaining things, and user-focus. If you worked in a shop, perhaps you have great experience working in a team and supporting colleagues. Most jobs have transferrable skills - think about them.