Skiff2 template · page architecture
A page is three files: what it shows, in what order, and what it says.
The registry names each slot's rendering, the sections list fixes their order, and this file holds the copy. Only the first is code — the other two are plain data, which is what lets the same page render from a checked-in file today and a service later.
slots on this page
renderings registered
file holding the copy
Every number above is a fact about this page, countable in the sections list and the registry. Add ?slots to the URL and each band names the slot it fills.
Where a real page's content actually sits
Measured on the moe-pass branch, whose MoeTraining page has twelve sections. Its content came to 804 lines across twelve files — which is the reason the copy gets its own page-level file rather than being inlined into the twelve-line section list.
| Section | Lines of content |
|---|---|
| What the stack runs at | 133 |
| The metric that lied | 87 |
| Fewer bits | 80 |
| What didn't work | 75 |
| Learning to hack | 75 |
wc -l over sections/*/seed.ts on the moe-pass branch, 2026-08-20
Recent papers
| Title | Venue | Year | Citations |
|---|---|---|---|
| OLMo: Accelerating the Science of Language Models | ACL | 2024 | 412 |
| Dolma: an Open Corpus of Three Trillion Tokens | ACL | 2024 | 287 |
| Molmo and PixMo: Open Weights and Open Data | CVPR | 2025 | 194 |
Example content for the variants mechanism — the papers are real, the citation counts are invented.