Part I — From Your Editor to the Internet
Build tools, package managers and the supply chain, Git and CI, continuous delivery, DNS/TCP/TLS/HTTP, CDNs and caching, and where HTML should be made.
“A lot of devs learn coding and start building and keep on building, but leave these ‘glue’ things, which make the whole experience stick and are what separate good from the best.”
This book is about that glue. It’s written for a frontend engineer with a few years of shipping behind her — strong in React and CSS, a designer’s eye for how things feel — who wants to understand every hop between her editor and her users’ eyes well enough to explain it on a whiteboard, make the call in a design review, and defend it to leadership.
Part I — From Your Editor to the Internet
Build tools, package managers and the supply chain, Git and CI, continuous delivery, DNS/TCP/TLS/HTTP, CDNs and caching, and where HTML should be made.
Part II — Inside the Browser
Processes and threads, the critical rendering path, frames and jank (the deepest chapter), the event loop, storage, security, browser APIs and accessibility.
Part III — Performance, Measured
Every metric and what it means, a real audit decoded row by row, real devices and networks, and an optimization playbook with before/after numbers.
Parts IV–V — Motion, Graphics, Found, Observed
Animation that feels right, the GPU from Canvas to WebGL to WebGPU, SEO plumbing, observability, and thinking like a staff engineer.
Every chapter opens with a story that builds the mental model before the jargon arrives, then walks the same arc: what it is, why it exists, the world without it, how it works (with hand-drawn SVG diagrams that work in light and dark mode), how to do it, the best way and when “best practice” is wrong, real incidents, a 🧑🏫 Whiteboard Version, a self-quiz, and exercises in three tiers — warm-ups, hands-on labs on a running project called Lumen, and staff-level challenges — with collapsible solutions.
Interactive demos (the main thread vs. the compositor, layout thrashing, live blur cost with an FPS meter, a frame-budget calculator, LCP sub-parts, layout shifts, easing and springs, raw WebGL) load only when you scroll to them, and each has a plain-text fallback.
This edition was written as a conceptual explainer, primarily from the author’s knowledge as of late 2026. Mechanisms and principles are stated with care; incident details are told for their lessons with approximate figures; and browser support for fast-moving APIs changes quickly — check MDN, caniuse or Baseline before relying on a specific version number. See the Colophon for how the book was made.