Pages
The Pages collection, nested docs, slugs and homepage resolution.
On this page
The Pages collection stores editor-built routes. It is enabled by default and uses Systhema's catch-all renderer. Use pages: false to disable it, or an object to configure its default template.
Document fieldsLink to this section
| Field | Purpose |
|---|---|
title | Required Admin title, also available to SEO title templates. |
pageTemplate | Required template name, initially default. Hidden when the default is the only choice. |
default.hero | Hero fields for the default template. The hero title is separate from the document title. |
default.content | Root-tier Lexical state for the default template, with Component insertion enabled. |
parent | Parent Page relationship when nested documents are enabled. |
slug | Route segment, generated from the title unless unlocked. |
fullPath | Computed route path used for lookups, previews and internal links. |
meta | Page SEO overrides and search-index control when SEO is enabled. |
Template-specific groups and tabs change the content fields; see Page templates. The collection is orderable, supports trash, and shows title, fullPath and updatedAt in its default list columns.
Nested pagesLink to this section
With nestedDocs: true, assign a parent to build paths from ancestor slugs. A child with slug team below /about resolves at /about/team. Breadcrumbs store the ancestry used to calculate fullPath. Changing a parent or slug can change descendant routes, so check their internal links and old public URLs.
Slugs and pathsLink to this section
The slug field starts locked to the title. Unlock it to author the segment yourself. fullPath is computed rather than edited as independent route data. See slugField / nestedSlugField.
Access and publishingLink to this section
Unauthenticated reads expose published documents. Authenticated reads require pages.read; create and delete require pages.create and pages.delete. Full content changes require pages.update. Scoped capabilities such as pages.seo.update allow their field group while other fields stay read-only. Publishing also passes the publish-capability guard; see Access control.
Pages retain up to 50 versions per document. Draft autosave waits 800 ms after changes, and scheduled publishing uses 15-minute time choices. Draft content is available through authenticated preview, while public routes resolve published content. With localized status, publication is per locale; see Per-locale publishing.
Homepage resolutionLink to this section
General Settings can select any Page as the homepage. / renders the selected document; its own route redirects to / outside draft mode. If there is no usable published selection, the renderer looks for a Page with an empty slug. See Homepage resolution.
Rendering and revalidationLink to this section
Use Rendering pages to connect the collection to your catch-all route. The renderer selects pageTemplate, populates relationships needed by forms and posts, and renders the corresponding component. Save, publish, move, trash and delete hooks invalidate affected cached routes; see Revalidation.
PreviewLink to this section
Pages expose Preview and Live Preview using fullPath. Client mode can display unsaved form state for templates that provide a client view; server mode refreshes saved draft content. See Live preview.