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 three 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.
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
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
HolidayLogic
A holiday-lighting and exterior-care company: design, install, service all season, take it down on the agreed date. A lighting brand, so the dark is the product — a night register in incandescent gold, its own homepage body, and the template carrying everything underneath.
What was changed
- Its own homepage body inside the template’s page, so the structured data and chrome upgrades still arrive
- Its own typography (Poppins) and a soft 0.9rem radius, set in config rather than in framework CSS
- Its quote questions run on the platform’s question flow, so every answer lands as a lead
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
Common questions
What does the template look like before you customize it?
A complete working site with marketing pages, a blog, FAQ, contact, a member portal and a full operator dashboard — deliberately plain, with neutral typography and generic placeholder copy. It is designed to be a starting point rather than somebody else’s design you have to undo first.
Can sites built on the same template look completely different?
Yes. Three live examples share no page design: an event company with a cinematic near-full-screen homepage, its own typography and its own stylesheet; a holiday-lighting installer in a dark, warm-gold night register; and a dense technical platform site with a live animated hero and around ninety generated pages. None edited a framework file and all still merge every upstream release.
The part worth noticing
None of the live sites edited a single framework file, and all of them 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.