Plate № 01 · Meta · the patterns, applied

A pattern from the gf.cx specimen book

Surface assembled from patterns

The problem

Every gf.cx subdomain used to start from scratch. Bespoke setup work — Pages project, custom-domain binding, fonts, diagnostic probes, 404 page, social card, favicon, provenance footer — got rediscovered and hand-rolled each time. Surfaces shipped under-finished: the favicon wired but no social card, the social card wired but no made-with footer. Without a pattern, the floor didn't rise — it just drifted.

The other failure was invisibility. A surface might look finished while silently missing two of the five baseline layers. There was no audit contract, no manifest, nothing to diff a surface against. You had to eyeball the HTML and hope you'd checked everything.

Bolt-on per-surface = friction, drift, and surfaces that never get the treatment. Scaffold-injected = the floor rises every time a new surface ships. — Dan, 2026-06-04

The element, in-page

The live demo below renders the five-layer surface baseline — the concrete checklist that every new gf.cx surface ships with when scaffolded by gfcx_subdomain_new.py. Each row is a hard-wired default, not an optional extra. A surface missing any of the five is under-finished, not minimal.

Where it applies

Any new gf.cx subdomain scaffolded with gfcx_subdomain_new.py ships this pattern automatically — the five layers are injected at scaffold time, not bolted on after. The first live proof is brand.gf.cx: assembled in one session from the portfolio patterns, with the full baseline wired before the first piece of content ever landed.

Surfaces that pre-date the scaffold receive the layers on the next sweep — gfcx_favicon.py audit and the site.config.json manifest are the drift-guards that make omissions visible rather than silent.

Reusable elements

• gfcx_subdomain_new.py — the canonical scaffold; lives at ~/bin/gfcx_subdomain_new.py (part of the xlab-co/toolkit checkout). Run it with a name, get a repo with every layer pre-wired. See also: the scaffold pattern page for the full spec.
• Five-layer surface baseline — inline-link promotion, rollover thumbnails, social card auto-capture, favicon control-plane wiring, and made-with provenance footer. Each sub-pattern has its own patterns.gf.cx page: built-with provenance footer is the canonical reference for layer 5.
• site.config.json declarative config — the audit contract; declares which baseline layers are wired and whether CF Access is enabled. An audit tool can diff a surface against its manifest without eyeballing HTML.
• Smart-404 — every scaffolded surface ships a context-aware 404 that suggests real paths rather than dead-ending the visitor.
• Post-deploy og:image capture — post_deploy.sh calls og_capture.py after each Pages deploy; the social card is always fresh after a deploy, never a stale screenshot.

Reference

Source

brand.gf.cx assembled from the patterns in one session, 2026. The case study that proved the scaffold + five-layer baseline compound in practice, not just in theory.

In use / example

brand.gf.cx — the surface assembled from the patterns. Scaffolded with gfcx_subdomain_new.py, shipped with the full belts-and-braces baseline, first content a cinematography lighting set-up ingested, transcribed, and footed with the built-with provenance footer.

Reusable elements

gfcx_subdomain_new.py scaffold · five-layer surface baseline · site.config.json manifest · smart-404 · post-deploy og:image capture (all listed above).

Origin

The surface-baseline vision: "It should be hard-wired, along with social cards for every surface. Applying it globally, across all surfaces, is where it gets harder to manage. It's the vision anyway." — Dan, 2026-06-04. Bolt-on per-surface = friction, drift, surfaces that never get the treatment. Scaffold-injected = the floor rises every time a new surface ships.