What changed in the lean web stack

Release 0.311.0 lets users copy and paste design tokens across projects and stops malformed styles from blocking publishing. Release 0.309.0 (30 Oct) let project owners use Content mode and allowed ES module asset uploads. Release 0.310.0 (6 Nov) improved advanced styles and CSS variables.

Why it matters: Reusing tokens across client projects makes it easier to keep a shared agency design system.

Webstudio 0.306.0 introduced a new Form component and fixed a server-side request forgery (SSRF) issue in the resource loader. Follow-up releases 0.307.0 to 0.310.0 (24 Oct to 6 Nov) added customisable form progress feedback, field reset after submission, structured error codes and documentation for a self-hosted email API.

Why it matters: Contact and lead forms without a third-party form service are a common agency need; the SSRF fix is a reason to make sure self-hosted builds are updated.

Release 0.294.0 added a dark Builder theme, Content Block creation from MDX files and a review step for unused assets before deletion. Release 0.298.0 (11 Sep) made the publishing allowance scale with workspace seats and restored Cloudflare publishing with Wrangler 4.

Why it matters: Teams on workspace plans get more publishes as they add seats, and self-hosters who deploy to Cloudflare can publish again.

Oleg Isonen admits that for some simple sites an agent alone may be enough. He argues that Webstudio's value is the workflow after the first version: content-only client access, workspace permissions, publish checks, hosting, and editing the same project through either the Builder or MCP. He also says the Content Engine is deliberately not an enterprise CMS.

Why it matters: This is a useful way to frame client conversations about AI-built sites compared with managed visual projects.

The Content Engine turns Markdown frontmatter and JSON files into queryable data with filtering, sorting, pagination, references and slug-based dynamic pages. Webstudio moved its own blog off Ghost onto it. Source files sit in R2 and only a compact metadata index is compiled at build time.

Why it matters: Blogs, docs and portfolios no longer need a separate headless CMS subscription, and the content stays as portable files.

Webstudio says it re-engineered its core runtime so that the visual editor and MCP read, change and build the same project, with no separate AI copy of the site. The MCP runs locally through the Webstudio CLI and can build, preview, drive a browser and take screenshots so agents can check their own changes. It works with any capable MCP client, such as Codex, Claude Code, Cursor or VS Code.

Why it matters: Agencies can let an agent handle bulk edits and still hand the client a project they can edit visually, without paying for vendor-hosted agent compute.

Release 0.274.0 lists two features: multiselect in the Builder and an 'API and CLI for everything'. The releases that followed in July and August repeatedly harden MCP workflows, for example runtime contract guardrails for MCP (0.275.0) and Cursor-compatible MCP tool names (0.283.0).

Why it matters: This is the base for editing Webstudio projects from coding agents and scripts, which lets small teams automate repetitive site work.

Release 0.269.0 added page templates, copy-paste for pages, folders and page templates, timezone selection for the Time component and greedy redirects. The earlier 0.268.0 release (1 June) added basic authentication, plain-text page support and the option to stop content editors from cloning projects.

Why it matters: Page templates and password protection speed up multi-page client builds and staging reviews.