Dollie Editor SDK guide

Page Templates

Start editor users from a complete compatible page instead of an empty canvas

A Page Template is a ready-made PageConfig with metadata describing what it needs.

Templates give Editor users a useful starting point while preserving the same Catalog and validation rules as a Page created from scratch.

What a Template contains

A Template normally includes:

a stable id;
a name and description;
the complete Page definition;
a computed list of required Section and Element ids;
optional vertical or use-case metadata.

The definition remains ordinary Page data:

{
  "sections": [
    { "component": "free-hero-split" },
    { "component": "free-feature-grid" },
    { "component": "free-pricing-tiers" },
    { "component": "free-faq-accordion" },
    { "component": "free-cta-banner" }
  ]
}

Compatibility before import

A Template can only render if the active Catalog contains its required content.

Check compatibility before offering Use template. The CLI import command can report missing requirements and can create a partial Page only when you explicitly request it.

Silent partial imports are dangerous because they can produce a page that looks complete in data but omits unknown Sections at render time.

Catalog templates and saved templates

A CatalogPackage can bundle curated Page Templates with the Sections they require. createCatalog gathers those templates as catalog.templates.

An application can also let Editor users create templates from their own Pages. Those templates use the same JSON contract, but the host owns their storage, visibility, and lifecycle. Dollie Editor does not assume that a user-created template belongs in a distributable Catalog.

Pass the templates for the current surface through PageBuilderEditorRuntime.templates. The Editor then offers its built-in picker. Applying a template to existing content requires confirmation and remains undoable.

Templates and Copilot remixing

A Copilot can remix a compatible Template while keeping its Section structure.

This works well when you want:

the same proven layout for a new industry;
new copy in another language;
customer-specific content;
a variation that preserves approved conversion structure.

The Copilot changes props and data within the template rather than inventing a new component tree.

Templates are content, not framework setup

The word Template also appears in CLI onboarding for framework choices such as Next.js or TanStack Start. Documentation qualifies these as integration templates.