18 Mar 2026

feedDrupal.org aggregator

The Drop Times: Designing for Difference: Practical Strategies for Building a Neuroinclusive Organization

Matthew Saunders will present a talk on neuro-inclusive system design at DrupalCon Chicago 2026, focusing on how organisational structures create friction for neurodivergent individuals. The presentation outlines practical changes to hiring, team operations, and leadership practices, positioning neuroinclusion as a systems-level design problem rather than a policy concern.

18 Mar 2026 2:46pm GMT

Nonprofit Drupal posts: March 2026 Drupal for Nonprofits Chat

Join us THURSDAY, March 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.

18 Mar 2026 2:14pm GMT

UI Suite Initiative website: Announcement – Display Builder 1.0.0-beta4 is released

Just one week after beta 3, we are happy to announce the release of Display Builder 1.0.0-beta4! This is a focused stabilization release, shipping a solid batch of bug fixes - in particular around Entity view overrides - alongside improved API error logging and a handful of developer-facing improvements.A big thank you to the 6 contributors who made this release possible: anruether, fmb, ipumpkin, mogtofu33, nickolaj, and pdureau.

18 Mar 2026 10:25am GMT

Tag1 Insights: Preparing File Upload Secure Validator for Drupal 12 with AI

At Tag1, we believe in proving AI within our own work before recommending it to clients. This post is part of our AI Applied content series, where team members share real stories of how they're using Artificial Intelligence and the insights and lessons they learn along the way. Here, Stefanos Petrakis, maintainer of the File Upload Secure Validator module, shows how he used AI to modernize a small but widely used Drupal security module and prepare it for Drupal 12.

From "I'll Get to It" to Done: Modernizing File Upload Secure Validator

I've been meaning to clean up the File Upload Secure Validator project and get it ready for Drupal 12 for a while now. This small, focused module has been around for nearly a decade. Despite its simplicity, it continues to serve more than 10,000 reported sites, and adoption has only accelerated with the introduction of Drupal AI. With the help of Cline and Claude, I finally did a full overhaul of the codebase: switching to Drupal 11-only support, expanding the automated test suite, and positioning the project for Drupal 12.

Graph showing Drupal usage over time and reflecting an increase since the release of Drupal AI.
Figure 1: Weekly File Upload Secure Validator usage report, that refects an increase in usage post Drupal AI release.

A Decade-Old Module Meets Drupal 12

This was the kind of maintenance work I kept putting off, the same feeling I get when I need to sit down and do my taxes. I knew the project needed cleanup and modernization, but I wanted a little push and some company in doing the work. The missing motivation and sense of camaraderie were, in many ways, the biggest challenges.

On top of that, I had a clear vision for how I wanted to extend the test suite, and I knew it would be time-consuming. Time, or the lack of it, was a major factor, especially for this kind of detailed, behind-the-scenes work on an open source module.

Turning a Wish List Into a Working Plan

To move things forward, I turned to Cline and Claude to help plan the future of the module. I started by writing down a list of "wishes" for the project: the improvements I wanted to see in the code, tests, and overall quality.

Cline turned that list into a detailed execution plan. It also generated questions about the approach, which led us into a few iterations before we settled on the final course of action. That planning process gave structure to the work and made it much easier to tackle in focused sessions.

All of the changes happened in the project's repository on the 2.2.x branch, with the final result released as version 2.2.1 on Drupal.org.

From Red CI Pipelines to Green Across the Board

Before this overhaul, the project had accumulated a number of issues:

After the overhaul, the picture looks very different:

This overhaul gave me the "manpower" and momentum I was missing to push the project forward. Just as importantly, it gave me confidence that I can continue supporting this module in the future.

AI-Amplified Maintenance for Critical Dependencies

Maintaining and supporting open source libraries can often become demanding because of limited time and resources. In client projects, dependencies on under-maintained open source projects can increase the effort required to maintain or upgrade the client's own platform.

Partners like Cline and Claude can change the game in an advantageous way. Such a change can help teams keep critical open source dependencies up to date, improve quality, and reduce risk without requiring a huge amount of extra human capacity.

This post is part of Tag1's AI Applied content series, where we share how we're using AI inside our own work before bringing it to clients. Our goal is to be transparent about what works, what doesn't, and what we are still figuring out, so that together, we can build a more practical, responsible path for AI adoption.

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

