Explain the offer without rebuilding the page system.
Compose product, service, company, proof, and campaign pages from reusable patterns while the theme keeps the brand coherent.
- Page sections
- Reusable
- Brand system
- Consistent
Static-first site infrastructure
Give AI a system. Ship better sites.
Sights turns structured content into fast, accessible, production-ready websites using strict contracts, reusable components, semantic themes, and a quality gate that travels with every build.
- ConstrainedContent cannot smuggle in code or styling.
- ReusableTested components compound across every site.
- Static-firstDurable files are the default delivery model.
- Agent-readableGenerated contracts expose every valid choice.
The difference
A website system beats another plausible-looking page.
AI can generate markup quickly. The expensive part is keeping every page coherent, accessible, responsive, secure, and maintainable after the first prompt.
| What has to hold up | SightsShared contracts and tested behavior | Bespoke generationPage-specific markup and decisions |
|---|---|---|
| Content model | Strict, discoverable schemas | Implicit shapes that drift |
| Responsive behavior | Verified once and reused | Reimplemented on every page |
| Design decisions | Semantic theme roles | Local styling and prompt residue |
| Accessibility | Component and browser gates | Depends on each generation |
| Runtime behavior | Declared and audited | Easy to add, hard to account for |
| Next edit | Small content diff | Another round of page surgery |
One connected platform
Every layer has a clear job.
Sights keeps authoring, presentation, rendering, and verification separate enough to change safely—and connected enough to ship as one dependable site.
Content contracts
JSON and Markdown stay focused on meaning. Unknown fields, bad links, missing assets, and unsafe markup fail early.
Explore content contracts
Component system
Intent-based components own markup, responsive behavior, interaction, and accessibility instead of leaking those choices into content.
Explore the component system
Semantic themes
One validated theme controls color, type, spacing, shape, and motion across the entire component catalog.
Explore theming
Static delivery
Pages build into portable HTML, CSS, assets, metadata, discovery files, and host-ready redirect artifacts.
Explore delivery
Quality gates
Validation, build auditing, axe, keyboard checks, reflow, and three browser engines test the shared system and the consumer together.
Explore quality
Guarded extensions
Site-owned components can add unique behavior while keeping the same schema, documentation, review, and runtime rules.
Explore extensibility
Current product slice
Concrete contracts, not a slide deck.
The canonical consumer exercises the same package boundary, generated documentation, build pipeline, and browser gate expected of a real Sights site.
- Built-in components
- 24
- Plus one site-owned component registered through the same manifest contract.
- Browser engines
- 3
- Chrome, Firefox, and WebKit run the same consumer quality gate.
- Presentation escape hatches
- 0
- Page data cannot contain classes, styles, raw HTML, scripts, or secrets.
- Manifest source of truth
- 1
- Schema, docs, examples, catalog data, runtime declarations, and rendering stay aligned.
Built for real website work
One system, four useful site shapes.
Sights is intentionally optimized for sites where content, clarity, search visibility, and dependable delivery matter more than application state.
Pair persuasive pages with an honest interaction boundary.
Build focused landing pages and accessible intake interfaces. Persistence remains an explicit trusted capability, never a hidden endpoint in content.
- Form interface
- Accessible
- Server boundary
- Explicit
Turn collections and Markdown into an editorial system.
Publish index pages, article routes, featured media, metadata, breadcrumbs, related content, and discovery files from validated records.
- Collections
- Typed
- Markdown
- Sanitized
Add the one useful island without turning the site into an app.
Register a custom component with a strict schema and isolated runtime. Pages that do not use it do not load its code.
- Client runtime
- Isolated
- Capability contract
- Visible
The operating model
From brief to dependable build in five deliberate moves.
The workflow gives human and AI authors a bounded path that stays easy to inspect in version control.
Made for agents and humans
The site explains how it wants to be changed.
Sights generates a local agent guide, JSON Schemas, component and template catalogs, and examples directly from the same definitions used at runtime.
That makes the correct path discoverable: edit content first, reuse a component, validate the result, and cross the trusted-code boundary only when the site genuinely needs a new capability.
- Discoverable choicesEvery component says when to use it, what to avoid, which props it accepts, and what runtime it adds.
- Actionable failureDiagnostics identify the file, exact field, invalid value, expected contract, and likely correction.
- Reviewable changesContent stays concise, versioned, and separate from component implementation and visual tokens.
See the complete model
Start with the platform, then inspect the site it produced.
Explore the architecture, follow the authoring workflow, and open the live custom-component example. Every page you visit is another part of the proof.