Zero-JS showcase
100% of the catalog needs no JavaScript
288 of 289 assets declare no dependencies — pure CSS, or markup plus a stylesheet. The demos on their pages are React components like everything else, so this page answers the harder question: what does the site look like to a client that never runs a script?
Measured from the completed build on 2026-09-12 06:33 UTC (build eoCv1yhT4VQe) by npm run build && npm run measure, and committed as docs/build-report.json. The numbers are not re-derived while the page renders, because a build cannot see its own output.
Assets with no dependencies
288 / 289
100% of the catalog
CSS-only stacks
219
HTML/CSS builds — no framework, no runtime
Assets with dependencies
1
orbit-deck
The JavaScript-off view, measured
Each row is the page as a client with no JavaScript receives it — the HTML from a plain request, with every script ignored. Nothing is executed, so what the table shows is what a text browser or a crawler sees.
| Page | HTML | Demos deferred | Demos mounted | Card titles in HTML | Links |
|---|---|---|---|---|---|
| /components | 332.4 KB | 107 | 0 | 107 | 149 |
| /backgrounds | 73.2 KB | 33 | 0 | 0 | 41 |
| /prompts | 497.3 KB | 74 | 0 | 74 | 115 |
| /learn | 240.6 KB | 0 | 0 | 0 | 103 |
Read the third and fifth columns together: the demos wait, and the catalog does not. All 107 component titles and all 74 prompt titles are in the HTML, along with their links, kinds and scores — a visitor with no JavaScript can browse the whole library and simply does not see the animations, which are decoration on top of the information.
1 of the pages above have no prerendered file, because they are rendered on demand; those rows come from a live request rather than from the build output.
Four dependency-free examples from the catalog
- Prism SwitchReact / HTML/CSS · 1.2 KB
- Halo ButtonReact / HTML/CSS · 2.1 KB
- Pulse LoaderHTML/CSS / React · 0.8 KB
- Aurora VeilHTML/CSS / React · 2.6 KB
- Star MotesReact / HTML/CSS · 3.4 KB
- Scramble TextReact / HTML/CSS · 3.1 KB
Each one is rendered on its own page by the same demo registry, which is a client component. That is the honest limit of this claim: the asset needs no JavaScript — the site that previews it currently does, because the preview is a React island. Making the previews themselves server-rendered is a real piece of work, and it is not claimed here.