The 2025 Annual Maintainer Check-In is now complete, a huge thank you to everyone who responded and to all the maintainers who continue to keep Drupal core moving forward.
As part of this process, we’ve confirmed that a number of Drupal Core subsystems and topic areas are currently without an active maintainer.
If you’ve ever thought about stepping into a maintainer role, or co-maintaining alongside others, now is the perfect time to get involved.
Why maintainers matterMaintainers play a key role in ensuring the quality, stability, and momentum of Drupal core.
Maintainers help shape the direction of their subsystem or topic area, guide contributors as well as triage issues and review merge requests.
You don’t need to be a long-time contributor, if you’ve been active in a related area or are keen to grow your involvement, we’d love to hear from you.
Learn more about the maintainer role:
Areas currently without an active maintainer SubsystemsIf you’d like to maintain or co-maintain one or more of these areas:
Once interest is expressed:
Thank you to everyone who contributes as a Drupal maintainer, your work is what keeps Drupal core secure, stable, and evolving.
Search engine optimization (SEO) is a rich and multi-dimensional craft, with numerous best practices and techniques to apply on your Drupal site. Optimizing your content, configuring an XML sitemap, and creating well-structured URLs are just a few examples of what should be done for SEO success.
Today we are talking about the community working group, What they do, and how you can help with guests AmyJune Hineline, Mark Casias, and Matthew Saunders. We'll also cover Drupal CMS Geo Images as our module of the week.
For show notes visit: https://www.talkingDrupal.com/530
TopicsAmyJune Hineline - volkswagenchick Matthew Saunders - jamesmatthewsaunders.ai MatthewS Mark Casias - omibee.com markie
HostsNic Laflin - nLighteneddevelopment.com nicxvan John Picozzi - epam.com johnpicozzi
MOTW CorrespondentMike Anello - drupaleasy.com ultimike
DrupalCon Asia 2025 in Nara, Japan, closed with a strong sense of momentum. Dries Buytaert’s Q&A format replaced a traditional keynote, and it paid off with direct insight into where Drupal is heading. The discussion tracked real trends across the ecosystem. Drupal CMS adoption continues to rise, the upcoming Drupal Canvas release is shaping expectations for easier site building, and the planned site template marketplace signals a shift toward faster delivery for agencies and teams.
Government interest in open source also stood out. Dries noted that digital sovereignty is becoming a priority across regions, positioning Drupal well for long-term public-sector growth. On the ground in Nara, the commitment felt real. The city’s mayor, Gen Nakagawa, opened the event by stating his goal to make Nara the most Drupal-friendly city in the world. It is rare for municipal leadership to tie open source directly to civic strategy, and it captured the tone of the week.
Beyond the sessions and the packed YouTube playlist, the Drupal CMS leadership team used the conference as a working sprint to align on priorities for the next six months. Agencies and end users shared where they need support, shaping the product roadmap. The result is a community that feels focused, confident, and ready for another cycle of growth.
INTERVIEWOPINIONTUTORIALSWe acknowledge that there are more stories to share. However, due to selection constraints, we must pause further exploration for now. To get timely updates, follow us on LinkedIn, Twitter, Bluesky, and Facebook. You can also join us on Drupal Slack at #thedroptimes.
Thank you.
Kazima Abbas,
Sub-editor,
The DropTimes.
For the past three years, the Drupal Advent Calendar has spotlighted shiny new modules, clever projects, and all sorts of open-source goodness.
This year we’re hanging up our “new module smell” stockings and doing something different.
It’s time to celebrate the people, the elves, reindeer, and magical snow-folks who keep the Drupal project running behind the scenes.
This year’s theme is The People of Drupal, and we’re on a quest to find the unsung heroes who quietly make the magic happen.
We’re asking initiative leads to nominate someone from their project who’s made a meaningful impact but hasn’t…
This year, DrupalCamp Scotland was held on the 7th November, at the University of Edinburgh.
On the morning of the conference I made the quick walk from by bed and breakfast and arrived at 50 George Square to join in with around 60 attendees to a day of talks and chatting.
The morning coffee and a selection of pastries was set out in the corridor outside the main room of the conference. I'm sure a few of the tasty pastries were lost to passing students.
After getting settled in we had a quick introduction session by Stratos Filalthis before we started the day.
The first talk of the day was with Paul McCrodden and Laura Waldoch, with their talk Less Is More: Streamlining 500+ Diverse University Sites into One Central Platform. Paul and Laura both work at the University of Cambridge and the talk was a look at how the university is taking the 500+ websites that are dotted around and consolodating them into a single resource. That single resource is powered by Drupal 11 and the talk looked at how they were building a Drupal install profile that could handle the requirements that these different sites had.
Managing content workflows in Drupal requires tools that track content from draft to publication. Drupal provides options for implementing workflows at different levels, from basic content moderation to field-level state management and webform submission tracking.
In the video above, you'll learn how to set up and configure Content Moderation, use field-level state management with the Field States Transitions module, and track webform submissions with the Webform Workflows Element.
The Drupal Association is excited to announce that our t-shirt design contest will be returning for DrupalCon Chicago!
We want to see the Drupal community's design ideas for the official t-shirt, available for all attendees to wear and enjoy. Do you have a fantastic idea in mind? Let’s see your creativity!
The winner will get THEIR design on the front of the official t-shirt for DrupalCon Chicago!
What the judges are looking forJudges are looking for a combination of creativity, impact, and relevance to the Drupal community. A design that tells a story and aligns with the values and aspirations of DrupalCon attendees is likely to capture attention.
While exploring bold ideas, consider how your design will resonate with a diverse audience. Think of classic elements that make a T-shirt memorable while pushing creative boundaries. Avoid overcomplicating things; sometimes less is more, especially if every element adds value to the message.
Now, for the finer details…Your design must include the DrupalCon Chicago Logo and will only be featured on the front of the t-shirt. Sponsor logos will be added to the t-shirts sleeves after the design is finalized.
Specs:All designs must be submitted by 21 December 2025 at 23:59 UTC, after which the submission form will close.
The Drupal Association will then select 4 designs to go forward to a public vote.
The top three designs as chosen by the Drupal Association will then be voted upon by the public, with voting open 5 January until 12 January 2026 at 23:59 UTC.*
The winning design will be printed on the front of the official DrupalCon Chicago t-shirt and the winner will receive a complimentary ticket to their choice of either DrupalCon Chicago 2026 or DrupalCon North America 2027.
References Winning designs from previous years Graphic Elements How to enterSimply create your design, then fill out our submission form by 21 December 2025 to submit your final design. We also ask that you include a sentence or two describing why you chose your design and how it represents the Drupal community.
So, what are you waiting for? Submit your design now, and please help us spread the word throughout the Drupal community!
Good luck!
* Dates for public voting dates are subject to change but will be open for a minimum of 1 week.
** Drupal Association staff and members of the DrupalCon Chicago Steering Committee will not be permitted to enter this contest.
Vibe-coding is all the rage today. Who needs a developer when you can get an AI to develop an application for you? There are scads of application development tools now that promise to create that app you always wanted -- and surprisingly, these often work!
Sustainable/Open Business Read MoreOmedia has put a lot of effort into getting the 1.2 version of MCP out. The module is now security covered, it works with the Tool API, adds OAuth authentication, a much better configuration system and a first preview of MCP Studio.
It now fully supports the HTTP and STDIO transports and independent where you want to source your tools, AI function calling, Drush commands or Tool API its all just available.
Read more about Giorgi Jibladze’s post on LinkedIn.
LMStudio is StableThanks to Andrei Ivnitskii (ivnish), the first stable version of the LMStudio provider for the Drupal AI module is now available. This release introduces full integration with LMStudio, giving developers a local, flexible, and GUI-driven environment for running and testing AI models directly from their Drupal site.
This integration is built for developers and data scientists who need a controlled testing environment, but find Ollama or vLLM too complex to set up and use. By pairing Drupal AI with LMStudio, you can iterate quickly, test safely, and work offline - perfect for preparing models before scaling up to cloud-based providers.
Try it out and help out in https://www.drupal.org/project/ai_provider_lmstudio
Meet the QA team!I met with the awesome AI Initiative QA team a couple of weeks ago and they have set up processes for how both manual and automated QA can happen on issues.
They have an issue where you can follow their work on here: https://www.drupal.org/project/ai_initiative/issues/3550700
The idea is to standardize the “Needs QA” tag, where you as a developer can request manual testing and get feedback on the process.
Next steps, include looking into how DrupalForge/DrupalPod can be used for AI purposes to start images based on an issue on DrupalForge with the push of a button and also local development environments.
If you want to get in touch with the team they are on #ai-quality-insurance Slack channel.
Work on the 2.0 release is on its wayWe have already started working on deprecations of modules, and other code for an 1.3.0 release and the work on all the refactors needed for 2.0 is started. The goal is to have a version ready by the end of the year and that fixes up a lot of architectural decisions made in 1.x branch and also removes a lot of features that were experimental, but never really usable.
Note that there will not be that many features in the 2.0 branch, but the focus is rather on better code architecture, better UX, extraction of modules and removal of features that don't work well.
By removing modules, we hope we can have an even faster development and release pace going forward.
Check the issue queue for more information.
Multiple Automators on one fieldOne of the larger rewrites for 2.0 is Automators - and one of the features this will bring is the possibility to add multiple Automators one field. While this has been possible in theory in the 1.x branches, this required you to do complex config imports - now they will be a part of the native UI/UX of the Automators.
This together with the Field Widget Actions, means that you can have multiple ways of generating one part of a field, or one button per part of a field.
This means that on an image field for instance, you could setup a button that generates the image, another that renames the file name and a third that creates an alt text.
Or if you want a summarize button in a friendly manner and another in a formal manner, you can have both on the same field.
This is ready to be tested on 2.0.x-dev, but please note that the external Automators modules will also need changes due to breaking changes.
A huge thanks to Bryan Sharpe from ImageX for this and anyone helping with testing and reviewing.