18 Mar 2026 12:00am GMT

17 Mar 2026

feedDrupal.org aggregator

Four Kitchens: When the people who run the platform aren’t the people who run the content

Dave Hansen-Lange

Dave Hansen-Lange

Director of Technical Strategy

Dave has been crafting websites since 2003 and has been active with Drupal communities around the world, sharing a passion for improving effectiveness, editorial experience, and long-term success.

January 1, 1970

A dashboard isn't just a summary page. It's a statement of priorities. Every item that appears, and everything that doesn't, tells editors what the organization believes actually matters.

That's worth thinking carefully about, because most dashboards aren't designed that way. They're assembled. A few shortcuts here, some default widgets there. The result is a starting screen that reflects what was easy to build rather than what editors actually need.

We help manage a Drupal platform that supports 500 editors across 130 sites. Getting a dashboard right for that kind of scale required us to ask some uncomfortable questions about what we actually valued, and what we'd been ignoring.

The quarterly PDF problem

Before we built our dashboard, someone on our platform team was manually generating reports for each of the 130 sites every quarter. Accessibility problems. Broken links. Duplicate content. All compiled, formatted, and sent out as a PDF.

It was better than nothing. But it had two serious problems.

First, people were unlikely to act on it. A PDF that arrives by email, detached from the website itself, is easy to file away and forget. Second, even the editors who did read it had no way of knowing whether they were improving until the next quarter's report showed up. The feedback loop was three months long.

This is a pattern that's common across organizations: the information that would most help editors do better work exists somewhere, but it's separated from the moment when they're actually ready to act on it. Updates get coordinated in chat threads. Content issues arrive by email. Broken link reports live in spreadsheets.

Editors are expected to carry all of that context across multiple tools and respond when something surfaces. For people whose primary job isn't web publishing, that's a lot to ask.
A dashboard brings that context back into the CMS, the place where the work actually happens.

The right moment to surface information

Editors don't log into a CMS at random. They arrive with a purpose: fixing a typo, publishing a new story, or checking whether a content import ran correctly. Whatever the task, they're already in the right mindset. They're thinking about the website and are ready to make changes.

That makes login the ideal moment to surface what needs attention.

On our dashboard, we highlight the pages with the most accessibility errors. We show a list of broken links. We surface draft content that never got published. These aren't things editors have to go hunting for. They appear right when editors are ready to do something about them.

We also use the dashboard to answer questions editors commonly ask us. One recurring one: how does content get into the site from other university systems? Faculty profiles, events, and course data. All of it comes in through automated imports. Drupal has robust tools for this, but its default interface exposes every option and setting, which is overwhelming for a content editor. So we'd never exposed it to them at all. Editors had no visibility into something that was working fine. They just didn't know it.

The dashboard gave us a place to show a simplified view of those imports: here's when faculty profiles last synced, here's the kinds of courses that are imported to this site. Just enough to answer the question and build confidence. Support requests about content imports dropped significantly after we added that.

From awareness to action

Information alone doesn't change much. The problem usually isn't awareness. It's timing.

When a broken link shows up in a quarterly report, the path from seeing it to fixing it is long and uncertain. Someone reads the report, makes a mental note, hopes they remember. Most of the time, they don't. By integrating that same information into the dashboard, the cycle changes:

content management dashboardQuarterly report → read → maybe remember → maybe act later

becomes

Login → see issue → click → fix

The feedback loop collapses from months to minutes. A broken link becomes a clickable item. A page stuck in draft becomes a quick decision. A list of accessibility errors becomes something an editor can start working through today.

One practical note from experience: some data sources introduce delays. Our broken link list comes from Siteimprove via API, which means that when an editor fixes a broken link, it won't disappear from the dashboard immediately. We didn't think about that until after we launched. It's not a dealbreaker, but it's worth designing around. At minimum, set expectations with editors so a fixed link that still appears on the list doesn't feel like a bug.

Every dashboard reflects a choice

Dashboards aren't neutral. They're curated.

Every item that appears is there because someone, explicitly or quietly, decided it mattered. Looking at our current dashboard, I can tell you what it says about our priorities: we value accessible content (pages with the most accessibility errors are one of the most prominent blocks), and we value simplicity and iteration over comprehensiveness.

content dashboard menu

