17 Nov 2026
Drupal.org aggregator
The Drop Times: Drupal AI Content Review Alpha Can Overwrite Entire Fields
An AI suggestion may change more of a Drupal page than an editor expects. Tests reveal when the original content remains recoverable.
17 Nov 2026 2:44pm GMT
Specbee: How to make your Drupal content readable by AI Crawlers and LLMs with Markdown Mirror
Serve AI crawlers a clean Markdown version of your Drupal pages. See how the Markdown Mirror module works and how to set it up in 5 steps.
17 Nov 2026 12:13pm GMT
The Drop Times: Why Some Drupal 11 Module Fixes Have Yet to Reach Official Releases
A patch marked ready for review may still leave a Drupal 11 upgrade blocked. Issue histories show why packaged releases, runtime behaviour and maintainer decisions need separate checks.
17 Nov 2026 11:32am GMT
Drupal Association blog: In the Open: Telling Drupal’s story together
In the Open is a weekly series from Drupal Association Interim CEO Tiffany Farriss, sharing what she is hearing across the Drupal community and where the Association is headed. In this episode: why closing the gap between what Drupal can do and what the market knows is urgent, how the new Drupal advocacy program recognizes advocacy with contribution credit, and how it connects to the new Drupal Certified program.
"Advocacy has always happened in our community, but it's really been very scattered and unrecognized."
The following is a transcript of Tiffany's remarks, lightly edited for readability.
Closing the perception gap
Drupal is light years ahead of its reputation. Our software has improved much faster than our story, which leaves a real gap between what modern Drupal can actually do, especially around AI and Drupal CMS, and what the broader market realizes.
I'm Tiffany Farriss, the Interim CEO of the Drupal Association, and this is In the Open, my regular update on what's happening at the Association as we navigate a year of change.
Closing the perception gap is urgent. People increasingly learn about technology from AI assistants, and those assistants learn from the open web. When governments, universities, and enterprises run serious platforms on Drupal quietly without publishing about it, the public record falls behind. Every genuine story about Drupal on LinkedIn, on Reddit, YouTube, or any sort of tech blog improves what both people and AI systems know about our project.
You can't buy that kind of credibility. It comes from real people sharing results that are verifiable and accessible to anyone.
The Drupal advocacy program
That's why we launched the Drupal advocacy program. Advocacy has always happened in our community, but it's really been very scattered and unrecognized. Now, helping people understand what Drupal can do earns contribution credit through the exact same system that recognizes code and other community contributions.
Adoption and education are crucial parts of sustaining open source. A digital public good creates the most value when people actually know what it can do and use it.
Four rules for advocacy
To keep our credit meaningful, we set four clear rules.
First, translation, not amplification. Sharing someone else's post is fine, but the highest value work comes from your own perspective, your industry, your language, speaking to your clients, what you actually know.
Two, crowd surf, not AstroTurf. It's not about repeating someone else's words, it's about what you've done, your experience. And your organization's work is excellent evidence, as long as you're telling Drupal's story and not just pitching your own services. That's great, too. It's just not Drupal advocacy.
Three, proof over claims. Back it up. Whatever you say needs to be something that people can check, whether it's a live site or a working demo or a recorded talk or other data. Let's make it provable.
Four, quality and reach over volume. Ten super thoughtful pieces that reach 3,000 people outside of our community does way more for Drupal than 30 posts that reach the same 300 insiders.
What we saw in month one
We're already seeing what happens when people put this into practice. Thanks to Ryan Witcombe and the DA marketing team standing up this pilot, we reviewed 264 pieces of advocacy from nearly 150 contributors around the globe, in seven languages, in just one month alone.
We've awarded 2,400 contribution credits in that first month to people like John Money, Kai Gertz and Tojio ai Gertz, who took live AI demos onto stages at non-Drupal conferences. There's Ivan Zugec, who published over 100 videos helping newcomers learn about Drupal. And Mike Anello, doing what Mike Anello always does and has done for years. He uses his platform to spotlight and amplify the work of fellow community members.
You can see all 15 standout contributors from month one in the link below.
Advocacy and the new Drupal Certified program
Formalizing this advocacy also directly connects to how we're evolving the Drupal Certified Partner program into the new Drupal Certified program. Instead of a single weighted score, organization profiles will now show three distinct ways that organizations contribute: maker, patron, and advocate.
Drupal is a registered digital public good, and the code is free forever. But running and sustaining the project, for everything that we do beyond the code itself, takes sustained, ongoing operational resources. From the DA, it's roughly $10 per site every year. That doesn't count the roughly $30 or more in community time for ongoing roles like core release management, security coordination, and testing.
The new Drupal Certified program is a public trust registry that recognizes organizations that participate in our Drupal ecosystem in a sustainable way, shouldering their fair share of that ongoing operational load, either directly, or by sponsoring it through the DA, or directly to the community members who already do the work.
Publishing verified sector services and contributions as structured data makes certified organizations easier for AI answer engines and buyers alike to find and to cite. Longer term, it will give procurement teams a simple public ledger to verify whether and how a vendor actually participates in the open source ecosystem for the software solutions they're trying to sell.
It's a message of strength. Drupal is a digital public good, and organizations should choose vendors who sustain it.
How to take part
To keep our momentum going, the Association has set quarterly themes, and on-theme work earns double credit. Our Rotterdam theme is now wrapped up, and the next theme is around our Drupal 12 launch in December, though good Drupal advocacy qualifies year-round. Anything you publish about Drupal in 2026 still counts.
You can submit your work in about a minute at drupal.org/advocacy, or through the workflow in our Promote Drupal channel on Drupal Slack. We award credits monthly, alongside a roundup of the month's best work. So contributors get seen, not just scored, and we're going to be celebrating standout work that's been created as a part of this pilot at DrupalCon Orlando in 2027.
Stewarded open source takes more than just code. It takes infrastructure, it takes security, it takes release management, events, and advocacy, all working together to make sure that the right information is available at the right time to those who are looking for it.
No single organization can educate the market alone. When the Association does the shared groundwork once and recognizes the people who step up, we amplify those individual stories into a network effect. More people see what Drupal can do, more organizations choose it, and more contributors join in to keep our commons strong.
So thank you for helping the world see what Drupal can do, and I'll see you next week, in the open.
Follow the conversation
New episodes of In the Open publish each week. Subscribe on the Drupal Association YouTube channel to follow along.
With thanks to Stephen Cross of Second Signal Media for producing this series.
17 Nov 2026 9:26am GMT
Peoples Blog: Drupal 6 and 7 Websites: What Drupal 12 Means for Your Business Upgrade Plans
A business website may continue working for years without requiring major changes. Customers can visit pages, read information, submit enquiries and access services. From the outside, everything may appear normal. However, the technology supporting a website also evolves, and businesses that continue using older platforms may eventually face challenges when they need improvements, maintenance or new features.
17 Nov 2026 4:38am GMT
16 Nov 2026
Drupal.org aggregator
Nonprofit Drupal posts: November 2026 Drupal for Nonprofits Chat
Join us THURSDAY, November 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.
16 Nov 2026 9:59pm GMT
Droptica: When a Drupal product catalog needs an MCP server
Let connected AI assistants query approved product information without opening your entire catalog. Here's when a Drupal MCP server makes sense and what your team will need to maintain.
16 Nov 2026 5:02pm GMT
The Drop Times: When Search Answers Without a Click
Google Search is getting better at answering questions, but what happens when the answer is enough and nobody visits the website behind it? On 12 November, Google introduced Gemini 4 Hydrogen to Search, promising a better grasp of complicated questions, richer results and links to more sources. That sounds useful for people searching. For the publishers supplying those answers, the harder question is what happens after their work appears in a result.
There is reason to ask. Pew Research Center found that users clicked a traditional search result in 8% of visits when an AI summary appeared, compared with 15% when it did not. Those figures come from March 2025, well before Hydrogen, so they cannot tell us what the new model will do. Google has offered a different perspective: it says overall organic clicks from Search have remained relatively stable and the visits it sends are more engaged. The two accounts measure different things, and publishers have to live with that uncertainty.
For years, a useful search result was often a route to a website. Now a page can help answer someone's question without receiving the visit. Being discovered, being cited and being read on the original site are no longer interchangeable outcomes. That distinction matters to a small newsroom, an independent documentation project or a community publication that needs readers, contributors or subscriptions, not merely a mention in an AI response.
There is at least something practical to measure. Google's generative AI reports in Search Console provide a dedicated view of visibility in AI search features. They do not replace the need to examine clicks, engagement and the actions visitors take after arriving. Nor does the change require a new set of secret SEO techniques: Google's guidance still points site owners towards crawlable pages, clear internal links and helpful, accessible content.
For Drupal and the wider open-source web, this is about more than search rankings. Community sites, maintainers and independent publishers make information freely available because people need it. AI search may help more people encounter that knowledge, but who will keep producing and maintaining it if the visits that sustain those sites become harder to earn? That is the question worth carrying into the next round of Search changes.
Follow The DropTimes on LinkedIn and Bluesky, or join #thedroptimes on Drupal Slack.
Kazima Abbas wrote and curated this issue of Editor's Pick.
16 Nov 2026 3:39pm GMT
Gábor Hojtsy: Upgrade Status 5: triple the kinds of deprecations found, faster analysis and reporting, redesigned summaries for humans and LLMs
Upgrade Status 5: triple the kinds of deprecations found, faster analysis and reporting, redesigned summaries for humans and LLMs
This is a very long post, but trust me, it is worth it!
Upgrade Status is a Drupal module I maintain and is the centerpiece of getting a Drupal site ready for the next major version of Drupal core. It is currently used by more than 70,000 sites, and I hope this new version makes the work on all those sites significantly easier!
16 Nov 2026 11:31am GMT
Gspikes: City Website Design: What the 100 Biggest US Cities Put One Click Away
City website design study of the 100 biggest US cities: 9 in 10 homepages offer 311, payments and search, but under a third link to emergency alerts.
16 Nov 2026 7:00am GMT
15 Nov 2026
Drupal.org aggregator
Security public service announcements: Upcoming critical Drupal core releases on November 18, 2026 - PSA-2026-11-16
There will be a Drupal core security release for all supported branches on November 18, 2026 between 17:00 and 21:00 UTC. (To see this in your local timezone, refer to the Drupal Core Calendar.)
The Drupal Security Team urges you to reserve time for core updates at that time because exploits might be developed within hours or days.
The vulnerabilities are currently rated as critical and at least one can be exploited by anonymous users. More than one configuration is affected, so do not assume your site is safe.
We also recommend updating to the latest supported patch (bugfix) release for your site's version of Drupal before November 18, so that you can address any other upgrade issues before the security window.
Drupal Steward information
This issue is being mitigated by Drupal Steward. Sites that use Drupal Steward are already protected from known attack vectors. Other security advisories may be released on the same date without Drupal Steward mitigation. Sites should upgrade in the near future to ensure that they are protected from all published advisories.
Affected versions
All currently supported versions of Drupal core are affected, including:
- Drupal 11.4.x
- Drupal 11.3.x
- Drupal 10.6.x
Drupal 12.0.0-beta3 and 11.5.0-beta1 are also affected. New beta or release candidate versions will be provided following the security updates for the currently supported branches.
All versions of Drupal prior to 10.6.x as well as all versions of Drupal 11 prior to 11.3.x are end-of-life and no longer supported. Sites on those versions should apply the interim mitigation steps that will be provided in the upcoming security advisory, and update as soon as possible to avoid this and other publicly disclosed vulnerabilities.
Disclosure policy
Neither the Security Team nor any other party is able to release any more information about this vulnerability until the announcement is made. Security release announcements will appear on the Drupal.org security advisory page, which has RSS feeds. The announcement will also be made public on:
- The
#security-teamchannel of the Drupal community Slack - Bluesky
- Mastodon
- X (formerly Twitter)
- By email for those who have subscribed to our email list. (To subscribe to the email list: log in on Drupal.org, go to your user profile page and subscribe to the security newsletter on the Edit » My newsletters tab.)
If you have received an unsolicited email describing a potential Drupal core security issue, please do not forward it or act on instructions in it.
- Alex Pott (alexpott) of the Drupal Security Team
- Benji Fisher (benjifisher) of the Drupal Security Team
- catch (catch) of the Drupal Security Team
- cilefen (cilefen) of the Drupal Security Team
- David Strauss (david strauss) of the Drupal Security Team
- Greg Knaddison (greggles) of the Drupal Security Team
- Tim Hestenes Lehnen (hestenet)
- Lee Rowlands (larowlan) of the Drupal Security Team
- Dave Long (longwave) of the Drupal Security Team
- Drew Webber (mcdruid) of the Drupal Security Team
- Michael Hess (mlhess) of the Drupal Security Team
- Juraj Nemec (poker10) of the Drupal Security Team
- Pierre Rudloff (prudloff) of the Drupal Security Team
- Angie Byron (webchick) of the Drupal Security Team
- Jess (xjm) of the Drupal Security Team
15 Nov 2026 10:47pm GMT
Droptica: Search API and Solr for listings that scale
Slow filters and facet counts can hold back a growing Drupal catalog. Learn what a Drupal Search API Solr setup should index, how to handle languages and rebuilds, and when Solr earns its running cost.
15 Nov 2026 7:11pm GMT
14 Nov 2026
Drupal.org aggregator
Droptica: How a Drupal chatbot can answer product questions and guide customers
Help customers find suitable products, compare specifications, and locate manuals with a Drupal chatbot fed by your content. Here's what to build, connect, and test.
14 Nov 2026 4:59pm GMT
Droptica: Webhooks and event-driven Drupal integrations
Price, stock, and lead-time changes need to reach connected systems quickly. Learn how to choose and operate a Drupal webhooks module with reliable delivery, secure requests, and a clear recovery path.
14 Nov 2026 3:42pm GMT
Drupal Mountain Camp: Tickets for Mountain Camp 2027 Are on Sale

