Dollie Editor SDK
Playground

Dollie Editor SDK guide

Copilot Boundaries

Let an AI assistant create useful page proposals without giving it an unrestricted code-generation path

A Dollie Editor Copilot composes Pages. It does not write arbitrary application code at runtime.

The Catalog gives the Copilot:

  • valid Section ids;
  • Field descriptions;
  • available Elements;
  • compatible Page Templates;
  • Catalog-specific guidance.

The Page definition gives it the current state.

The proposal loop

Understand request
    → inspect Catalog
    → fetch required Fields
    → propose Page or Section
    → validate
    → user reviews
    → apply

This loop is the same across Vercel AI SDK, Laravel agent integrations, and custom AI runtimes.

Full-page proposals

Use a full Page proposal when the user asks to:

  • create a Page;
  • replace the complete draft;
  • remix a Template;
  • make a structural change affecting many Sections.

The proposal contains a complete PageConfig.

Single-section proposals

Prefer a single-section proposal for a focused edit:

  • rewrite the hero;
  • add one pricing plan;
  • swap the illustration;
  • translate the FAQ;
  • change one call to action.

The Copilot returns the complete replacement Section at a known Page index. The editor validates it, shows a focused diff, and replaces that Section without rebuilding the rest of the Page.

Small proposals are easier to review and less likely to damage unrelated content.

Progressive Catalog lookup

Large Catalogs should not be copied into every prompt.

Start with a deterministic index of ids and names. Give the Copilot a Catalog tool that can:

  • list Catalogs;
  • list Sections;
  • fetch Section Fields;
  • list and inspect Elements;
  • search;
  • list and fetch Templates.

The Copilot requests detail only for content it intends to use.

The user remains in control

A proposal is not a save.

Your application decides whether:

  • the user must click Apply;
  • a role may publish;
  • a draft can be autosaved;
  • a Copilot may call Page tools;
  • a high-impact change needs another approval.

The recommended default is simple: Copilot proposes, Editor user decides.

Coding agents are different

A Coding agent works in the Integrator's repository. It installs the SDK, registers components, and changes application code.

A Copilot works inside the finished product. It creates and edits structured Pages for an Editor user.

Keeping those terms separate prevents setup instructions from being confused with runtime permissions.