At DrupalCon Chicago 2026, the Drupal Community Working Group was honored to announce April Sides as the recipient of the 2026 Aaron Winborn Award. Named in memory of longtime contributor Aaron Winborn, this award recognizes individuals who embody kindness, integrity, and a deep, above-and-beyond commitment to the Drupal community.

About April Sides

April Sides truly embodies the spirit of the Aaron Winborn Award through the care, consistency, and intention she brings to everything she does in the Drupal community. She has been a driving force behind initiatives like A11yTalks and Drupal Camp Asheville, while also contributing to programs like MOSA and serving on the CWG Community Health Team to foster a more welcoming and supportive space for all. As a speaker, trainer, organizer, and volunteer at nearly every camp she attends, April shows up again and again for this community. Her work is grounded in accessibility, inclusion, and genuine care for people, and her impact is felt not just in what she builds but in how she supports and uplifts everyone around her.

Heartfelt Nominations

April is not just a stellar professional. They are a habitual contributor. Serving their local Drupal community and now serving on a non-profit board over Drupal events, April is an inspiration. When I think of April, I remember how they brighten the room, with humble fashion sense, making the multitudes of duties seem easy.

April Sides deserves the Aaron Winborn Award because she consistently shows up for the Drupal community with care, integrity, and a deep sense of responsibility for the people in it. April does the kind of work that often goes unnoticed, not because it isn’t important, but because it’s rooted in trust, discretion, and kindness. She makes space for people when they need it most and does so without expectation of recognition. Over the years, I’ve seen April take on some of the hardest and emotionally demanding roles in our community, including event leadership, community health work, and serving as a code of conduct contact. These roles require empathy, patience, and fairness, and April approaches them in a way that makes people feel heard and supported. When situations are complicated or uncomfortable, she listens, she helps, and she follows through. April’s commitment goes beyond maintaining community spaces. She actively works to make them better. April leads with kindness and integrity, and her quiet, consistent dedication has made the Drupal community a safer, more welcoming place for so many of us.

April is such a great person and cares so much about the community. She's an organizer of the second best DrupalCamp in the world (which is no small feat). I believe that camp would not exist without her hard work.

Award Creation

Special thank you to Annertech and CSGov in Czechia for creating and delivering the award this year.

Take a look at how the award was made.

About the Aaron Winborn Award

The award is named after a long-time Drupal contributor who lost his battle with ALS in 2015. This award recognizes an individual who, like Aaron, demonstrates personal integrity, kindness, and an above-and-beyond commitment to the Drupal project and community.

Previous winners of the award are  Cathy Theys, Gabór Hojtsy, Nikki Stevens, Kevin Thull, Leslie Glynn, Baddý Breidert, AmyJune Hineline, Angie Byron, Randy Fay, Mike Anello, and Kristen Pol. Current CWG Conflict Resolution Team members, along with previous winners, selected the winner based on nominations submitted by Drupal community members.

Nominations for next year's award will open in early 2027.

The Drupal CMS track is back at DrupalCon Europe! Whether you are a site builder, a contributor, an agency leader, or someone just getting started with Drupal CMS, this is the place to share your story, learn from others, and help shape the future of Drupal CMS together.

From Barcelona to Rotterdam

What began as a mini-track at DrupalCon Barcelona 2024 has quickly grown into one of the most popular tracks at DrupalCon Europe. In Vienna 2025, the track showcased the journey toward Drupal CMS 1.0 — and the community responded with enthusiasm, filling sessions and sparking conversations across the event.

          ^{Foto by PD Johnson}

Now, with Drupal CMS continuing to mature and gain adoption, DrupalCon Rotterdam 2026 is the perfect stage to highlight real-world experiences, new features, and the road ahead.

What We Are Looking For

We are interested in hearing from the innovators who are driving Drupal CMS development as well as organisations adopting Drupal CMS on topics such as:

• ​Amplify first impressions, onboarding, and quick wins for those getting started.
• ​Refine the conversation around site building, recipes, and extending functionality.
• ​Reframe the experience of moving from other platforms or upgrading from classic Drupal.
• ​Showcase how to get involved and why your contributions make an impact.
• ​Share case studies and lessons learned from real-world projects in production.
• ​Define the vision, roadmap, and community direction for the future.

Submit Your Session Proposal

Submit your session proposal today! Visit the DrupalCon Rotterdam 2026 website to submit your proposal. Whether it is a talk, a panel, or a hands-on workshop, we want to hear from you.

Meet the Track Team

The Drupal CMS track is organized by a dedicated group of community members. This year's track team includes:

• Jeremy Chinquist
• Vladimir Roudakov
• Dan Lemon

Check out all tracks and track team members here. Have questions about the track? Reach out to us on Drupal Slack or e-mail Kuoni. 

DrupalCon Europe Rotterdam 2026 is shaping up to be an incredible event. The Drupal CMS track is your opportunity to contribute to the conversation, share what you have built, and connect with the community. We look forward to seeing you in Rotterdam!

Author: Priyanka Jeph

At DrupalCon Vienna, Dries Buytaert opened his keynote with a question the room was already asking: what happens to Drupal in a world full of AI?

He answered with a live demonstration showcasing three things the initiative had built and shipped:

• Pace of delivery: pages that used to take hours now get built in minutes. 
• Brand and voice control: a new Context Control Center feature lets teams set their brand voice once, and every AI agent applies it. 
• Governance at scale: autonomous agents scan the site, find internal references, and propose updates.

The keynote highlighted an important aspect: humans stay in the loop and approve every change before anything goes live.

The Drupal AI Initiative arrives in Chicago with more to show

Since Vienna, 10 new organisations have joined as partners, bringing the total to 31. The initiative has now secured the equivalent of $1.5 million in combined support, comprising both direct funding and a committed contribution of 50 staff dedicated to advancing the work.

What is most exciting to me is not just what we’ve built, but how we’ve built it. With a growing group of contributors and more than $1.5 million in funding, this is now a coordinated effort to bring AI into Drupal in a way that is open, trusted, and built to last.

Dries Buytaert 

A portion of funds is being invested in delivery management. The initiative conducted a formal Request for Proposal (RFP) process to appoint delivery partners responsible for coordinating work across both the innovation and product development streams. QED42 and 1xINTERNET were selected to lead the innovation and product development work streams respectively.

Progress is also visible in what has shipped since Vienna. Drupal AI 1.2.0 came first. MCP support followed. Drupal CMS 2.0 launched with Canvas as the default editing experience.

Drupal AI 1.3.0 introduced governance controls, editorial workflows, and production visibility for organisations running AI seriously.

Dedicated AI Marketing Leads Appointed

With the increased momentum in development it has been essential to scale marketing capacity. Paul Johnson announced the appointment of 10 marketing leads. Each will specialise on delivering specific key elements of the marketing strategy.

