Browse documentation
Visual builder
Edit semantic page structure, responsive styles, reusable components, and content bindings.
Pages are semantic documents
The canvas represents a versioned document tree rather than a screenshot. Elements retain stable identities so selection, operations, history, collaboration, and publishing can refer to the same structure.
Use the canvas for direct manipulation and the inspector for exact values. Structural actions such as inserting, moving, wrapping, and deleting elements are validated before they become authoritative operations.
Design responsively
Set base styles first, then add breakpoint-specific overrides only where the layout needs them. Preview each supported viewport before requesting review.
Prefer layout constraints such as grid, flex, gap, min/max sizing, and intrinsic content flow over fixed coordinates. This keeps components resilient when content changes.
- 01
Build the desktop structure
Establish hierarchy and reusable layout constraints at the largest viewport.
- 02
Inspect tablet behavior
Adjust column count, spacing, and navigation before content becomes compressed.
- 03
Resolve mobile flow
Verify reading order, tap targets, overflow, and reduced-motion behavior.
Use reusable components
Create a component when a pattern should stay consistent across pages. Component instances can expose controlled properties while retaining a shared canonical structure.
Use variants for intentional visual or behavioral states. Avoid duplicating a component merely to change content that should be represented by a property or CMS binding.
Still need help?
Find recovery guidance or contact the DevAssistant team.