What's not on the dashboard is equally revealing. We don't have traffic metrics or analytics. For this particular higher ed institution, that's a deliberate choice. The focus is on content quality and editor success, not marketing outcomes. For other clients we work with, traffic data would need to be front and center. The dashboard has to reflect what that organization actually cares about.

The conversations that happen while building a dashboard are often more valuable than the dashboard itself. When you ask your team what should appear on it, you surface competing priorities that usually haven't been written down anywhere:

  • What are editors most commonly asking us for help with?
  • What do we wish editors were doing that they aren't?
  • What should be the first thing someone sees when they log in?
  • What action should be easiest to take?

Those questions don't always have obvious answers. But asking them is how you build something useful rather than something that just looks like a dashboard.

And don't let perfect be the enemy of good. Our first dashboard was basic: simple tables, in a single column, nothing animated or interactive. If you get a dozen useful things on a dashboard, the organization as a whole is going to be better for it. Start there, then build up.

Guidance, not enforcement

There's a real risk that a dashboard drifts into feeling like a compliance tool, a place that exists primarily to point out what's wrong. If the only things editors see when they log in are warnings and error counts, the dashboard starts to feel like surveillance.

The same information can be framed very differently. A list of pages with accessibility errors isn't a punishment; it's a prioritized to-do list. A reminder about draft content that was never published helps an editor finish work that might otherwise be abandoned. A note that a component has recently changed gives editors a heads-up to check their pages before finding out something looks broken.

That last one is something we've gotten real value from. Our platform has 130 sites, which means making a breaking change to a component has a wide impact. Before we had the dashboard, that kind of communication was difficult. We still do targeted communications about breaking changes. But now we also use a simple announcements block (it pulls from a Google spreadsheet where each row is an announcement) to reach editors right where they're working. It's low-tech, but it means we can flag an upcoming change and tell editors exactly what to check. That's made us more comfortable shipping improvements we might otherwise have sat on.

The goal isn't to catch mistakes. It's to help editors succeed.

Supporting editors at scale

When your platform supports hundreds of editors across dozens of sites, traditional support breaks down fast. You can't train everyone personally. You can't answer every Slack message. And the editors who log in only a few times a year don't have the context that frequent users build up over time.

The platform itself has to take on more of that responsibility.

One thing that helped clarify our thinking: on the back end, your audience is actually more focused than it might seem. On the front end of a university website, you're trying to serve prospective students, current students, faculty, staff, donors, and more. But in the CMS, your primary audience is your content editors. There might be a few other users (stakeholders who log in occasionally to get a lay of the land, or interns assigned to clean up a single page), but by and large, you're designing for a pretty clear group.

For us, that meant focusing our first version on the editors who log in regularly and need to take action. We can add more guidance for infrequent users in later iterations. Starting with the core use case meant we shipped something useful without trying to solve everything at once.

A well-designed dashboard becomes a quiet guide embedded in the platform, helping editors move forward without needing someone from the platform team to step in. At scale, that kind of built-in guidance isn't just helpful. It's essential.

Join us at DrupalCon Chicago

In our session, "A Dashboard that Works: Giving Editors What They Want, But Focusing on What They Need," we'll share the story behind a dashboard built for 500 editors across 130 sites - the decisions we made, the things we got wrong, and how we figured out what actually belongs on a dashboard and what doesn't.

We'll walk through:

  • How we identified what editors needed versus what they asked for
  • How we balanced editorial priorities with technical realities
  • What we'd do differently if we were starting over

Whether you manage one site or one hundred, we hope you leave with something you can use.

If you go

If you're going to DrupalCon Chicago 2026, please make sure to attend the session with Dave Hansen-Lange and Albert Hughes.

Where: Hilton Chicago, 720 S Michigan Ave, Chicago, IL 60605, Williford B (3rd Floor)

When: Tuesday, March 24, 2026, 9:00-9:50am

For session details and tickets, click here.

The post When the people who run the platform aren't the people who run the content appeared first on Four Kitchens.

17 Mar 2026 9:33pm GMT

Specbee: How to add Taxonomy term references to Canvas (experience builder) components in Drupal

If you're struggling with taxonomy references in Drupal Canvas, you must read this! Add entity reference autocomplete fields using a simple $ref, no custom code needed.

17 Mar 2026 11:20am GMT

The Drop Times: Future-Proofing Accessibility for Government and University Drupal Platforms

