Planet Drupal

Today we are talking about Drupalcon Rotterdam, Canvas and evaluating modules. We'll also cover Revision Graph as our module of the week.

For show notes visit: https://www.talkingDrupal.com/573

Read more

This blog has been re-posted and edited with permission from Dries Buytaert's blog.

Drupal is now light-years ahead of its reputation. Closing that gap is our #1 challenge, and it was the main message of my DrupalCon Rotterdam keynote.

Just over two years ago, I launched Drupal Starshot. I did it because I wasn't sure we could still innovate like we used to. It turns out we can.

Starshot became Drupal CMS, which brings together Site Templates, Recipes, Drupal AI, Drupal Canvas and more to make building websites easier.

Alongside that work, Drupal Core has become a faster and better framework for developers. A stronger Drupal Core helps us build a better Drupal CMS, while building Drupal CMS has driven further improvements in Drupal Core.

Unfortunately, many people outside the Drupal community haven't seen what Drupal can do today. In Rotterdam, I showed how far we have come and where we're going next, and we launched an advocacy program to help more people see how great Drupal has become.

If you missed the keynote, you can watch the video below or download my slides (86 MB).

More ways to reach more people

The first part of my keynote showed improvements for multilingual sites, JavaScript front-ends, headless Canvas, and Drupal AI.

Read more

Yet another amazing DrupalCon Europe has come to an end, leaving us with unforgettable memories. This time, we gathered in a city where futuristic architecture meets historic streets, home to Europe’s largest port and an absolutely unique food market. Rotterdam is a city that has embraced the future and innovation and is sailing towards it with all sails set.

Sponsorship for Mountain Camp 2027 Is Now Open sinduri Thu, 08.10.2026 - 16:46 Text

Sponsorship for Drupal Mountain Camp 2027 is now open. On March 2-4, 2027, the camp returns to Davos Congress for its sixth edition, ten years after the first gathering in 2017.

This year's theme is Humans with AI in the loop. Over three days of talks, hands-on workshops and contribution sprints, we look at how AI is changing the way we build software, why digital sovereignty matters, and where open source fits in.

The camp brings together people who care about the open web: developers, designers, AI practitioners, public-sector teams and open source communities from Switzerland and beyond.

Why Sponsor Mountain Camp

As a sponsor, you have a visible place at the camp and time to talk with the people who attend. Sponsoring lets you:

• Share your tools, services and expertise with people who build with open source and AI.
• Meet developers and technical leads in person, over three days.
• Connect with attendees between sessions and at the social events.
• Support an independent, community-run event that has brought people together since 2017.

We welcome sponsors of any size and from any field who want to support an open, independent web.

Sponsorship Packages

There are four packages: Platinum, Gold, Silver and Bronze. Places are limited, with 3 Platinum, 5 Gold and 8 Silver packages available.

Depending on the package, benefits include:

• Introducing a keynote speaker on stage
• A promotional video at the opening and closing ceremony
• An exhibition stand
• Job listings on the website and at the venue

Every package includes conference tickets and a logo on our sponsor page.

Read more

My DrupalCon Rotterdam talk moved from MCP to the CLI. How Canvas Tools and agent skills let a coding agent build Canvas pages through Drush, and what's still rough.

Google has updated its guidance to emphasize human review of AI-generated content. Here’s what changed, what it means for SEO, and what website owners should check before publishing.

Vibe coding or AI rejection? Learn the pragmatic middle path for Drupal teams: what to delegate to AI, when, and how to verify it.

Drupal is now light-years ahead of its reputation. Closing that gap is our #1 challenge, and it was the main message of my DrupalCon Rotterdam keynote.

Just over two years ago, I launched Drupal Starshot. I did it because I wasn't sure we could still innovate like we used to. It turns out we can.

Starshot became Drupal CMS, which brings together Site Templates, Recipes, Drupal AI, Drupal Canvas and more to make building websites easier.

