Templates Library

The SG-Builder Templates Library — saved page and section patterns for reuse.

The Templates Library is the SG-Builder surface for reusable patterns. Operators save common page or section structures as templates and reuse them across pages and across sites where shared. This page is the Reference definition.

What is this for?

Read this page when you want the structural definition of templates — what counts as a template, where they live, and how reuse works.

Good use cases

• You are scoping a multi-page rollout that uses a recurring layout.
• You are explaining to a stakeholder how SG-Builder handles design reuse.
• You hit a "can we reuse this section across pages?" question and want the model laid out.

What NOT to use this for

• Step-by-step procedures — open the relevant Guide.
• Per-release shipped change — open What's New or Changelog.
• The Theme Editor (different surface) — open the Theme Editor Reference.

How this connects to other features

• SG-Builder Overview — parent surface.
• Builder Workspace — workspace where templates are inserted.
• Components — sibling Reference covering the component model templates are built from.

Definition

A template in SG-Builder is a saved pattern — a page or a section — that operators can insert into any page on the active site (or across sites where the template is shared at the account tier).

The defining property is reusability. Templates exist to avoid re-authoring the same structure repeatedly. Once saved, a template can be inserted any number of times.

Where to find it

Inside SG-Builder, open the Templates Library from the action bar or block library panel. Templates are available for the active site; account-shared templates appear alongside per-site ones where the plan supports it.

Template scope

Page templates

A full page structure saved as a template. Use cases: new-page setup with a known layout (landing page, feature page, post template).

Section templates

A single section saved as a template. Use cases: recurring patterns across multiple pages (testimonial section, CTA section, hero variants).

Where templates live

Per-site

Default scope. Templates saved on a site are available only on that site.

Account-shared

Where the plan supports it, templates can be promoted to account-shared scope and become available across every site under the account.

The insert flow

Open Templates Library

Inside SG-Builder, open the Templates Library (typically via a menu in the action bar or block library).

Browse and select

The library shows the available templates with thumbnail previews. The operator clicks Insert on the chosen template.

Template inserts at cursor

The template inserts at the operator's current selection point on the canvas. Operators can then customize the inserted instance.

Examples

Example 1 — Operator reuses a CTA section across pages

The operator saves a CTA section as a template. On subsequent pages, they open Templates Library, click Insert on the CTA template, customize the heading per page. The section pattern stays consistent across the site.

Example 2 — Agency promotes a template to account-shared

An agency operator saves a hero pattern that works for many client sites. They promote the template to account-shared. The template appears in Templates Library across every site under the account.

Example 3 — Operator updates a saved template

The operator opens the saved template, edits it, saves the new version. Future inserts use the new version; previously-inserted instances retain the version they were inserted with.

Related reading

• SG-Builder Overview — parent surface.
• Builder Workspace — workspace where templates insert.
• Components — component model templates build on.

Vocabulary cross-reference

• Template is a saved page or section pattern.
• Page template is a full-page saved structure.
• Section template is a single-section saved structure.
• Per-site scope is the default — templates stay on the site they were saved on.
• Account-shared scope is the cross-site promotion (where the plan supports it).

Related reading