Skip to main content
Webstorio supports two ways to build a site:

​
What each approach covers

Pages and layout
  • Dashboard: Build and edit pages in the AI builder and visual editor.
  • CLI: Edit React modules locally and deploy with webstorio push.
Feature schemas (structure) Schemas define the shape of CMS content types, Form & Survey forms, and App Data tables — not the entries, submissions, or rows themselves. Feature system pages Dashboard create page actions scaffold CMS list/detail, form, store, and auth routes from hosted templates. On the CLI, use webstorio generate to create equivalent local .tsx pages and register them in config (then webstorio push). Use the dashboard if you prefer a visual editor. Use the CLI if you want schemas in git next to your pages. You can start in either place — for example schema pull to bring dashboard definitions into the repo, or edit in the UI after a CLI push. → Feature schemas · Content & CMS · Forms · App Data Project data (entries and rows) CMS entries, form submissions, store products, and App Data rows are managed in the dashboard on either approach (or via MCP / the Client SDK where applicable). MCP does not replace either approach for creating or publishing page code. Runtime on the live site Published pages call window.webstorio the same way regardless of how you built them.

​
Recommendation

  • Prefer the dashboard if you will not maintain a local code repo.
  • Prefer the CLI if you want version control, shared components, local preview, zero deployment configuration, schemas in git, or your own editor / AI agent writing .tsx files.
  • Use MCP on top of either workflow to manage content and other project data from an agent.