Alongside that work, Drupal Core has become a faster and better framework for developers. A stronger Drupal Core helps us build a better Drupal CMS, while building Drupal CMS has driven further improvements in Drupal Core.

Unfortunately, many people outside the Drupal community haven't seen what Drupal can do today. In Rotterdam, I showed how far we have come and where we're going next, and we launched an advocacy program to help more people see how great Drupal has become.

If you missed the keynote, you can watch the video below or download my slides (86 MB).

More ways to reach more people

The first part of my keynote showed improvements for multilingual sites, JavaScript front-ends, headless Canvas, and Drupal AI.

Drupal has long had strong multilingual capabilities, but Drupal Canvas, our powerful new page builder, didn't yet support multilingual sites. Not only did we add multilingual support to Canvas, but we made all multilingual sites easier to set up.

Read more

Drupal AI can keep control of providers and model settings while Neuron handles agents and workflows. The new bridge also brings Neuron objects into Drupal's plugin system.

One node, many translations: how Drupal's translation model works, why Drupal 7 migrations break it, and the configuration that has to be right afterwards.

During the Driesnote at DrupalCon Rotterdam, one of the closing points was that Drupal has evolved light years beyond its reputation. And that's true. But it's also true that there is a whole world of people out there who've never heard of Drupal, and we need to talk about it differently to them than we do when talking amongst the Drupal-aware.

Enter The October "Off the Drupal Island" challenge.

The gist: During this, the spoooookiest month, go out to a local event (meetup, hackathon, etc.) where Drupal isn't, and no one has ever heard of "Drush" or a render array. ;) And ideally, where their local community presence is larger than ours.

For example:

• AI events
• JavaScript events
• WordPress events
• ...

NOT to pitch Drupal! To learn, quickly, and at scale. Be curious. Talk to people. Find out more about what they're building, where they're struggling, and what they wish was better.

Then, post a mini "field report" about your journey to this issue (there's a handy template there if you like).

We'll circle back on these learnings in a November AI Learners Club meeting, and strategize what kind of demo(s) we think would resonate best with these audiences, reflecting back their words and their use cases and pain points.

Then, we get louder about Drupal to them. ;) #DevRel at global scale.

Read more

DrupalCon brings love in every drop

So, last week was quite a big week, really. Both for me personally, more of that in a moment, and for the Drupal project as a whole, I think. 

Rachel Tue, 10/06/2026 - 21:19

Tags

• Drupal

• Read more about DrupalCon brings love in every drop
• Log in with GitHub or Google to post comments. Or, if you came across this post via Mastodon, just reply there!

Freedom with the form Attribute: More Flexible Drupal Views Exposed Filters Joel Steidl Tue, 10/06/2026 - 13:19 Drupal

Drupal Views exposed filters tend to accumulate controls.

A basic search form may start with a keyword field and a few filters. Add sorting and an items-per-page selector, and Drupal naturally renders everything as part of the same exposed form.

That makes sense structurally. It does not always make sense visually.

Sorting often belongs above the results. Items per page may belong next to pagination. Filters might live in a sidebar or drawer.

The HTML form attribute gives us a simple way to separate those concerns.

Form controls do not have to live inside the form

Most of the time, an input belongs to the <form> that contains it.

But HTML allows controls to explicitly reference a form by ID:

Read more

A first look at Gutenberg AI, the AI writing tools Ramsalt is building for Drupal Sohail Lajevardi Senior Drupal Engineer, Head of AI Engineering 06.10.2026

Most AI writing tools live in another browser tab. You copy text out, write a prompt, copy the answer back and fix the formatting. We wanted to get rid of that loop for people who write online. Gutenberg AI is the product we are building to fix that. It brings AI into the Gutenberg block editor, right next to the content it works on.

Video file Introducing Drupal Gutenberg AI by Ramsalt Lab

It is built on the Drupal AI framework, so it works with the chat provider you already use, whether that is OpenAI, Anthropic or a model running locally through Ollama. Everything it produces is standard Gutenberg blocks, so there is no lock-in.

