Drupal Planet

In this episode of Talking Drupal, we delve into the International Drupal Federation Initiative with our guest Tim Doyle, CEO of the Drupal Association. We explore the goals, structure, and potential impact of this initiative on the global Drupal community. Additionally, we cover the Modeler API as our module of the week, discussing its functionalities and future potential. Joining the discussion are hosts John Picozzi, Norah Medlin, Nic Laflin, and Martin Anderson-Clutz, who bring their insights and perspectives to the table.

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

• Meet the Guest: Tim Doyle
• Module of the Week: Modeler API
• Deep Dive into Modeler API
• Introducing the International Drupal Federation Initiative
• Governance and Global Impact
• Challenges and Future Prospects
• Annual Meeting and Governance Structure
• Challenges in Crafting Agreements
• Local Associations and Their Needs
• Engagement and Communication Strategies
• Regional Organizations and Governance
• US-Based Not-for-Profit Focus
• International Federation and Local Support
• Potential Risks and Governance Models
• Implementation Timeline and Costs
• Legal and Organizational Considerations
• Community Involvement and Feedback
• Conclusion and Contact Information

International Drupal Federation Initiative Recent DA Video Feature on The Drop Times ASBL

Tim Doyle - Drupal.org Tim D.

Nic Laflin - nLighteneddevelopment.com nicxvan John Picozzi - epam.com johnpicozzi Norah Medlin - tekNorah

with Martin Anderson-Clutz - mandclu.com mandclu

Modeler API

The Modeler API provides an API for modules like ECA - Events, Conditions, Actions, Migrate Visualize, AI Agents, and maybe others. The purpose is to allow those modules to utilize modelers like BPMN.iO, (and maybe others in the future) to build diagrams constructed of their components (e.g. plugins) and write them back into module-specific config entities.

Dear Readers,

Something subtle is shifting in the Drupal space. Over the past year, there has been a clear move to consolidate around Drupal CMS as the central message of the project. The intention is understandable. Making Drupal more accessible through low-code and visual tooling lowers the barrier for new users and small teams. But this unified direction, while strategic, risks unintentionally simplifying the perception of what Drupal is and what it is still capable of.

That concern comes into focus when we look at how DrupalCon Atlanta was structured. The sessions and keynotes gave the impression that Drupal CMS is not just a major initiative, but the primary path forward. Yet Drupal has always been more than a product. It has been a framework that adapts to a wide range of use cases, especially in enterprise environments. There was noticeably less visibility for advanced architectures, decoupled implementations, or the tools that support complex digital ecosystems.

This is where the reflections of community members like Jesus Manuel Olivas add useful contrast. His take on DrupalCon highlighted the gap between the official storyline and what many agencies are actively building. For organizations that rely on multi-site strategies, custom front-end frameworks, and API-first infrastructure, the current messaging does not quite reflect their day-to-day reality. These are not theoretical edge cases. They are living, large-scale implementations shaping digital strategy across industries.

Drupal's strength has always come from its flexibility. As the project evolves, it’s important to keep that core identity intact. There is room for Drupal CMS to grow without overshadowing the more complex and less visible work happening across the ecosystem. Honoring that balance is not just a matter of inclusion. It is a matter of relevance.

• "We Really Want More People Contributing to Drupal"

• The Future of Drupal Is Intelligent: Practical AI Integration for Smarter Web Experiences
• Drupal Public Data, Statistics & Silver Linings? An Exploration #6
• Drupal Introduces AI Initiative to Advance Drupal CMS
• Jesus Manuel Olivas' Alternative Vision for Drupal’s Future
• New Drupal Module Simplifies Configuration Exposure via GraphQL
• Drupal Modeler API Now Open for Community Testing
• Docktopus Launches All-in-One DDEV Stack for Local Web Development

• DrupalCamp Poland 2025: A Community-Focused Event with Strong Technical and Editorial Insights
• Women in Drupal Awards 2025: Applications Now Open
• What Drupal Agencies Are Bringing to London’s AI Summit

• Drupal, By Design: The drunomics Model for Sustainable Open Source

• amazee.io Announces Financial and Technical Support for Drupal AI Strategic Initiative
• Annertech Secures Full-Time Developer Role to Support LocalGov Drupal
   

We 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 and Facebook. You can also join us on Drupal Slack at #thedroptimes.

Thank you, 
Sincerely 
Alka Elizabeth 
Sub-editor, The DropTimes.

