Examples, exercises and guides for the Workflows module
You will need NPM installed on your computer to study this material
- Clone this repository:
- using SSH:
git clone [email protected]:HackYourFutureBelgium/workflows.git
- using SSH:
- navigate to the cloned repository
cd workflows
- Install dependencies:
npm install
- 🥚 ./guides: This folder contains short videos showing how to do many of the little skills and habits you need to learn in this module. Things like inspecting an element in the DOM, navigating a folder system from the Command Line Interface, and creating a new branch with Git.
- 🥚 ./file-extensions: Some guidance and exercises for recognizing the different languages you will learn at HYF. You will need to figure out what language is written in each file and add the correct file extension.
- 🥚 ./markdown: A few example files showing different formatting options available in Markdown.
- 🥚 ./project-starter: Starter materials for the HTML+CSS group project - backlog, wireframe, development strategy, code
expand/collapse
- Don't rush, understand! Programming is hard.
- The examples and exercises will still be there to study later.
- It's better to fail tests slowly and learn from your mistakes than to pass tests quickly and not understand why.
- Don't skip the examples! Understanding and experimenting with working code is a very effective way to learn programming.
- Write lots of comments in the examples and exercises. The code in this repository is yours to study, modify and re-use in projects.
- Practice Pair Programming: two people, one computer.
- Take a look through the Learning From Code guide for more study tips
If you can't finish all the material in this repository, that's expected! Anything you don't finish now will always be waiting for you to review when you need it. These 4 emoji's will help you prioritize your study time and to measure your progress:
- 🥚: Understanding this material is required, it covers the base skills you'll need for this module and the next. You do not need to finish all of them but should feel comfortable that you could with enough time.
- 🐣: You have started all of these exercises and feel you could complete them all if you just had more time. It may not be easy for you but with effort you can make it through.
- 🐥: You have studied the examples and started some exercises if you had time. You should have a big-picture understanding of these concepts/skills, but may not be confident completing the exercises.
- 🐔: These concepts or skills are not necessary but are related to this module. If you are finished with 🥚, 🐣 and 🐥 you can use the 🐔 exercises to push yourself without getting distracted from the module's main objectives.
There's so many examples and exercises in this repository, it's easy to forget of what you still need to finish or what you want to review again. Luckily VSCode is really good at searching through folders of code.
You can write hashtags in your comments while you're studying, then search for those hashtags later so you don't miss anything. Here's some ideas:
// #not-done, still a few blanks left- search for#not-donein VScode to find all the exercises you've started and not finished// coercion is confusing, #review this again next week- search for#reviewto find the files you need to study again- ... anything goes! Find the hashtags that work for you
Creating a project board on your GitHub account for tracking your study at HYF
can help you keep track of everything you're learning. You can create the board
at this link: https://github.com/your_user_name?tab=projects.
These 4 columns may be helpful:
- todo: material you have not studied yet
- studying: material you are currently studying
- to review: material you want to review again in the future
- learned: material you know well enough that you could help your classmates learn it
expand/collapse
This repository comes with some scripts to check the quality of this code. You can run these scripts to check the code provided by HYF, and to check the code you write when experiment with the examples and complete the exercises.
This script will format all of the code in this repository making sure that all the indentations are correct, the code is easy to read, and letting you know if there are any syntax errors.
This script will check all of the files in your repository for spelling mistakes. Spelling is not just a detail, is important! Good spelling helps others read and understand your programs with less effort.
spell-check is not so clever though, it doesn't have all possible words in
it's dictionary and it won't know if you wanted to spell a word incorrectly.
If you think one of it's "Unknown word"s is not a problem, you can either ignore
the suggestion or add the word to the "words": [ ... ], list in
.cspell.json.
This script will lint all the Markdown files in this repository, checking for syntax mistakes and other bad practices. Fixing linting errors will help you learn to write better code by pointing out your mistakes before they cause problems in your program.
Some linting errors will take some practice to understand and fix, but it will be a good use of time.
Just like lint:md, but for .css files. This script will lint all of the CSS
files in this repository, letting you know if there are any syntax errors or bad
practices.
Validating HTML is sort of like linting, but a little more involved. When you validate an HTML file the script will not only check the source code, but actually open the file in a headless browser and check the website for mistakes.
You can think of a headless browser as a normal browser, but one where you can't see the web page. They're generally used for testing and validation when it's not important that a user can interact directly with the web page