.tsx files in your editor, shared components, version control, and a live
local preview. When you’re ready, one command syncs everything to a Webstorio
project where the server compiles and hosts it.
Alpha — the Webstorio CLI is in active development, so commands and
configuration may change between releases. See the CLI
changelog for what’s new, and share feedback at
[email protected].
How it works
Pages and components are standard React (.tsx) — there’s no bespoke
framework to learn, just React plus the
window.webstorio SDK. A Webstorio site is a small set of files:
- a
webstorio.config.tsthat lists your pages and components, - one
.tsxmodule per page (each with adefaultexport), and - shared components you import from your pages.
push, the CLI composes each page into a single self-contained
module — inlining your relative imports (like Testimonials) and keeping
first-class packages (React, lucide-react, …) as imports. Installed
browser-compatible packages outside that set are bundled into the module. It
uploads only that code; the Webstorio server compiles it authoritatively
into the stored HTML. The CLI never uploads compiled output, so what you see
live always matches what the platform produced.
Production compilation always happens on the Webstorio server. The CLI only
composes and uploads source
code.Install
webstorio binary. Because the published package is
@webstorio/cli, the first (pre-install) command has to name the package in
full; once the CLI is a dependency of your project.
Quickstart
Next steps
- Project structure — folders and what goes where
- Local development — preview and data modes
- Routing — slugs, nested paths, and
{param}wildcards - Deploying — login, status, push, and publish
- Feature schemas — CMS / forms / App Data in
schemasDir - Configuration and Commands — reference
- CLI, MCP, and SDK — how the pieces fit
- CLI changelog — release notes