Document model
Nodes, styles, pages, components, and snapshots.
The Mini Agency document is the source of truth for editor state. Pages, artboards, nodes, styles, components, collections, media, settings, agents, and tasks live in the document or adjacent workspace records.
Pages and artboards
A page represents a route and contains artboards. Artboards represent breakpoints such as desktop, tablet, and mobile. The desktop artboard is the master design surface; tablet and mobile store overrides where they differ.
Nodes
Nodes are typed objects in a tree. Examples include frame, text, image, button, form, input, menu, repeater, and componentInstance. Nodes have fields and styles. Fields store semantic values such as text, src, alt, fieldName, required, or submitActions. Styles store CSS-like presentation.
Components
A component is a reusable master. A component instance points to the master and can carry overrides. Headers and footers should usually be components because they repeat across pages.
Design system
The document design system stores tokens and classes. Tokens give values names. Classes let nodes share style groups. Codegen, canvas preview, public rendering, and MCP tools all read the same design system.
Collections
Collections store structured items. Pages can bind to collections for listing or single-item rendering. Tokens such as {{title}} and {{@url}} connect node content to item fields.
Snapshots and versions
Persistent mutations increment document version and can create version history. Undo in the editor is separate from durable version snapshots, but both rely on clean mutation boundaries.