A DrupalCon Chicago session titled "Future-Proofing Accessibility: Strategies for Government & University Platforms" will examine practical approaches to accessibility implementation as compliance requirements evolve in the United States. Speakers from Lullabot will present lessons from government and university projects, highlighting Drupal's accessibility capabilities, common pitfalls, and strategies for building compliant digital services.

17 Mar 2026 10:04am GMT

16 Mar 2026

feedDrupal.org aggregator

Talking Drupal: Talking Drupal #544 - World Cancer Day

Today we are talking about World Cancer Day, how they use Drupal, and why Drupal was the right choice with our guests Charles Andrew Revkin & Diego Costa. We'll also cover PDFa11y as our module of the week.

For show notes visit: https://www.talkingDrupal.com/544

Topics

Resources

Guests

Diego Costa - 1xinternet.com diegofcosta Charles Andrew Revkin - worldcancerday.org revkin

Hosts

Nic Laflin - nLighteneddevelopment.com nicxvan John Picozzi - epam.com johnpicozzi Steve Wirt - civicactions.com Swirt

MOTW Correspondent

Martin Anderson-Clutz - mandclu.com mandclu

16 Mar 2026 6:00pm GMT

The Drop Times: When “Free Beer” Meets Infrastructure Reality

The modern web runs on Open Source. The software itself remains freely available, but the infrastructure that sustains the ecosystem operates under fragile funding models. In a recent blog post, Drupal founder Dries Buytaert draws attention to a structural imbalance familiar across many open-source projects: the registries, repositories, CI systems, and update services developers rely on are widely treated as public goods, yet their costs are rarely shared proportionally by the organisations that depend on them.

In Drupal's case, maintaining the ecosystem's infrastructure costs roughly $3 million each year, covering servers, bandwidth, content delivery networks, software systems, and operational staff. When distributed across the installed base, that amounts to roughly $10 per active Drupal site annually. The Drupal Association currently operates with about $7.50 per site, leaving a modest but persistent gap. The shortfall does not immediately break systems, but it accumulates as technical debt: upgrades are postponed, legacy infrastructure remains in service longer than intended, and improvements move more slowly than the community might expect.

The deeper issue is structural rather than financial. Hundreds of thousands of sites rely on Drupal.org services, yet the cost of operating those systems remains largely disconnected from the organisations that benefit from them. Much of Drupal's infrastructure is sustained through a combination of event revenue, sponsorship, corporate memberships, and generous in-kind contributions from partners such as AWS, the Oregon State University Open Source Lab, and Tag1. These contributions are invaluable, but they also illustrate how much the ecosystem depends on goodwill rather than predictable funding mechanisms.

Dries suggests that the next stage of maturity for open-source ecosystems may involve exploring models that better connect infrastructure usage with long-term sustainability. The software itself remains open and freely accessible, but the systems that support development, distribution, and updates must remain reliable as the ecosystem continues to grow. Raising the question now allows the Drupal community to discuss potential approaches calmly, before infrastructure pressures turn the conversation into an urgent problem.

The following stories highlight notable developments from across the Drupal ecosystem during the past week.

DISCOVER DRUPAL

EVENT

ORGANIZATION NEWS

DRUPAL COMMUNITY

Additional developments from across the Drupal ecosystem were published during the week. Readers may follow The DropTimes on LinkedIn, Twitter, Bluesky, and Facebook for continuing updates. The publication also maintains a presence on Drupal Slack in the #thedroptimes channel.

Thank you.

Alka Elizabeth
Sub-editor
The DropTimes

16 Mar 2026 3:57pm GMT

Dries Buytaert: Never submit code you don't understand

A humanoid figure stands in a rocky, shallow stream, facing a glowing triangular portal suspended amid crackling energy.

Years ago, in the early Drupal days, you would see a mantra everywhere: "Don't hack core".

It showed up in issue queues, conference talks, support channels, stickers, and even on T-shirts. It was short and memorable, and it solved a real problem: too many people were modifying Drupal Core instead of extending it properly.

Over time the mantra worked. The ecosystem matured. Not just the software itself, but also the habits and expectations around it. Today you rarely hear people say "Don't hack core".

With AI changing how code gets written, we may need a new mantra.