• Media Relations: Pritam Prasun, Open Sense Labs
• Social Media: Amber Henry, Morpht
• Webinars: Matthew Saunders, Amazee.io
• Events: Paul Johnson, 1xINTERNET
• Sales Enablement: James Tillotson, 1xINTERNET
• Case Studies: Rosie Gladden, ImageX
• Existing Capabilities: Duncan Worrel, Zoocha
• Upcoming Roadmap Capabilities: Will Huggins, Zoocha
• Demos: Dan Lemon
• Brand and Design Strategy: Dan Stratton, Zoocha

The initiative has been successful in bringing Drupal to external audiences across multiple global locations including Oaisys Conference in Pune, Drupal AI Summit Paris, DrupalCon Nara in Japan, the European Commission hackathon, and a growing number of workshops and meetups kept the work visible across contributors, regions, and practical discussions.

In the near future we have Drupal AI Summit New York City, May 14th, intended to bring the same conversation to enterprise leaders and practitioners. The team will exhibit at The AI Summit London as part of London Tech week which sees more than 45 000 attendees from around 90 countries across multiple days of programming.

In Chicago, that momentum was particularly easy to see

Drupal AI has moved beyond being merely a set of separate features. It is now realised through connected capabilities. Content, context, and editorial decisions begin to work together inside the same system.

Early in his Keynote at DrupalCon Chicago, Dries Buytaert widened the conversation. He said AI is now affecting three parts of Drupal at once. The product. The agencies around it. The open source community behind both.

That makes Chicago feel larger for Drupal AI. The releases matter. But they now sit inside a broader shift already affecting how Drupal is built, funded, and extended.

Photo: Paul Johnson

What Chicago made clear

Drupal AI is being deliberately designed as a native part of the platform, embedded within how Drupal operates rather than introduced as an additional layer on top. In doing so, AI becomes more useful as it works inside systems that already carry structure and context.

That is why Canvas AI mattered in Chicago. The demonstration was less about generating a page quickly and more about showing how content could move through Drupal while keeping structure, linking, and reusable patterns intact.

The same logic appeared when Dries returned to the Context Control Center, first introduced in Vienna. If AI is expected to assist meaningfully, organisational knowledge cannot remain outside the system. Brand rules, editorial priorities, and internal decisions need to stay close to where content is shaped. 

That is what Chicago makes clearer: Drupal AI is being positioned around context as much as capability.

What this means for agencies

One of the clearest shifts in Chicago came when the conversation moved from product to agency work.

AI is rapidly reducing the cost of production, but that does not reduce the need for judgment. It changes where the value sits.

Dries brought in Aidan Foster's observation directly: the bottleneck is no longer making things. The harder part is deciding what should be made, how it should work, and what quality still means when output becomes easier to create.

That is why agencies remain part of the same conversation. As production speeds up, strategy, interpretation, and institutional understanding begin to matter more, not less. 

In that sense, as production becomes easier, the harder part shifts elsewhere. Context, judgment, and internal knowledge begin to matter more, which is exactly where Drupal is placing more emphasis.

What do we want to accomplish by Rotterdam?

The initiative now feels materially different from where it stood even a few months ago. Prototypes are moving into alpha and beta stages, stable releases are approaching, and coordination across teams is visibly stronger. More people are involved, and the relationship between Drupal CMS, Drupal AI, and core has become easier to follow.

That shift matters because the work no longer reads as parallel experimentation. Product releases, editorial workflows, and context systems are beginning to move toward the same operating idea: AI becomes more useful when it works inside structures organisations already trust.

Photo: Jeremy Chinquist (jjchinquist)

The roadmap shown in Chicago reinforces that direction. For organisations already evaluating open source AI for digital platforms, Drupal AI now presents a clearer path to adoption.

For a complete view of how Drupal AI is framing that next stage, Dries Buytaert’s full DriesNote from Chicago is worth watching.

At DrupalCon Vienna, Dries Buytaert opened his keynote with a question the room was already asking: what happens to Drupal in a world full of AI?

He answered with a live demonstration showcasing three things the initiative had built and shipped:

• Pace of delivery: pages that used to take hours now get built in minutes. 
• Brand and voice control: a new Context Control Center feature lets teams set their brand voice once, and every AI agent applies it. 
• Governance at scale: autonomous agents scan the site, find internal references, and propose updates.

The keynote highlighted an important aspect: humans stay in the loop and approve every change before anything goes live.

The Drupal AI Initiative arrives in Chicago with more to show

Since Vienna, 10 new organisations have joined as partners, bringing the total to 31. The initiative has now secured the equivalent of $1.5 million in combined support, comprising both direct funding and a committed contribution of 50 staff dedicated to advancing the work.

What is most exciting to me is not just what we’ve built, but how we’ve built it. With a growing group of contributors and more than $1.5 million in funding, this is now a coordinated effort to bring AI into Drupal in a way that is open, trusted, and built to last.

Dries Buytaert 

A portion of funds is being invested in delivery management. The initiative conducted a formal Request for Proposal (RFP) process to appoint delivery partners responsible for coordinating work across both the innovation and product development streams. QED42 and 1xINTERNET were selected to lead the innovation and product development work streams respectively.

Progress is also visible in what has shipped since Vienna. Drupal AI 1.2.0 came first. MCP support followed. Drupal CMS 2.0 launched with Canvas as the default editing experience.

Drupal AI 1.3.0 introduced governance controls, editorial workflows, and production visibility for organisations running AI seriously.

Dedicated AI Marketing Leads Appointed

With the increased momentum in development it has been essential to scale marketing capacity. Paul Johnson announced the appointment of 10 marketing leads. Each will specialise on delivering specific key elements of the marketing strategy.

• Media Relations: Pritam Prasun, Open Sense Labs
• Social Media: Amber Henry, Morpht
• Webinars: Matthew Saunders, Amazee.io
• Events: Paul Johnson, 1xINTERNET
• Sales Enablement: James Tillotson, 1xINTERNET
• Case Studies: Rosie Gladden, ImageX
• Existing Capabilities: Duncan Worrel, Zoocha
• Upcoming Roadmap Capabilities: Will Huggins, Zoocha
• Demos: Dan Lemon
• Brand and Design Strategy: Dan Stratton, Zoocha

The initiative has been successful in bringing Drupal to external audiences across multiple global locations including Oaisys Conference in Pune, Drupal AI Summit Paris, DrupalCon Nara in Japan, the European Commission hackathon, and a growing number of workshops and meetups kept the work visible across contributors, regions, and practical discussions.

In the near future we have Drupal AI Summit New York City, May 14th, intended to bring the same conversation to enterprise leaders and practitioners. The team will exhibit at The AI Summit London as part of London Tech week which sees more than 45 000 attendees from around 90 countries across multiple days of programming.

In Chicago, that momentum was particularly easy to see

Drupal AI has moved beyond being merely a set of separate features. It is now realised through connected capabilities. Content, context, and editorial decisions begin to work together inside the same system.

Early in his Keynote at DrupalCon Chicago, Dries Buytaert widened the conversation. He said AI is now affecting three parts of Drupal at once. The product. The agencies around it. The open source community behind both.

That makes Chicago feel larger for Drupal AI. The releases matter. But they now sit inside a broader shift already affecting how Drupal is built, funded, and extended.

