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

The Sights platform

A narrow authoring surface over a serious site system.

Authors work with structured pages, local media, and Markdown. Sights handles the contracts underneath: component selection, design foundations, route resolution, metadata, static generation, review surfaces, and output auditing.

See how a build worksRead the getting-started guide
Three connected layers showing structured authoring, the Sights system, and static delivery

Platform principles

The constraints are the product.

Sights is not a visual canvas or another way to make JSX faster. It is a bounded system for producing dependable content-driven sites repeatedly.

  • Constrained composition

    Authors select complete components around intent instead of generating arbitrary markup from scratch.

  • One source of truth

    A component manifest drives validation, types, schemas, documentation, examples, catalog metadata, and runtime declarations.

  • Strict by default

    Unknown fields, invalid routes, missing assets, unsafe URLs, and unresolved references stop the build.

  • Theme-owned presentation

    Page content cannot carry classes, styles, colors, or arbitrary layout values.

  • Static-first output

    Ordinary pages remain deployable documents. Runtime behavior appears only when a declared capability needs it.

  • Visible boundaries

    Custom code, client JavaScript, internal pages, integrations, and future server behavior stay explicit and auditable.

System anatomy

Six layers turn approved source into a complete website.

Each layer owns one class of decision, which makes failures easier to locate and changes easier to review.

  1. Site configuration

    Identity, canonical URL, navigation, footer, structured organization data, review routes, and deployment preferences.

  2. Content graph

    Composed pages, collection-backed templates, Markdown sidecars, assets, breadcrumbs, and public section anchors.

  3. Manifest registry

    Built-in and custom components expose their schemas, examples, variants, accessibility needs, and runtime cost.

  4. Semantic theme

    Validated roles for color, type, spacing, containers, radius, focus, surfaces, actions, and motion.

  5. Astro renderer

    One resolved page model powers HTML, metadata, structured data, responsive media, and client capability loading.

  6. Production gate

    Validation, type checks, static output audits, redirects, accessibility, responsive behavior, and browser checks.

Explore the system

Go as deep as the decision requires.

Each capability page separates the user-facing benefit from the technical contract that makes it dependable.

  • Content contracts

    Structured page authoring, collections, Markdown, links, assets, visibility, and generated agent guidance.

    Explore content contracts

  • Component system

    Intent-based components, manifests, examples, variants, primitives, and the internal review catalog.

    Explore the component system

  • Theming

    Semantic color, typography, spacing, shape, tone, and motion foundations without page-level styling.

    Explore Sights theming

  • Delivery

    Astro static output, canonical URLs, metadata, JSON-LD, sitemaps, llms discovery, redirects, and capability isolation.

    Explore delivery

  • Quality

    Schema validation, output audits, keyboard checks, accessibility scans, responsive coverage, and three browser engines.

    Explore quality gates

  • Extensibility

    Site-owned components, trusted implementation code, shared primitives, and runtime declarations that remain bounded.

    Explore extensibility

Optimized scope

Sights is for websites, not every kind of software.

The strongest fit is a marketing, lead-generation, editorial, knowledge, or campaign site where clear content, organic discovery, durable delivery, and repeatable quality matter.

A site may add a focused client-side tool through a custom component. The current product slice deliberately does not pretend to be a CMS, database, authenticated application framework, or general-purpose visual page builder.

  • Excellent fitContent-driven sites with recurring page patterns, strong brand requirements, and a need for fast dependable delivery.
  • Explicit extensionSmall interactive tools whose code, schema, runtime, fallback, and accessibility contract can remain isolated.
  • Choose another foundationStateful products centered on accounts, real-time collaboration, or deeply dynamic authenticated workflows.

The practical path

See the system operate from brief to browser gate.

The workflow page follows a real Sights change through authoring, validation, rendering, review, and production output.

See how Sights works