In Open Source, all code needs to be understood and reviewed before it can be merged. That responsibility belongs to both contributors and maintainers. AI is changing how code gets written, but it does not change that responsibility. In fact, it may make it easier to forget.

Code you don't understand becomes someone else's problem. In Open Source, that someone is often the maintainer reviewing your patch.

Offloading bad code onto maintainers slows down reviews for everyone. Plus, you miss the chance to learn from the code and grow as a developer.

It shouldn't matter what tools you use. But if you submit code, you should be able to explain what it does, why it works, and how it interacts with the rest of the code.

Everyone starts somewhere. Even today's top contributors submitted imperfect patches early on. You are welcome here, with or without AI tools. Perfection isn't required, but understanding your code is. Own your code.

Maybe it's time for some new stickers and T-shirts.

Never submit code you don't understand.

Thanks to Natalie Cainaru, Jeremy Andrews and Gábor Hojtsy for reviewing my draft.

16 Mar 2026 3:37pm GMT

DrupalCon News & Updates: Drupal Powering Digital Ecosystems: Showcase your case study at the DrupalCon Europe 2026 Success Stories and Innovation track

As we look ahead to DrupalCon Europe 2026 in Rotterdam this October, we invite organizations, agencies, and digital leaders to submit their stories to the Success Stories & Innovation track.

This track showcases how Drupal is used today to power far more than websites. Across industries, Drupal enables organizations to build digital platforms, integrate complex systems, automate workflows, and create scalable ecosystems that support real business needs. From AI-driven personalization to DevOps automation and composable architectures, we want to highlight real-world projects that demonstrate how Drupal drives innovation.

In today's fast-moving digital landscape, organizations must continuously evolve to stay competitive. Digital transformation is no longer just about launching a new website - it's about building connected systems, automating processes, and delivering consistent experiences across multiple channels. Drupal plays a key role in this transformation as a flexible, secure, and extensible open-source platform that adapts to complex enterprise environments.

Foto by Paul Johnson https://flic.kr/p/2rzSoJP

Foto by Paul Johnson https://flic.kr/p/2rzSoJP

Why Drupal?

Drupal is not just a content management system. It is a powerful platform that can act as the backbone of digital ecosystems, integrating content, data, services, and applications into a unified experience.

Organizations use Drupal to power digital experience platforms, API-first architectures, multi-site environments, and enterprise integrations. Its flexibility, scalability, and strong security model make it a trusted choice for governments, universities, global companies, and nonprofits.

With the rapid growth of AI, automation, and composable architectures, Drupal continues to evolve. Teams are using Drupal together with modern DevOps pipelines, personalization engines, headless front-ends, and cloud platforms to create future-ready digital solutions.

Today, Drupal powers more than 1.6 million active sites worldwide and supports platforms used by governments, media companies, universities, healthcare providers, and global enterprises.

Foto by Paul Johnson https://flic.kr/p/2rzSprX

Foto by Paul Johnson https://flic.kr/p/2rzSprX

How organizations use Drupal for digital transformation

Drupal is used in a wide range of industries to power critical digital systems, large-scale platforms, and complex content environments. For many organizations, Drupal is not just a website CMS, but the foundation of a broader digital infrastructure.

Across sectors, Drupal supports platforms such as:

  • Government and public sector services
    Secure, accessible, and compliant platforms used by citizens, agencies, and institutions.
  • Higher education and research ecosystems
    Multi-site university platforms, student portals, research publishing, and internal collaboration systems.
  • Enterprise and corporate platforms
    Global websites, intranets, partner portals, and multi-brand environments.
  • E-commerce and transactional systems
    Commerce platforms connected to payment providers, product systems, and ERP integrations.
  • Healthcare and life sciences platforms
    Secure, multilingual, and compliant solutions for hospitals, research organizations, and health agencies.
  • Media, publishing, and content-heavy platforms
    High-traffic sites, editorial workflows, and multi-channel publishing systems.
  • Nonprofit and international organizations
    Fundraising platforms, campaign sites, and global content networks.
  • Content hubs and API-driven platforms
    Drupal as a central system connected to multiple front-ends, apps, and services.

In many of these environments, Drupal is part of a larger ecosystem that includes cloud infrastructure, external services, internal tools, and custom applications. We want to showcase how organizations are using Drupal in these real-world contexts.

Foto by Paul Johnson https://flic.kr/p/2rzR6US