In Drupal Views, "grouping" refers to the feature found in the Format section's Style options. When configuring a view's format (Table, HTML List, Grid, etc.), you can select one or more fields to group results by. This creates visual sections with headers for each unique field value, organizing content into logical categories.

Standard Views pagination in Drupal operates on individual rows, without awareness of the grouping structure. This results in a broken, inconsistent pager with groups split across multiple pages.

Views Grouping Field Pager treats each group as a pagination unit rather than each row. This ensures:

• Groups remain intact across pages
• The pager navigation works as expected displaying the correct number of items

• Project libraries grouped by category
• News articles organized by date
• Product catalogs grouped by type
• Event listings arranged by date
• Research collections organized by topic

The module:

Since the launch of the Drupal CMS earlier this year, we’ve been hard at work documenting everything you need to build and maintain a site using this new, streamlined Drupal experience. Our goal is to make the Drupal CMS User Guide a go-to reference for site builders of all experience levels — especially those coming to Drupal for the first time.

In this post, we'll share an update on the current state of the guide, highlight two new sections we’re especially excited about, and show you how your team or company can help move the project forward.

How partnerships benefit open source projects and their customers

Palantir has been contributing to open source projects for over 25 years, and we’re one of the world's leading contributors to the Drupal project and community. Over the years we’ve channeled our expertise into creating key modules now incorporated into Drupal core and helping organizations across healthcare, government, education, and more with Drupal solutions tailored to their needs.

We’re proud to announce that Palantir was recently accredited as a Top Tier Drupal Certified Partner. There are currently only three other companies in the entire world who have achieved this status based on their contributions to the project and community.

The Certified Partnership program arose within the Drupal community to recognize the efforts of agencies that significantly contribute to the platform. Drupal Certified Partners are service providers that demonstrate three key characteristics:

• A high level of expertise in Drupal
• Commitment to contributing to Drupal core
• Building the Drupal community

The program is overseen by the Drupal Association, which requires firms to demonstrate how they meet these criteria. Organizations looking for Drupal partners can trust Drupal Certified Partnership status to signal that the company leverages best-in-class Drupal expertise.

Organizations that work with Drupal Certified Partners can trust they’re collaborating with experts who not only build with Drupal— they help build Drupal itself. 

At Palantir, we have a decades-long track record of building, maintaining, extending and promoting Drupal. As a Top Tier Partner, our clients trust us to maximize the platform’s capabilities to deliver best-in-class web applications—learn more about our Drupal consulting services today.

One of our most recent Drupal innovations is EditTogether: a free, multi-user editing solution that allows you to write and edit exactly where you publish. Rather than relying on external tools for collaborative editing, Edit Together allows you to edit, comment, and version control any field on your Drupal site. This eliminates the need for copy-pasting between your editor and publisher, avoids vendor lock-in, and allows you to take advantage of Drupal’s commitment to data sovereignty in your editing workflows.

EditTogether was conceived as part of our client work for a division of a state agency that provides Medicaid services to its residents. Their content workflows were high-friction and inefficient, relying on transferring content between several proprietary tools for writing, editing, and publishing. After auditing the available solutions, we realized there wasn’t a highly customizable, extensible editor in Drupal that could meet our client’s rigorous security requirements—so our team of developers and architects built a rich text editor using ProseMirror tools and connected it to Drupal via the Drupal Text Editor API.

After successfully delivering the EditTogether solution to the client, we’re currently validating EditTogether against other use cases and preparing for wider release back to the community.

When the Drupal Association needed to modernize their own site, they trusted us to deliver. In 2024, the Promote Drupal team wanted to migrate Drupal.org from Drupal 7 to Drupal 10 to show off Drupal’s most recent capabilities. Drupal.org is the online home of the Drupal community—so they needed to balance modernizing the site for new adopters and evaluators with making sure the 12,000 pages of documentation and 50,000 modules on the site remained continuously available for the entire community.

The Drupal Association wanted to work with a firm that not only knew Drupal inside out, but could oversee an incremental development plan to deliver the new content as fast as possible while still maintaining excellent service for the existing community. They chose Palantir.net to tackle the job: we delivered their needed site modernizations, dramatically improved test coverage, and built a new components-based design system to make adding new content a breeze.

We’re continuing to work with the Drupal Association to enhance their development team with added technical expertise and strategic consulting for the next phases of the modernization plan.

