👋 Start Here
Welcome! Give this page 5 minutes and you’ll know exactly how to get the most out of this course.
First, three promises
- You are not “too non-technical” for this. This course assumes nothing. Not even what a file is. Every term is explained the moment it appears.
- Confusion is our bug, not yours. If a page loses you, the page is broken. (Truly — we track it: see the Contributing guide.)
- You will build real things. Not toy examples — by the end you’ll have code and a live website you made yourself.
What you need
| Thing | Details |
|---|---|
| A device with a web browser | A phone works. A cheap laptop is more comfortable. Nothing fancy. |
| A free GitHub account | You’ll create it in Module 08. It’s the only sign-up we’ll ever ask for. |
| Time | About 2–4 hours per module, at your own pace. There is no deadline and no falling behind. |
That’s it. You never need to install anything. Every hands-on lab runs inside your web browser using free tools.
How each module works
Every module is a folder with four short files:
- The lesson (
README.md) — read this first. It’s written like a friend explaining over coffee, full of analogies. ☕ - The lab (
lab.md) — do this second. Hands-on, step by step, in your browser. Doing is where the learning actually sticks. - The quiz (
quiz.md) — check yourself. Answers are included (click “Show answer”). The last question is always “explain it to a friend” — if you can do that, you own the idea. - Extra resources (
resources.md) — optional. Free videos and interactive sites if you want more.
The golden rules of learning this stuff
- Go in order. Each module builds on the previous ones. Skipping ahead is how courses start feeling “too hard”. (Exception: the Learning Paths page offers safe shortcuts for specific goals.)
- Do every lab. Reading about swimming doesn’t teach you to swim. The labs are short on purpose — never skip them.
- Say the answers out loud. The “explain it to a friend” questions work best if you literally explain it to a friend, a pet, or a rubber duck. (Engineers really do this. It’s called rubber duck debugging — you’ll learn about it in Module 09.)
- It’s normal to forget. You’ll re-look-up terms constantly. That’s what the Glossary is for. Professionals google basic things every single day.
- Take breaks between modules. Your brain files things away while you rest. One module a day is a great pace. One a week still finishes the course in under five months.
Suggested schedules
| Your situation | Plan |
|---|---|
| “I’m in no rush” | 1–2 modules per week → done in ~3 months, deeply understood |
| “I have a free month” | 1 module per weekday → done in a month |
| “I need specific knowledge fast” | Use a Learning Path — e.g. Manager Track is 7 modules |
A note on the labs and links
Every lab uses free, no-install, browser-based tools, and every module lists external resources (videos, interactive sites). The internet changes; if a link is dead or a tool changed its buttons, please tell us — and meanwhile, searching the tool’s name will almost always find the new location.
Ready?
Take a breath. You’re about to understand the machinery behind the modern world.