01
Plain words first
Every term is explained the first time it appears, in ordinary English. If a lesson needs jargon, it earns it: you hear what it means before you are expected to use it.
~/web-learning/about
Courses for people who learn after the day job
Most people who want to build for the web are not full-time students. They run a shop, look after children, work shifts or answer to a manager, and the hour they have is at nine in the evening, not nine in the morning.
Web-Learning makes recorded courses for that hour. Every lesson is a short video you can stop, rewind and come back to, with the code typed on screen and the result shown in a browser next to it. You work through it in your own editor at your own pace, for 18 months from the day you get access.
honest.md
What a recording can do, and what it cannot
We would rather say this before you buy than after. A good recording is patient: it never minds being played five times. It is also deaf: it cannot see your screen or answer the question you have at the moment you have it.
/* a recording can */
- show every keystroke, including the mistakes
- go at your speed, paused as often as you need
- put the topics in an order that builds
- show the finished answer to every exercise
/* it cannot */
- look at your code or mark it
- replace a tutor or a mentor
- give you a certificate or a qualification
- find you a job or promise one
If what you need is feedback from a person on your own code, a recorded course is the wrong tool and we would rather you knew. If you need a clear route and time to practise, read on. Questions before buying go to contact.
git log --oneline
How a course is made
- a1
Start from a problem
Each course begins with one sentence a learner might say, the kind of thing printed on every course page. Everything in the course has to help with that sentence.
- b2
Write it before recording it
The units, the exercises and the finished code are written first, then built from an empty file to check the order makes sense to someone starting cold.
- c3
Record with the code on screen
Lessons are kept short. The editor and the browser are both visible, so you see the cause and the effect in the same frame.
- d4
Re-record when tools change
Browsers and tools move on. When a lesson no longer matches what you will see on your own screen, it is redone. Each course page lists exactly what the course covers.
principles.css
Four things we hold to
02
You type it yourself
Watching is not learning. Each unit ends with an exercise you write in your own editor before the answer is shown, because the mistakes you make are the useful part.
03
No hype, no invented numbers
You will not find student counts, ratings or salary promises here. The only figures on this site come from the courses themselves.
04
Accessible by default
Keyboard use, contrast and screen readers are part of how pages are built in every course, not a separate chapter at the end.
ls ~/courses | wc -l
On the shelves today
The figures the catalogue itself gives, nothing added.
- Courses
- 13
- Tracks
- 3
- Lessons across the courses
- 486
- Video across the courses
- 95 h 5 min