Open source technologies give developers and communities greater levels of transparency, flexibility, and financial accessibility in their digital projects—but maintaining open source projects can be challenging. Funding is frequently tight, and governance organizations are often overwhelmed with support requests. Open source solutions rely on organizations contributing their time, expertise, and money back into the technology to keep the lights on. However, many companies view open source contributions as simply a marketing opportunity or a “nice to have”—and the first thing to get cut when to-do lists start to get unwieldy.

The Drupal project wanted to incentivize more people to become active open source contributors— and this is where Certified Partnerships come in.

In exchange for meeting certain requirements (for example, a specified number of code commits, or donating a certain amount of money to the open source foundation), organizations can become certified partners of their communities—and enjoy a range of associated benefits.

Certified partnerships are also advantageous to organizations looking for agencies with proven expertise in a specific open source technology. When you work with a certified partner, you’re working with a company who actively helps to build and maintain the software you need. Partners have an intimate knowledge of the software they contribute to, and how to make the most of its capabilities. This knowledge and expertise also enable them to build custom solutions that work well with the core technology.

The Drupal Certified Partnerships program recognizes companies and organizations that have “gone above and beyond to sustain and grow the Drupal program”.

Drupal Certified Partnerships don’t just recognize code contributions—they also reward active community participation and encouraging Drupal adoption. Organizations qualify for Certified Partnership through a number of criteria:

• Contributions and commit credits, weighted towards the aspects of Drupal that are most frequently used and need the most work
• Proven case studies and success stories of delivering Drupal solutions to clients
• Annual financial sponsorship of the Drupal Association
• Event organization, participation, and sponsorship
• Staff acting in contributor roles, such as board members, mentors, or content moderators
• Drupal Association members on staff

The partnership program bolsters the thriving community around Drupal. When organizations are looking to partner with service providers with deep technical expertise, they have a robust marketplace of partners to choose from across regional markets and industries. 

Open source software (OSS) offers rigorously maintained, transparent solutions, without the hefty price tags of proprietary software— offering organizations of all sizes many incentives to default to open. According to the MIT Technology Review, “The free and open-source software movement is not only alive and well; it has become a keystone of the tech industry.” Indeed, the US Digital Services Playbook encourages federal agencies to evaluate open source solutions at every level of their stack.

When organizations decide to partner with external agencies for their digital transformation and modernization projects, there’s good news and bad news. The good news: numerous agencies build with open source solutions. The bad news: numerous agencies build with open source solutions.

Working with Drupal offers you transparency, flexibility, built-in accessibility, and data sovereignty. Working with a Drupal Certified Partner means you’re working with the people who build Drupal—and who are uniquely positioned to make the most of its powerful capabilities. As Drupal Association CEO Tim Doyle puts it, “Drupal Certified Partners are esteemed agencies that exhibit a profound level of expertise in Drupal, representing a select group of contributors crucial to the vitality and future prosperity of the Drupal ecosystem.”

We’ve been trusted by clients across numerous industries—and by the Drupal Association themselves—to build and deliver highly customized, performant Drupal solutions prioritizing user-centered design, accessibility, and turnkey security.

Learn more about our modular approach to custom Drupal development, or get in touch to discover how we can tailor our expertise to your organization’s needs.

A huge joint stable release of AI was made yesterday, where 10 modules were updated to 1.1.0. This is a major milestone in the Drupal AI brings a host of improvements and significant new features. 

Announcement by Marcus Johansson.

Some technical facts of the AI release:

• 105 issues fixed on AI Core, 75 issues fixed on AI Agents and roughly 25 issues on providers.
• 90 unique contributors on AI Core
• 244 files changed, 6500 lines added, 15044 lines removed on AI Core.

The most important update is function calling and a new agent framework, but here is a list of some other new features:

• Custom Operation Types
• Drush command to run AI
• Make the chatbot tell it what its doing, while its doing it
• Make it possible to add autocomplete fields to AI Automator Chains on CKEditor
• AI Content Suggestion can be based on the rendered HTML of the entity
• Normalized Structured Response
• Any many more

Some things directly connected to it:

• Drupal CMS AI agents have been updated and are now 90% effective up from 80%.
• A new test framework has been created so can see their effectiveness more clearly and non developers can create new tests.
• Improvements to AI search making use of function calling means they will more accurately search when you ask it to.
• Over 1000 people in the #ai slack
• An officially funded AI position and a Strategic initiative with multiple companies to make this sustainable
• 4600 installs of AI up from 3000 at Atlanta

