Gallery
The same starting point, three very different endings
Including the starting point itself — because a gallery of finished sites proves nothing about a template unless you can also see what it looked like before anyone touched it.
Anyone can show you nice websites. The question that actually matters is whether the nice website and the thing you are being handed are the same thing — so the first entry below is the untouched base, and the others are what two live businesses made of it.
The artwork on each card is a live scene from our visualization engine, not a screenshot — we would rather label an illustration than pass off a mockup on the one page whose entire job is credibility. Follow the links for the real sites.
Starting point
The base template
What every clone looks like on day one, before a single change. A complete working site — marketing pages, blog, FAQ, contact, the member portal and the full operator dashboard — deliberately plain so it is a starting point rather than somebody else’s design you have to undo.
What you start with
- Neutral type and a soft 0.5rem radius — chosen to be unopinionated, not to be admired
- Six generic service cards and placeholder copy, all in the content lane
- The framework homepage, which a site can replace outright
MIT licensed · free · yours to forkThe template repository ↗
Utah's Events
An event company — weddings, rooftops, DJs, cinema nights. Built from one reference screenshot and a plain-language prompt: a cinematic near-full-screen homepage with its own typography, its own components and its own stylesheet. Nothing about it reads as a template.
What was changed
- Owns its homepage entirely, with its own layout and chrome
- Its own CSS and type scale — light weights, generous air, photography-led
- Its own components under components/, none of them framework files
50 files custom · 0 framework edited · 13 releases mergedVisit utahsevents.com ↗
BringTheFront
This site. A developer- and operator-facing platform site: dense, technical, built to be read by people evaluating infrastructure and by the AI assistants they ask. Around ninety pages, most of them generated from structured content rather than hand-authored.
What was changed
- Owns its homepage, with a full-bleed live scene instead of a photograph
- Its own typography and a crisp 0.25rem radius — deliberately unlike Utah’s Events
- Roughly 90 pages generated from content files, plus its own live-tile hero component
44 files added · 5 lane files edited · 0 framework editedHow this one was built →
The part worth noticing
Neither live site edited a single framework file, and both still merge every upstream release. The difference between them is not how much they changed — it is that they changed things in the lanes built for changing. That is the whole design, and it is why “make it mine” and “keep getting updates” stopped being a trade.