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

Content sites

Build a publishing system, not a pile of article templates.

Sights turns typed records and local Markdown into static index and detail routes with consistent featured media, dates, authors, breadcrumbs, related content, metadata, structured data, and discovery output.

Read the Sights insights
An editorial site with a featured article and structured article cards

Structured publishing

Every article joins the same content graph.

  • Typed records

    Each post has a stable id, title, summary, featured image, publication date, optional reading time and lede, plus a local Markdown path.

  • Index components

    Post grids resolve selected collection ids into consistent linked article cards with dates, summaries, images, and primary title links.

  • Detail templates

    A templated route selects one post record and resolves its hero, sanitized body, publication metadata, and related story into ordinary sections.

  • Safe Markdown

    Long-form prose supports headings, lists, links, code, and emphasis without raw HTML, unsafe protocols, or remote image tracking.

  • Editorial metadata

    Article routes derive dates and author relationships for visible content and validated Schema.org Article output.

  • Discovery output

    On indexable deployments, public articles join the sitemap and llms discovery automatically while internal and noindex pages remain excluded.

One article lifecycle

Add a story without rebuilding the editorial interface.

  1. Add the record

    Create a post id, metadata, summary, local featured media, publication date, and Markdown filename.

  2. Write the body

    Author readable Markdown with a clear heading structure and root-relative local images where needed.

  3. Create the route

    Add a templated page that selects the post id and supplies canonical route, SEO description, and breadcrumb relationship.

  4. Update discovery

    Reference the id from an index post grid or let a new index strategy select it through approved site code.

  5. Validate and publish

    Sights checks the record, template, route, asset, Markdown, links, metadata, related article, and generated production artifacts.

This site is the proof

The Sights insights section uses the same collection and template contract it describes.

Three product essays live as structured post records and sanitized Markdown sidecars. Their route files contain only page identity, canonical metadata, breadcrumb relationship, template selection, and the post id.

The post template resolves the detail composition, supplies Article structured data, and appends the newest available related post other than the current record.

  • BrowseThe index uses a collection-backed post grid with linked featured media and semantic publication dates.
  • ReadEach article renders a compact media hero followed by sanitized long-form content.
  • ContinueA related story closes the article without duplicating card data in the page file.

See it working

Read the essays generated by the collection you just learned about.

The index, article templates, metadata, breadcrumbs, featured media, and related content all come from the current Sights build.

Browse Sights insights