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: Every page shares site.css, theme.js, and a self-hosted type pairing of Cormorant Garamond, EB Garamond, and JetBrains Mono. Paper is the default ground; Night is a lamp-lit inversion of the same design, not a second one.
Artifacts stay isolated: Each public artifact keeps its own index.html and 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.