A verified reference corpus
Every claim traces to official docs, framework source, or a measurement someone ran. Code is extracted from demos that build, not typed into a code fence. CI fails when the two drift apart.
181
Articles
289
Cross-links
4
Corpora
44
Unresolved
The corpora
All articles →Caching, the server boundary, and the route tree
What Cache Components changed, and which of the old mental models still hold.
Rendering, state, and the escape hatches
Concept articles paired with symptom-first recipes drawn from real failures.
Signals, DI, and the component lifecycle
The framework's own primitives, read against its source rather than its tutorials.
The request lifecycle and the module graph
Where a request actually goes, and which decorator runs when.
Three ways in
The React render cycle
Twelve articles in reading order, concepts alternating with the recipes that exercise them.
All 181 articles
Grouped by repository and concept folder. No chronology, because there is none.
Concept map
289 cross-links across four corpora, drawn as one graph.
How to read this corpus
- ConceptExplains a mechanism. Read when you want to know how something works before it breaks.
- RecipeStarts from a symptom you have already seen, and works back to the mechanism.
- BaselineThe framework version every claim in an article was verified against. Claims are pinned, never floating.
- ProvenanceCode blocks name the demo file they were extracted from. Nothing is typed by hand into an article.