Read more

A buyer asks an AI assistant about your product, but the answer sits behind a click or an outdated page. A Drupal AI-readability audit checks whether intended services can reach your content, whether HTML delivers useful answers, and whether facts stay consistent across outputs.

Maciej Lukianski walks through five layers beyond classic SEO: access, delivered HTML, buyer questions, JSON-LD alignment, and multilingual consistency, plus what actionable findings should look like.

Choosing a CMS for catalogues, multilingual pages, and integrations means comparing how each platform handles relationships, editorial work, and delivery—not just content types on a slide.

Drupal vs Contentful, Sanity, and Storyblok take different paths: integrated application vs managed headless services, core translation and moderation vs SaaS localization, and visual editing vs configurable Drupal workflows. Maciej Lukianski walks through content models, permissions, JSON:API options, AI boundaries, and what growth costs look like on each stack.

Meet Dashi, the 'new' multilingual demo for Drupal CMS

On September 29, Dries Buytaert showed a multilingual food magazine demo in his DrupalCon Rotterdam Driesnote. That was Dashi, the culmination of our work to give Drupal CMS 2.2 standout multilingual features. Here is what it is, how you can try it and how it came to be.

Gábor Hojtsy Tue, 10/06/2026 - 17:17

Introduction

Adopting AI can feel overwhelming, so I am sharing a few tales from my experience creating, maintaining, and assisting with contributed Drupal modules. AI can do a decent job building a "greenfield" Drupal module from scratch, so my first tale is about using AI to build and contribute a module. For my next tale, I want to talk about using AI to maintain an existing "brownfield" Drupal module.

Growing up in NYC, I found brownfields often intimidating, with some so toxic that it can take years for backhoes and dump trucks to remove the contaminated topsoil before construction can begin. With code, a brownfield can contain technical debt, orphaned code, missing tests, etc. Simply put, a brownfield contains unknowns, which means more things can go wrong while working on it. Sometimes a brownfield is so big you need heavy machinery to maintain it, and that is exactly how I felt about using AI on the Schema.org Blueprints module.

Maintaining a large module using AI

Gradually, I have been experimenting with AI to help maintain the Schema.org Blueprints. At first, I would just throw a one-shot prompt at the AI to address a single issue, and it would do a decent job diagnosing and resolving the problem. As I became more confident steering the AI, I started asking it to create issue forks, commits, pushes, and even MRs. As I previously stated in my AGENTS.md I always have "Require me to review all changes before committing and pushing code." and most models respect this rule.

Read more

Drupal 12 and the End of Legacy Debt: A Forced Modernization for Enterprise Engineering bhavinhjoshi Tue, 10/06/2026 - 14:02

Just last month, a prospective client came to Joshi Consultancy Services asking for a cheap cron script to fix a runaway disk usage issue. The reality? They were bleeding money on a deep architectural flaw in their Drupal ingestion pipeline. We see this constantly. For years, the enterprise software industry tolerated a quietly expensive habit: carrying technical debt forward.

Historically, major CMS upgrades were treated as little more than UI refreshes. Agencies seamlessly dragged deprecated code, outdated PHP environments, and fragile database structures from one major version to the next. The result? Senior engineers stuck acting as caretakers for legacy code, while CXOs bled budget on endless maintenance retainers just to keep the lights on.

With the December rollout of Drupal 12, that loophole permanently closes.

The platform is fundamentally altering the rules of engagement. Instead of merely suggesting best practices, Drupal 12 enforces strict architectural modernization right at the server level. Here is why this shift is a massive win for both engineering teams and business leadership.

The Eradication of Deprecated APIs

Spaghetti code. We all hate it. But until now, deprecated code could linger in a system for years, propped up by complex workarounds.

Read more

The National Center for Family Philanthropy worked with DevCollaborative to reimagine their website, CRM, and other communications channels to effectively manage and scale their network of over 500 philanthropic families representing more than 3,000 individuals.