How we make a course
Every Lexington course starts as a real project a teacher shipped. Here's how it becomes four lessons.
- Written by
- Ingrid Halvorsen
- Published
- 12 July 2026
- Reading time
- 1 min read
People sometimes assume our courses are scripted in a studio. They’re not. Every one starts with a project the teacher actually shipped, at work or for a client, and works backwards from there.
One project, four lessons
We ask each teacher a single question: what would you want to know if you had to build this again from zero? The answers become the lessons. Anything that doesn’t serve the final project gets cut, however interesting it is.
Short on purpose
Most lessons run between fifteen and thirty minutes. Long enough to finish something, short enough to watch on a lunch break. If a lesson needs more time, it probably needs splitting.
Recorded, then rewatched
Before a course goes live, someone from the target audience takes it from start to finish and tells us where they got lost. We re-record those parts. It’s slow, and it’s the reason people finish our courses.
Keep reading.
· 2 min read
Why we teach Astro before React
Most beginners don't need a JavaScript framework. They need a page on the internet, and Astro gets them there faster.
Marco Bellini
· 2 min read
Auto layout is a shelf, not a spreadsheet
The mental model that finally makes Figma's auto layout click, and why it makes handoff easier too.
Ingrid Halvorsen
· 1 min read
The query behind every dashboard
Most product dashboards are the same four lines of SQL. Learn them once and you can check any number yourself.
Lucía Moreno