Foto by Paul Johnson https://flic.kr/p/2rzR6US

DrupalCon Europe 2026 Rotterdam: Share your success story

Join us at DrupalCon Europe 2026 in Rotterdam this October and present your case study in the Success Stories & Innovation track.

This track is designed for organizations, agencies, digital managers, CTOs, CMOs, product owners, and business leaders who use Drupal to build impactful digital platforms and innovative solutions.

Our sessions are aimed at decision-makers and teams who want to understand how Drupal is used in real projects - not just as a CMS, but as part of larger digital ecosystems.

Whether you are building enterprise platforms, integrating AI, automating workflows, or connecting multiple systems, your experience can help others learn what is possible with Drupal.

What can you showcase?

For the Success Stories & Innovation track, we are especially looking for case studies that go deeper into how Drupal is used, how projects were built, and what makes them innovative.

We welcome submissions that explore themes such as:

  • Drupal as part of a larger ecosystem or platform architecture
  • Using Drupal beyond traditional websites
  • Composable, headless, or API-first implementations
  • Using AI in Drupal projects, including content automation, personalization, or intelligent search
  • DevOps, CI/CD, and automated deployment workflows
  • Integrations with CRM, ERP, marketing, or data platforms
  • Automation of editorial, content, or business processes
  • Managing multi-site, multi-brand, or multi-product platforms
  • Building long-term, scalable, and maintainable systems
  • Security, compliance, and accessibility at scale
  • Using Drupal as a content hub, data hub, or integration layer

We are particularly interested in stories that show how decisions were made, what challenges were solved, and what others can learn from the experience.

Tell us not only what you built, but why you built it that way.

Foto by pdjohnson https://flic.kr/p/2rzLG3s

Foto by pdjohnson https://flic.kr/p/2rzLG3s

Why participate?

Tell your story

DrupalCon is the perfect place to share how your organization uses Drupal to solve real problems - whether you are building platforms, integrating systems, improving workflows, or creating new digital experiences.

Give back to the community

DrupalCon is about learning, sharing, and connecting with one of the largest open-source communities in the world. Your experience can inspire others and help shape the future of Drupal.

Submit your case study: https://events.drupal.org/rotterdam2026/submit-your-session-proposal

Are you ready to showcase your Drupal-powered innovation? Submit your proposal for the Success Stories & Innovation track at DrupalCon Europe 2026 in Rotterdam and share your story with the global Drupal community.

Let's build the future of digital experiences together.

See you in Rotterdam!

16 Mar 2026 12:41pm GMT

Jacob Rockowitz: Drupal (AI) Playground: Crawling with Recipes

Incorporating AI into my development workflow

I've just begun exploring how to incorporate AI into my development workflow to tackle ongoing challenges for my client. Drupal's AI initiative is progressing rapidly with continuous updates and improvements. At DrupalCon Chicago, there will be numerous discussions about the future of AI in Drupal.

At the same time, through various channels like the Talking Drupal podcast and Planet Drupal feeds, we are hearing about people achieving significant success with AI-driven development using coding agents such as Claude Code. There is understandable hesitation within the Drupal community about adopting AI. Additionally, there is a lot of buzz and hype around AI replacing traditional software development.

Personally, I cut through the hype to find the clear truths about AI. I am specifically listening to what senior engineers like Steve Yegge, Kent Beck, and Martin Fowler say about the future of AI, software, and software development. I recently found "The Pragmatic Engineer" podcast, which, for me, is the best place to get genuine, honest, and tangible insights into the future of AI-driven development.

Adapting and adopting AI-driven development

My personal conclusion is that, for better or worse, AI-driven development is something individuals, teams, companies, and communities need to adapt to and adopt. For me, the starting point is setting up a local Drupal...Read More

16 Mar 2026 12:15pm GMT

Undpaul.de: Drupal AI 1.3.0: Why This Update Matters for Editorial Teams, IT, and Compliance

The update brings new features, but above all greater maturity to the practical use of AI in Drupal. It strengthens governance, editorial workflows, and production operations.

16 Mar 2026 10:28am GMT

The Drop Times: What Accessibility Audits Reveal About Drupal Websites

