Dollie Editor SDK guide
What Your Application Owns
Keep storage, authorization, tenancy, branding, components, and publishing decisions in the host application
Dollie Editor is embedded infrastructure. It does not become the system of record for your SaaS.
The SDK owns reusable page-building machinery. Your application owns product decisions.
Responsibility boundary
| Dollie Editor owns | Your application owns |
|---|---|
| Editor shell and interactions | Which users can open the editor |
| Page and Catalog contracts | Which tenant owns a Page |
| Section renderer | React components and design system |
| Validation primitives | Additional business validation |
| Transport interfaces | Database and storage model |
| Reference stores | Production persistence |
| Capability flags | Role and entitlement decisions |
| Binding contracts | Which backend data may be exposed |
| AI catalog operations | Model, agent, prompts, and approvals |
| Proposal/apply seams | Save and publish authorization |
Storage stays host-owned
You decide whether a Page lives in:
- a JSON database column;
- a document store;
- a versioned content service;
- the Node file store;
- another backend.
The SDK does not create a tenant model or assume one Page table.
Authorization stays host-owned
Capability flags can hide or disable editor actions, but they are not a server security boundary.
Your backend must authorize:
- load;
- save;
- publish;
- revision restore;
- binding-source access;
- AI tools that read or change Pages.
Never trust the browser's capability object as proof of permission.
Components and branding stay host-owned
Your components determine:
- layout;
- typography;
- responsive behavior;
- animation;
- defaults;
- accessible markup;
- brand expression.
Dollie Editor supplies semantic UI primitives and a style contract for the editor surface. It does not replace the theme of published pages.
AI remains replaceable
The SDK can describe a Catalog and validate proposals without depending on one model vendor.
Your application chooses:
- the model;
- conversation storage;
- user context;
- rate limits and billing;
- which tools are available;
- whether applying or publishing requires human confirmation.
Adapters do not change the boundary
The Laravel adapter supplies framework-specific services and routes. It deliberately owns no Eloquent model, tenant, policy, or authentication decision.
An Adapter translates the shared contracts into a framework. It does not become the product.