The map
- Not started
- In progress
- Done
- Builds on
- 01The languageHow JavaScript runs and waits0/6
- 02The browserPixels, events, layout, access0/4
- 03The network and the userCaching, security, rendering, speed0/4
- 04Shipping with confidenceWhat to test, and in a real browser0/3
- 05Next: system designSame ideas, at service scale
- CDN and edge cachingLibrary ↗Hashed assets, cached HTML and streamed pages all end up at a CDN. This is how the edge stores, revalidates and purges them.
- Backend for frontendLibrary ↗A backend shaped for one frontend: fewer round trips, payloads that match the screen, and a place to keep secrets out of the browser.
- Feature flagsLibrary ↗Ship the code dark, turn it on for a few users, watch the Web Vitals and errors, then roll out or back without a deploy.
The first stage is shared with the JavaScript path, the last with QA automation; progress on shared topics counts on every map they appear on. The web topics are framework-neutral: what you learn about rendering, events and caching applies whether you use React, Vue, Svelte or none.