Tickets for Mountain Camp 2027 are now available. Our 6th edition, 10 years since the first Mountain Camp, takes place from 2 to 4 March 2027 at the Davos Congress Centre in Switzerland, and we would love to see you there.
At a Glance
- Dates: 2 to 4 March 2027
- Place: Davos Congress Centre, Davos, Switzerland
- Tickets: early bird CHF 90, regular CHF 120
Tickets
| Ticket | Price | Availability |
|---|---|---|
| Early bird | CHF 90 | First 25 tickets, until 30 November 2026 |
| Regular | CHF 120 | On sale now |
Speakers So Far
These are the first confirmed speakers. More featured speakers will be announced soon.
Keynote: Lena Fuhrimann
A Practical Guide to Fast and Private LLMs
Most AI tools send your text to someone else's servers. Lena's keynote shows how to run language models yourself, at home or at work, so your data stays with you and your costs stay clear.
She will cover the choices that actually matter: which model size fits the job, how to make it run faster and more efficiently, what hardware you need, and which software to run it on. Everything she shares comes from real setups.
Fireside Chat: Dries Buytaert
Dries Buytaert, founder and project lead of Drupal and Academy Member of the European Open Source Academy (EOSA), joins us in Davos for a fireside chat.
Featured Speaker: Pierre Dureau
Design tokens, the new frontier of Drupal theming
Drupal 11.5 comes with a new Design Tokens API. Pierre, Drupal core front-end manager, will explain why design tokens are important, why Drupal needed a new API when we already have Sass and CSS variables, and how to add tokens to your theme.
He will also show how the token format Drupal picked works with a large ecosystem of tools for designers and developers, opening the door to a fully automated, end-to-end design workflow in Drupal. The talk is for front-end developers, back-end developers, site builders, and content editors.
Featured Speaker: Alexander Varwijk
Mind the gap: done isn't delivered
Every team knows the moment work is done. Far fewer know how long it takes before anyone benefits from it: features wait for a release, updates wait for the next maintenance round, and fixes wait for a slot in the calendar.
Security releases are arriving at a record pace, and the time between a vulnerability becoming known and being exploited keeps shrinking. Alexander's talk looks at why the gap persists (from tooling in Drupal itself to habits and contracts) and what developers, module maintainers, agencies, and organisations could do to close it together.
Six Tracks
Sessions are organised into six tracks:
- Sovereign AI Base Camp: AI in Drupal, open models, running AI on your own infrastructure, European AI providers, and data sovereignty
- Frontend Ferrata: frontend frameworks, headless and decoupled architectures, design systems, accessibility, and performance
- Backend Ascent: backend languages, API design, architecture, migrations, DevOps, hosting, and application security
- Editorial Summit: authoring tools like Drupal Canvas and blökkli, content modelling, editorial workflows, and multilingual
- Open Col: open source sustainability and funding, public sector tech, open web policy, privacy, and community building
- First Pitch: getting started with Drupal, first contributions, mentoring, and career paths
See You in Davos
Whether you build sites, write content, maintain modules, or are just getting started with Drupal, there is something on the program for you. Early bird tickets are limited, so get yours before 30 November.
If you have questions about tickets or the program, write to us at info@drupalmountaincamp.ch.
14 Nov 2026 1:20pm GMT
13 Nov 2026
Drupal.org aggregator
Talking Drupal: Talking Drupal #578 - Rosetta
Today we are talking about Better traceability, better debugging, and Rosetta with guest Jürgen Haas. We'll also cover Maestro as our module of the week.
For show notes visit: https://www.talkingDrupal.com/578
Topics
- What Is Rosetta
- Rosetta Building Blocks
- Standards and Where to Join
- Rosetta End Goal Question
- Unifying Workflow APIs
- Fail Gracefully and Version
- Scaling Module Integrations
- AI Agents as Another UI
- Tools Discovery Explained
- Dependencies and Determinism
- Hooks Glue Code Reality
- Tracing with OpenTelemetry
- Sensitive Data Guardrails
- Big Challenges and Help
- Tool API Adoption Status
- Defining Rosetta Success
Resources
- One trace, inside and outside Drupal: a proposal for Rosetta
- Write a setting's rules once, in config schema, and use them for validation, forms and the published JSON SchemaMaestro
- Orchestration
- Dries blog post
- W3C open telemetry
- Drupal open telemetry
Guests
Jürgen Haas - lakedrops.com jurgenhaas
Hosts
Nic Laflin - nLighteneddevelopment.com nicxvan John Picozzi - epam.com johnpicozzi Emma Horrell - emma-horrell
MOTW Correspondent
Martin Anderson-Clutz - mandclu.com mandclu
- Brief description:
- Have you ever wanted to model a multi-step business process on your Drupal site, like a review and approval flow that routes tasks to different people, branches on their decisions, and can even hand steps off to AI? There's a module for that.
- Module name/project name:
- Brief history
- How old: created in Jun 2010 by Blaine Lang (blainelang) of Nextide, and is now co-maintained with Randy Kolenko (_randy)
- Versions available: 4.6.0, which works with Drupal 10.3 and 11, and 3.1.4, which also supports Drupal 9.4 through 11
- Maintainership
- Actively maintained, 4.6.0 came out last week
- Security coverage
- Test coverage
- Documentation: a handbook on drupal.org, plus a series of videos, including AI and agentic examples
- Number of open issues: 189 open issues, 55 of which are bugs, but many date back to the Drupal 7 and 8 branches, and half a dozen issues were closed just last week
- Usage stats:
- 785 sites
- Module features and usage
- Maestro's tagline sums it up: if it can be flow-charted, it can be automated with Maestro
- You build a workflow template in a visual drag-and-drop editor, and 4.6 adds a new ReactFlow-based editor as an alternative to the older diagram-js one
- Templates are made of tasks: interactive ones assigned to a user or role, plus non-interactive ones like If, And, Or, can set a process variable, batch functions, and spawn a sub-flow
- That gives you parallel approvals, serial steps, and dynamic routing, for example taking a different path depending on whether someone clicked Accept or Reject
- Each user gets a Task Console listing what's assigned to them, and tasks can be reassigned or delegated
- Under the hood, a background engine Maestro calls the orchestrator and does the work of advancing each process. You run it via a tokenized URL, cron, or drush maestro:orchestrate, and if it isn't running, nothing moves forward, so that's the first thing to set up
- Since 4.1 there's an AI task, built on the AI module, which can return a yes/no or true/false result that the next If task can route on, or store the response in a process variable
- There's also a Tool task for calling Tool API tools directly with no AI involved, and AI tools that let an agent list, start, and check on Maestro workflows
- New in 4.6, a trace view and trace archive let you see a snapshot of the process variables before and after each task, which is great for auditing or debugging
- For editorial and compliance teams, this is a natural fit for multi-stage content review, legal sign-off, or anything where you need a record of who approved what and when
- Maestro also has an ECA integration submodule: a Maestro task can fire an event for ECA to react to, and an ECA action can spawn a new Maestro process. We covered ECA in episodes #375 and #402
- Both ECA and Maestro let you visually model automation without code, but the mechanism is different. ECA reacts to events in the moment: something happens, conditions are checked, actions run, and it's done. Maestro is stateful: each process instance lives on for days or weeks, waiting for people to complete tasks, with the orchestrator advancing it in the background
- We haven't covered FlowDrop yet, but it's the newer option in this space, with an n8n-style graph editor where typed data flows from node to node, and it leans heavily into AI and data pipelines. It does have human-in-the-loop pauses, but Maestro's model is built around people and their task queues, while FlowDrop's is built around moving data through a chain of nodes
- The good news is they can work together: FlowDrop workflows can be published as Tool API tools, which Maestro's Tool task can call. And of course, the Rosetta initiative is all about reducing duplication of effort wherever possible, and making these solutions work seamlessly together
13 Nov 2026 7:00pm GMT