The by far largest feature is the new Agentic framework where anyone can build agents without writing a single line of code. They are stored as configurations, meaning that you can build once, export and ship anywhere. And you can trigger them from anywhere you want - Chatbot, CLI, widgets, via an API etc.

Because Drupal is such a flexible and stable CMF, it will be the perfect agent runner. It adheres automatically to your contents permissions, files etc. while also keeping humans in the loop.

With the announcement of the new AI Initiative the future looks bright for Drupal and AI, the announcement is here if you haven't seen it.

We’ve implemented the tooling in a MCP-standardized way, which opens the door for seamless integration with external tools—and makes it easier to share and reuse agents and tools across systems and languages.

Outside of this we have also added a visual AI Agents Testing Tool where you can setup complex scenarios and retest them over and over, without having to be a developer. An advanced agent tracing tool is also in the pipeline!

And in the 1.1.0 release we also have the possibility to setup the agents via the modeler api and BMPN.io in a graphical way thanks to Jürgen Haas! He also has a visual way of building tools on the way.

The hope is that everything we build, should be possible to use directly from the browser!

🙌 Thank You

I thought I would thank a list of people that have contributed to this, but I checked the unique contributors via git and got 90 people. So I will not try to list everyone, because I will surely forget someone - but special thanks to James Abrahams and FreelyGive Ltd for giving me the opportunity to work with this full time (and more :) )!

It will be really exciting what kind of agents people will build, we have already tried everything from agents that checks configuration diffs for you, to agents that builds components from images. Hopefully your imagination, and not the framework, will be the limit ;)

We have a MR that can be tested for using this within Drupal CMS as well.

For anyone interested in the new agent framework I did a presentation on it at Drupal Days Leuven and also have a longer developers preview. More videos and documentation to follow.

As users click, scroll, and explore your website, something remarkable happens behind the scenes. A quiet engine hums in the background — not made of metal, but of code.

This blog has been re-posted and edited with permission from Dries Buytaert's blog.

Drupal launches its AI Initiative with more than $100,000 in funding and a dedicated team to build AI tools for website creation and content management.
 

Imagine a marketer opening Drupal and with a clear goal in mind: launch a campaign for an upcoming event.

They start by uploading a brand kit to Drupal CMS: logos, fonts, and color palette. They define the campaign's audience as mid-sized business owners interested in digital transformation. Then they create a creative guide that outlines the event's goals, key messages, and tone.

With this in place, AI agents within Drupal step in to assist. Drawing from existing content and media, the agents help generate landing pages, each optimized for a specific audience segment. They suggest headlines, refine copy based on the creative guide, create components based on the brand kit, insert a sign-up form, and assemble everything into cohesive, production-ready pages.

Using Drupal's built-in support for the Model Context Protocol (MCP), the AI agents connect to analytics tools and monitor performance. If a page is not converting well, the system makes overnight updates. It might adjust layout, improve clarity, or refine the calls to action.

Every change is tracked. The marketer can review, approve, revert, or adjust anything. They stay in control, even as the system takes on more of the routine work.

AI is changing how websites are built and managed faster than most people expected. The digital experience space is shifting from manual workflows to outcome-driven orchestration. Instead of building everything from scratch, users will set goals, and AI will help deliver results.

This future is not about replacing people. It is about empowering them. It is about freeing up time for creative and strategic work while AI handles the rest. AI will take care of routine tasks, suggest improvements, and respond to real-time feedback. People will remain in control, but supported by powerful new tools that make their work easier and faster.

The path forward won't be perfect. Change is never easy, and there are still many lessons to learn, but standing still isn't an option. If we want AI to head in the right direction, we have to help steer it. We are excited to move fast, but just as committed to doing it thoughtfully and with purpose.

The question is not whether AI will change how we build websites, but how we as a community will shape that change.

Drupal already has a head start in AI. At DrupalCon Barcelona 2024, I showed how Drupal's AI tools help a site creator market wine tours. Since then, we have seen a growing ecosystem of AI modules, active integrations, and a vibrant community pushing boundaries. Today, about 1,000 people are sharing ideas and collaborating in the #ai channel on Drupal Slack.

At DrupalCon Atlanta in March 2025, I shared our latest AI progress. We also brought together key contributors working on AI in Drupal. Our goal was simple: get organized and accelerate progress. After the event, the group committed to align on a shared vision and move forward together.

