What Is a Page Template?

A page template is a complete page saved as a reusable blueprint. It captures the full page as it was when published: every region, every block, layout settings, page variables, and connected data sources. When a new page is started from a template, it receives a deep copy of all of that content — a ready-to-edit starting point that already reflects your team's patterns and design standards.

Templates are not limited to pages. Modules and walkthroughs can each be saved as templates using the same mechanism. The concept and workflow are identical across all three.

Note: A page template is a blueprint used once at creation time. After a page is created from it, the two are independent — changes to the template do not flow to pages already built from it. A template component is different: it is a reusable component that pages embed and keep referencing live. Do not confuse the two.

What a Template Record Stores

Every saved template holds the following information:

The Template Library

The template library is the central place to view, manage, and create templates. Access it from the application's main menu or from within the page builder.

The library has two tabs:

Each entry in the list supports the following actions:

Creating a Template from Scratch

Use this approach when you want to define a template before building a specific page — for example, to establish a standard layout pattern your team will reuse across many new pages.

1. Open the template library: Navigate to the template library and click Create page template. A setup stepper opens.

2. Choose Platform: Select Web or Mobile. This determines which template picker the new template appears in when teammates are creating pages.

3. Choose Kind: Select Page, Module, or Walkthrough. Most teams creating page templates select Page here.

4. Choose Base Device: Select Desktop, Tablet, or Mobile. This records which breakpoint the template was primarily designed for — it does not restrict usage, but it informs teammates browsing the library.

5. Fill in Details: Enter a Name and an optional Description. The name appears in the template picker. A clear, descriptive name helps teammates quickly identify the right starting point.

6. Finish and build: The new (empty) template record is created. You can then open the associated page in the builder to design the layout that will be captured when you publish the template.

Publishing an Existing Page as a Template

This is the most common workflow. You build a page, are happy with its design, and want to save it as a reusable blueprint for future pages.

1. Open the page in the builder: Navigate to the page you want to save. The page must be fully built — the template captures a snapshot of the current state.

2. Open the page menu in the Hierarchy panel: In the block hierarchy (left panel), locate the root page entry. Click its overflow menu (…) to open page-level actions.

3. Click "Publish as template": A dialog opens asking you to fill in the template's metadata. Once published, this menu item changes to Manage template — indicating that this page is now linked to a template record.

4. Fill in metadata: Complete the following fields:

5. Click Publish: The template is saved and immediately appears in the Custom tab of the template library. It is now available for any teammate to use when creating new pages.

Updating a Published Template

After a page is linked to a template, you can update the template at any time to reflect improvements made to the page design.

1. Make changes to the linked page: Edit the page in the builder as you normally would. The linked template is not updated automatically — you must trigger an update explicitly.

2. Open "Manage template" from the page menu: In the hierarchy panel, open the page's overflow menu and select Manage template. This opens the template management dialog.

3. Click Update / Sync: The template record is updated with the current page content and settings. The preview image is refreshed if you recapture it. Metadata (name, description, tags) can be edited here as well.

Warning: Updating a template does not modify pages that were previously created from it. Each page is an independent deep copy. The update only affects future pages created from the template after the update.

Unlinking a Page from Its Template

The link between a page and its template can be broken. Once unlinked:

• The page continues to exist and function normally — nothing about the page itself changes.

• The template continues to exist independently in the library.

• The page's hierarchy menu reverts from "Manage template" back to "Publish as template."

• Future republishing from this page would create a new, separate template record rather than updating the old one.

Starting a New Page from a Template

When creating a new page, you can choose an existing template instead of starting from a blank canvas.

1. Start creating a new page: From the Navigator panel or the page list, click Create New Page (or the equivalent add page button).

2. Choose a template instead of Blank Page: The page setup dialog shows a template picker with two tabs: Custom (your team's templates) and System (built-in starters). Browse by visual preview or filter by tag. Select any template to use it as the starting point.

3. Complete page setup: After selecting the template, fill in the standard new-page fields: page name, parent folder, slug, privacy setting, and whether to add the page to navigation.

4. Start building: The new page opens in the builder pre-populated with the template's layout, blocks, variables, and settings. From this point the page is completely independent — edit it freely. Changes to the original template or the page it came from will not affect this new page.

Tip: Creating a page from a template is a one-time deep copy operation. The new page shares no ongoing connection to the template. You are free to modify every detail of the new page without worrying about affecting the template or other pages built from it.

Templates for Modules and Walkthroughs

The same templating mechanism works for modules and walkthroughs. The workflow — publish from the hierarchy menu, manage and update from the same menu, browse from the library — is identical. When browsing the template library, filter by Kind to show only Page, Module, or Walkthrough templates.

Best Practices

Tip: Build your first few pages by hand, settle on patterns that work well, then publish those pages as templates. Every subsequent page benefits from a tested starting point rather than reinventing the layout.

Tip: A visual preview dramatically speeds up template discovery in the picker. Teams with five or more templates will thank you for a clear screenshot instead of a blank placeholder.

Tip: Use consistent tag conventions across your team — for example by department (sales, operations), layout type (list, detail, form), or platform (mobile, web). Tags appear as filters in the template picker.

Warning: If you need a reusable component that all pages stay in sync with, use a template component — not a page template. Page templates are blueprints for initial creation, not a propagation mechanism for ongoing design changes.

Quick Reference