Webiny Enterprise CMS+ ⚡️

How well does your CMS handle scale? Are you locked in to an expensive SAAS product that doesn't allow you the freedom to customize it around your business? Introducing Webiny. The Enterprise open-source CMS made for scale and control. youtube.com/watch?v=-KWwVt…

Yesterday we shared the `@nextjs` starter kit. Today — the full guide. A set of articles that walk you through setup and usage, step by step: webiny.com/learn/course/w… Build it. Understand it. 🚀

As mentioned yesterday, Website Builder in v6 works with multiple frameworks. To get you started, we’ve prepared a Next.js starter kit: github.com/webiny/website… Plug in your frontend. Keep full control. Add visual editing on top. More frameworks coming. 🚀

In v5, pages were built and served inside Webiny — with its own website app and prerendering engine. Powerful, but something new to learn. In v6, things change. Use any framework you want — Next.js, SvelteKit, Vue. And still get the in-admin visual editing experience. Your stack. Webiny editing. 🚀

📚 In v6, part of our documentation will be fully autogenerated reference docs. Always up to date. Structured. Ready to be consumed by developers. And yes — by AI agents too. Docs as an interface. 🚀

Feature flags in v6 give you real control. Enable or disable platform features per environment — directly in code. Turn off threat detection in non-prod. Disable audit logs locally. Keep production strict. Declarative. Environment-aware. Under your control. 🚀

We’ve been exploring oxfmt (and oxlint) and are looking forward to trying them out in the near future! 🎉 Congratulations to the team on reaching 1 million weekly downloads! 🎉 It’s an impressive tool for the JavaScript ecosystem. x.com/boshen_c/statu…

In v6, Page Builder becomes Website Builder. But here’s the real shift: The editor doesn’t own components or styles. It loads `your` frontend app (Next.js, SvelteKit, etc.) inside an iframe. Your real components. Your real styles. Webiny stores page structure. Your app renders everything. Framework freedom + visual editing. That’s the new foundation. 🚀

We use @rspack_dev and @tailwindcss at Webiny — so this will definitely come in handy for us. Love seeing improvements in the tools we rely on every day. 🚀 x.com/jait_chen/stat…

Defining your own custom permissions is now extremely straightforward, no matter how complex your permissions are. Simple, declarative API allows you to quickly add new custom permissions to Webiny v6, and have them instantly appear in your Roles and API Keys.

In v6, alongside the brand new Webiny SDK, we also built an SDK Playground. The SDK, in your browser. Already authenticated. Already tenant-aware. Zero setup. Instant execution. This is how experimentation should feel. 🚀

With the new code model builder, v6 also brings autocomplete to field renderers. You can now see exactly which renderers are applicable to the current field type, so no more guessing! 🎉 And you can also augment the interface with your own custom renderers! 🚀 #developerexperience #headlesscms

Webiny v6 isn’t just an upgrade. It’s a mindset shift. v5 → give you everything, let you configure it. v6 → give you what you need, let you extend it. Less overwhelm. More intention. Better foundations.

In v5, validators were defined via config objects and string rule names. In v6, validation is built directly into the field type. `text()` gives you `email()`, `minLength()`, `maxLength()` `number()` gives you `gte()`, `lte()` Typed. Autocomplete-driven. Just method calls. And these are just the built-ins — there are more available, and you can define your own. Same capabilities. Much better developer experience. 🚀

In v5, saving a simple contact form meant writing a manual GraphQL mutation. Now? It’s a single SDK call. No hand-written GQL. No custom wiring. No friction. Form → CMS → done. 🚀

In v5, when defining models via code, help text was just plain text. In v6, it supports Markdown — links, emphasis, richer hints… rendered automatically in Admin. Make your help text actually useful. Highlight important parts. Add links. Guide users properly. Small detail. Big DX win. 🚀

Webiny v6 delivers a proper solution for managing browser’s LocalStorage. Local storage can quickly become a mess if you don’t have a system around managing keys. In v6, you can safely run your localhost admin app for various deployments and tenants, and their local storage will be completely isolated, per deployment, and per tenant within a deployment. Keys are now also organized in proper namespaces that are easy to read. Better #developerexperience, less friction, easier context switching 🚀

File uploads are about to get a whole lot easier. 📦 No more manually generating S3 POST payloads. No separate GraphQL mutation just to register the file in the database. Just upload the file. 🚀 Yes — things like chunked uploads were technically possible before… but you had to wire them up manually. Powerful, but not exactly fun. Now that uploads are abstracted behind the SDK, we finally have the right foundation for smarter handling — chunking, resumable uploads, better retries, and more. The groundwork is in place.

Talking to Webiny APIs in v6 just got easier. 🧩 With the new Webiny SDK, interacting with Webiny’s GraphQL APIs becomes simple, typed, and ergonomic — no manual query building, no boilerplate. Initialize once, then work with CMS data using a clean, high-level API. Less glue code. More shipping. 🚀

Webiny v6 keeps the API Playground right where you expect it. Test queries, execute mutations, explore the API — just like in v5. Continuity first. Improvements under the hood.

Docs in progress 📚 Just wrapped up a big chunk of the `Headless CMS` section — 14 lessons deep, covering content models, content management, and the CMS API. Still writing, still refining. This is where a lot of real-world Webiny usage comes together.