▲ Next.js

The page in front of the query — routing by folder, the server/client boundary that decides where your query runs, streaming a report whose slow section is still loading, tables and filters in the URL, charts aggregated server-side, and an honest first episode on when a BI tool is the better answer.

No lessons published yet — this is the roadmap, so you can see exactly what the course will cover before it lands.

Before you start: Learn SQL — Series 1, and Series 2. Every screen in this track is a query with a page around it. You need to be able to write the aggregate and the join yourself, because the interesting problems here — pagination, filters, a chart's dataset — are query problems wearing a user interface.

Short on time? The 19 episodes marked core are the shortest path to being productive at work. Start there and pick up the rest whenever a job asks for them.

Series 1 · Pages, and the Line Between Server and Browser

routing by folder, and the one distinction everything else depends on

01
A Page in Front of a Query — What This Buys Over a BI Dashboard, and When It Does Not
coreintermediatecoming soon
02
Folders Are Routes — page, layout, loading and the Files With Meanings
coreintermediatecoming soon
03
Server by Default — the Boundary That Decides Where Your Query Runs
coreintermediatecoming soon
04
Metadata, CSS, Fonts and Images — the Page Furniture, in One Pass
intermediatecoming soon
05
Project — One Page, One Query, Rendered on the Server
coreintermediate#projectcoming soon

Series 2 · Getting the Data In and Out

fetching, caching, mutating — and the part that changes between versions

01
async Components — Awaiting Data With No Hook, and the Waterfall to Avoid
coreadvancedcoming soon
02
The Connection — One Pool, Server-Only, and Not Caching a Query You Should Fix
coreadvancedcoming soon
03
Caching Is a Promise About Staleness — Deciding How Old an Answer May Be
coreadvancedcoming soon
04
Streaming and Suspense — Sending the Page Before the Slow Query Finishes
coreadvancedcoming soon
05
Server Actions — a Public Endpoint That Looks Like a Function Call
coreadvancedcoming soon
06
Route Handlers — When You Actually Need an API, and Streaming a Large Export
advancedcoming soon
07
Project — A Report That Streams Its Slow Section and Refreshes on Demand
coreadvanced#projectcoming soon

Series 3 · The Screens Data People Actually Build

tables, filters, charts and who is allowed to see them

01
A Table Over a Real Dataset — Paging in the Query, Not in the Browser
coreadvancedcoming soon
02
Filters in the URL — a View You Can Send Someone, and the Sort Column You Must Not Interpolate
coreadvancedcoming soon
03
Charts — Aggregate on the Server, Draw on the Client, Ship a Hundred Points
coreadvancedcoming soon
04
Who May See This — Checking Beside the Query, Not in the Layout
coreadvancedcoming soon
05
Export to CSV and Excel — the BOM, the Delimiter, and the ID Excel Turned Into 1.2E+15
advancedcoming soon
06
Project — A Filterable Table, a Chart and an Export, Behind a Login
coreadvanced#projectcoming soon

Series 4 · Shipping It

what the build produced, where it can run, and keeping up

01
Static or Per-Request — Reading the Build Output Before You Wonder Why Numbers Froze
coreadvancedcoming soon
02
Environment Variables — the Prefix That Puts a Secret in the Browser Bundle Forever
coreadvancedcoming soon
03
Managed, Node or a Container — and the Database That Is Not on the Internet
coreadvancedcoming soon
04
Where the Time Went — Query First, Payload Second, Framework Last
advancedcoming soon
05
Upgrading — the Cadence, the Codemods, and Reading the Guide Before the Release Notes
advancedcoming soon
06
Project — Deploy the Internal Tool Where It Can Reach the Database
coreadvanced#projectcoming soon

Not here, on purpose

Writing the queries behind the screens — covered in Learn SQL. In this course, Series 2 · 05 covers only how a query is called from a page and where the connection lives
Choosing the right chart, and whether it tells the truth — covered in BI & Data Visualization, Series 1. This course renders the chart you already decided on
JavaScript and TypeScript themselves, and React fundamentals — not covered; they are assumed. A reader who has never written a component should learn React first — this track teaches the framework around it
The Pages Router — not covered, deliberately. Named once in Series 1 · 00 so a reader recognises it in existing code, and never taught
Hosting, containers and the machine it runs on — covered in Data Ops, and Kubernetes for Data Workloads if it lands on a cluster. In this course, Series 4 · 10 covers only what the build output requires

▲ Next.js

Series 1 · Pages, and the Line Between Server and Browser

A Page in Front of a Query — What This Buys Over a BI Dashboard, and When It Does Not

Folders Are Routes — page, layout, loading and the Files With Meanings

Server by Default — the Boundary That Decides Where Your Query Runs

Metadata, CSS, Fonts and Images — the Page Furniture, in One Pass

Project — One Page, One Query, Rendered on the Server

Series 2 · Getting the Data In and Out

async Components — Awaiting Data With No Hook, and the Waterfall to Avoid

The Connection — One Pool, Server-Only, and Not Caching a Query You Should Fix

Caching Is a Promise About Staleness — Deciding How Old an Answer May Be

Streaming and Suspense — Sending the Page Before the Slow Query Finishes

Server Actions — a Public Endpoint That Looks Like a Function Call

Route Handlers — When You Actually Need an API, and Streaming a Large Export

Project — A Report That Streams Its Slow Section and Refreshes on Demand

Series 3 · The Screens Data People Actually Build

A Table Over a Real Dataset — Paging in the Query, Not in the Browser

Filters in the URL — a View You Can Send Someone, and the Sort Column You Must Not Interpolate

Charts — Aggregate on the Server, Draw on the Client, Ship a Hundred Points

Who May See This — Checking Beside the Query, Not in the Layout

Export to CSV and Excel — the BOM, the Delimiter, and the ID Excel Turned Into 1.2E+15

Project — A Filterable Table, a Chart and an Export, Behind a Login

Series 4 · Shipping It

Static or Per-Request — Reading the Build Output Before You Wonder Why Numbers Froze

Environment Variables — the Prefix That Puts a Secret in the Browser Bundle Forever

Managed, Node or a Container — and the Database That Is Not on the Internet

Where the Time Went — Query First, Payload Second, Framework Last

Upgrading — the Cadence, the Codemods, and Reading the Guide Before the Release Notes

Project — Deploy the Internal Tool Where It Can Reach the Database

Not here, on purpose