π§πΎβπ»
Prep
Lays out the prep / textbook view for a sprint
Prep
Block composition
Prep views are the textbooks of the course.
As with all views, compose the page with blocks in the front matter. Some examples are given here. The blocks can be any of the types available in the common-docs theme. If you need a new block type, please raise an issue in the curriculum repo. It’s pretty simple to make them to be honest, so if it’s a good idea and needed we will probably get it done.
Each block is shown as a solo view and the learner can step through in a structured learning path. We use a flipped classroom method to maximise the time in class for questions and practical exercises.
Right and left arrow will page through the blocks, as will swipe and button click. The learner can also click on the block name to jump to a specific block, and you can link directly to any block with hash links.
We probably have a maximum time of around 3 hours for a prep view, and then we typically move learners into projects on their backlog.
This layout in other contexts
The default view for this page is the first item in a sprint.
You can also, and we strongly recommend, add a prep view to an entire module, and put all the setup work in there. Anything that needs to happen before the entire module can begin should go there, including stuff like application forms, agreements, account signups, and so on.
You can turn any page into a prep view by setting the layout to prep
and adding blocks.
π Readme
TEMPLATE repo for Modules
Tasks
- Set up example board https://github.com/orgs/CodeYourFuture/projects/126/ and turn on auto-add
- Populate repo with coursework issues, updating fields and board plan
- Check coursework time does not exceed 20 hours per sprint/week
- Add core Actions from org store https://docs.github.com/en/actions/creating-actions/sharing-actions-and-workflows-with-your-organization
Youtube: Youtube video or playlist
ποΈ Code waiting for review π
Below are trainee coursework Pull Requests that need to be reviewed by volunteers.
|Deborah Gamedze| Modulejs1 | Week3 π
Subject: Pull Request Review Request
Hi Sergey,
I hope you are doing well. I have submitted my pull request for review. I would appreciate it if you could take a look at it when you have the time.
I want to mention that I tried to solve the problem by myself first, and I did some research online for additional insights. This practice has been really helpful for me in deepening my understanding.
Thank you for your guidance and support!
Start a reviewFeature/week 3 exercises π
Questions
Understanding Assertions Iβm a bit confused about writing assertions in JavaScript. Could you explain why we use them in code and how they are beneficial?
Seeking Help Online I used Google to solve these problems. It was helpful.
Function Retention When I learn a new function, I understand it in the moment, but I often forget it when a similar problem comes up again. Do you have any tips for better retention of functions Iβve already used?
Start a reviewFabio Medina D/RicardoMedina/Paths/week1 π
Learners, PR Template
Self checklist
- I have committed my files one by one, on purpose, and for a reason
- I have titled my PR with COHORT_NAME | FIRST_NAME LAST_NAME | REPO_NAME | WEEK
- I have tested my changes
- My changes follow the style guide
- My changes meet the requirements of this task
Changelist
Briefly explain your PR.
Questions
Ask any questions you have for your reviewer.
Start a review