For 25 years, Drupal has provided the velocity builders need. However, trying to serve every audience with a single tool often meant compromise. The recent strategic distinction between Drupal Core and Drupal CMS has unlocked a new path: parallel improvements that embrace the specific ways different builders work.
With the arrival of Drupal CMS 2, the introduction of Drupal Canvas and Site Templates fundamentally changes the game. These tools shift the focus to visual, component-based building, allowing users to launch new sites with best-practice features already configured.
But what does this shift mean for the future of Drupal Core and the wider ecosystem? For those not using Drupal CMS (yet)—and for critical use cases like headless architectures, social platforms, and e-commerce—what is the path forward? What can developers and architects expect as we look toward Drupal 12?
Join us to discuss how catering to these distinct needs will shape the broader ecosystem and what the long-term implications are for the community.
High level concepts in the Drupal community are useful to know, but not necessarily required to understand the session.
- Why Drupal CMS?
- How Drupal CMS 2 ups the game?
- What does this mean for those using and not using Drupal CMS?
- Drupal 12 is also coming, this is confusing
- What do these mean for other parts of the ecosystem (themes, modules, distributions, etc)
- Who is Drupal core now for?
- Will Drupal CMS components be standard in the future?
- How is stability ensured alongside larger innovation velocity?
