Pages
| Field | Value |
|---|---|
| Audience | public |
| Page type | reference |
| Area | sg-admin |
| Updated | 2026-05-14 |
The SG-Admin Pages module — administer site pages, hand off to SG-Builder for composition.
The Pages module in the admin is the per-site surface for administering site pages — the persistent records that make up the navigable site. Operators create, edit, organize, and publish pages from this module, with visual composition handed off to SG-Builder via the Edit with SG Builder action. This page is the Reference definition.
What is this for?
Read this page when you want the structural definition of the Pages module — what records it administers, what the page lifecycle looks like, and how the module pairs with SG-Builder.
Good use cases
- You are scoping editorial workflows and need the Pages module model.
- You are explaining to a stakeholder how SGEN handles page administration.
- You hit a "where do I make a new page?" question and want the model laid out.
What NOT to use this for
- Step-by-step procedures — open the relevant Guide.
- Visual page composition — open SG-Builder (after opening the page record here).
- Per-release shipped change — open What's New or Changelog.
How this connects to other features
- SG-Admin Overview — parent surface (GENERAL pillar).
- SG-Builder Overview — visual editor that opens from a Pages record.
- Content Update Workflow — the everyday update cycle.
Where to find it
Open SG-Admin for the active site. Pages is in the sidebar under the content group. The page list, add-new action, and page-detail views are all reachable from this section. Editor and Admin access can publish; Authors can draft but may require review depending on workflow configuration.
Definition
The Pages module administers the persistent page records for the active site. Each page record carries identifying metadata (title, slug, route), structural metadata (template, parent page, hierarchy), and content (the page body, edited via SG-Builder).
The defining property is record-anchored. Pages are records first; visual composition layers on top via SG-Builder.
Purpose
The purpose of this page is to define the Pages module as a Reference layer rather than a configuration walkthrough. It explains the module's record model, the page lifecycle, and the SG-Builder pairing.
Scope
This page covers Pages at the Reference level.
The page covers:
- The page record model.
- The lifecycle (draft → published).
- Hierarchy and navigation (parent pages, child pages).
- The handoff to SG-Builder.
- Per-step procedures — Guides.
- Visual composition — SG-Builder Reference.
- Per-release shipped change — What's New or Changelog.
The page record model
Each page record carries:
- Title — the page heading and default sidebar label.
- Slug — the URL fragment.
- Route — the full path on the public site.
- Template — the layout template the page uses.
- Parent — for hierarchical site structures.
- State — draft / published.
- SEO metadata — meta title, meta description, canonical URL.
Site · SG-Admin · Pages
87 pages
| Title | Route | Template | Status | Updated | |
|---|---|---|---|---|---|
| Home | / | Homepage | Published | 2h ago | Edit with SG Builder |
| Pricing | /pricing | Landing | Published | 1d ago | Edit with SG Builder |
| About | /about | Standard | Published | 4d ago | Edit with SG Builder |
| New feature page | /features/new | Landing | Draft | 14 min ago | Edit with SG Builder |
Page lifecycle
Create
Operator adds a new page from the inventory list. Title, slug, template selected at creation.
Compose
Operator opens the page in SG-Builder via Edit with SG Builder. Composes the body visually.
Publish
Per the Publishing Workflow — explicit, atomic, validated, audited.
Update
Per the Content Update Workflow — open record, edit, re-publish.
Archive
Operator can archive a page rather than delete it; archived pages remain in the record set but are not served on the public site.
Hierarchy and navigation
Pages can carry a parent reference for hierarchical site structures. The hierarchy informs default sidebar nav and breadcrumb generation. Hierarchy is independent of route — operators can construct hierarchy that matches navigation intent without changing public URLs.
Constraints and boundaries
Pages is a Reference area for the page record model.
Use this Reference for:
- Understanding the page record model.
- Confirming the page lifecycle.
- Visual composition — SG-Builder Reference.
- Per-step procedures — Guides.
- Per-release shipped change — What's New or Changelog.
Public boundary
This page is intentionally public-safe.
Examples
Example 1 — Editor adds a new feature page
Editor opens Pages, clicks Add new page, names it, selects Landing template, opens in SG-Builder, composes, publishes. The new page is live at the chosen route.
Example 2 — Operator restructures site hierarchy
Operator opens Pages, edits the parent reference on several pages to match a new sidebar shape. Routes stay unchanged; the navigation reorganizes.
Example 3 — Editor archives an old page
Editor archives a deprecated page rather than deleting. The page disappears from the public site; the record stays in the system for reference.
Documentation guidance
Use this page as the structural definition for the Pages module. Visual composition lives in SG-Builder Reference; per-step procedures live in Guides.
Reading order
Open this page when scoping page administration. Pair with SG-Builder Overview for the visual composition surface.
Related reading
- SG-Admin Overview — parent surface.
- SG-Builder Overview — composition handoff.
- Content Update Workflow — everyday cycle.
Vocabulary cross-reference
- Page record is one row in the Pages module's inventory.
- Slug is the URL fragment that identifies the page.
- Route is the full public path.
- Template is the layout template the page uses.
- Parent reference is the hierarchy pointer for nested pages.
Maintenance discipline
When the Pages module changes across releases (new field, new lifecycle event, new template option), update this Reference and log the change in Changelog.
Related reading
| Topic |
|---|
| SG-Admin |
| SG-Builder |
| Content Update Workflow |