Browse documentation
Introduction
Understand how DevAssistant connects visual design, structured content, collaboration, and production publishing.
How DevAssistant works
DevAssistant treats a website as one connected system. Pages, reusable components, CMS content, review revisions, domains, and releases remain attached to the same workspace instead of becoming separate handoffs.
The visual editor changes semantic site documents. Preview and publishing compile those documents through the same runtime contract, so the layout reviewed by your team is the layout intended for production.
The core workflow
Most teams move through the same four stages. You can enter the workflow from a generated draft, a template, or a blank project.
- 01
Create a site
Choose a starting point and establish the page structure, styles, and content model.
- 02
Build and manage
Design responsive pages, create components, and connect structured CMS content.
- 03
Review a revision
Share an immutable review link and resolve feedback against a known version.
- 04
Publish a release
Build immutable artifacts, verify production readiness, and promote the release.
Workspace model
A workspace is the security and billing boundary for your team. It contains sites, members, invitations, plan limits, operational notifications, and workspace-level settings.
Each site contains its own pages, documents, components, CMS resources, assets, domains, review history, and releases. Access is evaluated against the workspace role and the requested site.
Recommended starting point
Create one workspace for a company or agency team. Use separate sites for individual brands, campaigns, or client projects.
Still need help?
Find recovery guidance or contact the DevAssistant team.