Part 0 · 3 chapters · ~5 min

How to Use, and the Index

A reference of 312 frontend terms across thirteen layers. What a card holds, how the layers fit together, and an index by layer and A to Z with a live filter.

1

How to use this module

This is a reference, not a course. It has 312 terms in thirteen layers, and each term gets one card:

what a card holds
  1. A diagram of the mechanism: a flow, a stack, a timeline, a comparison, a tree, a sequence or a snippet. If you can redraw it from memory, you can explain the term.
  2. A one-line meaning you could say out loud in a design review.
  3. In practice: where you will meet the term, such as a DevTools panel, a header, a bug report or a review comment.
  4. Deep dive: links into the course part that explains the mechanism in full.

Each layer opens with an animated map that places its terms in pipeline order. The map below does the same for the layers themselves. Every card has its own anchor, so you can link a teammate straight to part-06-runtime.html#t-microtask.

a revision drill
Open a layer, cover the meaning under each diagram, and say what the diagram shows. Any card you cannot explain from its drawing is the next deep-dive link to follow.
THIRTEEN LAYERS, ONE PIPELINE
the order a page is fetched, built, run, shipped and held to account, and where each layer of terms lives
swipe the figure sideways, or tap expand for full screen
1/6
arrive
Arrive: bytes come over the network and are parsed into a DOM and running scripts.
2

Index by layer

Every term, grouped by layer in the order the module presents them. Type to filter.

3

A to Z

The same terms in alphabetical order, each tagged with its layer. The filter above also filters this list.

KKeys P7
XXSS P12