&w=3840&q=80)
We’re bringing you our latest monthly overview of top Drupal articles and news. We hope you enjoy this month’s selection!
Drupal AI 1.4.0: Unveiling Extensibility, Enterprise Resilience, and Advanced Guardrails
First on this month’s recap, we have Paul Johnson’s announcement of the release of Drupal AI 1.4.0, a mere two months after version 1.3.0 was released. As Paul also states, this two-month release cadence will continue as the product has become more mature and stable.
Drupal AI 1.4.0 brings five new areas of improvement:
- Improved extensibility of Drupal AI for contrib developers, thanks to Markdown Editor extensibility, news AI skills, and drush generate commands
- Normalisation for chat systems across processes
- Streamlined content management with AI automators and Views Bulk Operations
- Optimisation of enterprise-grade operations
- Advanced guardrails that also boost real-time security
Read more about Drupal AI 1.4.0
AI and the great CMS unbundling
We continue with an article from Dries that’s less Drupal specific and more relevant to the broader CMS conversation. In it, he describes what he calls the great CMS unbundling, i.e. the separation of the control plane from the execution plane of a content management system, which is happening because of AI.
Dries argues that, since AI lowers the cost of content creation, control and trust become even more important, and this is what the CMS should lean into. The main consideration here is how shared the work is, so, how many people, agents, channels and systems are involved.
Read more about the great CMS unbundling
Freedom is Not Free: A Model for Open Source Sustainability
The next article from June, this one by Tiffany Farriss of Palantir.net, is also not specifically focusing on Drupal, but rather open source software in general. It’s based on her recent talk from the United Nations Open Source Week about the need to improve the sustainability of open source software and the vast infrastructure it supports.
Giving Drupal’s contribution credit system as an example, Tiffany highlights the need for sustainable participation and sustainable use standards, which would make it easier to distinguish open source Makers from the Takers and the Fakers. This would also align procurement and public policy, with the goal of making it easy and expected to support open source projects.
Read more about open source sustainability
Getting Started with Views in Drupal CMS
Moving on, we have a tutorial from Ivan Zugec of WebWash showing how to get started with using Views in the new Drupal CMS. As Views is one of the most useful Drupal modules for site builders, they need to be comfortable working with it in the context of Drupal CMS, and on top of that it also integrates well with Drupal Canvas.
Ivan’s tutorial starts with the basics, i.e. explaining Views, creating them and managing fields. He goes more in depth as the article progresses, covering things like configuring the page and creating an admin back end page. As always, he also includes a video version of his tutorial for those who prefer watching.
Read more about using Views in Drupal CMS
Vibing Drupal: New Kids on the Block
Next up, we have an article from Jacob Rockowitz’s series of exploring AI, this one focusing on concerns people in the community have about the impact of AI and on how to better “onboard” AI tools.
The first challenge that Jacob highlights is the tendency to overprepare for AI and overthink our approaches for optimal collaboration. He identifies AI and LLM’s lack of persistent memory as one of the main reasons for this.
The solution that he proposes is to treat AI as a new developer that needs to be onboarded every morning and offboarded at the end of the day.
Read jrockowitz’s thoughts on collaborating with AI
Vibe Coding Drupal: A Force Multiplier for Contrib
In the sixth article, Martin Anderson-Clutz of Acquia documents the process of using AI as a co-maintainer when working on the Fullcalendar module, the maintenance of which he had taken over together with Jürgen Haas.
Critically, AI is really good at handling repetitive, tedious tasks, which are precisely what demoralises maintainers the most and causes burnout most easily. With the help of AI, Martin was able to cut down work that would have taken a full day to under one hour.
As he points out, this has very positive implications for open-source software maintenance and sustainability. While humans still need to be in the lead, vibe coding significantly reduces the barriers to getting the work done in the first place.
Read more about boosting Drupal maintenance with AI
Do AI coding agents recommend Drupal?
In the next article on this month’s overview, Dries shares his experiment of asking Claude Code whether it would recommend Drupal for the development of a new website. The response suggested Next.js plus a headless CMS first, followed by WordPress as the second and then Drupal as the third best option.
The key reasons why Drupal did not rank higher were high setup costs, thin and old training data, and the fragmented front-end tooling of Drupal. Session time risk was the major drawback, but as Dries highlighted, one of the goals of the new Drupal CMS is to address precisely this, with both Recipes and Site Templates easing the website creation process.
Read more about how AI coding agents recommend Drupal
Launching Drupal's Outside AI workstream
We conclude the June recap with a third article from Dries. In it, he announces the split of the Drupal AI strategy into two separate workstreams: the already existing Inside AI, led by Christoph Breidert of 1xINTERNET, and the new Outside AI, led by Acquia’s Scott Falconer.
Dries explains Outisde AI as “a person uses an agent, and the agent uses Drupal.” This will mostly serve three different types of users: newcomers to Drupal, experienced Drupal developers, and external agentic systems and workflow automation tools. This change aims to streamline Drupal’s role as the CMS control layer in the AI-dominated landscape.
