fidzu : Drupal

Managing multiple Drupal sites from a single codebase can deliver significant efficiencies, but configuration management quickly becomes complex as sites, features, and environments diverge. In his upcoming DrupalCon Chicago 2026 session, Jordan Thompson will demonstrate how Config Split can be used to structure multisite configuration in a predictable and maintainable way. The talk presents practical patterns, reusable templates, and workflow techniques designed to simplify configuration management across large Drupal multisite deployments.

06 Mar 2026 5:35pm GMT

The full programme for Drupal Developer Days 2026 shows how the Drupal ecosystem is responding to major shifts in modern web development. Artificial intelligence features prominently across multiple sessions, alongside discussions about Drupal CMS architecture, developer tooling, and evolving community practices. Together, the sessions suggest a community exploring how Drupal adapts to AI-assisted development while continuing to modernise its technical foundations.

06 Mar 2026 3:21pm GMT

Hot on the heels of beta 2, we are happy to announce the release of Display Builder 1.0.0-beta3! This new release focuses on stability, with a solid round of bug fixes, but also ships meaningful new features.

06 Mar 2026 1:00pm GMT

Join Us for Drupal Mountain Camp 2027

admin Fri, 03/06/2026 - 13:09

06 Mar 2026 12:09pm GMT

When people face urgent legal questions, finding trustworthy information quickly matters.

Recently, Electric Citizen partnered with LawHelpMN.org to help launch a new landing page that gathers key immigration resources in one place: www.lawhelpmn.org/immigration-legal-help

The page was created in response to Operation Metro Surge, a controversial immigration enforcement effort that has created significant disruption and uncertainty for many Minnesota communities. The goal was to provide a clear starting point where people can quickly understand their rights and find trusted legal help.

06 Mar 2026 9:03am GMT

Accelerating Drupal Core development

ashrafabed Thu, 03/05/2026

05 Mar 2026 3:37pm GMT

DrupalCon Chicago is going to be huge for Dripyard! We have one training, three presentations, one site template session, 400 stickers, and a very limited supply of beanies to give away!

05 Mar 2026 2:57pm GMT

The DropTimes contacted Drupal contributor Mike Herchel ahead of DrupalCon Chicago to discuss the sessions he will present during the conference week. His responses outline a full-day training on modern Drupal theming, a session on contributing to Drupal projects with Matt Glaman, and participation in a keynote highlighting ongoing work around Drupal CMS and the ecosystem emerging around it.

05 Mar 2026 2:42pm GMT

Implementing accessibility best practices on your Drupal website and taking care of search engine optimization may seem like separate priorities. In reality, they are more closely intertwined than you might expect.

05 Mar 2026 12:59am GMT

DDEV v1.25.1 introduced validation that checks for Docker Buildx, and you may encounter an error when running ddev start if your system isn't configured correctly. This post explains why this dependency exists, who's affected, and how to resolve it. Note that DDEV v1.25.2 will bundle a private Docker Buildx to eliminate this configuration requirement.

Table of Contents

Who's Affected

Most users won't need to do anything. Docker Desktop, OrbStack, and Rancher Desktop bundle Docker Buildx automatically.

You may need to take action if you're using:

• macOS with Lima or Colima - requires manual installation via Homebrew
• Ubuntu or Debian with Docker from Ubuntu/Debian repositories instead of Docker's repositories - older versions don't meet requirements
• NixOS - requires package update

If you're running Docker Desktop, OrbStack, or Rancher Desktop, you can skip this article.

The Error

When running ddev start on DDEV v1.25.1 without a compatible Buildx version, you'll see:

$ ddev start
Docker buildx check failed: compose build requires buildx 0.17.0 or later: docker CLI plugin "buildx" not found.
Please install buildx: https://github.com/docker/buildx#installing

Or if Buildx is installed but doesn't match the required version:

$ ddev start
Docker buildx check failed: compose build requires buildx 0.17.0 or later.
Installed docker buildx: 0.13.1 (plugin path: /usr/lib/docker/cli-plugins/docker-buildx)
Please update buildx: https://github.com/docker/buildx#installing

Why This Requirement Exists

This is an upstream dependency from Docker Compose, not a DDEV-specific choice.

Here's how we got here:

1. Docker Compose v2.37.0 (released June 2025) made the bake builder the default build backend
2. Docker Compose v2.40.2 (released October 2025) introduced a minimum version requirement for Docker Buildx (≥0.17.0)
3. DDEV v1.24.8 (released September 2025) updated to Docker Compose v2.39.3, which uses the bake builder by default
4. DDEV v1.25.1 (released February 2026) added validation to catch this configuration issue early and provide clear guidance

The requirement comes from Docker Compose itself. DDEV now validates your system configuration to prevent confusing build failures.

Solutions by Platform

macOS with Lima or Colima (or if you have this problem for any reason)

Install Docker Buildx via Homebrew:

brew install docker-buildx

