Templates
| Field | Value |
|---|---|
| Audience | public |
| Page type | reference |
| Area | sg-admin |
| Updated | 2026-05-14 |
The SG-Admin Templates module — site-wide layout templates governing page-type rendering.
The Templates module in the admin is the per-site surface for managing layout templates — the structures that govern how each page-type record renders. SG-Admin Templates is the master list (single source of truth); SG-Builder Templates Library is the in-editor visual picker referencing this list. This page is the Reference definition.
What is this for?
Read this page when you want the structural definition of templates at the site-wide level — the master list, the application model, and the relationship to SG-Builder Templates Library.
Good use cases
- You are scoping site-wide layout governance.
- You are explaining to a stakeholder why pages render consistently.
- You hit a "where do I edit the post template?" question.
What NOT to use this for
- Step-by-step procedures — open the relevant Guide.
- In-editor template insertion — open SG-Builder Templates Library.
- Per-release shipped change — open What's New or Changelog.
How this connects to other features
- SG-Admin Overview — parent surface.
- Pages — pages reference templates.
- SG-Builder Templates Library — in-editor counterpart.
Where to find it
Open SG-Admin for the active site. Templates is in the sidebar under the design or appearance group. The master list, template type filters, and usage counts are all visible from the Templates surface. Admin access is required to create or modify template definitions.
Definition
The Templates module administers the site-wide layout templates. Each template carries identity, type (page template, post template, product detail, custom-object detail), structural definition (the layout shape), and per-template configuration. Records (Pages, Posts, Products, Custom Objects) reference a template; the template governs default rendering when SG-Builder per-page composition does not override.
The defining property is single source of truth. SG-Admin Templates is canonical; SG-Builder Templates Library is the visual surface that references the canonical list.
Purpose
Define the Templates module as a Reference layer.
Scope
Covers the template record, type model, and the the admin → SG-Builder relationship. Does not cover per-step composition (SG-Builder Reference) or per-release shipped change.
Template record + types
Page templates
Layout templates for Page records (Homepage, Landing, Standard, etc.).
Post templates
Layout templates for Blog post detail pages.
Product detail templates
Layout for store product detail pages.
Custom Object detail templates
Layout for Custom Object detail pages where the object type carries page rendering.
Site · SG-Admin · Templates
Master list
| Template | Type | Records using | Updated |
|---|---|---|---|
| Homepage | Page | 1 | 4d ago |
| Landing | Page | 14 | 2d ago |
| Standard | Page | 52 | 9d ago |
| Post detail | Post | 340 | 1d ago |
| Product detail | Product | 156 | 3d ago |
SG-Admin / SG-Builder relationship
Templates lives in the admin as the canonical list. SG-Builder Templates Library is the visual picker that references this list during composition. Editing a template here propagates to every record that uses it; saving a template from SG-Builder writes back to this list.
Constraints and boundaries
Templates is a Reference area for site-wide layout governance.
Do not use for: per-step composition (SG-Builder Reference), per-release shipped change.
Public boundary
This page is intentionally public-safe.
Examples
Example 1 — Operator updates the Post detail template
Operator opens Post detail in Templates, edits the layout. Every existing post that uses the template now renders with the new layout (subject to per-record overrides authored in SG-Builder).
Example 2 — Operator scopes a new template type
Operator creates a new Landing template variant for Q2 campaigns. Pages can reference the new template; the master list shows usage count.
Example 3 — Stakeholder asks "what templates are available?"
Operator opens this Reference + the master list, answers structurally.
Documentation guidance
Use this page as the structural definition for the Templates module.
Reading order
Open this page when scoping site-wide layout governance. Pair with SG-Builder Templates Library Reference for the in-editor surface.
Related reading
- SG-Admin Overview — parent surface.
- Pages — page records reference templates.
- SG-Builder Templates Library — in-editor counterpart.
Vocabulary cross-reference
- Template is one site-wide layout structure.
- Template type is one of page / post / product / custom-object.
- Master list is the canonical Templates inventory in the admin.
- Reference is when a record points at a template for default rendering.
Maintenance discipline
When the Templates module changes across releases (new template type, new application model), update this Reference.
Related reading
| Topic |
|---|
| SG-Admin |
| Pages |
| Templates Library |
