I started working with Drupal in 2008, right around the time Drupal 6 was coming onto the scene.
I’ve carried sites through version after version since then, including the Drupal 7 to 8 rewrite. I’ve watched Drupal become more powerful, more sophisticated and more capable of running websites that organizations depend on every day.
I’ve also watched it make some things much harder than they needed to be.
That was always the tradeoff. With great power came... great complexity. But with Drupal CMS 2.0, the platform finally gets its hero arc.
Drupal could do almost anything, but getting all that power into the hands of the people actually managing the content often took more effort than it should have. Developers understood why Drupal was special. Editors did not always have the same experience.
That’s where Drupal CMS 2.0 enters the picture. It’s not just another version of Drupal.
It feels like Drupal has finally brought two things together that used to live much farther apart: serious engineering underneath and an editing experience that content teams can actually enjoy using.
Canvas changes the conversation
Drupal Canvas may be the part I am most excited about.
Canvas is now the default editing experience in Drupal CMS 2.0. Editors can drag components onto a page, see what they are building as they work and edit directly in context instead of bouncing back and forth between administrative forms and previews.
That sounds simple until you have spent years building CMS websites. The ability to give an editor a visual, drag-and-drop experience without giving up the structure underneath is more of a big deal than one may realize. An editor can work with things that make sense to an editor: a hero, a card, a testimonial, an accordion or a callout. Drupal CMS ships with reusable components for exactly those kinds of building blocks.
But developers are not giving up engineering discipline to make that possible.
Drupal’s Single Directory Components, or SDCs, provide a component architecture where a component’s metadata, markup and, when needed, CSS and JavaScript coexist. They are modular, reusable building blocks rather than one-off page constructions.
That matters because good visual editing should not mean chaos underneath, as visual builders lacking underlying structure often do.
The editor gets freedom while the organization gets consistency. And the developer? The protagonist in this story, still gets maintainable code.
That’s the balance I have wanted Drupal to reach for a very long time.
This is one piece of a longer reflection on Drupal CMS 2.0, more coming.