drupal

Picozzi.com: Recap: My Return to Drupal GovCon 2025!

Recap: My Return to Drupal GovCon 2025! Image removed. john Fri, 08/15/2025 - 14:38

After more than five years away, I was happy to return to Drupal GovCon, hosted on the beautiful campus of the University of Maryland in College Park. The event brought together an incredible mix of government technologists, open source enthusiasts, and Drupal community members—all with plenty of hot topics (especially AI) to dig into.

Talking Drupal: Talking Drupal #516 - Drupal CMS & Recipes

Today we are talking about Drupal CMS Analytics, Recipes, and how to use both with guest Dharizza Espinach. We’ll also cover Field Data as our module of the week.

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

Topics
  • Drupal CMS Analytics Track
  • Balancing Personal and Work Contributions
  • Planning and Estimating Contributions
  • Team Effort and Collaboration
  • Challenges and Solutions in UI and Integration
  • Future Enhancements and Roadmap
  • Conclusion and Contact Information
Resources Guests

Dharizza Espinach - dharizza

Hosts

Nic Laflin - nLighteneddevelopment.com nicxvan John Picozzi - epam.com johnpicozzi Rich Lawson - richlawson.co rklawson

MOTW Correspondent

Jacob Rockowitz - jrockowitz.com jrockowitz

  • Brief description:
    • Did you ever need to review all the data in a field on a content entity type or a specific bundle?
  • Module name/project name:
  • Brief history
    • How old: February 28, 2025
    • Versions available: 1.0.0-alpha12
  • Maintainership
    • Actively maintained
    • Test coverage
  • Documentation
    • Default settings include
    • Display only published field data
    • Display only field data in the default language
  • Usage stats:
    • 34 sites report using this module
  • Maintainer(s):
    • Jacob Rockowitz
  • Module features and usage
    • Adds a 'Data' tab to Drupal core's 'Field list' report (/admin/reports/fields), which allows administrators to view and download field data.
    • This module can be used while developing a migration to review field data before and after a migration.
    • This module also allows site builders and developers to identify unused fields.
    • Similar Modules
    • Schema Viewer
    • Provides a backend developer tool to view table schema by table name.
    • Entity Export CSV
    • Export Content Entity to CSV.

 

jofitz: drush generate plugin:manager walk-through

When creating a custom Drupal plugin manager the "drush generate plugin:manager" command is helpful in creating correctly structured boilerplate code for you.

This continues from last week's article, How to create a custom Drupal plugin. I recommend reading that first to understand the purpose of the files that will be generated. I will also be making reference back to the example module and files in those code snippets.

Setup

Obviously you will need to have Drush installed on your Drupal website to use this command, in most cases all you need is to run composer require drush/drush but otherwise I suggest reading Installing and Upgrading on drush.org.

Then simply run drush generate plugin:manager

The plugin-manager generator will then ask a number of questions to correctly name and locate the necessary boilerplate files additions and updates.

Module Machine Name

$ drush generate plugin:manager Welcome to plugin-manager generator! –––––––––––––––––––––––––––––––––––––– Module machine name... Read more

The Drop Times: Confronting Change Through Openness

Dear Readers,

Due to the recent conversations in the Drupal community about AI and its influence on the open source world, I was reminded of Geoffrey Hinton’s Nobel Prize banquet speech in December 2024. In it, Hinton, often called the “Godfather of AI”, highlighted that AI is no longer just a tool for advancement. He expressed concern about AI's role in creating divisive echo chambers, its misuse in mass surveillance, assistance in phishing scams, and even the potential to develop new viruses or autonomous weapons. Most worryingly, he warned about the possibility of creating digital beings smarter than us, and questioned whether humans will be able to maintain control. You can read his full speech here.

These warnings have not gone unheard in the open source world. Developers and communities are debating how transparency and shared governance can counter these risks. Open source advocates argue that keeping AI open allows more eyes to spot flaws, biases, and potential dangers. It’s a safeguard against corporations developing powerful systems with little public oversight and driven solely by profit.

Within Drupal, the conversation is equally active. The community has started initiatives to integrate AI responsibly, combining automation with human review. For instance, Drupal AI tools are being designed so that users maintain complete control over generated content and decisions, ensuring AI supports rather than replaces human judgment. Educational efforts, such as webinars and workshops, are also being used to build awareness around the ethical and practical challenges of using AI in Drupal.

The larger point is clear: Hinton’s warnings highlight why open source communities like Drupal matter in this era of rapid AI adoption. By building in the open, prioritising accountability, and keeping humans in charge of critical decisions, projects like Drupal can set an example of how technology can be advanced responsibly. In doing so, they remind us that innovation and ethics must move forward together.

