Pages — Reference

The Pages surface is where the static structure of a site lives — the home page, about, contact, landing pages, every routable URL that isn't a blog post, event, product, or other content-type record. It owns the URL slug, the layout, the SG-Builder canvas state, the publication state, the SEO meta, and the per-post revision history.

This page is a reference for platform engineers and integrators. Customer-facing walkthroughs for adding, editing, and publishing pages live in the customer docs set; this page describes the surface, not the workflow.

---

Overview

Pages live under the Pages module in SG-Admin. The module renders three primary views — the page list, the create / edit form, and the per-page revision history — and shares its write surface with the broader post-record system. The shared write surface is important: many of the operations described below (duplicate, soft-delete, restore, revision-restore, set-homepage, import) are implemented once at the post-record layer and reused by Pages, Blog posts, Events, and custom content types.

When you read the SG-Admin source, you will see the Pages module file is intentionally thin — most of the heavy work lives in the shared post-actions surface. Integrators should think of Pages as "the post-record surface filtered to records of type page" rather than as a separate engine.

Where it lives in SG-Admin:

• Sidebar: SG-Admin → Pages
• URL prefix: /sg-admin/pages/
• View templates: application/views/Admin/Pages/
• Shared write surface: the post-record action layer (also used by Blog, Events, Custom Objects)

A site has exactly one homepage at any moment. The homepage role is a property of the post record, not of the URL — see Data model below.

┌──────────────────────────────────────────────────────────────────────┐│ SG-Admin → Pages [+ Add new] │├──────────────────────────────────────────────────────────────────────┤│ Title Slug Status Homepage Updated ││ ────────────── ────────────────── ────────── ──────── ─────────││ Home home published ★ 2d ago ││ About about published — 5d ago ││ Pricing pricing published — 1d ago ││ Contact contact draft — now││ Legacy Landing legacy/spring-26 archived — 44d ago ││ ││ [⋯ Edit] [⋯ Duplicate] [⋯ Set as homepage] [⋯ Delete] │└──────────────────────────────────────────────────────────────────────┘

---

Actions

The Pages surface exposes the following operations. Some are implemented directly on the Pages module; most route into the shared post-record action layer.

List and search

Returns the page records, paginated, with title, slug, status, homepage flag, author, and updated-at columns. Supports column sort, free-text filter, and per-page count. The page list is the post-record list filtered to type page.

Create page

Opens an empty editor. Required: title and slug (slug auto-derives from title but stays editable until first save). Optional: layout template, parent page (for hierarchical URLs), SEO meta, visibility, and the SG-Builder canvas state. On submit, the record persists in draft status by default.

Edit page

Loads an existing record into the same editor used for create. Submit replaces the stored state with the posted values. The editor preserves the SG-Builder canvas as a serialized component tree on the record — opening the editor a second time deserializes that tree into the canvas.

Save and publish

Two-step publication. Save persists the draft; Publish moves the record into the published state and assigns it a publication timestamp. Republishing an already-published record updates the timestamp. The two operations are deliberately split so an operator can stage many edits before they go live.

Duplicate

Creates a new page record with the same content, a copy-suffix in the title, and a unique slug. The duplicate starts in draft status regardless of the source's status. The duplicate carries its own record identifier — relationships pointing to the source page do not transfer.

Set as homepage

Marks the page as the site's homepage. Exactly one page holds this role at any time; setting it on a new page clears it on the previous one. The homepage role affects URL resolution — the homepage's canonical URL is /, not /.

Engineering note. When a page becomes the homepage, the front-end sheds the body class derived from the slug. CSS scoped to body.page- stops applying. Scope custom CSS to body.page_id- (the numeric record identifier) for rules that should survive a homepage flip.

Soft delete

Marks the record as trash. Soft-deleted pages disappear from the default list but remain queryable via the trash filter. URL resolution stops serving the page immediately.

Restore

Returns a trashed page to its prior status (draft or published). The slug is preserved; if a new page has been created at the same slug in the meantime, restore returns a structured rejection with the conflicting slug named.

Permanent delete

Hard-removes a trashed record. Irreversible. Author attribution on associated revisions is preserved, but the revisions themselves are removed.

Per-page revision history

Every save writes a revision row. The history view lists revisions for a given page in reverse-chronological order with the saving operator, the timestamp, and a short diff summary. Restore revision loads the historic canvas state back into the live record as a new save — the restored state immediately becomes the current draft, with the prior live state preserved as another revision.

Import

Bulk-loads pages from an exported bundle (typically from another SGEN site). Import accepts the bundle file, validates structure and slug collisions, and reports per-record success or skip. The shape and import path are shared with Templates and Posts.

---

Data model

A page record carries the following fields.

Field	Type	Notes
id	integer	Primary key. Stable across edits.
type	enum	Always page for records managed by this surface.
title	string	Display title. Used in admin lists and as the default