For most of Drupal's history, the gap between "download Drupal" and "have a working website" was measured in days, not minutes. You needed to configure content types, set up workflows, install the right combination of modules, and build or buy a theme before the site was usable by non-developers. Project Starshot โ€” now released as Drupal CMS โ€” is the project's answer to that problem. And it's a genuine answer, not a cosmetic one.

1. What is Drupal CMS?

Drupal CMS is a curated distribution of Drupal 11 that installs in under five minutes and delivers a production-ready website with sensible defaults, a modern theme, pre-built content types, and an AI-assisted editorial interface. It is not a separate product โ€” it is Drupal 11 underneath, with a set of Recipes applied on top. This means:

  • All of Drupal's power is available when you need it
  • You're not locked into a proprietary distribution
  • Updates follow the standard Drupal release cycle
  • Any Drupal module works with Drupal CMS

2. How Recipes Power It

Drupal Recipes are configuration packages that can be applied to any Drupal site. Drupal CMS is effectively a collection of curated recipes applied during installation:

  • editorial_workflow โ€” draft / review / publish states with role-based permissions
  • content_types โ€” blog post, news article, landing page, event pre-configured
  • seo_tools โ€” Metatag, XML sitemap, redirect management pre-configured
  • performance โ€” caching, image optimisation, CDN-ready configuration
  • accessibility โ€” automated accessibility checks in the editorial interface
  • ai_assistant โ€” AI-powered content creation via the Drupal AI framework

Recipes are composable. If you don't want the blog content type, don't apply that recipe. If you want to add an events calendar later, apply the events recipe. The system is incremental and non-destructive.

3. What Ships Out of the Box

After a five-minute installation, Drupal CMS provides:

  • A polished, responsive default theme (based on Olivero, heavily customised)
  • A simplified admin toolbar and dashboard designed for non-developers
  • Blog, news, page, and event content types with fields pre-configured
  • Media library with drag-and-drop upload, image cropping, and focal point
  • CKEditor 5 with sensible toolbar defaults
  • Metatag and XML sitemap configured for SEO
  • Editorial workflow with draft, review, and published states
  • Role-based access: site admin, editor, author
  • Performance caching pre-configured
  • AI writing assistant (if API key provided)

4. The Installer Experience

The Drupal CMS installer has been redesigned from scratch. Gone is the multi-step technical form that asked users to choose database drivers. The new installer asks:

  1. Site name and language
  2. Admin account details
  3. Optional: AI provider API key

That's it. The rest is handled automatically. Hosting providers like Acquia, Pantheon, and Platform.sh have updated their one-click installers to offer Drupal CMS as a dedicated option.

5. AI Assistant in Drupal CMS

Drupal CMS ships with an AI writing assistant in the sidebar of every content edit form. Authors can:

  • Generate a first draft from a headline and bullet points
  • Improve tone, grammar, and reading level
  • Generate meta descriptions and social share text
  • Suggest related content to link

The assistant uses the Drupal AI module framework and supports OpenAI, Anthropic, and Gemini out of the box. All interaction is logged for audit purposes.

6. Who is it For?

Drupal CMS targets three audiences:

  • Organisations evaluating WordPress who want the simplicity of WordPress with Drupal's security, governance, and scalability
  • Existing Drupal clients who want a faster-to-deploy, easier-to-manage site for their marketing team
  • Agencies and developers who want a head-start on standard projects without building configuration from scratch

7. Developer Perspective

For developers, Drupal CMS is a starting point, not a ceiling. Everything that works in vanilla Drupal works in Drupal CMS. You can export all configuration to config/sync, deploy via Composer, manage with Drush, test with PHPUnit and Behat, and run the full CI/CD pipeline you'd use on any Drupal project. The only difference is that you started with a better baseline.