Routes and pages

Routes are a document (pull, edit, push) mapping paths to page kinds:

• home — the front door. Its config carries site presentation: siteName, title, description, an optional masthead (the site brands its own chrome; it defaults to your site name), footer text and links, optional nav, and an ordered sections list composing the page from your list routes (each entry: a route, an optional label, an item limit, a layout override). No sections config → every list route previews.
• list — a collection page targeting an entity type or a saved query. Serves facets, sort, result counts, pagination, and its own Atom feed at <path>/feed.xml.
• entity — detail pages at <path>/:slug, or a singleton page when the target pins a slug (/about serving one entity).
• relation — a page for one entity's related items (/boards/:slug/pins).
• search — the search page; config scope sets the default reach (see Search and the API).
• redirect — 302 (or 301 with "permanent": true).
• asset — one asset's bytes at a clean path (a PDF at /whitepaper.pdf).

Saved queries

Named queries with filters, sort, grouping (groupBy by enum, number, or date with year/month granularity), and limits. A list route targeting a saved query renders the query's order — the first result is the magazine lead, the group headers are the archive's years.

Everything a route serves as HTML is also available as JSON: append ?format=json or send Accept: application/json.