Drupal CMS, the result of the initiative first announced as "Starshot" in 2024, released its first version in January 2025. It packages Drupal 11 core with carefully chosen features so marketers, content teams and site builders can launch capable sites quickly, without assembling everything from scratch.
Drupal CMS vs. Drupal core
Drupal CMS is not a fork. It runs on standard Drupal core and the same contributed modules everyone uses. The difference is curation and experience:
| Drupal core | Drupal CMS | |
|---|---|---|
| Audience | Developers and architects | Marketers, content teams, site builders |
| Starting point | Minimal, build what you need | Ready-made features and sensible defaults |
| Built with | Modules and configuration | The same, assembled through recipes |
| Upgrade path | Standard Drupal | Standard Drupal |
What it brings
- Recipes: features such as blog, events, case studies, forms, SEO tools, accessibility tools and privacy basics are packaged as recipes you can add when needed.
- Project Browser: discover and add modules and recipes from inside the admin UI.
- Better defaults: an improved editorial experience out of the box.
- Optional AI: AI-assisted site building and content tools that can be enabled with your choice of provider.
- Visual page building: Drupal Canvas (formerly Experience Builder) is the direction for building pages visually from components.
When Drupal CMS is a great fit
- Marketing sites, campaign microsites and departmental sites that need to launch fast.
- Teams that want Drupal's security and flexibility without a large build phase.
- Organizations standardizing many smaller sites on a common baseline.
When to start from core instead
- Complex platforms with custom data models, integrations and workflows (portals, intranets, e-services).
- Decoupled or headless architectures where the front end is built separately.
- Projects with strict architectural standards you want to control from the first commit.
Even then, the recipes from Drupal CMS can still be reused selectively on a core-based build.
What it means for decision-makers
- Lower time-to-value: credible sites in weeks, not months, for standard needs.
- No lock-in: it is still Drupal; any Drupal partner can support it.
- Same upgrade path: it follows Drupal core's release cycle, so plan for Drupal 12 the same way.
Not sure whether Drupal CMS or a custom Drupal 11 build fits your project? Book a short consultation and we will give you a straight answer.