Single-file HTML templates: why the "boring" stack still wins for landing pages

傲遊天地、ブリストラベル、BLISS TRAVEL — Tue, 06 Oct 2026 13:14:37 +0000

Every few months a new meta-framework promises to make websites simpler by adding another layer. Meanwhile, some of the best-performing sites on the web are one HTML file and a stylesheet.

We build and sell website templates for a living - 200+ of them, all single-file. This isn't nostalgia; it's what we've watched win, over and over, for marketing sites, landing pages, and small business websites.

The case for boring

1. Performance by construction. No framework runtime, no hydration, no client-side router. The browser gets HTML, CSS, and a sprinkle of vanilla JS. You don't need to optimize your way back to fast - you start there.

2. Hosting is trivial and cheap. Any static host, any bucket, any nginx box. Zero build pipelines to maintain, nothing to redeploy when a dependency CVE drops.

3. Handoff that doesn't break. Agencies know the pain: the client can't edit a React app. They can edit HTML. Templates that real humans can maintain are underrated.

4. Longevity and auditability. You can read the whole page in one file. Legal review, accessibility audits, and SEO checks get dramatically easier when there is no generated output in the way.

5. It still meets modern expectations. Semantic HTML plus lightweight JS gives you scroll-driven motion, lazy images, and responsive layouts. You can have the polished, animated feel without shipping a large runtime to get it.

Where single-file is the wrong tool

Be honest about the limits: web apps with complex state, dashboards, real-time collaboration - build those with frameworks; that's what they're for. A landing page is not a web app. Most business sites are essentially documents that should look good and load fast.

A practical checklist

Design tokens in CSS custom properties (:root), so theming is one edit
Fluid type with clamp(), layout with Grid and Flexbox
Progressive enhancement: the page works without JS; motion is additive
prefers-reduced-motion respected
Images lazy-loaded and properly sized
No render-blocking third parties

The bottom line

Complexity is a loan; you pay interest on it forever. For the class of sites where most businesses live, the boring stack isn't a compromise - it's the shortest path to something fast, durable, and easy to hand off.

We publish 200+ single-file templates at zeusgroup.ai/tech/templates. Happy to nerd out in the comments about the approach.

We built 200+ website templates as single HTML files - here's what we learned

傲遊天地、ブリストラベル、BLISS TRAVEL — Tue, 06 Oct 2026 13:07:17 +0000

When we started BLISS TECH, we set a constraint that sounded almost silly: every template we ship must be a single, self-contained HTML file.

No package.json. No build step. No node_modules. One file you can drag onto any host (or even open straight from your desktop) and it just works.

Today the library has 200+ templates across 40+ industries - real estate, hotels, restaurants, clinics, law firms, SaaS, and more - and the single-file constraint has shaped everything about how we build. Here's what that looks like in practice, and why we'd make the same call again.

Why single-file?

1. Templates are products, not starter kits. When a small business buys a template, they want to edit a headline, swap a few images, and publish. A build chain is a liability for them. A single file deploys anywhere, needs zero tooling, and survives years of neglect.

2. Longevity. Sites built on heavy frameworks age fast; plain HTML/CSS/JS does not. When your product is the file, dependency rot is not a risk you carry.

3. One file is testable in isolation. You can open it via file://, audit its markup end to end, and diff versions meaningfully. No generated soup.

What's inside each file

Design tokens as CSS variables. Every color, type scale, and spacing decision lives in :root custom properties, so re-theming is a handful of variable edits - not a refactor.

Fluid typography and layout. Headings scale with clamp(), structure comes from CSS Grid and Flexbox, so one file looks right on every screen.

Motion without weight. Scroll reveals and parallax are driven by IntersectionObserver plus a requestAnimationFrame loop with an early exit when nothing is moving - transform/opacity only. And a prefers-reduced-motion guard is always in place.

Accessibility as a baseline. Semantic HTML5 landmarks, ARIA roles where they help, keyboard-visible focus, descriptive alt text. WCAG 2.2-minded from the start.

Lessons

"No build" is a feature customers feel immediately - in handoff, hosting costs, and editability.
The last 10% is the product. Motion polish and spacing rhythm take most of the time - and that's exactly what makes a template feel premium.
Constraints compound. The single-file rule kept our dependency count at zero and keeps the pages fast by construction.
Sell to businesses, not just designers. Most buyers care about time-to-launch, not tooling novelty.

Try it

You can browse the whole library at zeusgroup.ai/tech/templates - 200+ templates, 40+ industries, every demo live, every file production-ready.

If you build single-file sites too, I'd love to hear what constraints you work under. Drop a comment.

DEV Community: 傲遊天地、ブリス トラベル、BLISS TRAVEL