INTERVIEW

DISCOVER DRUPAL

EVENTS

ORGANIZATION NEWS

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

Thank you, 
Sincerely 
Kazima Abbas
Sub-editor, The DropTimes.

Talking Drupal: TD Cafe #008 - Martin Anderson-Clutz & Jürgen Haas

In this episode, Martin and Jürgen dive deep into the concept of modular API, ECA and more. Jürgen shares insights from Dev Days in Lubin, key improvements in ECA 3.0, and the exciting potential of leveraging the BPMN interface for AI. The conversation also addresses future aspirations for ECA. Additionally, Jürgen and Martin share their personal travel hacks and discuss the intersection of Drupal travel and photography.

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

Topics
  • Introduction to Modular API
  • Conversations at Dev Days
  • Exploring Modeler API
  • AI Integration and Future Prospects
  • Challenges and Comparisons with Other Tools
  • Community Collaboration and AI Initiatives
  • Future Roadmap for ECA
  • Travel Hacks and Personal Insights
  • Conclusion and Final Thoughts
Martin Anderson-Clutz

Martin Anderson-Clutz is a highly respected figure in the Drupal community, known for his extensive contributions as a developer, speaker, and advocate for open-source innovation. Based in London, Ontario, Canada, Martin began his career as a graphic designer before transitioning into web development. His journey with Drupal started in late 2005 when he was seeking a robust multilingual CMS solution, leading him to embrace Drupal's capabilities. Martin holds the distinction of being the world's first Triple Drupal Grand Master, certified across Drupal 7, 8, and 9 as a Developer, Front-End Specialist, and Back-End Specialist. He also possesses certifications in various Acquia products and is UX certified by the Nielsen Norman Group. Currently serving as a Senior Solutions Engineer at Acquia, Martin has been instrumental in advancing Drupal's ecosystem. He has developed and maintains several contributed modules, including Smart Date and Search Overrides, and has been actively involved in the Drupal Recipes initiative, particularly focusing on event management solutions. His current work on the Event Platform aims to streamline the creation and management of event-based websites within Drupal. Beyond development, Martin is a prominent speaker and educator, having presented at numerous Drupal events such as DrupalCon Barcelona and EvolveDrupal. He is also a co-host of the "Talking Drupal" podcast, where he leads the "Module of the Week" segment, sharing insights on various Drupal modules. Martin's dedication to the Drupal community is evident through his continuous efforts to mentor, innovate, and promote best practices within the open-source landscape.

Jürgen Haas

Jürgen Haas is a seasoned software architect, open source advocate, and long-time contributor to the Drupal community. Based in Germany, Jürgen brings decades of experience in enterprise IT solutions, specializing in system architecture, security, and digital transformation. He is known for his leadership within the ECA project and for being the track lead for privacy and data protection in Drupal CMS. Jürgen is an active participant in community initiatives, a frequent speaker at Drupal events, and a mentor to developers looking to deepen their expertise in scalable and secure web applications. His work reflects a passion for innovation, collaboration, and the power of open-source technology to solve real-world business challenges

Guests

Martin Anderson-Clutz - mandclu.com mandclu Jürgen Haas - jurgenhaas

Drupal AI Initiative: From strategy to delivery: Key outcomes of the Drupal AI Initiative off-site

The Drupal AI Initiative is responsible for leading the definition and delivery of major AI capabilities for Drupal. Whilst operating in the fast-paced AI industry, we recognise the importance of taking time to ensure plans to deliver our bold vision are robust.

With this in mind, last week, members of the Drupal AI Initiative gathered in-person and online for two days of structured activities dedicated to refining the initiative’s direction, funding model, operational framework, and marketing. 

The off-site fostered improved collaboration and strategic clarity. It also served as a valuable forum to present and critically review a newly developed marketing and communications strategy, ensuring plans are in place to extend awareness of Drupal AI far beyond markets where Drupal is well-established.

$300k funding secured to catalyse progress

Securing sustainable funding and growing the team is fundamental to the initiative’s success, and Dominique De Cooman is leading this area. Dominique has had numerous conversations with Drupal agency leaders regarding the Drupal AI Initiative and how they can get involved. He reported rising interest in support and confirmed a host of additional sponsors, known as “Makers”, joining the initiative.

Being a maker goes beyond financial support. Each agrees to allocate full-time staff dedicated to advancing key areas of the initiative. Combined, these commitments represent new funding worth $300,000, which will be used to accelerate progress towards our goals.

The first round of Drupal AI Makers (in alphabetical order) was announced in early June:

The latest Drupal AI Makers (in alphabetical order):

Their support brings the total number of Drupal AI Makers to 15, representing a significant milestone for the initiative. There is also an anonymous sponsor contributing funding. A more detailed blog post about these new makers is coming soon.

Image removed.

A workshop was held to explicitly define concrete deliverables across various functional areas, including product, external relations, operational processes, scaling the team, and financial sustainability.

Strategies to attract further funding were also discussed, together with discussions on how supporters may derive value. This covered details of the “early access” programme, which provides benefits to makers while remaining true to open source and Drupal community values.

Building delivery capacity with dedicated project management

Thanks to the new makers, we have greatly increased our capacity to deliver. The leadership team acknowledged the need to recruit a dedicated project manager (PM). This will bring clarity, structure, and accountability to product management, development, and delivery. A focused PM will ensure our development team works effectively, bolstering our ability to ship solutions frequently and maintain Drupal’s leading advantage in open-source AI.

Image removed.

The team developed a hiring plan for this critical position, including profiling the role, outlining timelines and budget, and identifying the individuals responsible for the hiring process.

Decisions were made regarding candidate assessment and communicating hiring plans, while interim candidates from makers were identified to fill the role and deliver immediate benefits.

Shaping the next phase of Drupal AI development

A deep dive into the product roadmap was conducted, where participants worked to define concrete milestones, delivery timelines, and assign ownership of features.

Image removed.

Discussions also focused on making the technology installable and packaging its various capabilities, with decisions made regarding demo versions to support evaluation.

An article detailing the roadmap planning is forthcoming.

Informed by the Drupal AI Survey

The off-site was intentionally held as the Drupal AI Survey drew to a close. Early analysis of 232 submissions ensured that our decision-making processes directly took into account feedback from end users.

The survey’s ranking method was designed to determine feature value and sentiment, helping to prioritise features based on market demand and perceived business value.

The top three features by overall weighted score were the Search Optimizer, Audit Trail Agent, and Content Librarian. Conversely, respondents ranked features such as Demand Driver and Lead Enhancer among those with the lowest business value, indicating they may benefit from reframing, clearer use cases, or potential deprioritization.

Fact Finder and Role Master generated the most commentary, which will undoubtedly enhance our approach once we enter the planning phase.

A full report from the Drupal AI Survey will be released via a special webinar on 28th August.

Marketing strategy

A substantial segment was dedicated to evaluating the draft external communication and engagement strategy.

Image removed.

The core objectives of this strategy are twofold: Grow the Drupal AI audience by focusing on the specific AI challenges faced by particular industries, and retain existing customers by positioning Drupal AI as a strong motivator for continued Drupal use.

The Drupal AI Marketing Strategy acknowledges a shift in buyer persona from marketing to AI procurements with more oversight from IT leaders. Over half of AI solution purchases are now funded by central IT budgets and have a strong focus on return on investment (ROI).

The core messaging frames Drupal AI as "a framework to accelerate AI adoption" that allows users to "Integrate today’s best-in-class AI and experiment with tomorrow’s breakthroughs” within the freedom of an open-source ecosystem. The strategy will ensure Drupal AI strengthens Drupal’s longstanding commitment to transparency and robust governance.

With increasing support from Makers, marketing efforts can be expanded by incorporating team members from these organisations who bring the skills and expertise necessary to achieve our aspirational goals.

Rounding off 2 days of intensive meetings

Image removed.

Nothing compares to the sense of togetherness and energy that face-to-face gatherings provide. Being together sparked numerous aha moments and new ideas. Of course, in true Drupal fashion, the conversations went on well into the evening. So much progress was made.

Image removed.

We concluded with a shared sense of purpose, a clear direction, and renewed enthusiasm to advance Drupal AI ahead of DrupalCon Vienna, by which time we will have much to showcase. See you there?

Get involved with Drupal AI

We have a variety of webinars, events, training and ways to contribute. There are opportunities for individuals across a range of skill sets plus we encourage organisations to become Makers of Drupal AI via sponsorship.

Visit the Drupal AI Initiative homepage to find out more.

Photos: Paul Johnson

Drupal AI Initiative: Drupal AI 1.2.0-alpha2 is out and comes with stability fixes and new features

Drupal AI 1.2.0-alpha2 was released on the 13th of August and it comes with a lot of stability fixes and some new features. 

Note that since this is an alpha, we will not provide upgrade paths from this alpha and more features will still be added before the beta releases.

To discover more about Drupal AI and to access full documentation visit the project page.

Stability Fixes