Photo: Paul Johnson

What Chicago made clear

Drupal AI is being deliberately designed as a native part of the platform, embedded within how Drupal operates rather than introduced as an additional layer on top. In doing so, AI becomes more useful as it works inside systems that already carry structure and context.

That is why Canvas AI mattered in Chicago. The demonstration was less about generating a page quickly and more about showing how content could move through Drupal while keeping structure, linking, and reusable patterns intact.

The same logic appeared when Dries returned to the Context Control Center, first introduced in Vienna. If AI is expected to assist meaningfully, organisational knowledge cannot remain outside the system. Brand rules, editorial priorities, and internal decisions need to stay close to where content is shaped. 

That is what Chicago makes clearer: Drupal AI is being positioned around context as much as capability.

What this means for agencies

One of the clearest shifts in Chicago came when the conversation moved from product to agency work.

AI is rapidly reducing the cost of production, but that does not reduce the need for judgment. It changes where the value sits.

Dries brought in Aidan Foster's observation directly: the bottleneck is no longer making things. The harder part is deciding what should be made, how it should work, and what quality still means when output becomes easier to create.

That is why agencies remain part of the same conversation. As production speeds up, strategy, interpretation, and institutional understanding begin to matter more, not less. 

In that sense, as production becomes easier, the harder part shifts elsewhere. Context, judgment, and internal knowledge begin to matter more, which is exactly where Drupal is placing more emphasis.

What do we want to accomplish by Rotterdam?

The initiative now feels materially different from where it stood even a few months ago. Prototypes are moving into alpha and beta stages, stable releases are approaching, and coordination across teams is visibly stronger. More people are involved, and the relationship between Drupal CMS, Drupal AI, and core has become easier to follow.

That shift matters because the work no longer reads as parallel experimentation. Product releases, editorial workflows, and context systems are beginning to move toward the same operating idea: AI becomes more useful when it works inside structures organisations already trust.

Photo: Jeremy Chinquist (jjchinquist)

The roadmap shown in Chicago reinforces that direction. For organisations already evaluating open source AI for digital platforms, Drupal AI now presents a clearer path to adoption.

For a complete view of how Drupal AI is framing that next stage, Dries Buytaert’s full DriesNote from Chicago is worth watching.

In his ‘#DriesNote’ presentation at DrupalCon Chicago 2026, Dries addressed the elephant in the room: AI is currently flooding the web with "average" content: fast to produce, but hard to distinguish. While there are tools that can generate beautiful prototypes in 15 minutes with no technical skill, those prototypes lack the structured data, governance, and durability required by serious organizations.

Drupal is bridging the gap between “AI speed” and enterprise assurance through two key innovations: the Context Control Centre (CCC) and Drupal Canvas AI, a new approach to building digital experiences.

The Context Control Centre (CCC): Institutional ‘Knowledge as a Service’

The most significant hurdle for AI today is a lack of context. Without it, AI simply gives you the "average response." The Context Control Centre changes this by allowing organizations to store their unique "DNA" directly within Drupal.

The CCC organizes institutional knowledge into actionable data:

• Brand Guidelines: Specific rules for tone, voice, and formatting.

• Personas: Detailed profiles of target audiences (e.g., Controllers vs. IT Ops).

• Dynamic Context: A groundbreaking feature where the CCC connects to live data sources like Google Analytics 4 (GA4).

Built into your Drupal CMS, AI tools don't just guess; they work within your specific business reality to ensure their output is always on brand, within guidelines, and relevant to the contextual nuances of the task at hand.

Drupal Canvas AI: Where Speed Meets Substance

The second half of the equation is Drupal Canvas AI, the next-generation page builder. 

Instead of dragging and dropping components, you can just tell the AI what you want with prompts that describe the page and content you want to produce. Canvas AI, in conjunction with the CCC, will create the page and include the components you need.

As Dries noted, production is becoming a commodity, but judgment and strategy remain human. Drupal AI doesn’t replace your teams, it amplifies their capability to deliver ‘Quality at Scale.’

In his ‘#DriesNote’ presentation at DrupalCon Chicago 2026, Dries addressed the elephant in the room: AI is currently flooding the web with "average" content: fast to produce, but hard to distinguish. While there are tools that can generate beautiful prototypes in 15 minutes with no technical skill, those prototypes lack the structured data, governance, and durability required by serious organizations.

Drupal is bridging the gap between “AI speed” and enterprise assurance through two key innovations: the Context Control Centre (CCC) and Drupal Canvas AI, a new approach to building digital experiences.

The Context Control Centre (CCC): Institutional ‘Knowledge as a Service’

The most significant hurdle for AI today is a lack of context. Without it, AI simply gives you the "average response." The Context Control Centre changes this by allowing organizations to store their unique "DNA" directly within Drupal.

The CCC organizes institutional knowledge into actionable data:

• Brand Guidelines: Specific rules for tone, voice, and formatting.

• Personas: Detailed profiles of target audiences (e.g., Controllers vs. IT Ops).

• Dynamic Context: A groundbreaking feature where the CCC connects to live data sources like Google Analytics 4 (GA4).

Built into your Drupal CMS, AI tools don't just guess; they work within your specific business reality to ensure their output is always on brand, within guidelines, and relevant to the contextual nuances of the task at hand.

Drupal Canvas AI: Where Speed Meets Substance

The second half of the equation is Drupal Canvas AI, the next-generation page builder. 

Instead of dragging and dropping components, you can just tell the AI what you want with prompts that describe the page and content you want to produce. Canvas AI, in conjunction with the CCC, will create the page and include the components you need.

As Dries noted, production is becoming a commodity, but judgment and strategy remain human. Drupal AI doesn’t replace your teams, it amplifies their capability to deliver ‘Quality at Scale.’

Missed the Driesnote? You can watch it here.

Drupal, the open source content management platform that runs some of the most demanding websites on the planet, turned 25 in January. But while the community is celebrating what is a remarkable milestone for any open source project, it is actively strengthening its foundations to lead in the AI era and looking ahead to a future it intends to shape.

This week at DrupalCon Chicago, Drupal's creator Dries Buytaert delivered his annual keynote, the DriesNote, and it was one of the more honest talks you'll hear at a tech conference. A clear-eyed look at what's working, what's under pressure, and what the plan actually is.

AI is Disrupting Everything, But Deep Expertise is Irreplaceable

For more than two decades, the Drupal ecosystem has rested on three things: the platform itself, the agencies that build with it, and the community that maintains it. That triangle has survived waves of new technology and constant change. It's been remarkably resilient.

But what happens when AI disrupts all three sides at once? When anyone can spin up a decent-looking site in fifteen minutes, what does that do to the people who've spent years building something better? That’s what is happening at the moment, as the world is being flooded with AI-generated “average”. Average content, average code, average websites - average is easier to attain than ever.

What it means is that the only thing that will actually matter, to customers, to organisations, to the people trying to build something lasting on the open web, is genuine, hard-won, deep expertise.

What AI Actually Can't Do

