diff --git a/common-content/en/blocks/backlog/index.md b/common-content/en/blocks/backlog/index.md index 3d7dbd704..54ec9ad24 100644 --- a/common-content/en/blocks/backlog/index.md +++ b/common-content/en/blocks/backlog/index.md @@ -20,7 +20,7 @@ In software development, we break down complex projects into smaller, manageable A sprint backlog is like a to-do list. It lists what the team has decided to work on this sprint. It's chosen from a larger list, usually called the "product backlog," which holds the entire project to-do list. -The backlog is a set of work designed to build understanding beyond the concepts introduced in the course prep. For your course, we have prepared a backlog of mandatory work for each sprint. You will copy these tasks into your own backlog. You can also add any other tickets you want to work on to your backlog, and schedule all of the tasks according to your own goals and capacity. Use your planning board to do this. +In this course, the backlog is a set of work designed to build understanding beyond the concepts introduced in the course prep. For your course, we have prepared a backlog of mandatory work for each sprint. You will copy these tasks into your own backlog. You can also add any other tickets you want to work on to your backlog, and schedule all of the tasks according to your own goals and capacity. Use your planning board to do this. You will find the backlog in the **Backlog** view on every sprint. diff --git a/common-content/en/blocks/house-rules/index.md b/common-content/en/blocks/house-rules/index.md index 9ef515312..43d2be13f 100644 --- a/common-content/en/blocks/house-rules/index.md +++ b/common-content/en/blocks/house-rules/index.md @@ -28,7 +28,7 @@ We teach you how to look things up. Try to use Google to answer your own questio #### Use the computer yourself -Don't let volunteers or peers type for you. Ask for help, but do the work on your own. +Don't let volunteers or peers type for you. Ask for help, but do the work yourself. #### Help each other out diff --git a/common-content/en/blocks/wrap-party/index.md b/common-content/en/blocks/wrap-party/index.md new file mode 100644 index 000000000..a8b33716c --- /dev/null +++ b/common-content/en/blocks/wrap-party/index.md @@ -0,0 +1,18 @@ ++++ +title="Wrap Party" +time=180 +[build] + render = 'never' + list = 'local' + publishResources = false ++++ + +You made it! πŸŽ‰ + +Thank you so much for your hard work. You've learned a lot and built some amazing things. + +Whether you're continuing with another course at {{}} or moving on to employment, we're proud of you. 🌟 + +Now, join the wrap party and celebrate your achievements with your community. 🎈 + +Can you bring a snack or drink to share? πŸͺπŸ₯€ Or a board game? We love Dixit, Codenames, and Rush Hour in particular. diff --git a/common-content/en/blocks/wrap/index.md b/common-content/en/blocks/wrap/index.md new file mode 100644 index 000000000..40066a247 --- /dev/null +++ b/common-content/en/blocks/wrap/index.md @@ -0,0 +1,19 @@ ++++ +title="Wrap" +time=20 +[build] + render = 'never' + list = 'local' + publishResources = false ++++ + +You are done for the day. Take a moment to reflect on what you have learned and achieved. + +Stand in a circle and share: + +- πŸ“› your name +- πŸ’ͺ🏽 one thing you achieved today +- πŸ‘·πŸΎ the task you are going to work on next +- πŸ›Ÿ one thing you need help with + +Give yourselves a round of applause. Now you have earned your rest. Usually people go for a cup of tea or a pint after class. You are welcome to join and wind down together. diff --git a/common-content/en/energisers/in-person-and-online/index.md b/common-content/en/energisers/in-person-and-online/index.md new file mode 100644 index 000000000..7a4111d39 --- /dev/null +++ b/common-content/en/energisers/in-person-and-online/index.md @@ -0,0 +1,16 @@ ++++ +title="Energiser!" +emoji="πŸ”‹" +time=25 +[tasks] + 1="Energise the group with a fun game" + 2="Get everyone to participate" +[build] + render = 'never' + list = 'local' + publishResources = false ++++ + +Energisers are a big part of {{}}'s culture! Even as adults, we all feel a bit shy and uncertain when we join a new group. But when we let ourselves be silly together, we start to feel more at home. + +Here follows one energiser for in-person and one for online. diff --git a/common-content/en/module/fundamentals/next-steps/index.md b/common-content/en/module/fundamentals/next-steps/index.md index c0f21a218..065de0a97 100644 --- a/common-content/en/module/fundamentals/next-steps/index.md +++ b/common-content/en/module/fundamentals/next-steps/index.md @@ -1,7 +1,6 @@ +++ title = 'Next steps πŸ‘£' - -time="20" +time="30" facilitation = false emoji= '🧩' [objectives] @@ -21,21 +20,20 @@ In this section, you have a set of questions/tasks to orient you towards what is Pair up with a new person. In pairs, complete the following tasks: -{{}} -If you're unsure about the answer to any of the questions below, start a thread in Slack to clarify the answer (unless there is already a thread discussing this matter) -{{}} +> [!WARNING] +> If you're unsure about the answer to any of the questions below, start a thread in Slack to clarify the answer (unless there is already a thread discussing this matter). -1. Using the [curriculum website](https://curriculum.codeyourfuture.io/), locate the setup page and the prep page for sprint 1 of the upcoming Induction module. -1. List the things you need to install ( if anything ) for the upcoming module. -1. Check you can find the backlog page for the Induction sprint. Double check you've copied all the issues from the backlog over to your Course Planner. +1. Starting from the home page of this website, locate the setup page and the prep page for sprint 1 of the next module. +1. List the things you need to install (if anything) for the upcoming module. +1. Check you can find the backlog page for the next sprint. Double check you've copied all the issues from the backlog over to your Course Planner. 1. Double check you've copied all the issues from the backlog over to your Course Planner. 1. Identify all the issues with πŸ”‘ icon that are marked as **Priority**. What does the **Priority icon** πŸ”‘ mean? -1. When ⏰ should you start the prep work for the upcoming Induction module? -1. Experiment with your project planner: can you filter by Size, Week 1, Tech ed, PD etc.? +1. When ⏰ should you start the prep work for the upcoming module? +1. Experiment with your project planner: can you filter by Size, Sprint, or other fields? ## For volunteers -1. Locate the classroom planning board for your region ( if one exists ) +1. Locate the planning board for your region (if one exists) 1. Locate the day-plan for the next module 1. Check the instructions and links on the **Priority πŸ”‘ issues** for the upcoming week ( both Tech Ed and PD ) 1. In the day-plan for the upcoming week identify the instructions for any workshops and visit the repository containing that readme. Check the instructions make sense. diff --git a/common-content/en/module/how-our-curriculum-works/active-learning/index.md b/common-content/en/module/how-our-curriculum-works/active-learning/index.md index 25819bebf..421fca01d 100644 --- a/common-content/en/module/how-our-curriculum-works/active-learning/index.md +++ b/common-content/en/module/how-our-curriculum-works/active-learning/index.md @@ -15,3 +15,7 @@ time=10 [Active learning](https://www.pnas.org/doi/10.1073/pnas.1319030111) is at the heart of our educational philosophy. It is about encouraging learners to build, explore and discuss new concepts instead of being passive recipients of knowledge. {{}}https://www.youtube.com/watch?v=-GydYPMc74g{{}} + +Each adult learner is unique, with their own background, experiences and existing knowledge. It doesn't make sense to assume what people do and do not know already, or to broadcast the same information to everyone. Instead, we use questions to find out what people already know, and help each individual bridge their gap to meeting the course goals. + +With active learning we ask specific, targeted questions to find out what we _do not yet know_, so we can work on that together. diff --git a/common-content/en/module/how-our-curriculum-works/community-goals/index.md b/common-content/en/module/how-our-curriculum-works/community-goals/index.md index 79b7f1e68..889203290 100644 --- a/common-content/en/module/how-our-curriculum-works/community-goals/index.md +++ b/common-content/en/module/how-our-curriculum-works/community-goals/index.md @@ -1,9 +1,8 @@ +++ title = 'Community goals' - time = 10 facilitation = false -emoji= '🧭' +emoji= '🎯' [objectives] 1='Define our community goals' [build] @@ -15,20 +14,28 @@ emoji= '🧭' To achieve our mission, we bring people together to build self-empowered communities of learners. To this end, we have 3 community goals for achieving our mission: -### We build communities that can **self-educate** +### We build communities that can **πŸ’‘ self-educate** **Self educate** means the ability to draw on surrounding resources to learn new skills and concepts. Tech changes all the time. We must develop independent learners who can teach themselves new skills and technologies. -### We build communities that can self-coordinate +### We build communities that can **πŸ• self-coordinate** + +**Self-coordinate** means the ability to make things happen with the people we have. Code Your Future isn't a large company with lots of staff. (1-2 technical people on staff, worldwide.) We're a community of motivated people who want to help each other. We can't expect someone else will do everything - we need to make sure we get it done ourselves. + +We use the collective intelligence we have built up over the years to coordinate our courses. This means many problems _have_ been solved by others and many logistical "rules of the road" have been discovered collectively. We all use tools like [classplanner](https://classplanner.codeyourfuture.io/), [dashboard](https://dashboard.codeyourfuture.io/), Slack, [GitHub](https://github.com/CodeYourFuture/Table-of-Contents), and most importantly the curriculum plan to coordinate courses and help new people join our community. But on the ground, there are always unique learning journeys that need supporting, arising from the unique mix of people in each class. + +We are always pragmatic and outcomes focused. If a learner thinks we need a extra time learning a topic, they should suggest it! If a volunteer thinks a workshop on a topic would be helpful, they should give one, or find someone else who can. + +### We build communities that can **πŸ“ self-evaluate** -**Self-coordinate** means the ability to make things happen with the people we have. Code Your Future isn't a large company with lots of staff. We're a community of motivated people who want to help each other. We can't expect someone else will do everything - we need to make sure we get it done ourselves. +**Self-evaluating** means _we_ work out what we're doing well at, and what we need to improve. If you don't understand a topic, you must identify this and get help. If you're expecting to get code review and no one has reviewed your code after a week or so, you must raise this problem and get help. -This doesn't mean we can't ask for help - we can - but we need to make sure we make the best use of the knowledge and abilities of everyone around us. +Every piece of prep, every sprint, every module has learning objectives. Check them before and after you do them. If you aren't confident you understand the learning objectives, talk about it. -If a trainee thinks we need a extra time learning a topic, they should suggest it! If a volunteer thinks a workshop on a topic would be helpful, they should give one, or find someone else who can. +### Communities of adults helping each other -### We build communities that can self-evaluate +Don't assume someone else will notice your problems and fix them. Everybody in our community has agreed to help each other; we must also agree to ask for the specific help we need, or we can't win this game! -**Self-evaluating** means _we_ work out what we're doing well at, and what we need to improve. If you don't understand a topic, you should identify this and get help. If you're expecting to get code review and no one has reviewed your code, you should raise this problem and get help. +**Mentors**, it's so important that you ask questions and model asking for help in productive and methodical ways too. It's really hard to ask for help; it's even harder to ask for help in ways that make it easy for others to help us. Everybody in our community is always learning and working on this very difficult skill. -Don't assume someone else will notice you problems and fix them. Every piece of prep, every sprint, every module has learning objectives. Check them before and after you do them. If you aren't confident you understand the learning objectives, talk about it. +Let's work on being curious, humble, brave and kind together. What a team we can be! πŸš€ diff --git a/common-content/en/module/how-our-curriculum-works/importance-of-prep/index.md b/common-content/en/module/how-our-curriculum-works/importance-of-prep/index.md index 61e5e083b..cd1dc814c 100644 --- a/common-content/en/module/how-our-curriculum-works/importance-of-prep/index.md +++ b/common-content/en/module/how-our-curriculum-works/importance-of-prep/index.md @@ -16,8 +16,7 @@ In a flipped learning model, learners are expected to **prepare** before they me Trainees should show up to class with questions and problems they didn't understand from the prep they already did. This means that we can use our in-person time to work together to fix real problems people have! {{}} +correct="1" >}} diff --git a/common-content/en/module/how-our-curriculum-works/tasks-and-ratios/index.md b/common-content/en/module/how-our-curriculum-works/tasks-and-ratios/index.md new file mode 100644 index 000000000..b1dbdb971 --- /dev/null +++ b/common-content/en/module/how-our-curriculum-works/tasks-and-ratios/index.md @@ -0,0 +1,41 @@ ++++ +title="Tasks and Ratios: Capacity Planning" +emoji="βš–οΈ" +time=10 +[objectives] +1="Evaluate your capacity" +2="List the core tasks of a class" +[build] + render = 'never' + list = 'local' + publishResources = false + ++++ + +This section is for volunteers. To evaluate your capacity to run a class, here are some rules of thumb: + +### How many learners make a class? + +Fewer than 8 is too small. A class of 18 is a good size. A class of 30 is too large. + +### How many volunteers do we need? + +1 volunteer can support 3-5 learners. + +### What does a class do? + +The basic tasks are: + +- [Morning workshop](https://workshops.codeyourfuture.io/) on class day +- Afternoon study group. You can also do the following tasks during study group, or async online during the week: + - [Code review](/prs-needing-review): at least one per learner per sprint + - [Step review](https://dashboard.codeyourfuture.io/): one per learner per module + - Pair programming: at least one per learner per module + - Demo: attend at least one demo by a learner per module + +There are additional beneficial activities you can support learners with: + +- Rhythm of the week +- Mid-week study sessions online +- Codewars club +- Socials, games nights, meetups diff --git a/common-content/en/module/html-css/what-are-forms/index.md b/common-content/en/module/html-css/what-are-forms/index.md index a963ca839..c81158e39 100644 --- a/common-content/en/module/html-css/what-are-forms/index.md +++ b/common-content/en/module/html-css/what-are-forms/index.md @@ -48,7 +48,7 @@ So that's the point of all this. πŸ‘©πŸ»β€πŸ’»πŸ’¬ **Mentor:** Right! You put a piece into a form field; you just put _one thing_ in there. A form has many fields, and a field is a single piece of data. It is the smallest piece. -So we [structure data with forms](https://developer.mozilla.org/en-US/docs/Learn/Forms). And we do that by defining form fields. +So we [structure data with forms](https://developer.mozilla.org/en-US/docs/Learn/Forms). And we do that by defining form fields with [semantic HTML](https://web.dev/learn/html/semantic-html). {{}} @@ -127,7 +127,7 @@ What you need to focus on is _what you're actually doing_. We're structuring dat
πŸ§‘πŸΏβ€πŸ’»πŸ’¬ Trainee: But then aren't all form elements validation? -πŸ§‘πŸ½β€πŸ’»πŸ’¬ **Mentor:** You _could_ say that all the rules you make about what the user can put in a field are also validation. Every `type` we just named - input type checkbox, input type email, number, date... are rules about data. +πŸ§‘πŸ½β€πŸ’»πŸ’¬ **Mentor:** You _could_ say that all the rules you make about what the user can put in a field are also validation. Every `type` we just named - input type checkbox, input type email, number, [date](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input/date)... are rules about data. I think the difference is that there's no way to type into a checkbox: there's no error message, you just can't do it. If you type your birthday into an email field, the browser will tell you that's not a valid email address. So one is just impossible to do and the other gives you an error message, and that's normally what we mean by validation. diff --git a/common-content/en/module/induction/accounts/index.md b/common-content/en/module/induction/accounts/index.md index 29dd5d4ed..c319e3485 100644 --- a/common-content/en/module/induction/accounts/index.md +++ b/common-content/en/module/induction/accounts/index.md @@ -10,13 +10,15 @@ hide_from_overview=true +++ -Download and install the following software or register for the apps. +Download and install the following software or register for the apps if you have not done so already. Click on the links to go to the registration pages. Keep your login details for all sites/apps consistent and always use your real name. -{{}} -We recognise you may need to keep your birth name private. When we say real name, we mean the name you go by. It does not have to match your birth certificate or any other legal document. It has to be consistent and professional. -{{}} +> [!IMPORTANT] +> +> ##### Real name +> +> We recognise you may need to keep your birth name private. When we say real name, we mean the name you go by. It does not have to match your birth certificate or any other legal document. It has to be consistent and professional. Every time you create an account which can have a profile picture, you should set one up. Follow these [professional image guidelines](https://www.linkedin.com/business/talent/blog/product-tips/tips-for-taking-professional-linkedin-profile-pictures) when picking an image. Use the same picture for every account. @@ -41,20 +43,12 @@ This is your public professional email address. Use it to sign up for all your p - [ ] I have made a professional Google account and Gmail address. - [ ] I have explored the [Google Suite](https://applieddigitalskills.withgoogle.com/c/en/workspace), such as calendar, docs and spreadsheets. -### Google Chrome - -Google Chrome is the first browser we will all use together. - -- [ ] I have downloaded and installed Google Chrome. -- [ ] I have logged into my professional profile on Chrome. - -Use your professional Chrome profile for all your {{}} work. You will often have to share your screen during sessions, so keep your personal internet use private and away from your professional profile. - ### GitHub -You will use [GitHub](https://github.com/signup) to store your code and to collaborate with your peers. +You will use [GitHub](https://github.com/signup) to store your code and to collaborate with your peers. You have already made a GitHub account, but you need to check it is professional. You can change your username in your settings. You can add your professional email address in your settings too. (You can have more than one email address on your account.) -- [ ] I have made a GitHub account using my professional email address. +- [ ] My GitHub account shows my professional name +- [ ] I have added my professional email address to my GitHub account. ### LinkedIn @@ -71,7 +65,7 @@ Your cohort is your first network, and this is one of the most valuable things y ### Slack -[Slack](https://slack.com/intl/en-gb) is our community space and how we communicate with each other. Download and install it now. +[Slack](https://slack.com/intl/en-gb) is our community space and how we communicate with each other. Download and install it now. If you are not using your own computer, log in to the web version instead. - [ ] I have downloaded the [Slack](https://slack.com/intl/en-gb) app on my computer and phone. - [ ] I have logged in to the {{}} workspace. @@ -79,6 +73,17 @@ Your cohort is your first network, and this is one of the most valuable things y - [ ] I have updated my profile with my picture, my professional email address, my GitHub username, my Linkedin profile and my class. - [ ] I have introduced myself on Slack. +## Applications + +If you're working on a library computer, you can't download these applications. You will use [GitHub Dev](https://github.dev/) to complete coursework instead. + +### Google Chrome + +- [ ] I have downloaded and installed Google Chrome. +- [ ] I have logged into my professional profile on Chrome. + +Use your professional Chrome profile for all your {{}} work. You will often have to share your screen during sessions, so keep your personal internet use private and away from your professional profile. + ### VSCode We will use [Visual Studio Code](https://code.visualstudio.com/) (VSCode), a professional IDE you will use on this course and at work. diff --git a/common-content/en/module/induction/check-git-installation/index.md b/common-content/en/module/induction/check-git-installation/index.md index f62dde354..1e9129760 100644 --- a/common-content/en/module/induction/check-git-installation/index.md +++ b/common-content/en/module/induction/check-git-installation/index.md @@ -4,7 +4,7 @@ time = 15 facilitation = false vocabulary=[] emoji= 'πŸ“‹' -[objectives] +[tasks] 1='Double check Git is installed on your local machine' [build] render = 'never' @@ -25,3 +25,6 @@ git version 2.40.0 ``` Otherwise, you will need to [install](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git) it or ask for support on your Slack channel. + +> [!TIP] +> If you are working on a library computer, you do not have a terminal, but your github.dev account already has Git installed. (It's called "Source Control".) So you can skip this step. diff --git a/common-content/en/module/induction/checkout-a-commit/index.md b/common-content/en/module/induction/checkout-a-commit/index.md index 9ff6b2511..6a322b40d 100644 --- a/common-content/en/module/induction/checkout-a-commit/index.md +++ b/common-content/en/module/induction/checkout-a-commit/index.md @@ -18,7 +18,7 @@ Recall that a commit is a snapshot of our project at some point in time. Therefore, we should be able to check out a previous version of our project and look at the files and folders there. We can use the Github interface to check out the files and folders at a previous commit. -{{}} +{{}} Go back to this page https://github.com/CodeYourFuture/education-blog/commits/main diff --git a/common-content/en/module/induction/cyf-folder/index.md b/common-content/en/module/induction/cyf-folder/index.md index f7ae5f131..51feff60c 100644 --- a/common-content/en/module/induction/cyf-folder/index.md +++ b/common-content/en/module/induction/cyf-folder/index.md @@ -14,7 +14,12 @@ emoji= '🧰' +++ -You'll need to create a {{}} folder to store your projects on the course. +> [!IMPORTANT] +> Make a folder called `{{}}` in your home directory. Store all your work for the course in this folder. + +You'll need to create a {{}} folder to store your projects on the course. You can do this any way you like, but here we are using the terminal. + +### How to create a folder using the terminal 1. Open a terminal on your computer. @@ -33,3 +38,6 @@ You'll need a place to store your work for the course. 5. **C**hange **d**irectory into the `{{}}` directory. 6. Double check you're in the right place by **p**rinting your current **w**orking **d**irectory. + +> [!TIP] +> If you're working on a library computer, skip this step. You will store your work in your GitHub account. diff --git a/common-content/en/module/induction/development-process/index.md b/common-content/en/module/induction/development-process/index.md index ff4d751ae..84f042516 100644 --- a/common-content/en/module/induction/development-process/index.md +++ b/common-content/en/module/induction/development-process/index.md @@ -25,6 +25,6 @@ At the moment, the computer has a folder with the blog that looks like this: Describe some of the challenges that Ahmed and Naima face when trying to write a blog together in this way. -Create or join a thread 🧡 on Slack to share your answers. Did your cohort colleagues think of similar things? +Look in Slack. Has someone made a post describing Ahmed and Naima's challenge? Share your answers as a **reply** to this post, making a [conversation 🧡 thread](https://slack.com/intl/en-gb/help/articles/115000769927-Use-threads-to-organise-discussion). {{}} diff --git a/common-content/en/module/induction/dot-dev/index.md b/common-content/en/module/induction/dot-dev/index.md new file mode 100644 index 000000000..2b878ed64 --- /dev/null +++ b/common-content/en/module/induction/dot-dev/index.md @@ -0,0 +1,25 @@ ++++ +title = 'GitHub.dev' +description = 'Completing coursework on a library computer' +time = 20 +facilitation = false +emoji= '🧰' +[objectives] +1='Access the dotdev environment on a library computer if you do not have your own' +[build] + render = 'never' + list = 'local' + publishResources = false + ++++ + +If you do not have a computer of your own yet, here's how to complete your work directly on GitHub without a local environment. + +Each repo on GitHub has a `.dev` environment so you can edit the code in your browser using an online VSCode. + +You can go to this environment directly by replacing `github.com` with `github.dev` in the URL. For example, to open the [`Module-Onboarding`](https://github.com/CodeYourFuture/Module-Onboarding) repo, you can go to + +https://github.dev/CodeYourFuture/Module-Onboarding + +> [!TIP] +> If you do have a computer, you should set up VSCode and a local environment. This is a workaround for people who don't yet have the luxury of a personal computer. diff --git a/common-content/en/module/induction/github-poets/index.md b/common-content/en/module/induction/github-poets/index.md index 82ad14291..5cd23b166 100644 --- a/common-content/en/module/induction/github-poets/index.md +++ b/common-content/en/module/induction/github-poets/index.md @@ -5,7 +5,7 @@ time = 15 facilitation = false vocabulary=[] emoji= 'πŸ“– ' -[objectives] +[tasks] 1='Double check Github account is setup' 2='Double check Course planner is setup' [build] diff --git a/common-content/en/module/induction/github/index.md b/common-content/en/module/induction/github/index.md index e1c3d0ff9..dac4c7e7e 100644 --- a/common-content/en/module/induction/github/index.md +++ b/common-content/en/module/induction/github/index.md @@ -16,6 +16,6 @@ emoji= '🧩' ### Planner on GitHub -In Fundamentals, you should have set up your Coursework planner. +You should have set up your Coursework planner. Ensure you've completed the following issue πŸ‘‰ https://github.com/CodeYourFuture/Coursework-Planner/blob/main/readme.md diff --git a/common-content/en/module/induction/install-vscode/index.md b/common-content/en/module/induction/install-vscode/index.md index 97d9d20c8..4246b9e70 100644 --- a/common-content/en/module/induction/install-vscode/index.md +++ b/common-content/en/module/induction/install-vscode/index.md @@ -14,9 +14,20 @@ emoji= '🧰' +++ -We use VS Code to write all of our code in the course. It is known as an Integrated Development Environment (IDE) and really helps you write great code! +We use VS Code to write all of our code in the course. It is known as an Integrated Development Environment (IDE) and really helps you write great code. -[πŸ”— Download and install VSCode now](https://code.visualstudio.com/) +> [πŸ”— Download and install VSCode now](https://code.visualstudio.com/) + +{{}} + +> [!TIP] +> If you are working on a library computer, use the online version of VSCode called Github.dev. + +The interface is mostly the same, but you cannot install extensions or use the terminal. You can complete all the tasks in the onboarding module without these features. +<---> + +!["Github.dev can be accessed by pressing dot on any GitHub repo"](https://user-images.githubusercontent.com/856858/130119109-4769f2d7-9027-4bc4-a38c-10f297499e8f.gif "Press the dot while on any GitHub repo to open Github.dev.") + +{{}} -Watch this video if you'd like a quick introduction to VSCode: {{}}https://www.youtube.com/watch?v=B-s71n0dHUk{{}} diff --git a/common-content/en/module/induction/learning-as-community/index.md b/common-content/en/module/induction/learning-as-community/index.md index 3119b7fd6..6b0cbb759 100644 --- a/common-content/en/module/induction/learning-as-community/index.md +++ b/common-content/en/module/induction/learning-as-community/index.md @@ -1,7 +1,7 @@ +++ title = 'Learning as a community' -time="55" +time="60" facilitation = true emoji= '🏫' [objectives] @@ -20,18 +20,15 @@ In this session, we're going to describe how we harness our community to learn t ### Resources -The facilitator will use this presentation πŸ‘‰ [Learning as a community presentation](https://miro.com/app/board/uXjVPy92Cu8=/) +The facilitator will make a copy of this presentation πŸ‘‰ [Learning as a community presentation](https://miro.com/app/board/uXjVNeEASJc=/?share_link_id=563047396351) or set the same thing up on a physical board with sticky notes. ### Preparation -- [ ] Facilitator: Review this [presentation](https://miro.com/app/board/uXjVPy92Cu8=/) before class. -- [ ] Facilitator: Ensure everyone can access the Miro board presentation. +- [ ] Facilitator: Review [how this works](how-this-works) and the Miro board [Learning as a community](https://miro.com/app/board/uXjVNeEASJc=/?share_link_id=563047396351) before class. - [ ] Facilitator: Split the class into groups of no more than 5. -- [ ] Facilitator: Make sure every group has access to a laptop. -- [ ] Facilitator: Make sure every group has access to a piece of paper and pen +- [ ] Facilitator: Ensure everyone can access the board if you are online. +- [ ] Facilitator: Make sure every group has access to sticky notes and pens if you are in person. ### Introduction The facilitator will use the Miro board presentation to guide trainees and volunteers on a discussion about how we learn together as a community. - - diff --git a/common-content/en/module/induction/next-steps/index.md b/common-content/en/module/induction/next-steps/index.md index 72e00f62e..85bb12d9f 100644 --- a/common-content/en/module/induction/next-steps/index.md +++ b/common-content/en/module/induction/next-steps/index.md @@ -23,7 +23,7 @@ Get into pairs with somebody you've not paired up with today and try figuring ou 1. Using the curriculum, locate the page setup page for the upcoming module. 1. Using the [curriculum website](https://curriculum.codeyourfuture.io/), locate the page with the prep material for the first week of the next module -1. List the things you need to install ( if anything ) for the upcoming module. +1. List the things you need to install (if anything) for the upcoming module. 1. Check you can find the backlog page for the Induction sprint. Double check you've copied all the issues from the backlog over to your Course Planner. 1. Identify all the issues with πŸ”‘ icon that are marked as **Priority**. What does the **Priority icon** πŸ”‘ mean? 1. Go to your group Slack channel and start a thread 🧡 outlining times you're free to meet up to discuss the prep work during the week @@ -32,7 +32,7 @@ Get into pairs with somebody you've not paired up with today and try figuring ou ## For volunteers -1. Locate the classroom planning board for your region ( if one exists ) +1. Locate the classroom planning board for your region (if one exists) 1. Locate the day-plan for the next week/module -1. Check the instructions and links on the **Priority πŸ”‘ issues** for the upcoming week ( both Tech Ed and PD ) +1. Check the instructions and links on the **Priority πŸ”‘ issues** for the upcoming week (both Tech Ed and PD) 1. In the day-plan for the upcoming week identify the instructions for any workshops and visit the repository containing that readme. Check the instructions make sense. diff --git a/common-content/en/module/induction/previous-versions/index.md b/common-content/en/module/induction/previous-versions/index.md index 8057731ad..85f7d267f 100644 --- a/common-content/en/module/induction/previous-versions/index.md +++ b/common-content/en/module/induction/previous-versions/index.md @@ -13,7 +13,7 @@ emoji= 'πŸ“œ' We can view the different commits of a project on Github. This means we can see what the website looked like before, in previous versions. -{{}} +{{}} Here are some different versions of the same educational backlog. [Deployed version A educational blog](https://git-demo-week1-version-a.netlify.app/) diff --git a/common-content/en/module/induction/viewing-files/index.md b/common-content/en/module/induction/viewing-files/index.md index 7f1ac186f..d59a1a435 100644 --- a/common-content/en/module/induction/viewing-files/index.md +++ b/common-content/en/module/induction/viewing-files/index.md @@ -1,10 +1,9 @@ +++ title = 'Viewing files from a git clone' - time ="20" facilitation = false emoji= 'πŸ“˜' -objectives=["Open a cloned repository in VSCode","Explore the repository in VSCode","Open the Integrated Terminal in VSCode"] +objectives=["Open a cloned repository in your IDE","Explore the repository in your IDE","Open the Integrated Terminal in VSCode"] [build] render = 'never' list = 'local' @@ -30,6 +29,5 @@ VSCode is an application that enables developers to view and edit files on their {{}} -Here is a diagram representing how the repositories interact after forking and cloning: - -![fork-and-clone-diagram](fork-and-clone-diagram.png) +> [!NOTE] +> If you're working on a library computer, use dot dev to open the repo in your browser, and navigate the files and folder there. You cannot open a terminal in the library, so come to class to try this part out. diff --git a/common-content/en/module/induction/working-locally/fork-and-clone-diagram.png b/common-content/en/module/induction/working-locally/fork-and-clone-diagram.png new file mode 100644 index 000000000..fc47d1b24 Binary files /dev/null and b/common-content/en/module/induction/working-locally/fork-and-clone-diagram.png differ diff --git a/common-content/en/module/induction/working-locally/index.md b/common-content/en/module/induction/working-locally/index.md index dfd4601b8..fa7e9d742 100644 --- a/common-content/en/module/induction/working-locally/index.md +++ b/common-content/en/module/induction/working-locally/index.md @@ -14,6 +14,15 @@ emoji= 'πŸ’»' +++ +Here is a diagram representing how the repositories interact after forking and cloning: + +![fork-and-clone-diagram](fork-and-clone-diagram.png) + +Sketch this diagram in your notebook. When you inevitably get mixed lost about where your changes are, you can refer back to this diagram to help you understand what's happening. + +> [!NOTE] +> If you're working on a library computer, just fork the repo to your own GitHub account. You can't clone a repo on a library computer, so come to class to try cloning out. You can explore the files using dot dev in the same way as you would in Visual Studio Code. + We can also use Git on our local machine to perform similar tasks as we do on GitHub. So we need to address the following question: > How can we get a copy of an existing GitHub repository on our local machine? diff --git a/common-content/en/module/induction/wrapping-up/index.md b/common-content/en/module/induction/wrapping-up/index.md index 505b172b4..905427f99 100644 --- a/common-content/en/module/induction/wrapping-up/index.md +++ b/common-content/en/module/induction/wrapping-up/index.md @@ -16,7 +16,7 @@ hide_from_overview = true {{}} -πŸ“‹ Double check the learning objectives from this section. Make a note of those objectives that you're still struggling with. +πŸ“‹ Double check the learning objectives from this sprint. Make a note of those objectives that you're still struggling with. Now you'll need to **create a commit**. @@ -25,9 +25,10 @@ You can use the "How to commit changes and push them in Visual Studio Code" vide We'll cover this topic often in workshops. Come to a CYF centre to work on this with a mentor. 1. Try opening your clone of education-blog in VSCode -2. Make sure you're not on the `main` branch -3. Try fixing a typo in the `README.md` file -4. Try using the video to create a commit of your work. +1. Make sure you're on the `main` branch +1. Make a **new** branch for your changes +1. Try fixing a typo in the `README.md` file +1. Try using the video to create a commit of your work. {{}} diff --git a/common-content/en/module/js1/check-unix-os/index.md b/common-content/en/module/js1/check-unix-os/index.md index 5941856f9..c487568de 100644 --- a/common-content/en/module/js1/check-unix-os/index.md +++ b/common-content/en/module/js1/check-unix-os/index.md @@ -26,8 +26,6 @@ Code Your Future does not support Windows. We have found that we don't reliably have volunteers at class who can debug Windows problems, and they frequently come up, stopping trainees from making progress. We do not support Windows so as to not waste lots of trainee and volunteer time. We have made this decision even though Windows is a popular operating system and has features like WSL which help to get experience with Unix. - -You *must* use a Unix-based operating system at Code Your Future. {{}} If you have a Mac or Linux machine already, you already have a UNIX based operating system. All CYF-supplied laptops run Mac OS or Linux. If you have your own machine and it runs Windows, you should already have set up a Linux partition. diff --git a/common-content/en/module/onboarding/application/index.md b/common-content/en/module/onboarding/application/index.md new file mode 100644 index 000000000..9155929de --- /dev/null +++ b/common-content/en/module/onboarding/application/index.md @@ -0,0 +1,23 @@ ++++ +title="Entry Criteria" +time=10 +emoji="🎯" +hide_from_overview=true +objectives = [ + "List the mandatory requirements for this course.", +] +[build] + render = 'never' + list = 'local' + publishResources = false ++++ + +### Welcome + +To take this course you must have completed [Intro to Digital](https://itd.codeyourfuture.io) and received a micro-credential badge by email. Check your email. This badge is your ticket to access this course. + +You will receive an email within two weeks of completing ITD, inviting you to begin this course as a Learner. All operational details should be linked in this email. If you have not received an email, please tell us at contact@codeyourfuture.io. + +Log in to your [Course Portal](https://application-process.codeyourfuture.io/). This the same portal you used to complete ITD. A new set of steps should have appeared. These are the steps to complete ITP. + +If you are all signed up and logged in, please now continue... diff --git a/common-content/en/module/onboarding/blockers/index.md b/common-content/en/module/onboarding/blockers/index.md new file mode 100644 index 000000000..ffab3a34a --- /dev/null +++ b/common-content/en/module/onboarding/blockers/index.md @@ -0,0 +1,50 @@ ++++ +title = 'Sharing Our Blockers' +time = 45 +facilitation = false +vocabulary=["Blockers"] +emoji= '🧩' +[objectives] +1='Identify blockers' +2='Share blockers on a board or sticky notes' +[build] + render = 'never' + list = 'local' + publishResources = false ++++ + +We call problems that stop our progress "blockers". We talk through our blockers regularly and help each other get "unblocked" or "unstuck". + +{{}} +Join the online board or grab some sticky notes. Add your blockers. + +Make sure to add only one blocker per note. + +{{}} + +**Facilitator** Once everyone has added their blockers, group similar blockers together. + +**Facilitator** Next, discuss the blockers and help each other get "unblocked". Start with the most common blocker and work your way down the list. + +
+ + +#### Hints and Tips + + + +{{}} + +- I can't find a Slack channel people keep mentioning. +- People tell me I should be replying to a Slack message in a thread, and I don't know how. +- I can't open a PR, because... +- How do I fix extra stray files in my PR? +- I don't have a computer so I can't complete my work! +- How do I run Lighthouse? + +{{}} + +- Everyone should have blockers. If you aren't blocked on anything in the course, do you need to challenge yourself more? +- Ask "stupid" questions. Your question is not stupid! What we are doing is hard, and everyone has questions. If you're stuck, it's likely that someone else is too. Please help others and ask your question! +- If you have other more _advanced_ questions, do write them on the board but **don't** expect to answer them in Blockers. We will work on those in study group. +
diff --git a/common-content/en/module/onboarding/demo/index.md b/common-content/en/module/onboarding/demo/index.md new file mode 100644 index 000000000..def393b63 --- /dev/null +++ b/common-content/en/module/onboarding/demo/index.md @@ -0,0 +1,47 @@ ++++ +title="Demo" +time=45 +objectives = [ + "Explain your work to others at CEFR B2 level or higher.", + "Listen and understand standard speech spoken at a normal rate and follow even complex lines of argument provided the topic is reasonably familiar.", + "Participate in meetings in your area of expertise, if you have help understanding some points.", + "Ask clarifying questions and revise your response based on new information.", +] +[build] + render = 'never' + list = 'local' + publishResources = false ++++ + +At {{}} we expect you to demo your work to the class. You must have many opportunities to practice how to clearly and simply **explain your work to others**. This is really important for interviews and career success. + +## ⏰ Timekeeper + +The timekeeper will keep the groups on track. + +Split randomly into groups of no more than 4 people. Mix up your teams. Each person will have 2 minutes to demo their work to the group. After the demo, the group will ask questions or give feedback for 5 minutes. Then the next person will demo their work. + +## πŸ§‘πŸΌβ€πŸŽ“ Trainees + +### 1. Demo {{}}2{{}} + +You will demo something about your work to the group. + +You will have 2 minutes to explain what you did and why. It's ok to show broken code or a system that doesn't work yet. Just make sure your demo is interesting. + +### 2. Feedback {{}}5{{}} + +After the demo, the group will give you feedback for up to 5 minutes. It's smart to suggest what kind of feedback you want by asking some "generative" questions. For example: + +- I wasn't sure if it makes sense to try X. What do you think? +- I liked the way I did X, but I know there are other approaches, what did you do? +- I found X really confusing, did anyone else have the same problem? + +## πŸ’‘ Tips: + +- **Practice** the format of demos before class. +- **Keep it simple**. Don't try to show everything you did. Just show _one_ interesting thing. +- **Keep it short**. Two minutes is enough. +- **Explain** what you did and why. +- **Show** your code, system, or other artefacts of work. +- **Ask** for feedback. diff --git a/common-content/en/module/onboarding/development/index.md b/common-content/en/module/onboarding/development/index.md new file mode 100644 index 000000000..e7eb74681 --- /dev/null +++ b/common-content/en/module/onboarding/development/index.md @@ -0,0 +1,21 @@ ++++ +title="Study Group Development" +emoji="πŸ§‘πŸΏβ€πŸ”§" +time=120 +objectives = [ + "Create a strategy for implementing a program based on a set of requirements.", + "Express questions, problems and blockers as formal bug reports", + "Interpret business requirements and express them as test cases.", + "Open a pull request and iterate on it in response to feedback."] +[build] + render = 'never' + list = 'local' + publishResources = false + ++++ + +This time is set aside for you to work together in small groups to make progress on your coursework and objectives. You should have brought at least one ticket from your backlog to work on and ideally have prepared at least one question to get mentor support on. + +You can also choose to do structured activities to consolidate your objectives for this sprint. Your learning journey belongs to you. Think about what you need to do to achieve the objectives for this sprint and how you can use this time to work towards them. + +If you are working on a Pull Request, this is a great time to get real time code review from your peers and mentors. Remember to use the GitHub interface to comment on the code and ask questions so your work can be tracked. diff --git a/common-content/en/module/onboarding/do-the-prep/index.md b/common-content/en/module/onboarding/do-the-prep/index.md new file mode 100644 index 000000000..a17f88dc4 --- /dev/null +++ b/common-content/en/module/onboarding/do-the-prep/index.md @@ -0,0 +1,22 @@ ++++ +title="Do the Prep" +emoji="🧠" +time=5 +hide_from_overview="true" +[build] + render = 'never' + list = 'local' + publishResources = false ++++ + +You should have completed the prep listed in [Welcome to CodeYourFuture](/welcome/prep). If you haven't done that yet, go back and complete it now. + +> 🧠 You must always do the prep. + +If you have worked through the Welcome prep, move on to [Onboarding Sprint 1 Prep](onboarding/sprints/1/prep/) and begin the prep for the first sprint. + +{{}} diff --git a/common-content/en/module/onboarding/expectations/index.md b/common-content/en/module/onboarding/expectations/index.md new file mode 100644 index 000000000..041d90554 --- /dev/null +++ b/common-content/en/module/onboarding/expectations/index.md @@ -0,0 +1,39 @@ ++++ +title="βš–οΈ Expectations" +emoji="βš–οΈ" +time=5 +objectives = [ + "List the expectations of the course." +] +hide_from_overview="true" +[build] + render = 'never' + list = 'local' + publishResources = false ++++ + +## Learners, we expect you to: + +- Work in groups and individually, in class and during the week. +- Show up on time and participate in all activities, including helping others. +- Complete the work in the way it is specified. +- Do your best. + +## Learners, you can expect: + +- Fair, achievable requirements, explained as clearly as possible. +- Help from volunteers and other learners with your questions and blockers. +- A safe, inclusive environment where you can learn and grow. +- Many opportunities to succeed. + +## We expect everyone to: + +- Follow the [Code of Conduct](https://codeyourfuture.io/about/code-of-conduct/). +- Help each other. +- Do the prep. + +{{}} diff --git a/common-content/en/module/onboarding/goals/index.md b/common-content/en/module/onboarding/goals/index.md new file mode 100644 index 000000000..cac396d32 --- /dev/null +++ b/common-content/en/module/onboarding/goals/index.md @@ -0,0 +1,57 @@ ++++ +title="🎯 Goals" +time=10 +emoji="🎯" +hide_from_overview=true +objectives = [ + "List the core goals of the module", + "Find the learning objectives for Sprint 1", + "Describe what you need to do in order to complete the onboarding module" +] +[build] + render = 'never' + list = 'local' + publishResources = false ++++ + +You have joined us as a Learner. Your overall goal for this module is to understand how to succeed at the ITP course. + +To demonstrate you know how to succeed at the course, you should apply to enroll as a Trainee within the next three weeks. To do this, you will need to do show up every week, learn, get work done, and get your work reviewed. + +If eligible, you should enroll as a Trainee within the next three weeks. + +> 🎯 Complete onboarding and enroll as a Trainee + +Find the learning objectives for the text you are reading now. These are the goals for this text. This is what you should be able to do after completing this text. + +Now find the learning objectives for Sprint 1. We call these the "success criteria". These are the goals for the first sprint of the module. This is what you should be able to do after completing Sprint 1. + +This formal structure might be new to you. It is a way to help you evaluate for yourself whether you have achieved the goals of the module. If you have done (and can do) the things listed in the learning objectives, you have gained the skill. If you have not, you have not yet gained the skill, and should keep working at it. + +As we are just meeting this idea, let's go over them here too. The skills you'll learn in this module are based around these themes: version control, requirements and testing, code review, data, and scientific method. Write each of these themes down in your notebook. + +To complete the module, you will need to demonstrate you have learnt these skills, and apply to enroll as a Trainee. + +#### Version control + +_By the end of this module_ you will have tracked changes to data (your code) over time with Git and GitHub. Your goal is to build a mental model of Git "trees" and begin learning ways to travel through files using the "time machine" of Git. + +#### Requirements and Testing + +_By the end of this module_ , you will have tested your work using acceptance criteria, manual testing, and automated testing. Your goal is to interpret requirements and write code to meet acceptance criteria. + +#### Code review + +_By the end of this module_ you will have revised, refactored, and reviewed code using code review. Your goal is to form the habits of a professional who can think, talk, and write in a technical context. + +#### Data + +_By the end of this module_ you will have manipulated data with HTML, Git, and Google Sheets. Your goal is to begin to understand how data is structured and how to manipulate it. + +#### Scientific method + +_By the end of this module_ you will have written and asked well-structured developer questions. Your goal is to build a strategy to methodically solve problems. + +#### Enrollment + +_By the end of this module_ you will have enrolled as a Trainee. Your goal is to complete the onboarding process and enroll as a Trainee. diff --git a/common-content/en/module/onboarding/help/index.md b/common-content/en/module/onboarding/help/index.md new file mode 100644 index 000000000..999476169 --- /dev/null +++ b/common-content/en/module/onboarding/help/index.md @@ -0,0 +1,51 @@ ++++ +title="🧭 Help" +description="Make sure you have everything you need to come to class and do your work" +hide_from_overview="true" +time=30 +objectives = [ + "Find the Signposts website", + "List the financial learner support available to you" +] +[build] + render = 'never' + list = 'local' + publishResources = false ++++ + +🧭 _Everyone_ at {{}} has barriers to education, and we can [help with some things](https://signposts.codeyourfuture.io/). If you cannot come to an in-person class because you can't afford: + +#### πŸ§’ Childcare + +The onboarding module can be completed entirely online if necessary. Once you have completed this module and enrolled as a Trainee, we can help you with childcare costs. + +#### πŸ’» A computer or broadband + +The onboarding module can be completed entirely on a library computer. Once you have completed this module and enrolled as a Trainee, we can lend you a laptop and data if you need them. + +#### 🚌 Bus or train tickets + +Just like ITD, this onboarding module can be completed entirely online if necessary. Once you have completed this module and enrolled as a Trainee, we can help with travel costs. + +#### πŸ₯ͺ Food + +will always be provided in class. + +We ask that you complete the onboarding module step before we enroll you as a Trainee. We are obliged to only enroll people we have a reasonable expectation of being able to complete the whole course. But predicting the future is a challenge! We have created this module to try to give as many people as possible a fair chance to show they can do this. + +{{}} + +{{}} + +We all help each other at {{}}. We are a community. + +You are not competing against each other for a limited number of places. We will accept everyone who meets the success criteria. + +- You should ask for help +- You should help others + +{{}} diff --git a/common-content/en/module/onboarding/overcoming-blockers/index.md b/common-content/en/module/onboarding/overcoming-blockers/index.md new file mode 100644 index 000000000..3be55f086 --- /dev/null +++ b/common-content/en/module/onboarding/overcoming-blockers/index.md @@ -0,0 +1,20 @@ ++++ +title="Overcoming Blockers" +time=20 +facilitation=false +[build] + render = 'never' + list = 'local' + publishResources = false + ++++ + +{{}} + +[Overcoming Coding Blockers](https://www.linkedin.com/pulse/how-overcome-coding-blockers-kingsley-ibe/) + +{{}} + +## Why are we doing this? + +In class we will talk about Iteration and Blockers. Read over the day plan. What does iteration mean? What are Blockers? Write down your answers. diff --git a/common-content/en/module/onboarding/pairing/index.md b/common-content/en/module/onboarding/pairing/index.md new file mode 100644 index 000000000..165562099 --- /dev/null +++ b/common-content/en/module/onboarding/pairing/index.md @@ -0,0 +1,18 @@ ++++ +title="Pair programming" +emoji="πŸ§‘πŸΏβ€πŸ”§πŸ§‘πŸΏβ€πŸ”§" +time=25 +objectives = [ + "Drive and navigate in a pair programming session"] +[build] + render = 'never' + list = 'local' + publishResources = false ++++ + +- Switch between driver and navigator roles after {{}}10{{}} +- The "driver" is the person typing on the keyboard, just thinking about what needs to be written +- The "navigator" reviews what the driver is doing and is thinking about to write next +- Don't dominate - this is teamwork + +βŒ› Time's up! Take a {{}}5{{}} break! Make a cup of tea. Good job, partners! diff --git a/common-content/en/module/onboarding/pomodoro/index.md b/common-content/en/module/onboarding/pomodoro/index.md new file mode 100644 index 000000000..fad119713 --- /dev/null +++ b/common-content/en/module/onboarding/pomodoro/index.md @@ -0,0 +1,19 @@ ++++ +title="Pomodoro" +emoji="πŸ…" +time=60 +objectives = [ + "Complete a small-scoped ticket in 25 minutes"] +[build] + render = 'never' + list = 'local' + publishResources = false ++++ + +Each group member, take a small-scoped piece of work from your backlog. Set a timer for {{}}25{{}}. Use this focused time to complete your ticket and open a PR. + +βŒ› Time's up! Take a {{}}5{{}} break! Make a cup of tea. Walk around a bit. + +Now set a new {{}}25{{}} and review each PR as a group. + +βŒ› Time's up! Take a {{}}5{{}} break! Make a cup of tea. Stretch! Look at how much progress you made in one hour. ✨ diff --git a/common-content/en/module/onboarding/preparation/index.md b/common-content/en/module/onboarding/preparation/index.md new file mode 100644 index 000000000..0c4ad0edc --- /dev/null +++ b/common-content/en/module/onboarding/preparation/index.md @@ -0,0 +1,33 @@ ++++ +title="Prep" +time=10 +hide_from_overview="true" +[build] + render = 'never' + list = 'local' + publishResources = false ++++ + +Double-check you have everything you need to start this course. + +- [ ] You have completed ITD and received an invitation to join this course by email +- [ ] You have signed the [Code of Conduct](https://codeyourfuture.io/about/code-of-conduct/) +- [ ] You have signed the Learner agreement sent to you by email +- [ ] You know how to get to class in person or online +- [ ] You have read and understood the success criteria + +If you need help with any of these, ask in Slack or go to the [Signposts website](https://signposts.codeyourfuture.io/). + +Now go read over the day plans, backlogs, success criteria and complete the quiz. You can do it! πŸš€ + +{{}} + +{{}} diff --git a/common-content/en/module/onboarding/read-the-day-plan/index.md b/common-content/en/module/onboarding/read-the-day-plan/index.md new file mode 100644 index 000000000..5371a9fa4 --- /dev/null +++ b/common-content/en/module/onboarding/read-the-day-plan/index.md @@ -0,0 +1,18 @@ ++++ +title="Prepare for the day" +time=10 +hide_from_overview="true" +[build] + render = 'never' + list = 'local' + publishResources = false ++++ + +Read the day plan and make sure you are ready to start the day. What will you be working on? What does the workshop cover and expect you to know already? Professionals **prepare** for their work, so take a moment to get ready. + +- [ ] You have read the day plan for this sprint +- [ ] You have covered the prerequisites for any workshop that has been planned +- [ ] You have started your backlog tasks and written down your questions for study group +- [ ] You have organised childcare if you need it +- [ ] You know how to get to class +- [ ] You have read and understood the success criteria diff --git a/common-content/en/module/onboarding/steps/index.md b/common-content/en/module/onboarding/steps/index.md new file mode 100644 index 000000000..63f21b891 --- /dev/null +++ b/common-content/en/module/onboarding/steps/index.md @@ -0,0 +1,13 @@ ++++ +title="Submitting your steps" +emoji="πŸ‘£" +time=15 +[build] + render = 'never' + list = 'local' + publishResources = false ++++ + +Your goal for this sprint is to submit your first step and enroll as a Trainee. This is a big milestone, and we want to make sure you have all the support you need to get there. + +All the information you need to complete this step is in the prep. Make sure to read it carefully. If you have something blocking you from submitting, use this time to resolve your blocker and submit your step. diff --git a/common-content/en/module/onboarding/wrap-party/index.md b/common-content/en/module/onboarding/wrap-party/index.md new file mode 100644 index 000000000..468d195bf --- /dev/null +++ b/common-content/en/module/onboarding/wrap-party/index.md @@ -0,0 +1,16 @@ ++++ +title="Wrap Party" +time=180 +[build] + render = 'never' + list = 'local' + publishResources = false ++++ + +You made it! πŸŽ‰ + +Thank you so much for your hard work. We will send you the results of your interview by email by the end of the week. + +Now, join the wrap party and celebrate your achievements with your community. 🎈 + +Can you bring a snack or drink to share? πŸͺπŸ₯€ Or a board game? We love Dixit, Codenames, and Rush Hour in particular. diff --git a/common-content/en/module/onboarding/wrap/index.md b/common-content/en/module/onboarding/wrap/index.md new file mode 100644 index 000000000..e47c130e3 --- /dev/null +++ b/common-content/en/module/onboarding/wrap/index.md @@ -0,0 +1,19 @@ ++++ +title="Wrap" +time=20 +[build] + render = 'never' + list = 'local' + publishResources = false ++++ + +You are done for the day. Take a moment to reflect on what you have learned and achieved. + +Stand in a circle and share: + +- πŸ“› your name +- πŸ’ͺ🏽 one thing you built today +- πŸ‘·πŸΎ the task you are going to work on next +- πŸ›Ÿ one thing you need help with + +Give yourselves a round of applause. Now you have earned your rest. Usually people go for a cup of tea or a pint after class. You are welcome to join and wind down together. diff --git a/common-theme/assets/styles/04-components/block.scss b/common-theme/assets/styles/04-components/block.scss index ab3301868..3d2391a62 100644 --- a/common-theme/assets/styles/04-components/block.scss +++ b/common-theme/assets/styles/04-components/block.scss @@ -16,6 +16,10 @@ gap: var(--theme-spacing--gutter); } + &__objectives { + width: 100%; + } + &__series { display: grid; gap: var(--theme-spacing--gutter); @@ -61,7 +65,7 @@ font-size: var(--theme-type-size--6); } } - + // TODO track down and rm this &--pd.c-block { box-shadow: none; border: none; diff --git a/common-theme/layouts/partials/block/issue.html b/common-theme/layouts/partials/block/issue.html index dab0c23f2..52b51b2b6 100644 --- a/common-theme/layouts/partials/block/issue.html +++ b/common-theme/layouts/partials/block/issue.html @@ -26,7 +26,7 @@ {{ $extractedObjectives := partial "strings/extract-github-objectives.html" $response.body }} {{ if gt (len $extractedObjectives) 0 }} -
+

