Pages
Pages are the site’s structural content: the About, Services, Contact, and everything else that lives at its own URL. This page covers creating and editing pages, parent/child hierarchy, choosing templates, and how slugs work.
Creating and editing pages
From the Pages section choose New page. You set a title and body, pick a language from your site’s configured languages, and choose a slug (see below). Save as a draft or publish immediately; publishing is subject to the approval workflow if it’s switched on, in which case a non-admin’s publish attempt becomes a submit-for-review.
The editor gives you the standard fields plus the extras on hand:
- Featured image with alt text and focal-point coordinates (which part of the image stays in view when cropped).
- Sticky: marks a page to sort first in built listings.
- Schedule publish / unpublish: datetimes interpreted in the site timezone (the scheduled entry only appears on the site when its time arrives, and leaves again after the unpublish window).
- Per-page SEO: meta title, meta description, og title/description/image, explicit canonical URL, and sitemap controls: include in sitemap, priority, and change frequency.
- Schema type: pick a structured-data type (e.g. Product) to emit the matching JSON-LD and fill the type-specific fields.
A “Start from template…” dropdown offers body-text presets (the landing layout, key-benefit lists, etc.); applying one replaces the current body content, with a confirm dialog.
Hierarchy
Pages nest: each page can have a parent, and the built URL is the full parent chain (e.g. /en/about/philosophy/). The admin list and the page View links resolve those nested paths, using the actual slug chain, including per-language localized slugs.
A couple of structural rules worth knowing:
- Unpublishing or scheduling a parent governs only that page; each child is its own publish decision.
- Deleting a parent doesn’t cascade; the children keep existing, just with the parent reference cleared.
Templates
Each page selects a template (default page.tt). The dropdown lists every page-appropriate template the system can find: core template files plus the files in your active theme, deduplicated, and it always keeps the page’s currently assigned template listed, even if its home theme is inactive, so a routine re-save can’t accidentally swap the template to the alphabetical-first option.
Slugs and language
Slugs are unique per language: the same slug may exist for an English page and its Spanish edition. Under the hood, so the elements that read that data are safe when you edit things twice: deleting content does NOT free the slug immediately: trash removes pages from availability but keeps identity in the slug uniqueness set until permanent deletion.
When you change a slug, the next build generates automatic redirects from the old URLs so visitors and search engines aren’t stranded. The redirect rules land in the redirects screen, where you can delete a rule if the old address shouldn’t redirect.
Pages are referenced by their slug + language combination, and the admin’s view/preview links always compute the same nested URLs the builder does, so what you see in the admin URL is what ships.
Privacy-protected pages
Pages support password protection: set a password and the page drops out of built listings and the sitemap so it doesn’t leak; the page is only discoverable if you link or share it directly. Every page also supports a preview token: a generated link that shows a draft or unpublished page without requiring sign-in.
Before publishing
- Pages default to draft; non-admins don’t publish without approval if that’s enabled in Settings → Workflow.
- Review, schedule, and sticky workflows all live in the same editor panel. Pages default to drafts; the build’s SEO report is the pre-publish safety net; it counts pages with empty or duplicate meta descriptions and empty canonical URLs so you can fix them before they go live.
- The static build reports pages with empty or duplicate meta descriptions and empty canonical URLs as SEO issues, so check the build report before pushing live.