14 parts · 29 chapters

Frontend Terms, Visualised

Every field has a vocabulary, and most of the confusion in a frontend conversation is two people using one word for different things, or two words for one thing. This module is the vocabulary: each term with a diagram, a one-line meaning, where you meet it in practice, and a link into the course that explains the mechanism. Read it as a reference, not a course: search the index, jump to a card, follow the link when the one line is not enough.

Thirteen layers, in the order a page is built and a product is run: network, parsing, style, layout, paint and compositing, the runtime, React, build, testing, performance, accessibility, security, and architecture. Each layer opens with an animated map of its terms in pipeline order, so the cards sit in the place they belong rather than in an alphabetical pile.

a reference · every term a diagram, a meaning, where it shows up, and the course that goes deepevery level · a reference to search, not a course to read in order
a diagram per termEvery card has a small drawing of the mechanism: a flow, a stack, a timeline, a comparison, a tree.
one-line meaningsThe definition you could say out loud in a review, without the hedge words.
where it shows upThe place in practice you will meet it: a DevTools panel, a header, a bug, a review comment.
deep linksEach card links to the course part that explains the mechanism in full.
layer mapsAn animated pipeline per layer, so the terms sit where they belong.
an indexEvery term A to Z by layer, one click to its card.
A companion to every other courseEach card is a pointer into the Browser, JavaScript, React, Architecture, Design, Disciplines and other courses. Use it as the glossary when a term in another course is unfamiliar, and as revision when it is not.