Learning Objectives

 diff --git a/org-cyf-how-this-works/content/sprints/self-coordinate/backlog/index.md b/org-cyf-how-this-works/content/sprints/self-coordinate/backlog/index.md index 0cc2ea12e..f79048783 100644 --- a/org-cyf-how-this-works/content/sprints/self-coordinate/backlog/index.md +++ b/org-cyf-how-this-works/content/sprints/self-coordinate/backlog/index.md @@ -5,5 +5,5 @@ emoji= 'πŸ₯ž' menu_level = ['sprint'] weight = 2 backlog= 'Module-How-our-curriculum-works' -backlog_filter= 'Self coordinate' +backlog_filter= 'πŸ• Self coordinate' +++ diff --git a/org-cyf-how-this-works/content/sprints/self-coordinate/prep/index.md b/org-cyf-how-this-works/content/sprints/self-coordinate/prep/index.md index cf2c37674..4bbe56a50 100644 --- a/org-cyf-how-this-works/content/sprints/self-coordinate/prep/index.md +++ b/org-cyf-how-this-works/content/sprints/self-coordinate/prep/index.md @@ -26,4 +26,7 @@ src="module/how-our-curriculum-works/study-groups" [[blocks]] name="backlog" src="module/how-our-curriculum-works/backlog" +[[blocks]] +name="tasks and ratios" +src="module/how-our-curriculum-works/tasks-and-ratios" +++ diff --git a/org-cyf-how-this-works/content/sprints/self-educate/backlog/index.md b/org-cyf-how-this-works/content/sprints/self-educate/backlog/index.md index 88d11cfb4..a6202b654 100644 --- a/org-cyf-how-this-works/content/sprints/self-educate/backlog/index.md +++ b/org-cyf-how-this-works/content/sprints/self-educate/backlog/index.md @@ -5,7 +5,7 @@ emoji= 'πŸ₯ž' menu_level = ['sprint'] weight = 2 backlog= 'Module-How-our-curriculum-works' -backlog_filter= 'Self educate' +backlog_filter= 'πŸ’‘ Self educate' +++ This view lists the issues for this sprint. You can think of the issues in this view as **actions** to guide you in your first interactions with the community. diff --git a/org-cyf-how-this-works/content/sprints/self-evaluate/backlog/index.md b/org-cyf-how-this-works/content/sprints/self-evaluate/backlog/index.md index a72f6a002..88f327757 100644 --- a/org-cyf-how-this-works/content/sprints/self-evaluate/backlog/index.md +++ b/org-cyf-how-this-works/content/sprints/self-evaluate/backlog/index.md @@ -5,5 +5,5 @@ emoji= 'πŸ₯ž' menu_level = ['sprint'] weight = 2 backlog= 'Module-How-our-curriculum-works' -backlog_filter= 'Self evaluate' +backlog_filter= 'πŸ“ Self evaluate' +++ diff --git a/org-cyf-itp/content/_index.md b/org-cyf-itp/content/_index.md index 43c943bac..5c6e10ce6 100644 --- a/org-cyf-itp/content/_index.md +++ b/org-cyf-itp/content/_index.md @@ -1,6 +1,6 @@ +++ title="Intro to Programming" -menus_to_map=["start here", "programming", "next steps"] +menus_to_map=["start here", "course schedule", "next steps"] description="New? Lost? [Quickstart](how-this-works/prep/#overview)" emoji= "πŸ§‘πŸΏβ€πŸ«" +++ diff --git a/org-cyf-itp/content/data-flows/_index.md b/org-cyf-itp/content/data-flows/_index.md index 340d8206a..a19e94f19 100644 --- a/org-cyf-itp/content/data-flows/_index.md +++ b/org-cyf-itp/content/data-flows/_index.md @@ -3,6 +3,6 @@ title = 'Data flows' description = 'Collaborate in code; Define and manage state; Use asynchronous programming to handle events and data; ' layout = 'module' emoji= 'πŸ₯' -menu = ['syllabus', 'core', 'programming'] +menu = ['syllabus', 'course schedule'] weight='5' +++ diff --git a/org-cyf-itp/content/data-groups/_index.md b/org-cyf-itp/content/data-groups/_index.md index 31325e35b..36d54362d 100644 --- a/org-cyf-itp/content/data-groups/_index.md +++ b/org-cyf-itp/content/data-groups/_index.md @@ -3,6 +3,6 @@ title = 'Data groups' description = 'Organise and structure data; Build interactive user interfaces; Break problems down into sub-problems; Interpret acceptance criteria to form test cases' layout = 'module' emoji= '🐣' -menu = ['syllabus', 'core', 'programming'] +menu = ['syllabus', 'course schedule'] weight='4' +++ diff --git a/org-cyf-itp/content/guides/teaching/timeline/index.md b/org-cyf-itp/content/guides/teaching/timeline/index.md new file mode 100644 index 000000000..92e287db5 --- /dev/null +++ b/org-cyf-itp/content/guides/teaching/timeline/index.md @@ -0,0 +1,53 @@ ++++ +title = "Timeline " +description = "Check your class progress against the ITP timeline" +time = 30 +facilitation = false +emoji= "πŸ“…" ++++ + +## Timeline of ITP, staying on track: + +The course starts on the 1st of the month but there may be 7 days until the first Saturday, so we have written this to cover that variance. + +There are 12 learning weeks in the curriculum, which you will schedule over a maximum of 16 weeks. Most people should complete this course in 12 weeks of classes. Some will go faster (and this is encouraged). A few people will have adverse life events and need a couple of weeks to catch up. Once a learner is a full module behind, it's not realistic for them to catch up. + +So that's your rule of thumb for staying on track. What does this look like in practice, week by week? + +## 🫢🏽 Day 1 Week 1 + +Week 1: you have logged in to the dashboard to see your list of learners and welcomed them by name in Slack. + +## 🀝 Module 1: [Weeks 2, 3, 4](/onboarding) + +🀝 Week 2: you have met everyone in person or at Zoomschool + +- Week 2: most people have opened a PR +- Week 2: most people have gotten a code review + +🀝 Week 3: 100% of learners have opened a PR or withdrawn/deferred +🀝 Week 4: Focus on enrollment: 60% of learners have completed the [Onboarding Module](/onboarding) and enrolled as a trainee + +## πŸ₯š Module 2: [Weeks 5, 6, 7](/structuring-data) + +πŸ₯š Week 5: 60% of learners have enrolled as a trainee +πŸ₯š Week 6: Everybody has begun [Structuring and Testing Data](/structuring-data) at least as we are halfway through the course! +πŸ₯š Week 7: Focus on step review: keep the momentum going. Advise learners who have made no progress to withdraw as there is no chance of making up the work now. + +## 🐣 Module 3: [Weeks 8, 9, 10](/data-groups) + +🐣 Week 8: Most people have begun [Data Groups](/data-groups) +🐣 Week 9: Every trainee has benefited from at least 5 pair programming sessions +🐣 Week 10: Every trainee has engaged in at least 8 code reviews + +## πŸ₯ Final Module: [Weeks 11, 12, 13](/data-flows) + +πŸ₯ Week 11: Everybody has begun [Data Flows](/data-flows). Most trainees are completing their TV Show Projects - encourage demos! +πŸ₯ Week 12: Most trainees are submitting their final step +πŸ₯ Week 13: You are reviewing and approving final step submissions + +## 🎁 Wrapping up: Weeks 14, 15, 16 + +🐟 Week 14: Trainees who have fallen behind by less than 1 module have caught up and completed. Trainees going for [the Piscine](https://piscine.codeyourfuture.io) have applied. +πŸ‘£ Week 15: You are wrapping up and supporting trainees to take their next steps. +πŸŽ‰ Week 16 : This course has completed. 100% of learners have completed or withdrawn. Have a party. diff --git a/org-cyf-itp/content/onboarding/_index.md b/org-cyf-itp/content/onboarding/_index.md new file mode 100644 index 000000000..8ce8ffe31 --- /dev/null +++ b/org-cyf-itp/content/onboarding/_index.md @@ -0,0 +1,8 @@ ++++ +title = 'Onboarding' +description = 'Evaluate and fix code with Lighthouse; use version control with Git and GitHub; Plan your study and set goals; Enroll as a Trainee' +layout = 'module' +emoji= 'πŸ«±πŸΎβ€πŸ«²πŸΏ' +menu = ['syllabus', 'course schedule'] +weight='2' ++++ diff --git a/org-cyf-itp/content/onboarding/prep/index.md b/org-cyf-itp/content/onboarding/prep/index.md new file mode 100644 index 000000000..4f67bf047 --- /dev/null +++ b/org-cyf-itp/content/onboarding/prep/index.md @@ -0,0 +1,11 @@ ++++ +title = 'Prep' +description = 'What to do before the module starts' +layout = 'prep' +emoji= 'πŸ§‘πŸΎβ€πŸ’»' +menu_level = ['module'] +weight = 1 +[[blocks]] +name="Do the prep" +src="module/onboarding/do-the-prep" ++++ diff --git a/org-cyf-itp/content/onboarding/sprints/1/_index.md b/org-cyf-itp/content/onboarding/sprints/1/_index.md new file mode 100644 index 000000000..ffc1960dd --- /dev/null +++ b/org-cyf-itp/content/onboarding/sprints/1/_index.md @@ -0,0 +1,9 @@ ++++ +title = 'Sprint 1' +description = 'What to do, in order, to complete Sprint 1' +layout = 'sprint' +emoji= '⏱️' +menu_level = ['module'] +weight = 2 +theme = 'Version control' ++++ diff --git a/org-cyf-itp/content/onboarding/sprints/1/backlog/index.md b/org-cyf-itp/content/onboarding/sprints/1/backlog/index.md new file mode 100644 index 000000000..fa8b4b62a --- /dev/null +++ b/org-cyf-itp/content/onboarding/sprints/1/backlog/index.md @@ -0,0 +1,9 @@ ++++ +title = 'backlog' +layout = 'backlog' +emoji= '🏷️' +menu_level = ['sprint'] +weight = 2 +backlog= 'Module-Onboarding' +backlog_filter='πŸ“… Sprint 1' ++++ diff --git a/org-cyf-itp/content/onboarding/sprints/1/day-plan/index.md b/org-cyf-itp/content/onboarding/sprints/1/day-plan/index.md new file mode 100644 index 000000000..2a308af16 --- /dev/null +++ b/org-cyf-itp/content/onboarding/sprints/1/day-plan/index.md @@ -0,0 +1,63 @@ ++++ +title = 'day-plan' +layout = 'day-plan' +emoji= 'πŸ§‘πŸΎβ€πŸ€β€πŸ§‘πŸΎ' +menu_level = ['sprint'] +weight = 3 +[[blocks]] +name="Energiser" +src="energisers/in-person-and-online" +[[blocks.nested.blocks]] +name="Zip Zap Boing" +src="energisers/zip-zap-boing" +time=0 +[[blocks.nested.blocks]] +name="Popcorn Show and Tell" +src="energisers/popcorn" +time=0 +[[blocks]] +name="Morning orientation" +src="blocks/morning-orientation" +time=15 +[[blocks]] +name="Workshop: Using the Curriculum" +src="module/fundamentals/using-the-curriculum" +time=60 +[[blocks]] +name="Morning break" +src="blocks/morning-break" +[[blocks]] +name="Workshop: Using GitHub" +src="https://github.com/CodeYourFuture/Developer-Specs" +time=60 +[[blocks]] +name="lunch" +src="blocks/lunch" +[[blocks]] +name="Blockers! Getting Unstuck" +src="module/onboarding/blockers" +time=75 +[[blocks]] +name="Afternoon break" +src="blocks/afternoon-break" +[[blocks]] +name="Study Group Development" +src="module/onboarding/development" +time=75 +[[blocks.nested.blocks]] +name="Optional structured activity: Pomodoro" +src="module/onboarding/pomodoro" +[[blocks.nested.blocks]] +name="Optional structured activity: Pair Programming" +src="module/onboarding/pairing" +[[blocks.nested.blocks]] +name="Bikes for Refugees Project" +src="https://github.com/CodeYourFuture/Module-Onboarding/issues/22" +[[blocks]] +name="Code Review" +src="https://github.com/CodeYourFuture/Module-Onboarding/pulls" +time=0 +[[blocks]] +name="Wrap" +src="blocks/wrap" ++++ diff --git a/org-cyf-itp/content/onboarding/sprints/1/prep/index.md b/org-cyf-itp/content/onboarding/sprints/1/prep/index.md new file mode 100644 index 000000000..826df5bbe --- /dev/null +++ b/org-cyf-itp/content/onboarding/sprints/1/prep/index.md @@ -0,0 +1,74 @@ ++++ +title = 'prep' +layout = 'prep' +emoji= 'πŸ§‘πŸΎβ€πŸ’»' +menu_level = ['sprint'] +weight = 1 +[[blocks]] +name="GitHub Dot Dev" +src="module/induction/dot-dev" +[[blocks]] +name="Install VS Code" +src="module/induction/install-vscode" +time=10 +[[blocks]] +name="Check Git" +src="module/induction/check-git-installation" +time=5 +[[blocks]] +name="Create CYF Folder" +src="module/induction/cyf-folder" +time=5 +[[blocks]] +name="Fork your Planner" +src="https://www.youtube.com/watch?v=cnx0RuAu2tc" +time=5 +[[blocks]] +name="Make your Planning Board" +src="https://www.youtube.com/watch?v=Hbtfil-G0h0" +time=15 +[[blocks]] +name="Set up Planner" +src="https://github.com/CodeYourFuture/Coursework-Planner/tree/main" +time=30 +[[blocks]] +name="cyf blog" +src="module/induction/cyf-blog" +[[blocks]] +name="development-process" +src="module/induction/development-process" +[[blocks]] +name="version control" +src="module/induction/version-control" +[[blocks]] +name="sharing history" +src="module/induction/sharing-history" +[[blocks]] +name="explore" +src="module/induction/checkout-a-commit" +[[blocks]] +name="previous versions" +src="module/induction/previous-versions" +[[blocks]] +name="forking a repository" +src="module/induction/forking-a-repository" +[[blocks]] +name="working locally" +src="module/induction/working-locally" +[[blocks]] +name="viewing files" +src="module/induction/viewing-files" +[[blocks]] +name="branching" +src="module/induction/branching" +[[blocks]] +name="wrapping up Git" +src="module/induction/wrapping-up" +[[blocks]] +name="Using GitHub Dev to complete coursework on a library computer" +src="https://www.youtube.com/watch?v=qkEL0LaTc4k" +time=15 +[[blocks]] +name="backlog" +src="blocks/backlog" ++++ diff --git a/org-cyf-itp/content/onboarding/sprints/1/success/index.md b/org-cyf-itp/content/onboarding/sprints/1/success/index.md new file mode 100644 index 000000000..80de64748 --- /dev/null +++ b/org-cyf-itp/content/onboarding/sprints/1/success/index.md @@ -0,0 +1,9 @@ ++++ +title = 'success' +layout = 'success' +emoji= 'βœ…' +menu_level = ['sprint'] +weight = 4 +backlog= 'Module-HTML-CSS' +backlog_filter='πŸ“… Week 1' ++++ diff --git a/org-cyf-itp/content/onboarding/sprints/2/_index.md b/org-cyf-itp/content/onboarding/sprints/2/_index.md new file mode 100644 index 000000000..c5bdef8c4 --- /dev/null +++ b/org-cyf-itp/content/onboarding/sprints/2/_index.md @@ -0,0 +1,11 @@ ++++ +title = 'Sprint 2' +description = 'The plan for the week' +layout = 'sprint' +emoji= '⏱️' +menu_level = ['module'] +weight = 3 +theme = "Collecting and formatting data" ++++ + + diff --git a/org-cyf-itp/content/onboarding/sprints/2/backlog/index.md b/org-cyf-itp/content/onboarding/sprints/2/backlog/index.md new file mode 100644 index 000000000..cef86232f --- /dev/null +++ b/org-cyf-itp/content/onboarding/sprints/2/backlog/index.md @@ -0,0 +1,9 @@ ++++ +title = 'backlog' +layout = 'backlog' +emoji= '🏷️' +menu_level = ['sprint'] +weight = 2 +backlog= 'Module-Onboarding' +backlog_filter='πŸ“… Sprint 2' ++++ diff --git a/org-cyf-itp/content/onboarding/sprints/2/day-plan/index.md b/org-cyf-itp/content/onboarding/sprints/2/day-plan/index.md new file mode 100644 index 000000000..907422493 --- /dev/null +++ b/org-cyf-itp/content/onboarding/sprints/2/day-plan/index.md @@ -0,0 +1,56 @@ ++++ +title = 'day-plan' +layout = 'day-plan' +emoji= 'πŸ§‘πŸΎβ€πŸ€β€πŸ§‘πŸΎ' +menu_level = ['sprint'] +weight = 3 +[[blocks]] +name="Energiser" +src="energisers/wemoji" +[[blocks]] +name="Morning orientation" +src="blocks/morning-orientation" +time=15 +[[blocks]] +name="Workshop: Asking Questions" +src="https://github.com/CodeYourFuture/CYF-Workshops/tree/main/asking-questions/" +time="120" +[[blocks]] +name="Blockers! Getting Unstuck" +src="module/onboarding/blockers" +time=30 +[[blocks]] +name="lunch" +src="blocks/lunch" +[[blocks]] +name="Study Group" +src="module/onboarding/development" +time=75 +[[blocks.nested.blocks]] +name="Optional structured activity: Live Code Review" +src="blocks/mentored-code-review" +[[blocks.nested.blocks]] +name="Optional structured activity for consolidating Git" +src="https://github.com/CodeYourFuture/CYF-Workshops/tree/main/git-day-1" +time=0 +[[blocks]] +name="Code Review" +src="https://github.com/CodeYourFuture/Module-Onboarding/pulls" +time="0" +[[blocks]] +name="Afternoon break" +src="blocks/afternoon-break" +[[blocks]] +name="Study Group" +src="module/onboarding/development" +time=60 +[[blocks.nested.blocks]] +name="Optional structured activity for consolidating HTML forms" +src="https://github.com/CodeYourFuture/CYF-Workshops/tree/main/get-forms" +[[blocks.nested.blocks]] +name="Optional structured activity: Pair Programming" +src="module/onboarding/pairing" +[[blocks]] +name="Wrap" +src="module/onboarding/wrap" ++++ diff --git a/org-cyf-itp/content/onboarding/sprints/2/prep/index.md b/org-cyf-itp/content/onboarding/sprints/2/prep/index.md new file mode 100644 index 000000000..f470b6a79 --- /dev/null +++ b/org-cyf-itp/content/onboarding/sprints/2/prep/index.md @@ -0,0 +1,32 @@ ++++ +title = 'prep' +layout = 'prep' +emoji= 'πŸ§‘πŸΎβ€πŸ’»' +menu_level = ['sprint'] +weight = 1 +[[blocks]] +name="Forms in 25 minutes" +title="Form building" +src="https://www.youtube.com/watch?v=fNcJuPIZ2WE" +time=25 +[[blocks]] +name="How to structure a web form" +src="https://github.com/CodeYourFuture/Module-Onboarding/issues/71" +time=60 +[[blocks]] +name="Spaced Repetition" +src="blocks/spaced-repetition" +[[blocks]] +name="What are Forms" +src="module/html-css/what-are-forms" +[[blocks]] +name="Google Sheets Query Function Explained" +src="https://www.youtube.com/watch?v=oCKvAcXTLZo" +time=20 +[[blocks]] +name="Databases with Google Sheets" +src="module/databases/databases-with-sheets" +[[blocks]] +name="backlog" +src="blocks/backlog" ++++ diff --git a/org-cyf-itp/content/onboarding/sprints/2/success/index.md b/org-cyf-itp/content/onboarding/sprints/2/success/index.md new file mode 100644 index 000000000..4d03ccd8f --- /dev/null +++ b/org-cyf-itp/content/onboarding/sprints/2/success/index.md @@ -0,0 +1,9 @@ ++++ +title = 'success' +layout = 'success' +emoji= 'βœ…' +menu_level = ['sprint'] +weight = 4 +backlog= 'Module-HTML-CSS' +backlog_filter='πŸ“… Week 2' ++++ diff --git a/org-cyf-itp/content/onboarding/sprints/3/_index.md b/org-cyf-itp/content/onboarding/sprints/3/_index.md new file mode 100644 index 000000000..48ba0f430 --- /dev/null +++ b/org-cyf-itp/content/onboarding/sprints/3/_index.md @@ -0,0 +1,11 @@ ++++ +title = 'Sprint 3' +description = 'The plan for the week' +layout = 'sprint' +emoji= '⏱️' +menu_level = ['module'] +weight = 4 +theme = "Querying data, considering presentation" ++++ + + diff --git a/org-cyf-itp/content/onboarding/sprints/3/backlog/index.md b/org-cyf-itp/content/onboarding/sprints/3/backlog/index.md new file mode 100644 index 000000000..59ef304de --- /dev/null +++ b/org-cyf-itp/content/onboarding/sprints/3/backlog/index.md @@ -0,0 +1,9 @@ ++++ +title = 'backlog' +layout = 'backlog' +emoji= '🏷️' +menu_level = ['sprint'] +weight = 2 +backlog= 'Module-Onboarding' +backlog_filter='πŸ“… Sprint 3' ++++ diff --git a/org-cyf-itp/content/onboarding/sprints/3/day-plan/index.md b/org-cyf-itp/content/onboarding/sprints/3/day-plan/index.md new file mode 100644 index 000000000..b96196b6f --- /dev/null +++ b/org-cyf-itp/content/onboarding/sprints/3/day-plan/index.md @@ -0,0 +1,57 @@ ++++ +title = 'day-plan' +layout = 'day-plan' +emoji= 'πŸ§‘πŸΎβ€πŸ€β€πŸ§‘πŸΎ' +menu_level = ['sprint'] +weight = 3 +[[blocks]] +name="Energiser" +src="energisers/slack-libs" +[[blocks]] +name="Morning orientation" +src="blocks/morning-orientation" +time=15 +[[blocks]] +name="Workshop: Developer Tools" +src="https://github.com/CodeYourFuture/CYF-Workshops/tree/main/devtools/" +time="120" +[[blocks]] +name="Study Group" +src="module/onboarding/development" +time=30 +[[blocks.nested.blocks]] +name="Optional structured activity: Pair Programming" +src="module/onboarding/pairing" +[[blocks.nested.blocks]] +name="Optional structured activity: Submit your Step" +src="module/onboarding/steps" +[[blocks]] +name="lunch" +src="blocks/lunch" +[[blocks]] +name="Blockers! Getting Unstuck" +src="module/onboarding/blockers" +time=45 +[[blocks]] +name="Afternoon break" +src="blocks/afternoon-break" +[[blocks]] +name="Study Group" +src="module/onboarding/development" +time=90 +[[blocks.nested.blocks]] +name="Optional structured activity: consolidating SQL" +src="https://github.com/CodeYourFuture/CYF-Workshops/tree/main/google-sheets-sql-quiz" +time=0 +[[blocks.nested.blocks]] +name="Optional structured activity: know your computer" +src="https://github.com/CodeYourFuture/CYF-Workshops/tree/main/know-your-computer" +time=0 +[[blocks]] +name="Code Review" +src="https://github.com/CodeYourFuture/Module-Onboarding/pulls" +time="0" +[[blocks]] +name="Wrap" +src="module/onboarding/wrap" ++++ diff --git a/org-cyf-itp/content/onboarding/sprints/3/prep/index.md b/org-cyf-itp/content/onboarding/sprints/3/prep/index.md new file mode 100644 index 000000000..0170b468c --- /dev/null +++ b/org-cyf-itp/content/onboarding/sprints/3/prep/index.md @@ -0,0 +1,19 @@ ++++ +title = 'prep' +layout = 'prep' +emoji= 'πŸ§‘πŸΎβ€πŸ’»' +menu_level = ['sprint'] +weight = 1 +[[blocks]] +name="Enroll as a Trainee" +src="https://github.com/CodeYourFuture/Module-Onboarding/issues/72" +time=30 +[[blocks]] +name="Record a Goose" +title="Accessibility audit" +src="https://github.com/CodeYourFuture/Project-Record-A-Goose/" +time=180 +[[blocks]] +name="backlog" +src="blocks/backlog" ++++ diff --git a/org-cyf-itp/content/onboarding/sprints/3/success/index.md b/org-cyf-itp/content/onboarding/sprints/3/success/index.md new file mode 100644 index 000000000..617668fa0 --- /dev/null +++ b/org-cyf-itp/content/onboarding/sprints/3/success/index.md @@ -0,0 +1,9 @@ ++++ +title = 'success' +layout = 'success' +emoji= 'βœ…' +menu_level = ['sprint'] +weight = 4 +backlog= 'Module-HTML-CSS' +backlog_filter='πŸ“… Week 3' ++++ diff --git a/org-cyf-itp/content/onboarding/success/index.md b/org-cyf-itp/content/onboarding/success/index.md new file mode 100644 index 000000000..3152d5f20 --- /dev/null +++ b/org-cyf-itp/content/onboarding/success/index.md @@ -0,0 +1,40 @@ ++++ +title = 'success' +description = 'How do we know we have completed Onboarding?' +layout = 'success' +emoji= 'βœ…' +menu_level = ['module'] +weight = 11 +[[objectives]] +1="Link to your PR for [Wireframe to Web Code](https://github.com/CodeYourFuture/Module-User-Focused-Data/issues/90)" +2="Link to your PR for [Form Controls](https://github.com/CodeYourFuture/Module-User-Focused-Data/issues/88)" ++++ + +> 🎯 Complete onboarding and [apply to enroll as a Trainee](https://forms.gle/vRuofa7aeL5DsbhGA) + +### 🎯 You've achieved your learning objectives if you can: + +```objectives +- Explain to someone how we use prep, backlogs, day plans, and success pages at {{}}. +- Track changes to data (your code) over time with Git and GitHub. +- Validate data with HTML forms. +- Analyse structured data with SQL in a spreadsheet. +- Plan your new life as a tech professional. +``` + +### πŸ’― To complete _any_ module, you must: + +```objectives +- Do your work: complete all mandatory backlog issues +- Come to class +- **Submit** the step for this module +``` + +## βœ… To complete _this_ module, you must: + +1. Make a new issue on your own Coursework Planner. +1. Link to the two Pull Requests on your issue. You don't have to wait for your PRs to be reviewed, but you must have made them. +1. Submit the issue link to step 1 of ITP on [CYF Course Portal](https://application-process.codeyourfuture.io/). +1. [Apply to enroll as a Trainee](https://forms.gle/vRuofa7aeL5DsbhGA). + +Here are those PRs again: diff --git a/org-cyf-itp/content/structuring-data/_index.md b/org-cyf-itp/content/structuring-data/_index.md index c5889d837..6a32be16f 100644 --- a/org-cyf-itp/content/structuring-data/_index.md +++ b/org-cyf-itp/content/structuring-data/_index.md @@ -3,6 +3,6 @@ title = 'Structuring and testing data' description = 'Find meaning behind syntax; Step through functions like a computer; Break problems down into sub-problems; Interpret acceptance criteria to form test cases; Recognise patterns' layout = 'module' emoji= 'πŸ₯š' -menu = ['syllabus', 'core', 'programming'] +menu = ['syllabus','course schedule'] weight='3' +++ diff --git a/org-cyf-itp/content/user-data/_index.md b/org-cyf-itp/content/user-data/_index.md index b58ca78ea..482d9e919 100644 --- a/org-cyf-itp/content/user-data/_index.md +++ b/org-cyf-itp/content/user-data/_index.md @@ -1,8 +1,10 @@ +++ -title = 'User focused data' -description = 'User focused data: Build up robust interfaces by structuring data and interactions; analyse and interrogate code with tools; decompose interfaces into components; recognise patterns' +title = '[ARCHIVED 2024] User focused data' +description = 'This module has been archived and replaced by the Onboarding module.' layout = 'module' emoji= 'πŸ“‡' -menu = ['syllabus', 'core', 'programming'] -weight='2' +[build] + render = false + publishResources = false + list = 'never' +++ diff --git a/org-cyf-itp/content/welcome/_index.md b/org-cyf-itp/content/welcome/_index.md new file mode 100644 index 000000000..276571e1b --- /dev/null +++ b/org-cyf-itp/content/welcome/_index.md @@ -0,0 +1,8 @@ ++++ +title = 'Welcome to Code Your Future' +description = 'Our first day together ' +layout = 'module' +emoji= '🫢🏽' +menu = ['syllabus', 'course schedule'] +weight='1' ++++ diff --git a/org-cyf-itp/content/welcome/day-plan/index.md b/org-cyf-itp/content/welcome/day-plan/index.md new file mode 100644 index 000000000..e0f80ebf6 --- /dev/null +++ b/org-cyf-itp/content/welcome/day-plan/index.md @@ -0,0 +1,54 @@ ++++ +title = 'day plan' +layout = 'day-plan' +description='The agenda and activities for our first day together' +emoji= 'πŸ§‘πŸΎβ€πŸ€β€πŸ§‘πŸΎ' +menu_level = ['module'] +weight = 3 +[[blocks]] +name="Energiser" +src="energisers/in-person-and-online" +[[blocks.nested.blocks]] +name="Zip Zap Boing" +src="energisers/zip-zap-boing" +time=0 +[[blocks.nested.blocks]] +name="Popcorn Show and Tell" +src="energisers/popcorn" +time=0 +[[blocks]] +name="Morning orientation" +src="blocks/morning-orientation" +time=15 +[[blocks]] +name="Welcome to Code Your Future" +src="https://www.youtube.com/watch?v=QBfhPkBW9Pk" +time=5 +[[blocks]] +name="Workshop" +src="module/induction/learning-as-community" +[[blocks]] +name="Morning break" +src="blocks/morning-break" +[[blocks]] +name="Traffic Jam" +src="energisers/blockers" +time=60 +[[blocks]] +name="lunch" +src="blocks/lunch" +[[blocks]] +name="Blockers! Getting Unstuck" +src="module/onboarding/blockers" +time=75 +[[blocks]] +name="Afternoon break" +src="blocks/afternoon-break" +[[blocks]] +name="Next Steps" +src="module/fundamentals/next-steps" +time=45 +[[blocks]] +name="Wrap" +src="blocks/wrap" ++++ diff --git a/org-cyf-itp/content/welcome/prep/index.md b/org-cyf-itp/content/welcome/prep/index.md new file mode 100644 index 000000000..1094aa7b1 --- /dev/null +++ b/org-cyf-itp/content/welcome/prep/index.md @@ -0,0 +1,29 @@ ++++ +title = 'Prep' +description = 'What to do before you come to class' +layout = 'prep' +emoji= 'πŸ§‘πŸΎβ€πŸ’»' +menu_level = ['module'] +weight = 1 +[[blocks]] +name="Application" +src="module/onboarding/application" +[[blocks]] +name="Goals" +src="module/onboarding/goals" +[[blocks]] +name="Expectations" +src="module/onboarding/expectations" +[[blocks]] +name="Help" +src="module/onboarding/help" +[[blocks]] +name="Preparation" +src="module/onboarding/preparation" +[[blocks]] +name="Professional Accounts" +src="module/induction/accounts" +[[blocks]] +name="House Rules" +src="blocks/house-rules" ++++ diff --git a/org-cyf-itp/content/welcome/success/index.md b/org-cyf-itp/content/welcome/success/index.md new file mode 100644 index 000000000..90423744c --- /dev/null +++ b/org-cyf-itp/content/welcome/success/index.md @@ -0,0 +1,14 @@ ++++ +title = 'success' +description = 'How do we know we have completed day one successfully?' +layout = 'success' +emoji= 'βœ…' +menu_level = ['module'] +weight = 11 +[[objectives]] +1="Come to class in person or online if you cannot travel" +2="Name 5 people in your class" +3="Find and begin your prep for the Onboarding Module" ++++ + +### 🎯 You've achieved your learning objectives if you can: