Drupal CMS receives headless starters and why that's relevant if you are evaluating Storyblok!

If you are picking a CMS in 2026 for a JavaScript-frontend project, "headless CMS with a built-in visual editor" has yielded few options. Storyblok has owned the shape of that conversation for the past few years: it was built headless from day one, ships a polished visual editor, has field- and space-level i18n out-of-the box, and is Made in Austria, which makes for an easy procurement story in EU contexts.

That short list now has a second contender, one that is well worth looking into: Three Drupal-side milestones have converged into one usable story, and the last one landed just last month.

Sources: Drupal CMS 1.0 release · Drupal CMS 2.0 release · Drupal Canvas · lupus_decoupled_starter · drunomics/lupus-decoupled-nuxt-starter. Drupal side is covered by the Drupal Security Team; both starters are MIT/GPL-licensed.

Net effect: one install on the Drupal side, one on the Nuxt side, and a content team is dragging Canvas components onto a page that renders through a Nuxt frontend. The historical Drupal objection — "the API is great, but the in-product editor experience is not" — is the one that Drupal CMS 2 + Canvas + the lupus-decoupled-starter systematically closes.

What follows is a brief overview, not a full matrix. A more detailed comparison including additional CMS systems will follow in the coming weeks.

Storyblok's narrative of a typical team searching for that polished content API that can quickly be production-ready with a visual editor, is appealing. If that's the entire requirement, Storyblok remains a reasonable pick. Where Drupal pulls ahead is the depth behind the content layer, including structured-content primitives, a contribution module ecosystem that covers cases Storyblok plugins do not (e.g. Drupal's form API), the option to evolve into hybrid or traditional rendering later without changing platforms, and content that stays in standard formats rather than forced to use a vendor's schema.

Storyblok is a single SaaS product: Storyblok hosts the CMS, you pay a subscription. Pricing scales with seats, traffic, and feature tier — workflows and advanced roles are gated to the enterprise plan.

Drupal + the lupus-decoupled-* starters carry no hosting in the package. You pick the deployment shape:

• Self-host — zero license cost (GPL on the Drupal side, MIT on the Nuxt side). You pay for servers, ops, and patching cycles.
• Generalist managed Drupal hoster — Pantheon, Acquia, Platform.sh, Amazee.io / Lagoon, and similar. Infrastructure and patching handled; you still own configuration and code releases.
• Fully-managed Drupal SaaS — drunomics' mossbo is the closest like-for-like to Storyblok's posture: transparent monthly pricing (Cloud Lite €249, Cloud Pro €499, Enterprise custom), ISO/IEC 27001 EU hosting, AI inferences EU-only, security and major-version upgrades in the background, no per-seat fees, no feature gating by tier.

The honest trade-off: Storyblok gives you one pricing dial and one provider to call. The Drupal + Lupus path gives you platform freedom — but you (or your hosting partner) own the choice of where the site runs and how it stays patched.

Two repositories working hand-in-hand:

The two talk to each other through nuxtjs-drupal-ce. Drupal renders its custom-elements JSON; Nuxt picks up the components by name from the component-index. Decoupling without losing the editor experience.

The Nuxt-side components are deliberately skeleton — they demonstrate the contract; the design is yours to write. A frontend starter shouldn't lock you into someone else's design system.

The website documents two simple preview options:

• Drupal CMS - Nuxt Starter on DrupalForge
• DDev Setup documented on Drupal.org

drunomics has been shipping decoupled-Drupal + Nuxt for over a decade. The lupus-decoupled.org distribution is the upstream upon which all is built. The starter is the path we wished had existed when we onboarded teams in 2022 and 2023: a single repo to clone, the same wiring we use ourselves, no opinionated theme to fight, and a clear handshake with Canvas. It's also our answer to a question we keep getting from agencies and procurement teams."What do we hand a customer looking at headless options?" In 2026 that answer is simple: clone this, and you are running a Drupal CMS site with a Nuxt frontend before lunch, with the full Drupal toolkit available if your requirements grow.

• The overview: lupus-decoupled.org
• Nuxt side: drunomics/lupus-decoupled-nuxt-starter (start here; the README links to a Codespace).
• Drupal: drupal.org/project/lupus_decoupled_starter.
• Issues, PRs, ⭐ — both repos are open source. The Nuxt-side starter is the right place to file a Canvas-decoupled issue.

Clone it, try it, let us know what you think of it.