Here's something worth understanding, because it gets lost in the noise.

AI can generate a beautiful website in about fifteen minutes. Tools like Lovable and Replit are genuinely impressive. You give them a prompt, they give you something that looks polished and professional. It feels like magic.

But a prototype is not a production system.

The moment you need structured content that editors can actually update, workflows that a real team can follow, permissions, governance, security, accessibility, multilingual support, compliance... you're not building a website anymore. You're building a system. And building systems is exactly what Drupal has excelled at for 25 years.

The demo at DrupalCon made this tangible. A beautiful event site built in Lovable in minutes, then migrated into Drupal CMS using AI coding tools, where the hard-coded layout became structured, reusable, editable content. Same visual ambition. Completely different foundation.

The pitch is simple: AI gets you to visual ambition fast. Drupal makes that ambition durable.

What's Actually Shipping

This isn't a vision talk. Things are being built and released.

DrupalCMS 2.1 landed at DrupalCon, built on top of Drupal Core 11.3. Over the last 18 months, core database and cache utilization have roughly halved, meaning every Drupal site in the world gets faster when it upgrades. That's not a minor thing. That's the compounding benefit of a serious engineering community.

Site templates and a marketplace are now live at marketplace.drupal.org, with more than ten purpose-built templates covering nonprofits, education, healthcare, events, government, and SaaS, built by agencies that understand those sectors. Free and premium options, with direct access to the people who made them if you need help.

Canvas, Drupal's new page-building layer, lets teams create and customise pages at speed without sacrificing the structured content underneath.

The Context Control Centre is a system for storing and managing your organisation's institutional knowledge (brand guidelines, content strategy, audience personas, live analytics) and it's moving from prototype to production. The idea is that AI tools are only as good as the context they're given. Without it, you get the average of the internet. With it, you get something that actually knows your brand.

And in the AI layer itself, a demo showed what it looks like when a marketer can drop a raw content brief into Drupal, have the system read it, load the right brand and strategy context, ask clarifying questions, and generate a production-ready page, with proper cross-linking, structured data for AI search engines, and an accessibility check built in.

That's not a concept. That's a demo running on real code.

One Developer, Six Weeks, 90,000 Lines of Code

The most striking moment of the keynote was a contribution from Jurgen Haas, one of the Drupal community's most experienced developers. He builds ECA, Drupal's automation engine, running on thousands of production sites.

Three years ago, he knew what ECA needed. He knew how to build it. He never had the time.

Six weeks ago, he started. With AI as a collaborator, handling scaffolding, generating tests, refactoring code, he shipped a completely rebuilt workflow editor: a new visual interface, built-in debugging and replay, in-context automation for non-technical users. 90,000 lines of code. Full test coverage. One person.

"This is what one Drupal developer can build in six weeks," he said. "Imagine what all of us can build next."

The key detail: Jurgen could explain every line. He could defend the architecture. He owned what he built. AI removed friction. It didn't replace expertise.

The Harder Conversation

Not everything in the keynote was product news.

Dries was honest about the pressure on Drupal agencies. When AI commoditises production, and it is, the business models that agencies have built over years start to look shaky. An agency leader named Aidan Foster, seventeen years into running a Drupal shop, described the feeling plainly: "AI had converted making things into a commodity. That shook the foundations I had spent 17 years building."

But Aidan's conclusion was interesting. The bottleneck isn't production anymore. It's creativity, strategy, and judgement. If you use AI without asking the hard questions, who are we, who are our audience, what makes us different, you get the boring average. The agencies that will win are the ones that get good at encoding expertise, not just delivering outputs.

There's also a challenge for the community itself. AI lowers the barrier to contribute code, which sounds good, until you realise the burden of reviewing that code falls on the same small group of maintainers. And when people use AI to skip the deep learning that used to come from contributing, the community gets shallower. A shallow community can't maintain what's been built.

Dries' response was a new mantra:never submit code you don't understand. It doesn't matter what tools you used to write it. If you submit it, you own it.

The Bet Worth Making

Twenty years ago, Dries was a bedroom inventor who collapsed from stress on a street in Belgium. He had a choice: take a safe job, walk away from the thing he'd built, or ask for help and become a deliberate leader.

He made the harder choice. The community that grew up around that choice is why Drupal is still here, still relevant, still running critical infrastructure for organisations around the world.

Now there's another crossroads. AI is both the flood and the drainage system. It destabilises the foundations and it can help rebuild them stronger.

Twenty-five years of Drupal is twenty-five years of expertise built patch by patch, merge request by merge request. A community that showed up not because it had to, but because it cared. That's not a liability in the age of AI. That's exactly what this moment needs.

DrupalCon Chicago runs through this week. The marketplace is live at marketplace.drupal.org. The Context Control Centre is approaching production. The Drupal AI initiative is moving fast.

Missed the Driesnote? You can watch it here.

Drupal, the open source content management platform that runs some of the most demanding websites on the planet, turned 25 in January. But while the community is celebrating what is a remarkable milestone for any open source project, it is actively strengthening its foundations to lead in the AI era and looking ahead to a future it intends to shape.

This week at DrupalCon Chicago, Drupal's creator Dries Buytaert delivered his annual keynote, the DriesNote, and it was one of the more honest talks you'll hear at a tech conference. A clear-eyed look at what's working, what's under pressure, and what the plan actually is.

AI is Disrupting Everything, But Deep Expertise is Irreplaceable

For more than two decades, the Drupal ecosystem has rested on three things: the platform itself, the agencies that build with it, and the community that maintains it. That triangle has survived waves of new technology and constant change. It's been remarkably resilient.

But what happens when AI disrupts all three sides at once? When anyone can spin up a decent-looking site in fifteen minutes, what does that do to the people who've spent years building something better? That’s what is happening at the moment, as the world is being flooded with AI-generated “average”. Average content, average code, average websites - average is easier to attain than ever.

What it means is that the only thing that will actually matter, to customers, to organisations, to the people trying to build something lasting on the open web, is genuine, hard-won, deep expertise.

What AI Actually Can't Do

Here's something worth understanding, because it gets lost in the noise.

AI can generate a beautiful website in about fifteen minutes. Tools like Lovable and Replit are genuinely impressive. You give them a prompt, they give you something that looks polished and professional. It feels like magic.

But a prototype is not a production system.

The moment you need structured content that editors can actually update, workflows that a real team can follow, permissions, governance, security, accessibility, multilingual support, compliance... you're not building a website anymore. You're building a system. And building systems is exactly what Drupal has excelled at for 25 years.

The demo at DrupalCon made this tangible. A beautiful event site built in Lovable in minutes, then migrated into Drupal CMS using AI coding tools, where the hard-coded layout became structured, reusable, editable content. Same visual ambition. Completely different foundation.

The pitch is simple: AI gets you to visual ambition fast. Drupal makes that ambition durable.

What's Actually Shipping

This isn't a vision talk. Things are being built and released.

DrupalCMS 2.1 landed at DrupalCon, built on top of Drupal Core 11.3. Over the last 18 months, core database and cache utilization have roughly halved, meaning every Drupal site in the world gets faster when it upgrades. That's not a minor thing. That's the compounding benefit of a serious engineering community.

