ResultSpace
Editor

Templates

Reuse whole pages or single blocks — with their AI commands — and move pages between organizations as JSON.

Templates come in two kinds: page templates (a whole page, captured with its AI commands) and block templates (a single saved block). Both are stored per organization.

The Pages screen

The Pages screen puts your pages list first. Below it, Page templates and Sections are foldable panels: expand Page templates to reuse or manage templates, or Sections to organize your pages. Collapse either panel when you want to focus on the list. The Pages help link opens this guide.

Page templates

Saving a page as a template

Open the page in the editor and choose Save as template from the topbar's More (⋯) menu or the Actions group of the Page rail section, then give it a name and an optional description.

The template captures the page's blocks and its AI commands — the badges in the templates list show what is inside (for example "9 blocks · 1 AI command").

Managing templates

Expand the Page templates panel below the pages list to see your organization's page templates:

  • Create page starts a new page from the template;
  • Rename changes the name or description;
  • Delete removes the template (pages created from it are unaffected).

Creating a page from a template

Two entry points: expand Page templates on the Pages screen and choose Create page, or use the Start from template picker in the New page form (page templates are listed first, with their block and command counts).

The new page starts as a private draft with fresh copies of the template's blocks — identifiers are regenerated, so nothing collides — and the template's AI commands. A template without commands still yields a page with the default "Draft with AI" command.

Composing a page

The Composition group contains four layout blocks:

  • Page section creates a top-level band with an optional heading, background, content width and vertical padding. It cannot be nested inside another block.
  • Stack groups blocks vertically and controls their gap and alignment.
  • Card adds a surface, padding and an optional title around related blocks.
  • Columns arranges children into two or three columns, then one column below 768px in the same reading order. Columns cannot be nested inside Columns.

Drop blocks into a container's children area. Nested content stays part of the page when copying, importing or exporting. Composition is bounded to four container levels, twelve children per slot and 120 blocks per page; the editor shows limit hints and invalid imports are refused rather than silently truncated. Empty untitled sections and cards do not appear on published pages.

Use the Page rail's Density setting for consistent horizontal and vertical spacing. See Appearance and Branding for organization defaults and per-page overrides. Inserting content from a template keeps the destination page's color and density choices.

Editing text blocks

Select a Rich text block on the canvas to edit its Content in the properties panel. Older plain-text blocks load their existing text into that editor, including blocks nested inside cards and stacks. Existing rich formatting is retained. Clearing Content removes the text rather than revealing an older plain-text copy. Changes are saved as a new draft; publishing remains a separate action.

Block templates

Inside the editor, the Templates section of the left rail saves the currently selected block for reuse:

  1. Select a block on the canvas.
  2. In Templates, give it a name (description and tags optional) and save.
  3. To reuse it, pick it from the same section and choose whether to insert it before or after the selected block (or at the end).

Inserted blocks always receive new identifiers, so a template can be inserted into any open page any number of times.

AI commands

The assistant header's AI commands menu contains saved prompts for the page. Draft commands pre-fill the AI draft dialog; chat commands send their prompt into the current conversation. Save any command as a personal preset and insert it on another page you can edit.

Commands belong to the page and are captured with its page template. For creating, editing, and reusing commands, see AI Assistant — AI commands.

Import and export

Moving pages between organizations

  • Export: on the Pages screen, open a page's actions menu and choose Export JSON. You get a portable <name>.page.json file with the page's blocks and commands — no organization-internal data is included.
  • Import: in the New page form, press Import from JSON and pick an exported file. A new private draft is created with the file's blocks and commands; identifiers are regenerated, and block types unknown to this deployment become visible placeholder blocks instead of disappearing.

Only staff can export and import; every import is recorded in the audit log.

In-editor snapshot

The Import / Export section of the editor rail exports and restores the current page's content as JSON — useful as a quick backup before risky edits. It keeps block identifiers, so restoring returns the page exactly as it was.

On this page