Frontend Development
The highest Layer-3 density on the map. Most of what looks foundational here churns on a 2–5 year cycle, and the durable part is the browser underneath it.
Clusters
Section titled “Clusters”Core web platform
Single-member in practice: there is one web platform and no substitute. Everything above it is a wrapper and every wrapper’s debugging eventually…
UI frameworks
The reactive, component-based, unidirectional-data-flow model transfers across React, Vue, Svelte and Solid — but only if learned as that model…
Meta-frameworks
File-system routing, the server/client boundary, per-route data loading and build-output shape transfer across all of them. Rendering-mode names and…
Static sites & docs
The build-time pipeline — content source, frontmatter schema, render, static output — plus file-system routing and incremental-build behaviour…
Styling
The cascade, specificity, the box model and layout algorithms transfer across every member and are Layer 1. Utility conventions, nesting syntax and…
Component libraries
Accessible component semantics — focus management, ARIA roles, keyboard interaction — transfer across all of them and are Layer 1 knowledge in…
State management
The split between server state and client state is the durable idea and transfers everywhere. Store APIs do not. TanStack Query and Redux answer…
Build tooling
Module graph, code splitting, tree shaking and the dev-server/HMR model transfer across all of them. Config schemas and plugin APIs are Layer 4 and…
Runtimes & package managers
Resolution algorithm, lockfile semantics and the node_modules layout transfer. CLI flags and workspace key names do not, and change between majors of…
Frontend testing
The test pyramid and what belongs at each level is Layer 1 and transfers completely. Runner APIs, selectors and mocking syntax do not.
Advanced topics
Accessibility and performance are Layer 1 platform knowledge that outlives every framework here. WebAssembly and PWA APIs are Layer 3.