Site templates and a marketplace are now live at marketplace.drupal.org, with more than ten purpose-built templates covering nonprofits, education, healthcare, events, government, and SaaS, built by agencies that understand those sectors. Free and premium options, with direct access to the people who made them if you need help.

Canvas, Drupal's new page-building layer, lets teams create and customise pages at speed without sacrificing the structured content underneath.

The Context Control Centre is a system for storing and managing your organisation's institutional knowledge (brand guidelines, content strategy, audience personas, live analytics) and it's moving from prototype to production. The idea is that AI tools are only as good as the context they're given. Without it, you get the average of the internet. With it, you get something that actually knows your brand.

And in the AI layer itself, a demo showed what it looks like when a marketer can drop a raw content brief into Drupal, have the system read it, load the right brand and strategy context, ask clarifying questions, and generate a production-ready page, with proper cross-linking, structured data for AI search engines, and an accessibility check built in.

That's not a concept. That's a demo running on real code.

One Developer, Six Weeks, 90,000 Lines of Code

The most striking moment of the keynote was a contribution from Jurgen Haas, one of the Drupal community's most experienced developers. He builds ECA, Drupal's automation engine, running on thousands of production sites.

Three years ago, he knew what ECA needed. He knew how to build it. He never had the time.

Six weeks ago, he started. With AI as a collaborator, handling scaffolding, generating tests, refactoring code, he shipped a completely rebuilt workflow editor: a new visual interface, built-in debugging and replay, in-context automation for non-technical users. 90,000 lines of code. Full test coverage. One person.

"This is what one Drupal developer can build in six weeks," he said. "Imagine what all of us can build next."

The key detail: Jurgen could explain every line. He could defend the architecture. He owned what he built. AI removed friction. It didn't replace expertise.

The Harder Conversation

Not everything in the keynote was product news.

Dries was honest about the pressure on Drupal agencies. When AI commoditises production, and it is, the business models that agencies have built over years start to look shaky. An agency leader named Aidan Foster, seventeen years into running a Drupal shop, described the feeling plainly: "AI had converted making things into a commodity. That shook the foundations I had spent 17 years building."

But Aidan's conclusion was interesting. The bottleneck isn't production anymore. It's creativity, strategy, and judgement. If you use AI without asking the hard questions, who are we, who are our audience, what makes us different, you get the boring average. The agencies that will win are the ones that get good at encoding expertise, not just delivering outputs.

There's also a challenge for the community itself. AI lowers the barrier to contribute code, which sounds good, until you realise the burden of reviewing that code falls on the same small group of maintainers. And when people use AI to skip the deep learning that used to come from contributing, the community gets shallower. A shallow community can't maintain what's been built.

Dries' response was a new mantra:never submit code you don't understand. It doesn't matter what tools you used to write it. If you submit it, you own it.

The Bet Worth Making

Twenty years ago, Dries was a bedroom inventor who collapsed from stress on a street in Belgium. He had a choice: take a safe job, walk away from the thing he'd built, or ask for help and become a deliberate leader.

He made the harder choice. The community that grew up around that choice is why Drupal is still here, still relevant, still running critical infrastructure for organisations around the world.

Now there's another crossroads. AI is both the flood and the drainage system. It destabilises the foundations and it can help rebuild them stronger.

Twenty-five years of Drupal is twenty-five years of expertise built patch by patch, merge request by merge request. A community that showed up not because it had to, but because it cared. That's not a liability in the age of AI. That's exactly what this moment needs.

DrupalCon Chicago runs through this week. The marketplace is live at marketplace.drupal.org. The Context Control Centre is approaching production. The Drupal AI initiative is moving fast.

Missed the Driesnote? You can watch it here.

Drupal, the open source content management platform that runs some of the most demanding websites on the planet, turned 25 in January. But while the community is celebrating what is a remarkable milestone for any open source project, it is actively strengthening its foundations to lead in the AI era and looking ahead to a future it intends to shape.

This week at DrupalCon Chicago, Drupal's creator Dries Buytaert delivered his annual keynote, the DriesNote, and it was one of the more honest talks you'll hear at a tech conference. A clear-eyed look at what's working, what's under pressure, and what the plan actually is.

AI is Disrupting Everything, But Deep Expertise is Irreplaceable

For more than two decades, the Drupal ecosystem has rested on three things: the platform itself, the agencies that build with it, and the community that maintains it. That triangle has survived waves of new technology and constant change. It's been remarkably resilient.

But what happens when AI disrupts all three sides at once? When anyone can spin up a decent-looking site in fifteen minutes, what does that do to the people who've spent years building something better? That’s what is happening at the moment, as the world is being flooded with AI-generated “average”. Average content, average code, average websites - average is easier to attain than ever.

What it means is that the only thing that will actually matter, to customers, to organisations, to the people trying to build something lasting on the open web, is genuine, hard-won, deep expertise.

What AI Actually Can't Do

Here's something worth understanding, because it gets lost in the noise.

AI can generate a beautiful website in about fifteen minutes. Tools like Lovable and Replit are genuinely impressive. You give them a prompt, they give you something that looks polished and professional. It feels like magic.

But a prototype is not a production system.

The moment you need structured content that editors can actually update, workflows that a real team can follow, permissions, governance, security, accessibility, multilingual support, compliance... you're not building a website anymore. You're building a system. And building systems is exactly what Drupal has excelled at for 25 years.

The demo at DrupalCon made this tangible. A beautiful event site built in Lovable in minutes, then migrated into Drupal CMS using AI coding tools, where the hard-coded layout became structured, reusable, editable content. Same visual ambition. Completely different foundation.

The pitch is simple: AI gets you to visual ambition fast. Drupal makes that ambition durable.

What's Actually Shipping

This isn't a vision talk. Things are being built and released.

DrupalCMS 2.1 landed at DrupalCon, built on top of Drupal Core 11.3. Over the last 18 months, core database and cache utilization have roughly halved, meaning every Drupal site in the world gets faster when it upgrades. That's not a minor thing. That's the compounding benefit of a serious engineering community.

Site templates and a marketplace are now live at marketplace.drupal.org, with more than ten purpose-built templates covering nonprofits, education, healthcare, events, government, and SaaS, built by agencies that understand those sectors. Free and premium options, with direct access to the people who made them if you need help.

Canvas, Drupal's new page-building layer, lets teams create and customise pages at speed without sacrificing the structured content underneath.

The Context Control Centre is a system for storing and managing your organisation's institutional knowledge (brand guidelines, content strategy, audience personas, live analytics) and it's moving from prototype to production. The idea is that AI tools are only as good as the context they're given. Without it, you get the average of the internet. With it, you get something that actually knows your brand.

And in the AI layer itself, a demo showed what it looks like when a marketer can drop a raw content brief into Drupal, have the system read it, load the right brand and strategy context, ask clarifying questions, and generate a production-ready page, with proper cross-linking, structured data for AI search engines, and an accessibility check built in.