Accessibility has long been part of Drupal's core philosophy, yet accessibility audits continue to uncover recurring issues across many Drupal websites. Findings from the DrupalFit Challenge Vienna Edition show that even professionally built Drupal projects can struggle with problems such as insufficient colour contrast, missing alternative text, and improper heading structure. As regulatory requirements expand and digital services become more essential, accessibility reviews are becoming increasingly important for Drupal teams working across government, education, healthcare, and enterprise platforms. The audit results offer practical insight into where development teams can strengthen accessibility practices across Drupal projects.

16 Mar 2026 9:57am GMT

Capellic: Developer Roundtable AI Edition

The developers at Capellic share how they're integrating AI tools like Junie and Rovo Dev into their daily Drupal work - not to replace expertise, but to eliminate repetitive tasks, reduce friction, and free up time for more creative and complex problem-solving.

16 Mar 2026 4:00am GMT

Tag1 Insights: It's 106 Miles to DrupalCon and We Got a Full Tank of Gas: Tag1 Is Headed to Chicago

DrupalCon is coming back to Chicago, March 23 to 26, and Tag1 will be there as a Champion Plus sponsor with sessions, coffee, and a lot to talk about.

DrupalCon Chicago logo

This year's conference coincides with Drupal's 25th anniversary, which feels like the right moment to take stock of where we've been and where the platform is headed. We've been building and contributing to Drupal since its earliest days, and the work the community is doing right now, particularly around AI integration, Workspaces, and modern developer tooling, is some of the most exciting we've seen.

We're bringing three sessions to DrupalCon Chicago this year, covering testing, enterprise content staging, and what happens when you point AI at a seriously complex migration.

Drupal Test Traits: Learn by Example

Moshe Weitzman | Tuesday, March 24 at 9:00 AM | Salon A-1

Stylized portrait of Moshe Weitzman

Moshe will kick off our session lineup with Drupal Test Traits (DTT), the open source testing framework he built that takes a fundamentally different approach to testing content-heavy Drupal sites. Rather than spinning up empty databases and populating them with mock data, DTT tests against your actual site content, so you're validating the things that actually matter to your editors and visitors. Expect practical examples drawn from Massachusetts' mass.gov testing suite.

Workspaces Is Revolutionizing Drupal Core

Fabian Franz & Peta Hoyes | Wednesday, March 25 at 3:00 PM | Salon A-4

Stylized portraits of Fabian Franz and Peta Hoyes

Fabian and Peta will present on Workspaces, one of Tag1's major contributions to Drupal core and the foundation for true enterprise content management in Drupal. If you've followed our recent work on the Drupal AI Initiative, you already know that Workspaces is the governance layer we're extending to manage AI-driven changes, but the session goes well beyond AI, covering site-wide content staging, publishing workflows, rollbacks, translation management, A/B testing, and more. If your organization has outgrown single-item content moderation, this is the session for you.

Migrate Smarter: How a Structured AI Methodology Unlocked a Complex Drupal 7 to 11 Migration

Marco Molinari | Wednesday, March 25 at 3:00 PM | Salon A-5

Stylized portrait of Marco Molinari

Yes, we know, we're double-booked. How awkward! Marco's talk on AI-assisted migration covers how he used BMAD (Breakthrough Method for Agile AI-Driven Development) to migrate an Italian humor site (132K nodes, 100K newsletter subscribers, 18 custom modules, 93 contrib modules) from Drupal 7 to Drupal 11. What makes the session valuable is Marco's candid assessment of where AI-assisted development delivered real acceleration and where human expertise was still irreplaceable.

Come See Us (and Try Something New)

You'll find us at the big orange Tag1 booth on the expo floor with coffee in the morning, cool drinks in the afternoons, and comfy seating all day. Come recharge with us!

We're also offering a special sneak peek of Tag1's Drupal AI site builder. It can generate multi-page sites with real content, multilingual support, and layout customization, all using Plus Suite, Workspaces and Drupal best practices. If you catch Fabian and Peta's Workspaces session, the demo is a natural next step to see that content staging infrastructure in action. And if you've read our recent post on joining the Drupal AI Initiative, this is where that work comes to life. Come play with it, and tell us how you're using AI on your own sites.

On Tuesday evening, we'll have two tables at the Drupal 25th Anniversary Gala. We're looking forward to great food, a special anniversary beer, live music, and a chance to celebrate 25 years of Drupal with the people who built it. We'd love to see you there.

See you in Chicago!

16 Mar 2026 12:00am GMT