The DrupalCon Chicago 2026 Driesnote kicked off with a keynote that was equal parts celebration and wake-up call. With 1,310 attendees in the room and Drupal turning 25, Dries Buytaert delivered one of his most candid Driesnotes yet. He acknowledged a tough market, AI disruption hitting all sides of the Drupal ecosystem at once, and then laid out a concrete plan for what comes next.
This wasn’t the typical “look what we shipped” keynote. Dries shared personal stories, showed real working demos, and ended with a direct challenge to every person in the room. I want to walk you through the 10 things that stuck with me the most.
In this article:
- Drupal turns 25 — and Dries framed it as a graduation, not a party
- Drupal CMS 2.1 is here
- 11 site templates and a new marketplace
- The new agency pitch: AI to prototype, Drupal to build systems that last
- The Context Control Center — Drupal’s AI secret weapon
- AI-powered content creation: from a copy deck to a production-ready page
- AI agents that monitor content after you hit publish
- ECA module: one developer + AI = 90,000 lines of code in 6 weeks
- “Average is cheap. Expertise is priceless.”
- “Are you out or are you in?”
1. Drupal turns 25 — and Dries framed it as a graduation, not a party
Few open-source projects make it to 25 years. Dries acknowledged that and gave the room a moment to appreciate it — literally. He borrowed a tradition from Fred Rogers and asked everyone for 10 seconds of silence to think about the people who helped them get where they are. It was a surprisingly emotional start.
But the framing was deliberate. Dries compared Drupal’s milestone to a graduation: it’s something to celebrate, but it’s also the moment where the real work begins. He drew a parallel to Chicago itself — back in the 1850s, the city had such bad flooding that engineers literally lifted entire buildings with jack screws to rebuild the foundations underneath. And while buildings were being raised, business continued inside them.
That analogy set the tone for the whole keynote: Drupal is rebuilding its foundations right now, and the work doesn’t stop while that happens.
2. Drupal CMS 2.1 is here
The headline product announcement was the release of Drupal CMS 2.1, built on top of Drupal Core 11.3. If you want to understand the broader context of what changed in Drupal 11 and its features, we covered that in a separate post. On the core side, one number stood out: a 50% reduction in database queries for uncached pages over the last 18 months. That’s not a small optimization — it means every Drupal site in the world gets more efficient just by upgrading. This is something that doesn’t get enough appreciation. When you build on Drupal and keep it updated over the years, you get a constant stream of performance improvements, security fixes, and new features for free. No renegotiating contracts, no paying for the next tier. You just upgrade and your site gets better.
Drupal CMS itself is the adoption-focused distribution. Its whole purpose is to make Drupal accessible to people who aren’t Drupal experts yet. And there are early signs it’s working — Dries mentioned that more and more WordPress developers are showing up in the Drupal CMS Slack channel asking for help. A few WordPress folks even raised their hands in the room. That’s a signal worth paying attention to.
3. 11 site templates and a new marketplace
This one moved fast. A year ago at DrupalCon Atlanta, site templates were just a concept on a slide. At Vienna six months ago, there was exactly one. Now there are 11, and they launched alongside a brand new marketplace at marketplace.drupal.org.
The templates cover real use cases: nonprofits, education, events, healthcare, government, and SaaS. There’s a mix of free and premium options. The first premium template, Meridian, can be installed directly from Drupal CMS. All templates are built on Drupal’s open-source foundation regardless of whether they’re free or paid.
This matters for two reasons. For new users, it means you can start with a polished, purpose-built site and customize from there — similar to how Drupal distributions have worked for years, but now with a marketplace and a much lower barrier to entry. For agencies, it’s a new channel. The marketplace is designed to drive leads back to the template creators when users want customization work.
One thing worth mentioning: one of those 11 templates — Haven — was built with our involvement at Droptica. You can see our logo on the template page. It’s good to see that we’re not just writing about the Drupal CMS ecosystem, but actively building parts of it.
4. The new agency pitch: AI to prototype, Drupal to build systems that last
This was the demo that made the room go quiet. Dries showed a website built in 15 minutes using Lovable, an AI tool. No developer. No designer. No discovery process. No agency involved. And it looked great — cinematic, editorial, polished.
Then he showed what was missing. The content was embedded directly in the generated site. No structured data. No workflows. No permissions. No editorial backend. None of the things that make Drupal a secure and scalable platform for real organizations. It looked like a production site, but it was a prototype.
Next came the Drupal part. Using the Drupal Canvas CLI and a set of AI skill files, the team migrated the same design into Drupal CMS — with real components, structured content, editorial tools, and all the governance that comes with Drupal. That took about two to three hours, with an engineer reviewing the output.
Dries quoted a board investor who said that many startups begin with AI tools but move off them once they hit $1M in annual revenue. The implication for agencies was clear: the new pitch is “we use AI to prototype fast, and then we use Drupal to build systems that last.” Speed from AI, substance from Drupal.
What I liked about this demo is that it was honest. Dries didn’t pretend AI doesn’t work — he showed that it works brilliantly for prototyping. He just made the case that prototypes aren’t production systems, and that’s where Drupal comes in.
5. The Context Control Center — Drupal’s AI secret weapon
At DrupalCon Vienna, Dries showed a rough prototype of the Context Control Center. Six months later, it’s in beta — Kristen tagged it the night before the keynote.
The idea is simple but powerful: store your organizational knowledge inside Drupal — brand guidelines, writing tone, content strategies broken down by page type, buyer personas, even live KPI data — and let AI use that knowledge automatically when creating or editing content.
The system is smart about what it loads. When you’re building a product page, it pulls the product page content strategy and brand guidelines. It doesn’t load article guidelines. The right knowledge at the right time.
What’s coming next is even more interesting. The Context Control Center will connect to external data sources — Google Analytics, CRM platforms, other tools in your martech stack — so that AI works with up-to-date information, not last quarter’s numbers. Dries calls this “dynamic context.”
The pitch is: “create knowledge once, scale quality forever.” I think this could be a genuine differentiator for Drupal. No other CMS I know of has a comparable system for feeding organizational knowledge into AI-assisted content workflows.
This is also a feature we’re planning to leverage in upcoming versions of Open Intranet — our open-source intranet system built on Drupal. We have a number of AI-related improvements on our roadmap, and the Context Control Center fits perfectly into what we want to offer for internal company communication and knowledge management. If you’re curious about building intranets on Drupal, check out our overview of the best Drupal intranet modules.
6. AI-powered content creation: from a copy deck to a production-ready page
The Finrop demo from Vienna came back, and this time it was significantly more advanced. Finrop is a fictitious financial services company that Dries uses as a running example. Jordan, the marketing manager, needs to create a landing page for a new product launch. The product team sent her a Word document with copy. No design. No pixel-perfect mockup. Just text.
She feeds the document into Canvas AI. The system recognizes it as a product page, loads the relevant brand guidelines from the Context Control Center, and asks Jordan two clarifying questions before it starts building. It then maps the unstructured text into the site’s actual UI components — following typography, imagery, and brand voice rules.
Jordan refines from there: swaps stock illustrations for real photography, converts a section into FAQ accordions, adds cross-links to related product pages (the AI uses semantic search to find them), and generates structured data so the page shows up properly in Google AI summaries and ChatGPT.
If you want to see what’s already possible today, we wrote about Drupal AI modules for content creation and automated content creation with Field Widget Actions — both of which are stepping stones toward what was shown in this demo.
The key here is that AI didn’t replace Jordan. It gave her the equivalent of a full team — a designer who knows the brand, an SEO specialist, a developer who understands the component library — showing up instantly and doing the repetitive work so she could focus on decisions.
7. AI agents that monitor content after you hit publish
This was the part that got me thinking. Most content fails quietly. A page goes live, the team moves on, and nobody checks whether it’s actually performing. Dries called this out directly.
The new capability lets you mark specific pages as important and set performance thresholds — bounce rate, engaged sessions, downloads. A background AI agent monitors these metrics and flags problems when they appear.
In the demo, two weeks after the Finrop travel page went live, the agent detected underperformance. But it didn’t just flag the problem — it analyzed the page against the current Context Control Center and found that the sales team had updated the pitch deck with new competitive positioning after the page was published. That context didn’t exist when Jordan built the page. The agent proposed specific changes based on the new data and even caught a brand violation before the updated page went live.
The vision Dries described is an AI system that orchestrates across 10+ martech tools — analytics, CRM, content platform — and keeps your content aligned with what’s actually happening in the business. It’s early, but the direction is clear: Drupal wants to move from “publish and forget” to continuous, AI-assisted content optimization.
8. ECA module: one developer + AI = 90,000 lines of code in 6 weeks
Jürgen Haas, a long-time Drupal contributor and the creator of the ECA (Events, Conditions, Actions) module, showed what he built in just six weeks using AI.
First: in-context customization. You’re looking at a Drupal form. You click a lightning bolt icon on any field. A list of automation templates appears. Pick one, configure it, save. Done. No code. No separate admin UI. You just customized Drupal’s behavior right where you were already looking. This alone is a huge UX leap.
Second: a completely new visual workflow modeler built from scratch in React Flow, with testing and debugging built directly into the canvas. You can trigger events, play them back step by step, and see all the token data at each point.
The numbers: 90,000 lines of code. Over 300 commits. Full test coverage and accessibility included. Six weeks. One person.
Jürgen said these ideas had been on his to-do list for three years — submitted at the DrupalCon Pittsburgh innovation contest. He knew what Drupal needed and how to build it. He just never had the time. AI removed the friction. It didn’t design the architecture, decide how workflows should work, or understand the user problems. That came from Jürgen’s years of expertise. AI handled the scaffolding, generated tests, refactored code, and helped explore ideas faster.
Dries asked the room: “What if we had 100 more Jürgens?” I think that’s the right question. AI doesn’t replace expertise — it amplifies it. For us at Droptica, this wasn’t exactly a surprise — we’ve been working this way for months, and we’re keen to share what we learn. Recently we published drupal-agents-md — an open-source template that generates a project-specific AGENTS.md file for any Drupal project, so AI coding tools like Cursor, Copilot, or Claude Code understand your architecture, standards, and workflows from the start. It’s great to see the broader Drupal community embracing AI-assisted development like this. If this trend continues — and I believe it will — it means more features in Drupal core, in Drupal CMS, in contributed modules. More people building more things faster. That’s how Drupal gets even better.
9. “Average is cheap. Expertise is priceless.”
Dries introduced the concept of a “stable triangle” that has held Drupal together for 25 years: the product at the top, agencies and the ecosystem on one side, and the open-source community on the other. His worry — and the thing keeping him up at night — is that AI is disrupting all three legs simultaneously.
He brought Aiden Foster on screen to talk about the agency side. Aiden has been running Foster Interactive for 17 years. By mid-2024, AI had built what he called “a sense of dread in my stomach.” His entire agency was optimized to take big projects, slice them into bite-sized chunks, and give them to specialists. AI made that production work a commodity.
But instead of panicking, Aiden got deeply involved in the Drupal AI initiative and reached a clear conclusion: “The bottleneck isn’t production anymore — it’s creativity, strategy, and judgment.” Those are innately human. His advice to agencies: start extracting your clients’ organizational knowledge. Get it out of people’s heads and into a system. The organizations that get this right will outcompete the ones who just delegate everything to AI and the ones who don’t use AI at all.
Dries also warned the community about AI slop in contributions. More AI-generated patches are landing on maintainers’ desks, and quality is dropping. His rule was simple: don’t submit code you don’t understand. “Contribute is not the same as contribute.”
A Drupal Pivot event for agency leaders is coming to Cambridge (near Boston) in a couple of months. If you’re running an agency and feeling the pressure, that seems like a practical place to start.
10. “Are you out or are you in?”
Dries closed with a personal story I hadn’t heard before. About 20 years ago — six years into Drupal’s life — he collapsed from stress while walking his dog at night. The pressure of scaling Drupal as a side project while finishing his PhD and starting a family had built up until it broke him. His mom asked if Drupal was the right thing for him. He considered getting a safe job at a Belgian bank.
Instead, he took a month off and approached the problem like an engineer. He wrote to open-source leaders — Tim O’Reilly, Chris DiBona (then at Google), Larry Augustin (VA Linux), Martin Mickos (MySQL) — and asked if he could visit them in California. They all said yes. He also emailed Linus Torvalds, who wrote back a long reply with advice like “worrying about making it big is a waste of time” and “pick the interesting stuff and let others take care of the rest.”
Dries chose to go all in. He went from being an accidental leader to a deliberate one. And then he asked every person in the room to make the same choice now. “Are you out, or are you in?”
The call to action wasn’t just emotional. He listed concrete next steps:
- Drupal Pivot event in Cambridge (Boston area) for agency leaders — coming in May.
- Drupal AI Summits in Paris and New York City (May 14, 2026).
- DrupalCon Rotterdam — September 28 to October 1, 2026.
- DrupalCon Orlando — March 22-25, 2027.
- A new Drupal Can Conference somewhere in Canada in summer 2027.
As for us at Droptica — we’re definitely in. We see how AI can make Drupal an even better engine for building systems that run for years and evolve for years. And that’s what organizations actually need to meet their business goals: solid, maintainable systems with real backends, real workflows, and real governance. Not a frontend prototype with no backend or a minimal one that breaks the moment requirements get serious.
What does this mean for the Drupal ecosystem?
This Driesnote felt different from previous ones. It was more honest about the challenges and more concrete about the path forward. If I had to summarize it in one sentence: AI is disrupting everything Drupal was built on, and Drupal’s answer is to use that same AI to rebuild stronger.
The product is moving fast. Drupal CMS 2.1, the marketplace, 11 site templates, the Context Control Center in beta, AI content creation that actually works. A lot of the AI features shown at the keynote are in alpha or beta now, and Dries hinted that several could reach stable releases by DrupalCon Rotterdam this fall. That’s the milestone to watch.
The agency model is evolving. The shift from production work to strategy and knowledge work is real, and this isn’t just happening in the Drupal world — it’s the same across the entire custom software development industry. Drupal is positioning itself as the platform that helps you put that expertise to work at scale.
And the community needs people who go deep, not wide. Quality over volume. Expertise over average.
If you’re evaluating Drupal for a new project or you’ve been in the ecosystem for years, this is a pivotal moment. I’d recommend keeping an eye on the Drupal AI initiative and trying Drupal CMS 2.1 yourself.
Need help building on Drupal?
At Droptica, we’ve been working with Drupal for over a decade — building enterprise platforms, intranets, and complex web applications. We’re actively contributing to the Drupal CMS ecosystem (including the Haven site template) and using AI to accelerate our development workflows every day.
Whether you’re starting a new Drupal project, migrating from another platform, or figuring out how AI fits into your content operations, our team can help. Visit our Drupal development services page to learn more about how we work, or contact us directly to discuss your project.
