Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
This is a maintenance release that contains bug fixes, improvements for Mercury, minor improvements for contributors and developers, and bumps the minimum required version of Drupal core (for security hardening).
Drupal CMS 2.1.0 introduces first-class support for free and premium site templates. The installer was completely refactored and now presents a site template selection step with screnshots, descriptions, links, and support for purchasing premium templates. The drush site:export and Blank site template offer an easy way to export the current site as a site template recipe.
This release also ships default DDEV configuration and a generic AGENTS.md in the project template.
We've been busy fixing bugs and adding new features to help site template creators. In particular, we added a new Blank site template which, as you might expect, is a blank slate. You get all the Drupal CMS functionality you know and love, including Drupal Canvas, but with a blank theme (based on core's starter kit) and no content except for the bare minimum. If you really want to start from scratch, this is a great place to start from.
Drupal CMS 2 is a new version that includes Drupal Canvas, the first site template, and a number of other enhancements.
Key features
Drupal Canvas integration
Drupal CMS introduces Canvas as the default editing experience, providing true drag-and-drop with live preview and real-time editing. The custom built Mercury component library provides common building blocks like cards, testimonials, heroes, menus and accordions.
Drupal CMS 2.0 is nearly upon us. But before that, let us revel in a week of release candidacy.
A number of bugs were fixed, but we were mostly focused on refining and improving the Byte site template and its theme. But we did make a few notable changes:
Another beta! So soon, you ask? Why, yes...we're fastcool like that. We fixed several bugs that surfaced in beta1 when Drupal core 11.3 was released, and added one great feature to the administrative UI.
As per usual with pre-releases, this release should be used for testing only and is not suitable for building websites. There is no update path for Drupal CMS.
To spin up a Drupal CMS project, use the following commands:
This beta release of Drupal CMS 2.0 includes improved integration with Canvas, an updated component library, and many bug fixes. This release should be used for testing only and is not suitable for building websites. There is no update path for Drupal CMS.
To spin up a Drupal CMS project, use the following commands:
This alpha release of Drupal CMS 2.0 includes tighter integration with Canvas, and many bug fixes. This release should be used for testing only and is not suitable for building production websites.
To spin up a Drupal CMS project, use the following commands:
The alpha version of Drupal CMS 2.0 includes Canvas integration and two site templates: Starter and Byte. This release should be used for testing only and is not suitable for building production websites.
To spin up a Drupal CMS project, use the following commands:
This is mostly a maintenance release of Drupal CMS. There aren't too many user-facing changes, but there are some under-the-hood enhancements to make life easier in the future, clear the way for Drupal CMS to be truly multilingual, and increase compatibility with more hosting platforms. This version also requires Drupal core 11.2, which has its own set of shiny new things.
We fixed bugs too, but almost all of those bug fixes are also in the 1.0.x releases, so take a look at those for more details.
Recipes have no update path; the change records provide instructions to make manual configuration changes to an existing Drupal CMS site. You do NOT need to make these changes if you don't want to; your site will continue working as it currently does.
Recipes have no update path, so instructions are provided for manually making the appropriate configuration changes to address certain bugs. You do NOT need to make these changes if you don't want to; your site will continue working as it currently does.
See the change records for information on the configuration changes that have been made in this version, and how you can implement them on your Drupal CMS site.