Since then, this team has been meeting regularly, almost every day. I've been working with the team to help guide the direction. With a lot of hard work behind us, I'm excited to introduce the Drupal AI Initiative.

The Drupal AI Initiative builds on the momentum in our community by bringing structure and shared direction to the work already in progress. By aligning around a common strategy, we can accelerate innovation.

The Drupal AI Initiative is closely aligned with the broader Drupal CMS strategy, particularly in its focus on making site building both faster and easier. At the same time, this work is not limited to Drupal CMS. It is also intended to benefit people building custom solutions on Drupal Core, as well as those working with alternative distributions of Drupal.

To support this initiative, we are announcing:

• A clear strategy to guide Drupal's AI vision and priorities (PDF mirror).
• A Drupal AI leadership team to drive product direction, fundraising, and collaboration across work tracks.
• A funded delivery team focused on execution, with the equivalent of several full-time roles already committed, including technical leads, UX and project managers, and release coordination.
• Active work tracks covering areas like AI Core, AI Products, AI Marketing, and AI UX.
• USD $100,000 in operational funding, contributed by the initiative's founding companies.

For more details, read the full announcement on the Drupal AI Initiative page on Drupal.org.

Some of the founding members of the Drupal AI initiative during our launch call on Google Hangouts.

Over the past few months, we've invested hundreds of hours shaping our AI strategy, defining structure, and taking first steps.

I want to thank the founding members of the Drupal AI Initiative. These individuals and organizations played a key role in getting things off the ground. The list is ordered alphabetically by last name to recognize all contributors equally:

• Jamie Abrahams (FreelyGive) – Innovation and AI architecture
• Baddý Breidert (1xINTERNET) – Governance, funding, and coordination
• Christoph Breidert (1xINTERNET) – Product direction and roadmap
• Dries Buytaert (Acquia / Drupal) – Strategic oversight and direction
• Dominique De Cooman (Dropsolid) – Fundraising and business alignment
• Marcus Johansson (FreelyGive) – Technical leadership
• Paul Johnson (1xINTERNET) – Marketing and outreach
• Kristen Pol (Salsa Digital) – Cross-team alignment and contributor engagement
• Lauri Timmanee (Acquia) – Experience Builder AI integration
• Frederik Wouters (Dropsolid) – Communications and outreach

These individuals, along with the companies supporting them, have already contributed significant time, energy, and funding. I am grateful for their early commitment.

I also want to thank the staff at the Drupal Association and the Drupal CMS leadership team for their support and collaboration.

I'm glad the Drupal AI Initiative is now underway. The Drupal AI strategy is published, the structure is in place, and multiple work tracks are open and moving forward. We'll share more details and updates in the coming weeks.

With every large initiative, we are evolving how we organize, align, and collaborate. The Drupal AI Initiative builds on that progress. As part of that, we are also exploring more ways to recognize and reward meaningful contributions.

We are creating ways for more of you to get involved with Drupal AI. Whether you are a developer, designer, strategist, or sponsor, there is a place for you in this work. If you're part of an agency, we encourage you to step forward and become a Maker. The more agencies that contribute, the more momentum we build.

Update: In addition to the initiative's founding members, Amazee.io already stepped forward with another commitment of USD $20,000 and one full-time contributor. Thank you! This brings the total operating budget to USD $120,000. Please consider joining as well.

AI is changing how websites and digital experiences are built. This is our moment to be part of the change and help define what comes next.

Join us in the #ai-initiative channel on Drupal Slack to get started.

How do you get a website back up, when it goes down?

In this episode, Ivan Stegic and Randy Oest discuss the impact of AI on junior developers and other roles, debating whether AI will be a disruptive force in the job market. They delve into the complexities of using LinkedIn for job hunting and effective networking strategies. The conversation shifts to new features in Figma, the potential of AI-driven coding tools like Cursor, and the importance of investing in junior developers. They also explore higher education design systems, innovative business strategies, and reflect on the balance between tactical and digital controls in modern cars. The episode wraps up with a light-hearted chat about slang, parental roles, and mentorship.

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

