This entire product site is authored, validated, and rendered with Sights.See how it works
Menu

Static-first delivery

A website should still be a document unless it needs to be software.

Sights prerenders ordinary content routes into portable files. Client behavior is opt-in, page-scoped, and declared by the component or shell capability that needs it.

Inspect the quality gate
Versioned source passing through validation, rendering, and auditing into deployable static files

Complete static output

The build includes the unglamorous parts that make a site real.

Every artifact comes from the same validated route and content model instead of being maintained as an unrelated afterthought.

  • HTML and CSS

    Semantic server-rendered pages, shared structural styles, compiled theme tokens, local fonts, and responsive media.

  • Canonical metadata

    Titles, descriptions, canonical URLs, page-specific generated share images, Open Graph, Twitter cards, robots directives, and article metadata.

  • Structured data

    Validated Schema.org graphs for Organization, WebSite, WebPage, BreadcrumbList, and collection-backed Article pages.

  • Search discovery

    A deterministic sitemap, browser-readable sitemap stylesheet, and robots file derived from public canonical routes.

  • AI discovery

    A concise llms.txt generated from explicit site metadata, navigation, and public page summaries.

  • Operational files

    Static 404 output plus a portable redirect manifest and host adapter for real HTTP canonical redirects.

Capability isolation

Static pages and interactive tools keep different runtime contracts.

The custom calculator in this product site proves that one interactive component does not need to turn every route into a client application.

Static pages and interactive tools keep different runtime contracts.
CapabilityOrdinary content pagePrerendered documentCustom calculator pageDeclared interactive island
Prerendered HTMLYesYes
Useful before client codeYesYes
Component runtime loadedNoYes
Runtime on unrelated pagesNoNo
Server execution requiredNoNo

Build pipeline

One resolved model drives every output.

  1. Resolve

    Materialize pages, collection records, component props, public visibility, breadcrumbs, media, and capability requirements.

  2. Render

    Use Astro to produce semantic page documents and load only the trusted client runtimes declared by used capabilities.

  3. Generate

    Derive metadata, structured data, sitemap, stylesheet, robots, llms discovery, 404, and redirect artifacts.

  4. Audit

    Check scripts, route output, internal-page isolation, metadata, public anchors, assets, and semantic foundation usage.

  5. Deploy

    Publish ordinary static files to a compatible host and let the declared adapter enforce canonical HTTP redirects.

Current boundary

Static-first does not mean pretending a form submission is static.

The current Sights slice includes an accessible, explicitly disabled consultation-form interface and a real isolated client-component proof. It does not yet ship a trusted server action or lead-storage layer.

When a production form arrives, its handler, input schema, secret requirements, origin protection, storage destination, and host capability must live in registered trusted code—not in page JSON.

  • Already realStatic routes, declared motion, dropdown navigation, custom client components, local assets, metadata, discovery, redirects, and audits.
  • Deliberately absentBundled databases, arbitrary endpoints, page-authored scripts, secret values, and silently enabled server execution.
  • Future ruleServer behavior must be named, typed, host-supported, protected, and visible in generated capability output.

Trust the output

A static build is only valuable if it holds up in real browsers.

The quality system checks contracts, output, keyboard behavior, accessibility, responsive layouts, and multiple rendering engines before handoff.

Explore quality gates