Sites

Four production sites, each its own Cloudflare Pages project on the wheelofheaven.world zone. All four are static — Zola for three, plain file serving for the asset CDN.

At a glance#

Per-site detail on the pages below.

What shares what#

flowchart TB
    subgraph submodules["Shared submodules"]
        dc["data-content<br/><i>markdown, 10 langs, 1330+ files</i>"]
        dl["data-library<br/><i>books JSON</i>"]
        bf["bifrost<br/><i>reading-site theme</i>"]
    end

    www["www"]
    api["api"]
    docs["docs<br/><i>only bifrost — for design tokens</i>"]

    dc -.-> www
    dl -.-> www
    bf -.-> www
    dc -.-> api
    dl -.-> api
    bf -.-> docs

    cdn[("Cloudflare Pages")]
    www --> cdn
    api --> cdn
    docs --> cdn

    di["data-images"]
    dcin["data-cinematics"]
    assets["assets<br/><i>CDN, not a submodule of others</i>"]
    di --> assets
    dcin --> assets
    assets --> cdn

The data-content submodule being shared between www and api is what guarantees both surfaces see the same content. Bump the pointer in one repo, then the other, and a content change goes live on both.

Build cost (typical)#

• www: ~30s (largest — 1,200+ pages, 10 langs)
• api: ~15s (smaller per-page output, plus a prebuild step)
• docs: ~20s
• assets: zero (no build, just file serving)

Why four separate Pages projects instead of subpaths on one#

• Independent build/deploy lifecycles. Content can ship to www without rebuilding the docs site, etc.
• Cleaner cache scoping — CDN behavior tuned per site
• Smaller blast radius on a bad deploy
• Each site can pin its own Zola version, npm tools, etc.

The cost is a bit of duplication in deploy config, which CI absorbs.

See also#

• Hosting and Caching — TTLs, cache invalidation, debugging stale content
• CI & Deploy — build commands, custom domains, GitHub app, redirects