That's not a concept. That's a demo running on real code.

One Developer, Six Weeks, 90,000 Lines of Code

The most striking moment of the keynote was a contribution from Jurgen Haas, one of the Drupal community's most experienced developers. He builds ECA, Drupal's automation engine, running on thousands of production sites.

Three years ago, he knew what ECA needed. He knew how to build it. He never had the time.

Six weeks ago, he started. With AI as a collaborator, handling scaffolding, generating tests, refactoring code, he shipped a completely rebuilt workflow editor: a new visual interface, built-in debugging and replay, in-context automation for non-technical users. 90,000 lines of code. Full test coverage. One person.

"This is what one Drupal developer can build in six weeks," he said. "Imagine what all of us can build next."

The key detail: Jurgen could explain every line. He could defend the architecture. He owned what he built. AI removed friction. It didn't replace expertise.

The Harder Conversation

Not everything in the keynote was product news.

Dries was honest about the pressure on Drupal agencies. When AI commoditises production, and it is, the business models that agencies have built over years start to look shaky. An agency leader named Aidan Foster, seventeen years into running a Drupal shop, described the feeling plainly: "AI had converted making things into a commodity. That shook the foundations I had spent 17 years building."

But Aidan's conclusion was interesting. The bottleneck isn't production anymore. It's creativity, strategy, and judgement. If you use AI without asking the hard questions, who are we, who are our audience, what makes us different, you get the boring average. The agencies that will win are the ones that get good at encoding expertise, not just delivering outputs.

There's also a challenge for the community itself. AI lowers the barrier to contribute code, which sounds good, until you realise the burden of reviewing that code falls on the same small group of maintainers. And when people use AI to skip the deep learning that used to come from contributing, the community gets shallower. A shallow community can't maintain what's been built.

Dries' response was a new mantra:never submit code you don't understand. It doesn't matter what tools you used to write it. If you submit it, you own it.

The Bet Worth Making

Twenty years ago, Dries was a bedroom inventor who collapsed from stress on a street in Belgium. He had a choice: take a safe job, walk away from the thing he'd built, or ask for help and become a deliberate leader.

He made the harder choice. The community that grew up around that choice is why Drupal is still here, still relevant, still running critical infrastructure for organisations around the world.

Now there's another crossroads. AI is both the flood and the drainage system. It destabilises the foundations and it can help rebuild them stronger.

Twenty-five years of Drupal is twenty-five years of expertise built patch by patch, merge request by merge request. A community that showed up not because it had to, but because it cared. That's not a liability in the age of AI. That's exactly what this moment needs.

DrupalCon Chicago runs through this week. The marketplace is live at marketplace.drupal.org. The Context Control Centre is approaching production. The Drupal AI initiative is moving fast.

Great digital experiences don't happen by accident, they're built with intention, inclusion, and users at the heart of every decision. At DrupalCon Rotterdam 2026, the UX, Accessibility and Usability track is bringing together designers, developers, content strategists, and decision-makers to explore how Drupal powers truly user-centred digital products.

We're looking for speakers with real stories to tell. Whether you've transformed an accessibility audit into lasting organisational change, built a design system that scaled beautifully across channels, or used user research to completely reshape a development roadmap — we want to hear from you.

          ^{Foto by Matthew Saunders}

We're particularly interested in sessions covering:

·    Accessibility beyond compliance - embedding WCAG and ATAG into everyday workflows

·    User research that drives real development decisions

·    Design systems and collaborative design-development workflows

·    Usability improvements backed by evidence and data

·    Content design and strategy, including practical uses of AI

·    Digital sustainability - designing for efficiency and longevity

This track is for anyone who believes that inclusion, usability, and good design aren't nice-to-haves — they're essential. Whether you're sharing a case study, a practical toolkit, or a freshperspective, your session could help Drupal practitioners everywhere build better, more inclusive digital experiences. 

Submissions close 13 April. 

Submmit your session: https://events.drupal.org/rotterdam2026/program-glance 

Don't wait! Share your expertise and help shape the conversation at DrupalCon Rotterdam 2026.

Recap of Drupal 12 release windows

Our release schedule includes three potential release dates for Drupal 12.0.0, depending on when critical requirements are completed:

1. Week of June 15, 2026, if beta requirements are completed by March 27
2. Week of August 10, 2026, if beta requirements are completed by May 15
3. Week of December 07, 2026, if beta requirements are completed by September 11

Our new target release date for Drupal 12.0.0 is the week of August 10, 2026

Many great improvements landed recently. The main branch is on Symfony 8 and most deprecated modules are removed already. With only a few days remaining until the March deadline of the first release option though, we are confident that not all critical requirements will be completed by March 27. Therefore, we are officially announcing that our new target release date for Drupal 12.0.0 is August 10, 2026, and the beta deadline for critical requirements is May 15, 2026.

We need your help to complete requirements by May 15!

While there are other pending improvements that are not hard requirements for Drupal 12's release, these are the most urgent needs:

1. PHPUnit 12 support

   While our ultimate goal is to support PHPUnit 13 in Drupal 12, there are significant API changes in PHPUnit 12 that we first need to adopt. See #3527936: Introduce support for PHPUnit 12

2. Import maps API

   CKEditor 5 is changing their installation method in the near future. See #3527914: [PP-1] Use New installation methods for CKEditor5

   To support this, we need a JavaScript import maps API in core. See #3398525: Add an API for importmaps

3. Update path related changes

   To test update paths from Drupal 11.3.0, we need to generate new database dumps. See #3569127: Add new 11.3.x database dump fixtures, without modules deprecated for removal in 12.x

   Remove older upgrade paths. See #3580877: [PP-1] Remove updates added prior to 11.3.0 from 12.x

4. Remove tests from release packages

   To reduce the size of core, we are excluding tests from core release packages, and offering them via a different namespace. This is a disruptive change and should only be done in a major release.
   See #3067979: Exclude test files from release packages.

5. Deprecate and remove libraries, modules, themes and dependencies

   The Toolbar Module needs to be removed from core now that the Navigation module is stable and in the standard profile. See #3484850: [PP-1] [meta] Deprecate Toolbar module

   There are more dependencies, modules and themes that are still possible to remove. See #3466088: [meta] Deprecate dependencies, libraries, modules, and themes that will be removed from Drupal 12 core

6. Move from Claro to Gin as admin theme

   Gin is in core as an alpha experimental extension. Help make it stable and so it can replace Claro.
   See #3576488: [meta] Admin theme: path to stable.

7. Update to ESLint 9

   The coding standard checks are using the unsupported ESLint 8. We need to update to version 9. See #3440225: Update to ESLint v9 with standard rules.
   See #3440225: Update to ESLint v9 with standard rules.

The above list are the current highest priorities. We'll keep identifying and tagging Drupal 12 release priority issues. The up to date list can be found using the Drupal 12.0.0 release priority tag.

Recap of Drupal 12 release windows

Our release schedule includes three potential release dates for Drupal 12.0.0, depending on when critical requirements are completed:

1. Week of June 15, 2026, if beta requirements are completed by March 27
2. Week of August 10, 2026, if beta requirements are completed by May 15
3. Week of December 07, 2026, if beta requirements are completed by September 11

Our new target release date for Drupal 12.0.0 is the week of August 10, 2026

Many great improvements landed recently. The main branch is on Symfony 8 and most deprecated modules are removed already. With only a few days remaining until the March deadline of the first release option though, we are confident that not all critical requirements will be completed by March 27. Therefore, we are officially announcing that our new target release date for Drupal 12.0.0 is August 10, 2026, and the beta deadline for critical requirements is May 15, 2026.

We need your help to complete requirements by May 15!

While there are other pending improvements that are not hard requirements for Drupal 12's release, these are the most urgent needs:

1. PHPUnit 12 support

   While our ultimate goal is to support PHPUnit 13 in Drupal 12, there are significant API changes in PHPUnit 12 that we first need to adopt. See #3527936: Introduce support for PHPUnit 12

2. Import maps API

   CKEditor 5 is changing their installation method in the near future. See #3527914: [PP-1] Use New installation methods for CKEditor5

   To support this, we need a JavaScript import maps API in core. See #3398525: Add an API for importmaps

3. Update path related changes

   To test update paths from Drupal 11.3.0, we need to generate new database dumps. See #3569127: Add new 11.3.x database dump fixtures, without modules deprecated for removal in 12.x

   Remove older upgrade paths. See #3580877: [PP-1] Remove updates added prior to 11.3.0 from 12.x

4. Remove tests from release packages

   To reduce the size of core, we are excluding tests from core release packages, and offering them via a different namespace. This is a disruptive change and should only be done in a major release.
   See #3067979: Exclude test files from release packages.

5. Deprecate and remove libraries, modules, themes and dependencies

   The Toolbar Module needs to be removed from core now that the Navigation module is stable and in the standard profile. See #3484850: [PP-1] [meta] Deprecate Toolbar module

   There are more dependencies, modules and themes that are still possible to remove. See #3466088: [meta] Deprecate dependencies, libraries, modules, and themes that will be removed from Drupal 12 core

6. Move from Claro to Gin as admin theme

   Gin is in core as an alpha experimental extension. Help make it stable and so it can replace Claro.
   See #3576488: [meta] Admin theme: path to stable.

7. Update to ESLint 9

   The coding standard checks are using the unsupported ESLint 8. We need to update to version 9. See #3440225: Update to ESLint v9 with standard rules.
   See #3440225: Update to ESLint v9 with standard rules.

The above list are the current highest priorities. We'll keep identifying and tagging Drupal 12 release priority issues. The up to date list can be found using the Drupal 12.0.0 release priority tag.

Join us THURSDAY, March 19 at 1pm ET / 10am PT, for our regularly scheduled call to chat about all things Drupal and nonprofits. (Convert to your local time zone.)

We don't have anything specific on the agenda this month, so we'll have plenty of time to discuss anything that's on our minds at the intersection of Drupal and nonprofits. Got something specific you want to talk about? Feel free to share ahead of time in our collaborative Google document at https://nten.org/drupal/notes!

All nonprofit Drupal devs and users, regardless of experience level, are always welcome on this call.

This free call is sponsored by NTEN.org and open to everyone.

Information on joining the meeting can be found in our collaborative Google document.

Authors: Will Huggins, Jeremy Chinquist

Drupal AI 1.3.0 is now available, delivering the largest feature update since the module's initial release. This version focuses on three areas that organisations told us matter most:

• Keeping AI safe and accountable
• Making AI useful for content teams
• Giving technical teams the visibility they need to operate AI in production with confidence

And because Drupal AI is open source, you stay in control of your models, your data, and your infrastructure.

AI Guardrails: stay in control of every AI interaction

Trust is the foundation of responsible AI adoption. Drupal AI 1.3.0 introduces AI Guardrails, configurable checks that run before or after any AI request.

Teams can define rules to control how AI interacts with their content and data. For example, they can block sensitive data from leaving their organisation, filter harmful responses, or enforce compliance policies. All of this can be configured without writing code.

Guardrails work across all AI operations in Drupal. This gives security and compliance teams a single place to oversee how AI is used across the site.

In practice, this means AI governance becomes part of the platform itself, rather than something teams must manage separately.

One-click AI for editors, right where they work

AI should meet editors in their workflow, not force them into a separate tool.

Drupal AI 1.3.0 introduces Field Widget Actions, one-click AI workflows attached directly to content fields.

Editors can now:

• Generate images from text descriptions and attach them as media
• Create structured FAQs from existing content
• Extract addresses from images using AI and Google Places
• Plot data from a CSV into a chart field
• Generate audio summaries with text-to-speech
• Auto-fill metadata such as telephone numbers and office hours from unstructured text
• Evaluate whether the content is ready for publication and update its moderation state

Each action is backed by a customisable workflow allowing site builders to tailor AI behaviour to their organisation’s needs and editorial standards without writing code.

A smarter, more flexible chatbot

Editors often need quick assistance while working on content. The built-in Drupal AI chatbot has been expanded to support this directly within the editing experience.

Open the chatbot via slide-in or full-screen mode, allowing the editor to choose the interface that best fits their workflow.

The chatbot receives page context, meaning it understands the content currently being viewed or edited.
Editors can ask questions such as:

• Make this title more engaging
• Summarise this article for social media

Because the chatbot receives the current page context, its responses relate directly to the content on the screen.
Custom loading messages replace generic spinners, allowing site builders to provide clearer feedback while AI requests are processed.

Better tools for developers and site builders

As organisations begin building AI-powered features in Drupal, developers need tools that simplify configuration and reduce boilerplate.

Drupal AI 1.3.0 includes a set of reusable form elements designed specifically for AI workflows.
These components provide consistent interfaces for working with AI providers, prompts, and structured outputs.

The new elements include:

• Markdown editor with WYSIWYG, diff view, and Word paste compatibility
• Mentions autocomplete, allowing users to type @ or { to insert prompt variables
• Provider Selector, a unified interface for selecting AI providers
• JSON Schema editor with validation for structured output configuration
• Chat History viewer that mirrors the conversational interface of modern AI playgrounds

Configuration files have also been improved. Prompts are stored in a human-readable format rather than single-line strings, making code reviews easier and reducing merge conflicts when teams collaborate on AI workflows.

New AI operation types: rerank, summarize, detect

Drupal AI’s provider-agnostic architecture continues to expand with three additional operation types.

Rerank reorders search results or document lists based on relevance to a query. This is particularly useful in retrieval-augmented generation workflows.

Summarize uses lightweight summarization models instead of full language models, reducing cost and processing time.

Object Detection identifies objects in images using traditional machine learning models. The AI Validations module already uses this to verify image content automatically.

All operation types work with compatible providers, allowing organisations to change models without rewriting integration code.

Production-grade AI observability

Running AI in production requires visibility into how systems behave. Drupal AI’s observability module exports spans, traces, and metrics through OpenTelemetry, the industry standard for application monitoring.

Teams are able to connect this data to platforms such as Datadog, Grafana, Sentry, or any OpenTelemetry-compatible system.

This allows engineering teams to monitor AI agent decisions, track usage and cost, and audit AI interactions across their sites.

Combined with the exclude-tags feature for logging, organisations also gain fine-grained control over what information is recorded and what remains private.

A maturing platform: consolidation and clear direction

Drupal AI 1.3.0 also simplifies parts of the platform.

AI Translate gives way to TMGMT (Translation Management Tool), aligning AI-assisted translation with Drupal’s standard translation workflow.

Field Widget Actions now provide a flexible framework for AI-assisted editorial tasks. AI Content Suggestions remains available as a contrib module for teams that want to continue building on that approach.

AI Validations will use the Object Detection operation type going forward, while still allowing different validation modules to build on the same abstraction.

These changes simplify the core architecture while leaving room for contrib modules and alternative implementations.

Closing the Loop

AI in a CMS brings practical challenges around governance, editorial workflows, and production visibility.

Drupal AI 1.3.0 shows that these problems can be handled directly within Drupal.

AI can be governed, integrated into everyday publishing workflows, and monitored in production as part of the platform.

Get started

• Documentation and guides: https://www.drupal.org/project/ai
• Download Drupal AI 1.3.0
• Join the conversation: #ai on Drupal Slack

Drupal AI remains open source and provider-agnostic, allowing organisations to integrate AI capabilities while maintaining control over their infrastructure, data, and model choices.

Full release notes

This post highlights the major additions. For the complete list of changes, bug fixes, and improvements in 1.3.0, see the full release notes on drupal.org.

Read more articles about Drupal AI.
 

Every year, the global campaign organised by the Union for International Cancer Control invites people affected by cancer to share their personal experiences as part of World Cancer Day. These stories provide an important human perspective on the realities of cancer. They help build solidarity, encourage early diagnosis, and ensure the voices of patients, survivors, families and carers are heard around the world.

However, when a global campaign encourages participation at scale, the practical challenges quickly become clear. Hundreds of deeply personal stories can arrive from many different countries in a short period of time. Each submission needs to be reviewed carefully, handled with sensitivity, and prepared for publication. For a small team responsible for managing the campaign, this can create significant pressure during the peak period around World Cancer Day.

To address this challenge, the World Cancer Day team partnered with 1xINTERNET to explore how artificial intelligence could support their existing editorial workflow within Drupal.

Balancing efficiency and human oversight in AI assisted moderation

Rather than attempting to automate the process entirely, the approach focused on supporting human decision making. AI was introduced to assist moderators by helping them review incoming submissions more efficiently. This allowed the team to process stories more quickly while ensuring that personal experiences remained at the centre of the review process.

The result is a practical example of how AI can be applied responsibly. Technology is used to assist people rather than replace them, helping organisations manage growing volumes of content while maintaining appropriate oversight and care.

In this upcoming webinar we will explore the approach taken by the World Cancer Day team and the lessons it offers for other organisations facing similar challenges.

Register for the webinar

What the webinar will cover

Participants will hear about:

• The role that personal stories play in the global World Cancer Day movement
• The operational challenge of moderating hundreds of submissions from around the world
• How AI supported a human moderation process rather than replacing it
• Practical lessons for organisations considering responsible applications of AI

The session is designed for organisational leaders, communications teams, and others exploring how artificial intelligence can be introduced in a considered and practical way. Using a real global campaign as its foundation, it offers a practical example of how AI can support teams managing large volumes of user generated content.

Event details

Title: Helping people tell their cancer stories using AI: Lessons from World Cancer Day
Date: 16 March 2026
Time: 2:00 PM GMT*
Format: Live webinar

Register now to secure your place.

*If the timing is not convenient, the session will be recorded and shared with everyone who registers so it can be watched afterwards.

Speakers

Charles Andrew Revkin

Communications professional working on the World Cancer Day campaign at the Union for International Cancer Control (UICC). Charles leads global storytelling efforts that amplify the voices of people affected by cancer around the world.

Diego Costa

Chief Operating Officer at 1xINTERNET. Diego works with organisations to design and deliver complex digital platforms using open-source technologies including Drupal.

Matthew Saunders

AI Ambassador at amazee.io and long-time member of the Drupal community. Matthew works on initiatives that help organisations adopt AI in ways that respect privacy, transparency, and human decision-making.

More webinars and events

This is part of a series of webinars and global events organised by Drupal AI. For full details visit our events calendar.

Written by guest blogger María Fernanda Silva

Something is shifting in how organizations think about AI. The early excitement around what it could do is giving way to a harder, more important question: how do you build AI that actually holds up — at scale, under pressure, and over time?

On 14 May 2026, New York City becomes the place where that question gets answered. The Drupal AI Summit brings together enterprise leaders, digital decision-makers, and senior practitioners from across the US and Europe — not to explore AI in theory, but to share what responsible, durable AI looks like in practice.

The decisions that define what AI becomes

Thirteen focused sessions. Real case studies. The Summit is built around the strategic and organizational questions that determine whether AI delivers real value or stays stuck in pilot mode: governance, investment, long-term architecture, and what it actually takes to scale. If you are responsible for those decisions, this is where you belong.

Open source and the architecture of trust

Most AI implementations fail quietly — locked into black boxes, disconnected from the workflows where real work happens, impossible to adjust without starting over.

There is a different path. When AI is embedded directly into content, data, and workflow systems (where enterprise work actually happens), teams maintain transparency, organisations retain control, and the architecture evolves alongside the business without the cost of replatforming. This is not a niche concern. It speaks to every enterprise leader navigating AI in environments where trust, regulation, and scale are not optional considerations — they are the entire challenge.

The Summit explores what this looks like in practice, with sessions grounded in the architectural and organizational choices that make responsible AI adoption real, not just possible.

What to expect on 14 May

From 9:00 am to 5:45 pm at 360 Madison Avenue in the heart of Midtown Manhattan, you will have access to thirteen sessions built entirely around case studies from peers who are applying AI in production environments. No theoretical frameworks. No technical deep-dives. Just honest, grounded conversations about what works, what doesn't, and what it takes to build AI your organization can trust for the long term.

Practitioners and leaders are flying in from across the US and Europe to share first-hand experience and to learn from each other. Your pass also grants access to the wider apidays New York event running across both days, connecting you with communities exploring APIs, AI agents, cybersecurity, and modern digital infrastructure — all under the same roof.

Explore the summit in detail

Want to learn more? Explore our dedicated AI Summit New York City hub where you can learn more about the format, who the event is designed for. This will also be where the agenda is published once finalised in mid March.

Early Bird tickets available until 13 April

Secure your place at the Drupal AI Summit NYC for $150 USD before 13 April 2026. After that, tickets are $200 USD.

The Paris edition sold out. If you're planning to join us in New York, early is the right call.

The foundations for enterprise-grade AI already exist. Come and see how they're being built — openly, responsibly, and together.

Secure your Early Bird ticket today!

Photos by Paul Johnson