Ivan is a prominent leader in the Drupal community and the founder of TEN7, a Minneapolis-based technology studio specializing in Drupal development, strategy, and digital transformation. With a background in physics and a passion for problem-solving, Ivan transitioned from science to tech, ultimately finding a perfect fit in the open-source world of Drupal. Since founding TEN7 in 2007, Ivan has championed Drupal as a powerful, scalable platform for mission-driven organizations, nonprofits, and enterprises. Under his leadership, TEN7 has delivered impactful Drupal solutions for clients across education, healthcare, and government sectors. Ivan is also known for fostering a people-first company culture grounded in trust, transparency, and continuous improvement. Beyond his work at TEN7, Ivan is an active contributor to the Drupal project, frequently speaking at DrupalCons and camps, hosting the ONE OF 8 BILLION podcast (formerly the TEN7 Podcast), and mentoring others in the community. His advocacy for open source and ethical tech underscores his commitment to using Drupal to make the internet—and the world—a better place.

Randy is a design strategist, creative director, and accessibility advocate helping mission-driven organizations craft inclusive, user-centered digital experiences. With a background that spans visual design, front-end development, and content strategy, Randy specializes in building scalable design systems and digital platforms—particularly within the Drupal ecosystem. As the former Creative Director at Four Kitchens, Randy led cross-functional teams in developing cohesive design strategies, architecting front-end systems, and aligning user experience with organizational goals. He’s known for bridging the gap between high-level vision and implementation, ensuring that every project is both beautiful and deeply usable. Beyond his client work, Randy is a frequent speaker at DrupalCon, regional camps, and virtual events, where he shares insights on accessibility, usability, and design systems. A passionate advocate for open-source collaboration and digital equity, he is committed to making the web a more inclusive and empowering space for everyone.

• Debunking AI Myths: Junior Developers Are Here to Stay
• Casual Catch-Up: Podcast Conversations and AI Avatars
• LinkedIn: A Wasteland or a Goldmine?
• Creative Networking: From Fortune Tellers to Meaningful Connections
• Figma Innovations: Draw and Sites
• The Future of Coding: AI Tools and Junior Developers
• Flying Cars and Spam Texts
• Dealing with Spam Texts
• Exploring Higher Education Design Systems
• The Onion's Creative Agency
• The Importance of Tactile Controls in Cars
• Wrapping Up and Future Plans

Ivan Stegic - TEN7 ivanstegic Randy Oest - amazingrando.com amazingrando

