Specification
Core Architecture
The foundational engineering decisions that ensure speed, reliability, and predictable behavior.
- Static-first architecture (no runtime application server)
- Build-time rendering via Hugo (deterministic output)
- Zero database dependency
- Zero backend execution surface
- No runtime API dependencies (unless explicitly added per project)
- Immutable deploy model (each deployment is a complete version)
- Fully CDN-delivered website (edge-first delivery)
Maximum stability, minimal failure surface, predictable performance.
- Pre-rendered HTML (no client-side rendering)
- Zero render-blocking JavaScript by default
- Minimal JavaScript footprint (only essential interactivity)
- CSS optimized via Tailwind + purge
- Responsive, lazy-loaded, WebP optimized images
- No animation libraries (CSS-only transitions)
- No layout shift (CLS-safe components)
- Optimized font loading strategy
Consistently high Lighthouse scores (90–100 range).
- Automatic image processing via Hugo Pipes
- Resizing, cropping, and optimization at build time
- WebP conversion and compression
- Lazy loading and responsive srcsets
- OG image generation (1200×630)
High-quality visuals with minimal performance cost.
Discoverability
Built-in systems that ensure visibility across search, social, and AI-driven discovery.
- Structured meta tags (title, description, canonical)
- OpenGraph + Twitter Card integration
- Automatic sitemap.xml generation
- robots.txt generation with sitemap reference
- Canonical URL enforcement
- Image optimization for social sharing (1200×630)
- Structured data via JSON-LD: Organization, WebSite, Article, VideoObject, FAQPage
- llms.txt generation and AI discovery headers
- Machine-readable content structure
Visibility across search engines and AI systems.
- llms.txt support for AI agents
- Structured data for machine understanding
- Clean semantic HTML
- No JS-heavy rendering barriers
- Content accessible to crawlers without execution
Ready for AI-driven discovery and indexing.
Security Standards
Production-grade safeguards that protect users, data, and infrastructure.
- HTTPS enforced by default
- No server/database attack surface
- CDN-level delivery (Cloudflare edge)
- X-Frame-Options (clickjacking protection)
- X-Content-Type-Options (MIME protection)
- Referrer-Policy (data leakage control)
- Permissions-Policy (browser capability lockdown)
- Strict-Transport-Security (HSTS)
- Content Security Policy (site-specific, enforced after validation)
Production-grade security without server complexity.
- Analytics support (GA4, Plausible, Umami)
- Disabled by default (privacy-first baseline)
- Consent-gated loading (no tracking before consent)
- Delayed script execution (performance-safe)
- Event tracking capability (forms, interactions)
Privacy-compliant analytics without performance degradation.
- Semantic HTML structure
- Keyboard navigability
- Accessible form inputs and labels
- Proper time and article element usage
- Sufficient color contrast (via design tokens)
- Reduced motion compliance (CSS-only animations)
Usable and compliant across devices and users.
Content System
Systems that define how content is structured, presented, and interacted with.
- Structured content model (Hugo-based)
- Section-driven page composition (modular architecture)
- No fragile WYSIWYG dependency
- Deterministic content rendering
- Clean URL structure
- Built-in content types: Pages, Blog, Portfolio, Legal, Video
- Dynamic sections: Hero, Features, CTA, Testimonials, Pricing, Accordion, Recent Posts
Scalable content system without CMS fragility.
- Token-based design system (colors, spacing, typography)
- Tailwind-based utility architecture
- Consistent component library
- Dark mode support (system + toggle)
- SVG-based icon system (theme-aware via currentColor)
- No inline styling or ad-hoc overrides
Visual consistency across all pages and future additions.
- Contact form integration (e.g. Formspree or equivalent)
- Spam protection (reCAPTCHA or provider-level)
- Accessible form structure
- Client-side validation (lightweight)
- Reliable submission handling
Stable lead capture without backend complexity.
- Config-driven navigation (no hardcoded menus)
- Header + footer menu systems
- Scalable multi-page structure
- Internal linking consistency
Predictable navigation that scales with content.
- Configurable branding via hugo.yaml
- Logo system: inline SVG (theme-aware) or external light/dark variants
- SEO-specific logo (logoSchema)
- Favicon + web manifest system
- Theme color integration (light/dark modes)
Consistent brand presence across UI, SEO, and devices.
Infrastructure
How the system is deployed, maintained, extended, and fully controlled over time.
- Deployment via Cloudflare Pages (edge CDN)
- Git-based deployment workflow
- Automatic build + deploy pipeline
- Zero hosting cost (within Cloudflare free tier limits)
- Global edge distribution
Fast, reliable, and maintenance-free hosting.
- No plugin ecosystem dependency
- No version drift or dependency conflicts
- No CMS updates or patch cycles
- Fully version-controlled architecture
- Deterministic builds (same input → same output)
- Platform updates via Git submodule
- Client sites remain stable and isolated
- No forced updates or breaking changes
Long-term stability with controlled evolution.
- Git submodule-based platform architecture
- Override system (client layouts override HTS safely)
- No core file modification required
- Feature gating via configuration
- Tailwind + Hugo extensibility
Flexible system without compromising stability.
- Full ownership of your website content and domain
- Full access to your project repository and implementation
- No dependency on proprietary platforms or closed systems
- Website can be deployed on any compatible static hosting provider
- No lock-in to a specific vendor or service
Complete control over your website with long-term flexibility and independence.
- Web app manifest included (site.webmanifest)
- Installable experience supported on compatible devices
- Home screen icon support (iOS & Android)
- Standalone display mode (app-like experience)
- No service worker implemented by default — no offline functionality
- Install prompt behavior depends on browser support and policies
Optional capability — full PWA features available separately if required.