Open source · Built for shadcn

The visual editing layer for the shadcn ecosystem

Turn the React components you already own into a guarded page builder for your customers and Copilots. You keep the source, the design system, and the backend. Dollie adds the editing layer.

Open the playground Use your shadcn components

Agent-led setup

Start with the coding agent you already use

Give your coding agent the official Dollie Editor skill. It inspects your application, confirms the integration path, installs Dollie Editor SDK, and helps register the first component without replacing your architecture.

Copy the complete setup prompt

Terminal

npx skills add DollieAI/editor

Help me add Dollie Editor SDK to this application.

Install and load the official Dollie Editor skills, inspect this repository, and ask me to choose the integration path before changing anything.

Start with @dollie_ai/editor and the Core catalog. Preserve my components, styling, storage, authorization, and tenancy.

From source-owned components to customer-owned pages

shadcn changed how React teams adopt UI: you install source, shape it to your product, and keep control of the result. But source-owned components are still static until you build the editing system around them.

Dollie Editor SDK adds that missing layer. Register a component as a Section, describe the fields people may change, and compose those Sections into a serializable PageConfig. The same catalog powers the visual editor, renderer, validation, and Copilot.

Your application remains in charge. Layout and brand stay inside your components. Storage, authentication, tenancy, and dynamic data stay in your backend. Your users get a focused page builder instead of unrestricted access to your UI.

A page builder that follows your architecture

Dollie turns the pieces you already trust into one editing contract without taking ownership away from your application.

Source-owned components

Fixed first

Any complete component can become a movable Section before you expose a single editable prop.

Structured fields

Choose exactly which text, media, options, and repeatable items an editor user may change.

One PageConfig

The canvas, renderer, storage layer, and Copilot all work with the same serializable page definition.

Host-owned backend

Keep persistence, authorization, tenancy, and application data behind contracts your product controls.

Catalog-bound Copilot

AI proposes pages from approved Sections and structured fields, then validation checks the result before it is applied.

Choose the path that matches what you already have

Dollie Editor SDK works with application-owned components and distributable registries. You do not need to rebuild either one from scratch.

Bring the components in your application

Register existing shadcn-style components as fixed Sections, turn an existing page into a PageConfig, and expose editable props only where they add value.

Use your components

Publish an editor-ready component pack

Add Dollie metadata to a shadcn-compatible registry so Integrators can install owned source that is already discoverable by the editor and Copilot.

For component authors

One catalog, three ways to build

Your React components

Start with the UI you already have

A complete component can enter the catalog as a fixed Section. When users need more control, lift selected values into serializable props and define the matching fields.

Keep styling and layout in your source
Make components movable before they are editable
Add authoring controls progressively

Your product

Give customers a focused visual editor

Customers arrange approved Sections and edit only the fields you expose. Their work becomes a PageConfig your application can store, render, revise, and publish.

Drag, drop, duplicate, and reorder
Structured fields instead of arbitrary HTML
The host decides what can be saved or published

Your AI

Let a Copilot work inside the same boundaries

Give an AI agent catalog tools instead of an open canvas. It can discover available Sections, propose valid configurations, and help users create variations without inventing unsupported UI.

Catalog-aware tools and prompts
Validation before a proposal is applied
Human review remains part of the workflow

Use cases

Built for pages that belong inside your product

Use the same Catalog and PageConfig model for customer editing, personalized experiences, or an internal page workflow.

Customer-facing SaaS editors

Let customers compose on-brand pages inside your product using the Sections and fields you approve.

Build an embedded editor

Personalized landing pages

Turn a lead conversation into a tailored PageConfig assembled from your product’s approved Catalog.

Personalize the journey

Internal prototyping

Give teams a visual and AI-assisted workspace for building pages that stay within established patterns.

Equip your team

Questions builders ask first

Build a page from real catalog Sections

Open the playground, rearrange Core Sections, edit their structured fields, and inspect the PageConfig your application would store.

Open the playground