Pages (Content Model)

Pages are the site’s structural content: the fixed-purpose URLs a website is assumed to have — home, about, services, contact, legal — as opposed to the running stream of posts. Pages nest, choose their own template, and can be individually scheduled, protected, or excluded from the sitemap.

Pages and posts share most machinery (drafts, revisions, scheduling, language, SEO fields) — this page covers what’s distinctive about pages. Full editor detail lives on the Pages authoring page.

How pages differ from posts

No date stream — pages don’t build archives, category listings, or RSS feeds; they exist at their own place in the URL tree.
Hierarchy — every page can have a parent; the built URL is the full chain (/en/about/philosophy/). Level changes never orphan children (deleting a parent just detaches the children).
Per-page template — each page picks its own render template (the default page.tt, plus landing and any theme-provided page templates).
Unique per language — the English and Spanish pages are separate records connected for translation signals, and may have entirely different slugs.

The specialist page abilities

Password-protected pages — drop out of built listings and the sitemap; discoverable only by direct link.
Preview tokens — share a draft with anyone via a generated link, no account needed.
Sitemap control — exclude a page from the sitemap or set priority/change frequency.
Structured data — pick a schema type (up to product-level detail: price, SKU, brand, availability) to emit matching JSON-LD.
Sticky — float a page to the top of built listings.
Landing pages — a block-oriented template for campaign-style pages (paired with the built-in landing content preset).

What lands where

The built URL of a page is the language segment (in path mode) plus the parent chain plus its slug, and the page’s template decides everything else about its layout. Meta/OG/canonical fields override the site defaults per page; leaving them blank falls back to sensible values from settings.