The release takes us closer to a production release, by fixing a lot of bugs on the added features since the 1.2.0-alpha1 release and it fixes minor bugs on the features that already exist.

Views Automators Type

This new AI Automators type gives a whole set of new powers to AI Automators by making it possible to invoke Views from anywhere in your Automators Workflows.

This means that any content you can express in a view, the Automator can use to automate or make part of an editorial workflow.

The following scenarios are some of thousands of different workflows that you could create within minutes using the AI Automators due to this new type:

  • You want to figure out not just what was the most commented articles last week, but you also want a short summary and semantic rating of if the comments were positive or negative for each article. You can now set that up in minutes.
  • You want to have a related content block on your article, but you want it actually written in free text as a couple of sentences, how the linked content connects to the article you are reading now. You can now set that up in minutes.
  • You want a weekly mail with quotes that touches a specific topic, filtered out from all the editorial content that was added last week. You can now set that up in minutes.

Field Widget Actions - now with more Automator Types and with improved accessibility 

The new Field Widget Actions module makes it possible to add interactive buttons on any entity form, to make it easy for editors to interact and fill out fields with AI from anywhere. With a push of a button you can have suggestions or picks - if you are not happy, you can push and ask again. This ensures that we can use AI to help the editor, but the editor has the final decision. 

We have now added so you can use select lists, numeric fields, e-mail fields and more using the Automators and Field Widget Actions.

Outside of that, the initial version lacked needed accessibility features, making it hard to be used by everyone. We have added fixes for this.

Fully flexible streamed response

Streaming has been a second class citizen up until now in the AI module. The problem with the architecture of PHP and how a streamed response works, made it hard to do things like logging, token counting, callbacks and other post streaming events.

This has now been alleviated and it's now possible to do all things that you can do in a normal response as a streamed response.

Better CKEditor experience

The AI CKEditor experience had a limited experience when using it with the text selection. We have now added improvements to how the plugin works when selecting text and using the AI CKEditor.

Normalized Token Usage

The token usage for chat clients has historically been represented as a raw value on the response, however now we have added normalization of token usage, meaning that any third party library that for instance wants to count usage costs or add usage limits now has the possibility to do this.

Work on such an module is already underway here

Thank you 

Thank you to the following contributors for your contributions:

marcus_johansson, leo pitt, bbruno, a.dmitriiev, mrdalesmith, anjaliprasannan, prashant.c, danielveza, sijumpk, johnpicozzi, bisonbleu, jayzalani34, sanket.tale, ishani patel, libbna, abhishek@kumar, kanchan bhogade, jofitz, sarvjeetsingh, techmantejas, project update bot, kristen pol, mgifford, ravimane23, prabha1997, annmarysruthy, valthebald, andrewbelcher, riyas_nr, murz, gxleano, aporie, sirclickalot, seogow, svendecabooter, breidert, dan2k3k4, akhil babu, michaellander, ralkeon, scott_euser, jurgenhaas, andypost, binoli lalani, nicholass, petar_basic, matthews, dunx

Thank you to the following organizations for supporting contribution:

  • 1xINTERNET
  • Acquia
  • Amazee Labs
  • amazee.io
  • CivicActions
  • Dropsolid
  • drunomics
  • Drupal India Association
  • EPAM Systems
  • European Commission and European Union Institutions, Agencies and Bodies
  • FAB Web Studio
  • Factorial GmbH
  • FreelyGive
  • Itty Bitty Byte
  • jofitz
  • LakeDrops
  • Noble Services Scotland
  • PreviousNext
  • QED42
  • Salsa Digital
  • Sixeleven
  • Skilld
  • Soapbox
  • Sven Decabooter
  • SystemSeed
  • Zoocha

Learn more about the Drupal AI Initiative and get involved

We have a variety of webinars, events and ways to get involved. There are opportunities for individuals across a range of skillsets plus we are keen to encourage organisations to become Makers of Drupal AI via sponsorship.

Visit the Drupal AI Initiative homepage to find out more.

Salsa Digital: Federal Circuit and Family Court of Australia — Rules as Code for divorce eligibility

Image removed.Overview Federal Circuit and Family Court of Australia’s challenge Divorce eligibility rules can be quite complex. People interested in applying for a divorce need to navigate through many pages of content before starting an application. This can make the process time consuming and confusing.  Federal Circuit and Family Court of Australia’s transformation Salsa worked with the team at the Federal Circuit and Family Court of Australia to create a Rules as Code proof of concept (PoC) for divorce eligibility. Users are taken through a series of questions and then told if they’re eligible for a divorce. In addition, they’re given tailored information about what documentation they need in their specific situation.