Skip to content
corpus.web
Start the course

Four corpora · one graph

Every claim resolves.

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.

196

Articles

445

Cross-links

4

Corpora

0

Unresolved

The corpora

All articles →

Who reads this corpus

Engineers learning a new framework

197 concept articles across Next.js, React, Angular, and NestJS. Pick the framework; read a curated path or grab one article and go.

Readers who want sources, not assertions

Every claim cites a verified demo or extraction; every article links to its neighbors. If you can't follow a thread, the site has failed, not the reader.

People who like their reference site ad-free

No tracking pixels, no popovers, no email capture. The text, the demo, and a link back to the source. That is the whole product.

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.
⌘K

Full-text across every adapting article. ↑↓ to move, ↵ to open, Esc to close.