After installation, configure Docker to find the plugin. Add cliPluginsExtraDirs to $HOME/.docker/config.json:

{
  "cliPluginsExtraDirs": ["/opt/homebrew/lib/docker/cli-plugins"]
}

You can see this information anytime with:

brew info docker-buildx

The post-install messages from Homebrew will show you the exact path for your system.

Debian

Debian 13 (Trixie) includes Docker Buildx v0.13.1 from the Debian repositories, which doesn't meet the ≥0.17.0 requirement.

Solution: Switch to Docker from the official Docker repositories.

1. Backup your DDEV projects with ddev snapshot -a.
2. Uninstall Docker packages from Debian repositories
3. Follow the Docker installation instructions in our documentation

The official Docker repositories provide current versions of all Docker components including Docker Buildx ≥0.17.0.

NixOS

NixOS users should track DDEV issue #8183. A NixOS patch is available - once merged, you'll get the fix through normal system updates without manual intervention.

Generic Solution

If the platform-specific solutions above don't work, you can manually place the docker-buildx binary in one of Docker's expected plugin directories:

Linux/macOS:

• $HOME/.docker/cli-plugins/
• /usr/local/lib/docker/cli-plugins/
• /usr/local/libexec/docker/cli-plugins/
• /usr/lib/docker/cli-plugins/
• /usr/libexec/docker/cli-plugins/

Traditional Windows (not needed for WSL2):

• %USERPROFILE%\.docker\cli-plugins\
• %ProgramFiles%\Docker\cli-plugins\

See Docker's plugin manager source for Linux/macOS and Windows for the complete list.

Alternatively, place the binary anywhere and configure Docker to find it by adding cliPluginsExtraDirs to $HOME/.docker/config.json (or %USERPROFILE%\.docker\config.json on Windows):

{
  "cliPluginsExtraDirs": ["/path/to/your/custom/plugin/directory"]
}

What's Next for DDEV

We're working to make this smoother in upcoming releases:

DDEV v1.25.2 (upcoming) will likely bundle a private Docker Buildx that DDEV uses exclusively. This eliminates the system configuration requirement for most users. I'm working on this in PR #8198.

Future releases will transition from our private Docker Compose binary to the Docker Compose SDK. This gives DDEV more control over upstream dependencies and reduces configuration complexity.

Need Help?

If you're still seeing issues after following these steps, reach out in any of the support channels.

---

This article was edited and refined with assistance from Claude Code.

05 Mar 2026 12:00am GMT

Build beautiful Drupal page layouts without writing a line of TWIG and CSSIf you've ever wished Drupal's block-based layout system came with a more visual, component-driven experience, the new Display Builder module is exactly what you've been waiting for.In this first video of the Display Builder series, Pierre walks through the Page Layouts feature, showing how fast you can build a fully styled, published page layout - no custom code required.

04 Mar 2026 1:19pm GMT

A Small Fix That Wasn't So Simple

My first contribution to the Drupal Metatag module started with what looked like a simple issue: fixing broken external documentation links. The task was logged as Issue #3559765 Fix broken links in the Meta tags section , and at first, it seemed like a quick cleanup job. But the deeper I looked, the more it revealed about the fragility of open source documentation, and how AI can speed up the repetitive parts of technical contribution work while still requiring careful human judgment.

Broken links may not sound exciting, but they highlight a widespread challenge in open source maintenance. Documentation links age fast. Websites vanish. URL structures change without warning. And because the Metatag module contains dozens of plugin files pointing to different sources, even a small fix meant a lot of detail work.

How AI Accelerated the Research Phase

To begin, I scanned the src/Plugin/metatag/Tag/ directory, which contains over 30 plugin files. This was where AI added real value, not by writing code, but by making the background research faster and more structured. I found six that had broken or unreliable links:

• SetCookie.php: Link to metatags.org was returning 404
• Rating.php: Link to metatags.org was broken, though the RTA link worked
• Google.php: Google webmasters link returned 404
• Expires.php: Link to csgnetwork.com calculator had connection errors
• Standout.php: Google News documentation was broken (404)
• NewsKeywords.php: Google News documentation was broken (404)

For each broken link, I needed to verify the issue, find a reliable replacement from an authoritative source, confirm it worked and was stable, then update it in the code without disrupting formatting or introducing linting errors.

Finding Every Link

Checking each file manually would have been tedious. Using AI, I generated efficient grep patterns for discovering URLs across the whole directory, like this suggestion that matched multiple URL styles: https?://|www\. That one line let me identify every external link across 30+ plugin files in minutes.

Verifying What Was Broken

The next challenge was figuring out which links actually worked. Instead of opening them one by one, AI recommended using a simple curl command to automatically test HTTP status codes:

curl -s -o /dev/null -w "%{http_code}" "https://example.com"

This approach let me quickly categorize links as 200 (working), 404 (broken), or 301 (redirects), giving me a precise list of which needed attention.

Finding Better Sources

