Principles
Five rules for deciding anything the rest of these docs do not cover.
1. Show the work
Lead with the thing itself: a figure, a demo that runs, code that copies and works. A page about a method should let the reader see the method act before it explains it.
- A paper page opens with its key figure, above the abstract.
- A demo opens on its default run, not on an empty form.
- Docs examples are live, with the code that made them underneath.
2. Play comes from working things
The world of these pages is a mathematics exhibition: models you can touch. Fun is allowed when something works, like the probability machine dropping real random balls. Ornament with no job is left out.
- Animation shows a process. It never decorates a heading.
- Tomato marks where you are and what moves, and the small marks that lead the eye there: the full stop, list markers, reference numbers. It never fills a panel or colors a paragraph.
3. One source of truth
Every value lives in tokens/tokens.json. CSS, Astro, Python, Tailwind, and LaTeX all read from it. A project that needs a new value adds a token rather than a hex code.
4. Three readers, one page
Academics want depth and rigor, recruiters want a fast read, students want clarity. Serve all three with structure rather than with three versions:
- The title states the claim or the subject in plain words.
- The first screen says what this is, why it matters, and where the details are.
- Depth follows below, in numbered sections, with equations and references where they belong.
5. Free to host, built to last
Everything builds to static files that GitHub Pages or Cloudflare Pages serve at no cost. Fonts are self-hosted. There is no tracking and no service that can disappear and take a page with it.