Rotterdam Tests Drupal’s Move Toward an Agentic, Production-Ready CMS

The useful part

Rotterdam Puts Drupal's Biggest Bets to the Test | TheDropTimes × Add as Preferred Source on Google It's a single step, just click the button below to open your Google preferences and tick the box beside TheDropTimes. Maybe later Add TheDropTimes as your preferred source on Google and get Drupal news and updates featured in your Google News and search results. 40 Rotterdam Puts Drupal's Biggest Bets to the Test 28 September 2026 Perhaps the most revealing thing about DrupalCon Rotterdam is that its programme does not tell one tidy story.

How it works

• Rotterdam moves quickly into hallucination, reviewer trust, orchestration, governed workflows and human control because production use raises harder questions about what an agent may do once it can act...
• Drupal CMS 2.0, Canvas, Recipes and AI-assisted tooling have changed the product presented to builders, but improved technology does not automatically change how Drupal is perceived beyond its existing...
• Follow The DropTimes on LinkedIn, X, Bluesky, and Facebook, or join #thedroptimes on Drupal Slack.
• Core contributors were still closing dependency, deprecation, testing, and release-note work as the window ended, and Drupal.org had not published a revised beta date by 21 September.
• Maintainers planning compatibility work therefore still have alpha1 as the latest Drupal 12 release while the November release-candidate and December stable milestones remain on the published schedule.

What to take from it

Those collisions matter because Drupal's next phase depends less on any one initiative succeeding than on whether these different bets can reinforce one another without carrying old friction forward. Connecting Drupal to models and agents is no longer the difficult part of the AI story. Digital sovereignty makes the question more demanding because Drupal is also being asked to apply its values inward.

Example or evidence

• Canvas has become central to Drupal CMS, yet Rotterdam will also put it against Display Builder in a real-world project.
• For Drupal teams, the sessions show how source grounding, institutional context, human review, sovereignty and existing platform architecture shape production AI.
• For Drupal teams, the sessions show how content models, governance, tests, team practices, and meaningful metrics can keep faster systems understandable and maintainable.
• Drupal is preparing to discuss its transformation into a production-ready Agentic CMS while another session asks, quite directly, why developers still do not choose Drupal.

Details worth keeping

Permissions, auditability, validation and human approval are becoming part of the product itself. If the Agentic CMS idea is going to mean more than a collection of AI capabilities, those boundaries have to become as deliberate as the capabilities they constrain. Adoption tests another part of the same argument.

Related coverage

• Thedroptimes: Big Blue Door's Rotterdam responses point to a question already being tested in councils and healthcare: how far can shared Drupal platforms be reused across organisations with different services, editorial...
• Thedroptimes: A workflow can report success and still be wrong, while a thriving community can quietly depend on too few people.
• Thedroptimes: Some Drupal problems begin with too much rather than too little: too much legacy HTML, hundreds of career choices and brand sites, or code generated faster than teams can understand it.
• Thedroptimes: What changes when Drupal becomes something an enterprise AI agent can act on, rather than the place where every user must work? Pantheon plans to show that model running end to end in Rotterdam.
• Tubantia: De nieuwe stadsbrug waar Rotterdam al jaren aan werkt, dreigt fors duurder te worden.