06 Oct 2026
Drupal.org aggregator
Gábor Hojtsy: Meet Dashi, the 'new' multilingual demo for Drupal CMS
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.
06 Oct 2026 2:17pm GMT
Jacob Rockowitz: Vibing Drupal: Tale 2 - Using AI to maintain a module, exploring the AI-possible
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.
My comfort level reached a point where I am creating {module}-issue-maintenance agent skills that extend my drupalorg-issue-maintenance skills. These maintenance skills have agents to track remote issues in...Read More
06 Oct 2026 9:40am GMT
joshics.in: Drupal 12 and the End of Legacy Debt: A Forced Modernization for Enterprise Engineering
Drupal 12 and the End of Legacy Debt: A Forced Modernization for Enterprise Engineering bhavinhjoshi
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.
Drupal 12 changes this by aggressively stripping out all deprecated core APIs. The system physically rejects structural laziness. If an agency attempts to stack new logic on top of a legacy foundation, the application simply will not run. You build within clean, modern boundaries from day one. Period.
Enforcing Modern Infrastructure Floors
Previously, organizations delayed server upgrades to save short-term costs, forcing modern applications to run on aging environments.
No longer. Drupal 12 introduces non-negotiable infrastructure floors: a PHP 8.5 minimum runtime alongside raised database requirements (MySQL 8.0 / PostgreSQL 18). This isn't just backend housekeeping. By enforcing these modern tiers, the core framework guarantees a baseline of performance that cannot be compromised by budget-saving shortcuts.
Security as a Structural Guarantee
Enterprise security is too often treated as an expensive, opt-in audit layer applied long after development is complete.
By making Argon2id the default for password hashing, Drupal 12 integrates military-grade resistance against GPU-driven brute-force attacks directly into the core blueprint. For the C-suite, this is an immediate reduction in liability. Security transitions from an ongoing maintenance headache to a baseline structural guarantee.
The Business Outcome: Eliminating the Maintenance Drain
The most profound impact lands directly on the balance sheet.
For CXOs, these forced architectural boundaries solve the most expensive problem in enterprise software: unpredictability. When the core framework refuses to execute legacy PHP and automatically enforces top-tier security standards, the financial drain of technical debt is cut off at the source. Organizations can finally stop paying agency retainers to manage bloated, unmaintainable code.
Drupal 12 is not just a feature upgrade. It is a forced modernization of your engineering culture.
If your organization treats this version bump as a standard IT afterthought, you are actively funding your own future liability. Stop paying for temporary bug fixes. Engineer the blueprint first.
Are your servers, and your budgets, ready for the rollout?
06 Oct 2026 8:32am GMT
DevCollaborative: From Costly Subscriptions to Streamlined Workflow
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.
06 Oct 2026 6:53am GMT
Specbee: The tools around Drupal have become simpler, complementing Drupal. Read our take on how Canvas, components, Drupal CMS, and AI are changing Drupal work.
The tools around Drupal have become simpler, complementing Drupal. Read our take on how Canvas, components, Drupal CMS, and AI are changing Drupal work.
06 Oct 2026 5:39am GMT
Peoples Blog: Drupal Already Manages Content. So What Does AI Actually Add?
AI is becoming part of almost every software platform, and content management systems are no exception. Drupal is no different. But there is an important question that often gets lost in the excitement around AI: if Drupal already manages content so well, what exactly does AI add?
06 Oct 2026 2:41am GMT
05 Oct 2026
Drupal.org aggregator
Freelock Blog: Beyond Bigger Servers: Keeping Websites Online Under Bot Attacks
Beyond Bigger Servers: Keeping Websites Online Under Bot Attacks
05 Oct 2026 10:00pm GMT
Très Bien Blog: WordPal: Theme Drupal with WordPress block themes
WordPal: Theme Drupal with WordPress block themes
One of the difficulty with starting a Drupal website is the lack of diversity in available themes. There has always been more choice in the WordPress world for themes. Maybe, just maybe, Drupal could use WordPress themes and get the best of both worlds?
theodore
05 Oct 2026 6:30pm GMT
The Drop Times: The Demo Is Over. Now Drupal AI Has to Become a Product.
After Rotterdam, one part of Drupal's AI story is no longer theoretical. The Northmoor University demo brought AI search, content review, translation, editing and externally connected assistants together on the same Drupal site. That made a collection of modules feel closer to a product experience, but it also exposed the next question: whether organisations can depend on the path between those pieces in production.
The stack does not yet sit at one level of maturity. Drupal AI 1.5 and Canvas are stable and covered by Drupal's security advisory policy. Context Control Center is a release candidate, while Tool API and MCP Server remain in beta. Rotterdam showed that these parts can work together. Production teams now have to decide which combinations are mature enough to trust, govern and support.
Permissions, human review and traceability are central to that decision. The demo drafts changes rather than publishing them, leaving a person to review what the AI proposes. Tool API brings access checking into executable capabilities, while MCP can expose Drupal tools to assistants outside the site. Context Control Center moves instructions and organisational knowledge toward managed, reviewed material. Taken together, those pieces point toward a production requirement that goes beyond capability: teams need to know what an agent may read, what it may change, which tools it may invoke, what context it received and who remains accountable for the result.
Provider choice and the connection between Tool API, MCP and Canvas make the remaining maturity gap visible. Drupal's provider abstraction supports different commercial and locally operated models, but workflows still need to remain testable as model behaviour, tool calling and context limits change. The Drupal AI Initiative's follow-up also draws a clear line between what Rotterdam demonstrated and what is available today: the simplified MCP approach shown on stage remains a prototype. Canvas Tools, which lets agents manipulate Canvas through Tool API, is likewise still beta and is not covered by the security advisory policy.
That does not make Drupal AI simply ready or not ready for production. Different parts of the stack already support different kinds of real use, with different levels of risk. Rotterdam instead changes what Drupal AI now has to prove: that permissions remain enforceable, context can be governed, costs and activity can be traced, providers can change without losing control, and interfaces can survive upgrades. Productisation does not mean closing the ecosystem or putting everything inside one package. It means reaching the point where an organisation can understand what an AI system will be allowed to do before deployment, and explain what it actually did afterwards.
Follow The DropTimes on LinkedIn, X, Bluesky, and Facebook, or join #thedroptimes on Drupal Slack.
Allen Jason wrote and curated this issue of Editor's Pick.
05 Oct 2026 2:30pm GMT
The Drop Times: DrupalCon Rotterdam Jobs Board Pairs Vacancies With Community Recommendations
A handwritten board at DrupalCon Rotterdam carried more than vacancy notices. Attendees could also recommend community members actively looking for their next Drupal role.
05 Oct 2026 1:16pm GMT
Salsa Digital: Drupal AI Context — first release candidate available
Drupal AI Context first release candidate The first release candidate (RC 1) of Drupal AI Context , also known as Context Control Center (CCC), is now available. This is a major milestone for the project. After five beta releases and months of community testing, refinement and expansion, RC 1 marks the final stage before the first stable 1.0 release. We're currently planning to release CCC 1.0 in about a month, subject to what we learn from testing the release candidate. There may also be an RC 2 release prior to 1.0. CCC helps Drupal sites provide governed, reusable context to AI-powered features, from brand voice and editorial standards to organisational knowledge, governance rules and other information that AI systems need to work effectively.
05 Oct 2026 12:00pm GMT
1xINTERNET blog: When the Next Flash Flood Hits, Will Your Phone Have the Right Answer?
FlashFloodBreaker partner meeting in Metz: 1xINTERNET shares digital and regional resilience insights to help improve Europe's response to extreme flash floods.
05 Oct 2026 12:00pm GMT
DrupalEasy: Don’t be afrAId – trAIn!
Prevent the AI skills gap from becoming an expanse The rapid pace of updates, new versions and new Drupal core and contrib module functionality of the past 5 years almost feels like a crawl compared to the "high-velocity production model" guiding The Drupal AI initiative . It has screamed past beta versions and into an enterprise ecosystem boasting more than 15,000 installs, funding totaling in the $millions (USD,) as well as dedicated product streams like Inside AI and Outside AI; all in just over a year of its official launch. In addition, the community has about made it beyond the debate of if , and are now comfortably addressing the reality of how to best, (and importantly,) responsibly employ Drupal AI so that it contributes to not just efficiencies, but to improved workflows, outcomes and ultimately the bottom line; both Inside and Out . That, after all, is the measurement used in the viability of any new product or process. Astutely, the effort is grounded in the mission: " …to
05 Oct 2026 10:31am GMT
Gspikes: Website Migration SEO: How to Rescue One That Has Already Gone Wrong
The migration launched and traffic is falling. The eight causes in the order to check them, what Search Console tells you, how long recovery takes, and when to roll back.
05 Oct 2026 7:00am GMT
Webpro Company blog: AI translation in Drupal: keeping three languages current
An Estonian service page changes its delivery time from five days to ten. The English and Finnish pages still promise five. AI can translate the new sentence quickly, but someone must notice the change and decide when the other languages should go live. Start with service pages WebPro recommends testing AI translation on one content type first: perhaps ten service pages in Estonian, English and Finnish. Use them to check the complete journey from a source edit to a published translation. Translating a thousand pages at once says little about whether next week's changes will reach the right places. Drupal's AI capabilities received renewed attention in Rotterdam in late September. The Drupal AI initiative's updates discuss translation alongside other editorial tools. For a business, the…
05 Oct 2026 6:00am GMT
The Drop Times: Japan Drupal Association Holds Founding Assembly, Files for NPO Certification
Japan's Drupal community now has a new voluntary association with a formal NPO application under review. Its first work begins before legal incorporation is complete.
05 Oct 2026 5:22am GMT
Add new comment