Colophon
How the Artifact Hub is built
A deliberately small static publishing system: public work stays portable, inspectable, and separate from the private sources that produce it.
The system
- Static by design
- Cloudflare Workers Static Assets serves the contents of
artifacts/directly. There is no build step, Worker script, or API handler for the public hub. - One visual system
- The hub and category pages share
site.cssandtheme.js, with self-hosted Cormorant Garamond, IBM Plex Sans, and JetBrains Mono. Paper and Night use the same layout. Individual essays retain their own typography and shareessay-chrome.cssfor navigation. The initial theme follows your device preference; an explicit choice is saved in your browser. - Artifacts stay isolated
- Each public artifact keeps its own
index.htmland local assets together inside one folder. That makes an artifact portable and keeps its public URL stable. - Cloudflare is the edge
- Only
artifacts/is deployed to the public Worker. Redirects, security headers, caching rules, and the custom 404 page live alongside that public surface. - Public output, private sources
- Canonical project files, drafts, and working notes remain in their source repositories, vaults, or workspaces until they are intentionally exported.
- No framework
- This is a static catalog, so direct HTML and CSS keep the publishing path inspectable and avoid complexity the site does not need. The architecture grows one self-contained artifact at a time.
- AI-assisted, human-directed
- AI supports research, implementation, criticism, adversarial review, and production. John retains direction, judgment, verification, and responsibility for the published result.