When replacing links, AI helped search for credible alternatives, suggesting sources like MDN, W3C, IETF, or Google Search Central. It also helped compare multiple options and recommend the best one.

When AI Needed a Human Touch

Despite its efficiency, AI couldn't make every decision. Some choices depended on contextual understanding, deciding whether a replacement even made sense.

Google News Documentation

Two plugin files, Standout.php and NewsKeywords.php, both referenced Google News documentation that no longer existed. AI surfaced generic help pages, but none were relevant. Since the tags were already marked @deprecated, I chose to remove the links entirely. This was a judgment call informed by understanding the code's context and the importance of avoiding misleading or obsolete references.

Content Rating (RTA) Documentation

In Rating.php, the existing RTA link technically worked but wasn't reader-friendly. The AI proposed a few options, but ultimately, I picked Wikipedia's page on content rating systems. It included the RTA standard, offered better context, and felt more accessible, a human decision about user experience, not just URL accuracy.

What This Taught Me

Several clear themes came out of this contribution:

• Third-party documentation is fragile. Even long-established sources like metatags.org and csgnetwork.com can disappear or restructure, breaking countless references.
• Redirects can cause silent problems. A 301 redirect still "works," but introduces slower load times and unnecessary chains. Direct links are cleaner.
• AI excels at repetitive verification. Checking and verifying dozens of URLs took minutes instead of hours.
• Context remains human. AI found replacements but couldn't know when removing links made more sense or why accessibility might matter more than originality.
• Authoritative sources reduce maintenance. Linking to MDN, IETF, or W3C means fewer headaches for future maintainers and reviewers.

The Outcome

The final patch replaced or removed all broken documentation links:

Fixed with authoritative replacements:

• SetCookie: MDN documentation
• Google: Google Search Central
• Expires: IETF RFC 1123
• Rating: Wikipedia

Removed (no suitable or relevant replacements):

• Standout : Google News documentation removed
• NewsKeywords: Google News documentation removed

The workflow became smoother, faster, and easier to reproduce. Using AI to handle repetitive validation tasks allowed me to focus my attention on decisions that actually required human reasoning.

A Better Way Forward

This contribution showed how AI can accelerate contribution workflows without replacing the thoughtful judgment that open source development depends on. By blending AI-assisted discovery with context-aware decision-making, contributors can move faster and still produce work that's accurate, accessible, and maintainable.

Maintaining external documentation links might never be glamorous, but it's a perfect example of how AI can make quality improvements faster and more sustainable, one verified link at a time.

Bring practical, proven AI adoption strategies to your organization, let's start a conversation! We'd love to hear from you.

04 Mar 2026 12:00am GMT

There is a big party happening at DrupalCon Chicago, and I can't wait.

On March 24th, we're celebrating Drupal's 25th Anniversary with a gala from 7-10 pm CT. It's a separate ticketed event, not included in your DrupalCon registration.

Some of Drupal's earliest contributors are coming back for this, including a few who haven't attended DrupalCon in years. That alone makes it special.

If you've been part of Drupal's story, whether for decades or just a few months, I'd love for you to be there. It's shaping up to be a memorable night.

The dress code is "Drupal Fancy". That means anything from gowns and black tie, to your favorite Drupal t-shirt. If you've ever wanted an excuse to dress up for a Drupal event, this is it!

Tickets are $125, with a limited number of $25 tickets underwritten by sponsors so cost isn't a barrier. All tickets must be purchased in advance. They won't be available at the door. Registration closes March 18th, so grab your tickets soon.

Organizations can reserve a table for their team. Even better, invite a few contributors to join you. It's a great way to give back to the people who helped build what your business runs on.

For questions or sponsorship opportunities, please reach out to Tiffany Farriss, who is serving as Gala Chair and part of the team coordinating the celebration.

Know someone who should be there? Share this with them.

What matters most is that you're there. I can't wait to celebrate together in Chicago.

03 Mar 2026 3:55pm GMT

A new alpha experimental "Admin" theme just landed in Drupal 12 dev (and 11 dev) which is a merge of the Claro and Gin themes. Gin historically extended Claro which caused complications on both sides. The merged theme allows to iron out things much faster and more effectively without duplication of efforts in two themes. Going forward the plan is for "Admin" to replace Claro. Until "Admin" becomes stable, Claro will remain the default admin experience. https://www.drupal.org/project/drupal/issues/3556948

03 Mar 2026 2:56pm GMT

The 0.7.0 release was housekeeping - fixing the release notes command and clearing out deprecation warnings. 0.8.0 has two goals: add native GitLab issue fork and merge request commands, and make the CLI useful for developers using AI agents to assist with Drupal.org issues.

03 Mar 2026 2:00pm GMT

More good news in Drupal 12 development. Long time in the making, the Navigation module just replaced Toolbar as the default navigation experience in the upcoming Drupal version. Not only more customisable, the new UI is also faster to use even with deep administration trees. https://www.drupal.org/project/drupal/issues/3575171

03 Mar 2026 1:36pm GMT