A Full-Featured Blog Post
A reference post demonstrating the full set of blog features supported by HTS.
Read More
Hugo Tailwind Starter
A production-grade platform for building and operating zero-maintenance business websites at scale.
Built for Performance
90
/100
Lighthouse Performance (Mobile)
<
1
s
Page Load Time (Typical)
0
Runtime Dependencies
One-off vs Systems
Two different ways of building and evolving websites.
Isolated Projects
- Each site built independently
- Architecture varies by project
- Performance tuned manually
- Consistency by convention
- Upgrades handled per site
- Scattered Knowledge Base
Integrated Projects
- Each site based on the core
- Opinionated central architecture
- Performance guaranteed by default
- Consistency enforced structurally
- Upgrades propagate automatically
- Centralized Knowledge Base
How HTS Works
A centralized platform deployed to client sites as a Git submodule — one system, many deployments.
- 1
HTS evolves centrally
Architecture changes, performance improvements, and new components are made once in the HTS repository.
- 2
Client sites consume HTS as a submodule
Each client site includes HTS via Git submodule. No forking, no divergence.
- 3
Content lives in client repos
Pages, copy, images, and configuration all live in the client site — never inside HTS.
- 4
Updates propagate safely
Running a submodule update pulls HTS changes into every client site simultaneously, with no per-site refactoring.
Deployment Model
Root:
client-site/
Submodule:
hts/ (read-only)
- 1. content/ — client owns
- 2. static/ — client owns
- 3. hugo.yaml — client owns
- 4. hts/ — submodule (read-only)
- 5. layouts/ — overrides only
- 6. assets/css/custom.css — optional
Highlighted entries are HTS-owned. Client sites never edit files inside hts/.
Optimizations
Built-In Performance
Static architecture, minimal JavaScript, delayed analytics, and CDN delivery ensure fast loads without ongoing tuning.
Controlled Visual System
Design tokens, section contracts, and layout invariants prevent visual drift across sites while allowing safe evolution.
Centralized Evolution
Our system evolves once and propagates safely across all client deployments without divergence.
System Constitution
HTS is a system, not a theme. It encodes architectural decisions so performance, security, and structure are guaranteed by default.
System Intent
Design Principle
HTS
This site exists as a reference and validation layer. It is built using the same system deployed to real client sites.
Operational Reality
Why This Exists
HTS
HTS is not a public framework, starter kit, or drop-in solution for independent use. These constraints are intentional.
Explicit Non-Goals
Scope Boundary
HTS
