The Guide · Replicable Method

How the Twenty-Five were made.

Twenty-five distinct 3D websites, one per industry, each designed and engineered autonomously by Fable. This is the honest, replicable account of the system behind them — so you can build your own.

25 sites 1 shared brief 3 iteration passes each 0 templates
01 — The idea

One brief, twenty-five worlds.

The goal was not twenty-five variations of a template. It was twenty-five genuinely different visual worlds — a rolling ocean for a marine company, a raymarched diamond for a jeweler, a wind-blown field of grass for a landscaper — each one convincing enough that its industry would claim it as their own.

The trick to making different scale without collapsing into sameness is to separate two things: a shared standard of craft that never moves, and a per-site creative spec that changes everything else. Hold the first constant; vary the second wildly.

02 — The system

Spec-driven design.

Every site starts as a small structured spec — a plain object that names the industry, a brand, a palette, a font pairing, a signature technique, a motion language, the sections, and a one-word mood. It is the DNA. Because the fields are identical across all twenty-five, the differences are deliberate rather than accidental.

// one entry from specs.json — the DNA of a single site
{
  "slug": "marine",
  "brand": "Chesapeake Marine",
  "signatureTechnique": "Three.js real-time Gerstner-wave ocean
     with sun glint and foam; horizon fog; boat silhouette",
  "palette": { "bg":"#07171C", "accent":"#C69A4C", "accent2":"#3E8E9C" },
  "fonts":   { "display":"Spectral", "body":"Archivo" },
  "mood": "coastal luxury, nautical, tidewater, brass-and-teak"
}

Alongside the specs sits a single brief: the non-negotiable contract of craft. It defines the technical rules (self-contained HTML, pinned CDN libraries, clean-URL routing, capped pixel ratio, reduced-motion safety, zero console errors), an excellence rubric (typographic authority, a restrained palette, real depth and light, motion with meaning), and — just as important — an anti-slop list of banned patterns.

The anti-slop list is the secret weapon. It explicitly forbids the tells of generic AI design: the centered hero with two pill buttons, the purple blur-blob gradient, three identical icon cards, emoji as icons, lorem ipsum. Naming the clichés is what keeps the work from drifting toward them.

03 — The build

Autonomous agents, one per site.

Each site is built by a dedicated agent that reads the shared brief and its own spec, then writes one self-contained index.html and a matching guide/ page. The agent is asked not to fill a template but to art-direct: to make the hero deliver the signature technique with real craft, to write copy a real owner in that trade would approve, and to redesign anything that could belong to any other site.

The sites are orchestrated in parallel through a deterministic workflow — a small script that fans work out across agents, each writing to its own folder so nothing collides. This is how twenty-five bespoke sites get built without twenty-five separate sittings.

04 — The techniques

Three families of motion.

Almost everything you see is generated live in the browser — no video files, no pre-rendered frames. The twenty-five draw from three rendering families, chosen per site by what the industry feels like:

Three.js scenes

Real geometry, lighting, and camera: the ocean, the assembling shield, the globe, the wind-blown grass, the wireframe-to-solid house.

GLSL shaders

A full-screen fragment shader doing the heavy lifting per pixel: the raymarched diamond, the molten-gold metaballs, the living marble, the water caustics.

Canvas systems

2D particle and path work: rising embers, drifting bokeh, kinetic type streaks, procedural blooms, curling steam.

Binding them together is a single motion language — GSAP with ScrollTrigger for scroll-driven reveals, parallax, and staggered entrances — plus a consistent set of guardrails: the render loop pauses when the tab is hidden, the pixel ratio is capped for performance, and if a visitor prefers reduced motion, each site freezes to a single beautiful static frame instead of animating.

05 — The iteration

Three fine-tooth-comb passes.

A first draft is never the deliverable. After it builds, every site goes through three deliberate passes, each with a different job:

  1. Correctness & craft. No console errors; the signature animation actually runs and is beautiful; responsive at 380 / 768 / 1280px; reduced-motion handled; every link relative and working; no layout overflow.
  2. Design elevation. Hunt down anything that reads generic or flat. Increase typographic contrast, tighten the spacing rhythm, deepen the palette with gradient and grain and light, strengthen the signature moment, sharpen the easing. Make it more specific.
  3. Content & finish. Every word made industry-literate and particular; believable stats and named testimonials; title, meta, favicon; the guide page completed; a final consistency sweep. Ship-ready.
06 — The stack & the ship

Static, self-contained, fast.

Each site is a single HTML file with its CSS, JavaScript, and shaders inline; libraries load from pinned CDNs; fonts come from Google Fonts. There is no build step and no framework — which makes the sites trivially portable and quick to load.

Routing is done with folders, not a router. A directory with an index.html becomes a clean URL automatically, so /sites/21-marine/ and /sites/21-marine/guide/ just work. The whole public/ tree deploys to Netlify as a static site; a small netlify.toml sets sensible caching and pretty-URL behaviour.

Want to replicate it? Write a spec object per project. Write one strict brief with an anti-slop list. Give each build its own agent and its own folder. Insist on three iteration passes. Keep every site self-contained. Deploy the folder. That is the entire method.

07 — Takeaways

What travels to your work.

  • Constrain craft, free aesthetics. A fixed quality bar plus a variable creative spec is what lets a set feel unified and unrepeatable at once.
  • Name the clichés you want to avoid. An explicit anti-slop list does more for taste than any amount of positive direction.
  • Generate motion, don't ship it. Live WebGL, GLSL, and Canvas keep pages tiny and infinitely crisp — and let one idea (a wave, a facet, an ember) carry a whole brand.
  • Iterate in named passes. Correctness, then elevation, then finish — each pass looking for one class of problem — beats one vague polish.
  • Respect the visitor. Cap the pixel ratio, pause off-screen, honour reduced motion. Spectacle and performance are not a trade.