The Modeler API is a new module that has been created by the Drupal community to address the requirement of existing modules and ecosystems with complex configurations, providing modern and easy-to-use UIs for non-technical users so they can independently create, modify, and maintain their own sites. Examples of such ecosystems are ECA (Events, Conditions, Actions - Drupal's modern rules engine), AI Agents, and Migrations.

With privacy regulations like GDPR, CCPA, and ePrivacy directives tightening globally, implementing a robust cookie consent solution on your Drupal site is essential. Drupal offers several cookie consent modules to help website owners comply with these laws while enhancing user trust. In this blog post, we’ll compare the most prominent Drupal cookie consent modules, including Klaro Cookie & Consent Management, to help you choose the best fit for your site. We’ll explore their features, ease of use, and compliance capabilities, concluding with a detailed comparison table.

Disclaimer: No liability is assumed regarding compliance with GDPR or other regulations. Always consult legal experts to ensure your site meets local privacy requirements.

Here’s a breakdown of the key Drupal cookie consent modules available as of June 2025, based on their functionality, configuration options, and compliance features:

• Source: https://www.drupal.org/project/klaro
• Description: Klaro is an open-source consent management module that integrates the Klaro! JavaScript library, offering a lightweight, user-friendly way to manage cookie consent. It provides fine-grained control over services, purposes, and external resources, ensuring compliance with GDPR and ePrivacy regulations. Klaro automatically blocks non-essential scripts until user consent is granted and supports multilingual sites.
• Key Features:
  • Customizable consent banners with opt-in/opt-out options.
  • Automatic attribution of HTML script tags to block third-party resources.
  • Supports multiple dialog modes (Silent, Notice, Modal, Consent Modal).
  • Multilingual support with translatable texts.
  • Blocks unknown external resources by default.
  • Stores consent decisions in a strictly necessary cookie (klaro).
  • Actively maintained with a stable 3.x branch release candidate as of December 2024.
• Ease of Use: Requires some technical knowledge to configure services and purposes, but the admin interface is intuitive. Automatic attribution simplifies script management for developers.
• Best For: Sites needing a lightweight, open-source solution with granular control over third-party services.

• Source: https://www.drupal.org/project/cookies
• Description: The COOKiES module focuses on GDPR-compliant user consent management, enabling third-party integrations (e.g., Google Analytics, Facebook Pixel) to function only after user consent. It offers a fully customizable, responsive banner and supports accessibility.
• Key Features:
  • Fully responsive and translatable UI.
  • Accessibility-compliant design.
  • Supports third-party integrations like Google Tag Manager, Matomo, and video embeds.
  • Customizable styling via CSS variables or SCSS.
  • Includes a “Cookies settings” link for user preference changes.
  • Configurable scroll limit to delay banner display for performance.
• Ease of Use: Developer-friendly with examples for integrating third-party modules. Configuration is straightforward via the admin interface, though styling may require CSS knowledge.
• Best For: Sites with multiple third-party integrations needing a customizable, accessible banner.

• Source: https://www.drupal.org/project/cookieyes
• Description: CookieYes is a third-party service integrated into Drupal, offering automated cookie scanning and compliance with GDPR, CCPA, and other privacy laws. It provides a user-friendly front-end integration without backend modifications.
• Key Features:
  • Automatic cookie scanning and categorization.
  • Customizable opt-in/opt-out banners with multilingual support.
  • Geo-targeting to display banners only in specific regions.
  • Consent logging and proof-of-consent documentation.
  • Supports Google Consent Mode and IAB TCF.
  • Blocks non-essential scripts until consent is granted.
• Ease of Use: Extremely easy to set up due to automated scanning and minimal configuration. Ideal for non-technical users, though it relies on an external service.
• Best For: Sites seeking a plug-and-play solution with automated compliance features.

• Source: https://www.drupal.org/project/eu_cookie_compliance
• Description: One of the oldest and most widely used Drupal cookie consent modules, EU Cookie Compliance provides a GDPR-compliant banner with flexible consent methods. It supports blocking cookies and scripts until consent is obtained and is actively maintained with Drupal 10 compatibility.
• Key Features:
  • Multiple consent methods: consent by default, opt-in, opt-out.
  • Customizable banner placement (top/bottom) and styling.
  • Geo-targeting with Smart IP or GeoIP modules.
  • Multilingual support for global audiences.
  • Blocks cookies and scripts until consent is granted.
  • Roadmap for a 2.0 rewrite with enhanced features.
• Ease of Use: User-friendly configuration with clear options for consent methods and banner placement. Some advanced features (e.g., geo-targeting) require additional modules.
• Best For: Sites needing a mature, reliable solution with EU-specific compliance options. Note: Maintainers recommend switching to Klaro for modern Drupal sites due to focus on maintaining stable releases.

• Source: https://www.drupal.org/project/simple_klaro
• Description: A lightweight alternative to the main Klaro module, Simple Klaro provides a minimal implementation of the Klaro! JavaScript library. It relies on a single configuration file for settings, making it ideal for simple setups.
• Key Features:
  • Basic consent banner with customizable texts and translations.
  • Controls script execution based on consent.
  • Deletes cookies via regular expressions when consent is revoked.
  • Minimal configuration via a single file.
  • Multilingual support based on HTML lang attribute.
• Ease of Use: Requires manual configuration of the Klaro JSON file, which may be challenging for non-developers. Cache clearing on settings changes simplifies updates.
• Best For: Small sites or developers comfortable with JSON configuration seeking a lightweight Klaro implementation.

• Source: https://www.drupal.org/project/cookieconsent
• Description: CookieConsent integrates the Cookie Consent JavaScript plugin (version 2.0.9) to provide a simple, lightweight solution for EU Cookie Law compliance. It’s maintained by Synetic but has no stable releases as of June 2025.
• Key Features:
  • Lightweight consent banner with basic customization.
  • No external module dependencies.
  • Uses an older version of the Cookie Consent plugin.
  • Limited to basic cookie consent functionality.
• Ease of Use: Easy to set up for basic needs, but lacks advanced features and modern compliance options. Configuration is minimal but dated.
• Best For: Small sites with minimal cookie usage needing a quick, basic solution. Note: Limited maintenance and outdated plugin version make it less suitable for modern compliance needs.

When selecting a cookie consent module, consider the following factors:

• Compliance Needs: Ensure the module supports GDPR, CCPA, and other relevant regulations. Features like consent logging (CookieYes) or geo-targeting (EU Cookie Compliance, CookieYes) are critical for region-specific compliance.
• Ease of Setup: Non-technical users may prefer CookieYes for its automation, while developers might opt for Klaro or COOKiES for customization.
• Third-Party Integrations: If your site uses tools like Google Analytics or Facebook Pixel, COOKiES and Klaro offer robust integration options.
• Multilingual Support: All modules support multilingual sites, but CookieYes and EU Cookie Compliance excel in global audience targeting.
• Maintenance and Support: Actively maintained modules like Klaro, EU Cookie Compliance, and CookieYes are safer bets for long-term use. CookieConsent’s lack of stable releases is a concern.
• Performance: Lightweight options like Klaro and Simple Klaro minimize performance impact, while CookieYes’s external service may introduce slight overhead.

Choosing the right Drupal cookie consent module depends on your site’s specific needs:

• Klaro is ideal for developers seeking a lightweight, open-source solution with granular control and active development.
• COOKiES excels for sites with multiple third-party integrations and a focus on accessibility.
• CookieYes is perfect for non-technical users needing automated scanning and comprehensive compliance features, though it’s a paid service.
• EU Cookie Compliance remains a reliable, mature option for EU-focused sites, but its maintainers suggest transitioning to Klaro for modern setups.
• Simple Klaro suits small sites with basic needs and developers comfortable with manual configuration.
• CookieConsent is outdated and best avoided for modern compliance requirements.

For most Drupal sites, Klaro or CookieYes are the top contenders due to their balance of features, compliance, and maintenance. If budget is a constraint, Klaro’s open-source nature makes it a strong choice, while CookieYes is worth the investment for automated compliance and peace of mind.

Note: Always verify compliance with legal experts, as module features may not cover all regulatory nuances.

Welcome to the June 2025 DDEV Newsletter
This month: TYPO3 Community Budget Proposal (VOTE NOW), Randy is back from bikepacking, Running Old PHP versions, Vite and DDEV with WordPress, DDEV Architecture, and more.

• Q3 TYPO3 Budget Proposal: Improved GitHub Codespaces and Dev Containers support - We’ve proposed significant enhancements to make DDEV shine in GitHub Codespaces and Dev Containers. This will help TYPO3 and all DDEV users. If you're a TYPO3 member, please cast your vote to help the DDEV proposal using the email you received from the TYPO3 Foundation before June 16. → Read more↗

• Randy is back from bikepacking!
  We covered lots of territory out in the state of New Mexico and had a great time. I'll never forget though, laying in my tent when we had some coverage and watching the DDEV community continue on supporting each other so very successfully. And every support answer from Stas was exactly what I would have said. I'm proud and amazed by this wonderful community.
• Using DDEV to Spin Up A Legacy PHP Application
  A guest blog by TYPO3 contributor Garvin Hickling on how to use DDEV to run a (very) old PHP 5.3/MySQL 5.5 application → Read more↗
• Securing DDEV’s Future: Our Commitment to Financial & Community Sustainability Read more↗
• 106 GitHub Sponsors
  We now have 106 GitHub Sponsors! Breaking our aggregation script was a delightful milestone—thank you for believing in DDEV.
• May 2025 Advisory Group Meeting Notes → Read more↗. Join us July 2; ask for a calendar invitation in the DDEV Discord or the contact page.

• Integrating Vite and DDEV into WordPress → Read more↗
• AI-generated DDEV Architecture by DeepWiki, pretty impressive! → Read more↗
• Setup an existing WordPress multisite locally with DDEV (with Bonus Pantheon support!) from Kalamuna → Read more↗

• Apache Foundation-inspired Project Management Committee Exploration
  We’re exploring a governance model inspired by the Apache Foundation and Backdrop CMS to better support long-term sustainability and shared leadership. Take a look and join the conversation about future DDEV governance → Details↗

• Monthly average income up from $7,639 to $7,809 (65% of $12,000 goal, up a percent since early May!). Every contribution helps sustain our work—thank you! → Become a sponsor↗

• Blog↗
• LinkedIn↗
• Mastodon↗
• Bluesky↗
• Discord↗

Join us THURSDAY, June 12 at 1pm ET / 10am PT, for our 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 doc: 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. 

Please note that, since the meeting was moved a week early due to the Juneteenth holiday, the Zoom link for this month's call is different. Please use the following link for June’s call:

• Join the call: https://us02web.zoom.us/j/87657453970?pwd=naknkSONquhpyIAIR5zLaHcroNbQvi.1

  • Meeting ID: 876 5745 3970
    Passcode: 507410

• Follow along on Google Docs: https://nten.org/drupal/notes

View notes of previous months' calls.