Talking Drupal

Today we are talking about The Midwest Open Source Alliance, What they do, and How they support Drupal with guests April Sides & Tearyne Almendariz. We'll also cover Canvas Field Component as our module of the week. For show notes visit: https://www.talkingDrupal.com/552 Topics Congratulations to April as the 2026 Aaron Winborn award! What is MOSA, and what gap in the Drupal ecosystem was it created to fill? How did MOSA get started, and who were the key people behind its formation? MOSA acts as a fiscal sponsor—what does that actually mean in practice for Drupal events and initiatives? What are some of the projects or camps MOSA currently supports? How does MOSA help sustain and grow regional Drupal communities over time? What does membership in MOSA look like, and who should consider getting involved? How does MOSA balance local community focus with broader, national or global Drupal efforts? What are the biggest challenges MOSA faces as a nonprofit supporting open source communities? How has MOSA evolved in recent years, and what's different today compared to when it launched? Looking ahead, what's the long-term vision for MOSA and its role in the Drupal ecosystem? Resources MOSA Website MOSA Drupal Project Aaron Winborn Handbook Moline, Illinois Guests Tearyne Almendariz - nlbcworks.com NineLivesBlackCat April Sides - weekbeforenext Hosts Nic Laflin - nLighteneddevelopment.com nicxvan John Picozzi - epam.com johnpicozzi MOTW Correspondent Martin Anderson-Clutz - mandclu.com mandclu Brief description: Have you ever wanted to place Drupal-rendered fields into your Drupal Canvas templates? There's a module for that. Module name/project name: Canvas Field Component Brief history How old: created in Apr 2026 by me! With some help from a couple of AI models Versions available: 1.0.0, which works with Drupal 11.2 or newer Maintainership Actively maintained Security coverage Test coverage Documentation - a README, but is designed to be narrow in scope Number of open issues: technically 5 open issues, but all marked as fixed Usage stats: 41 sites Module features and usage By design, when using Drupal Canvas to create templates for content types, the idea is to map field values to properties in the template's components That is a new system, however, so site builders may find there are gaps in terms of available mappings for field types they need to use, or may want to draw on mature formatting options such the responsive image definitions that come with Drupal CMS With the Canvas Field Component module installed, you'll find a new "Field display" option available in your Canvas component library. When you drag that into a Canvas template layout, you can choose which field from the content type you want to display, and the formatter to use That, in turn, will expose all settings for the chosen formatter, as well as any third-party settings available, for example if using Date Augmenters with Smart Date fields Those settings will be reflected in real-time inside the Canvas UI preview, and then on rendered content once the template changes are published This module started as a simple idea, based on my own experience using other UI-based Drupal solutions for laying out content type templates, like Layout Builder or Acquia Site Studio. Over the years, I've come to appreciate the flexibility of being able to place Drupal-rendered fields into templates, so you can mix-and-match existing, robust formatting options with flexible ways of pulling field values into layouts that also include more bespoke elements. Or, just use this as a way to add more layout flexibility to Drupal's default, linear display controls. That's what I do on my own blog, where I use Layout Builder but don't have a single custom layout on the site. It's only used for enhancing the layout of structured content. Full disclosure: I also used the idea for Canvas Field Component as the impetus to venture into vibe coding, inspired by the conversations happening in the AI Learners Club, which listeners will hear more about in an upcoming episode.

Kevin Thull, who leads the Drupal Recording Initiative (DRI), joins us to discuss why DRI started, how it scaled from Kevin recording local camps to supporting many events, the hub-and-mentorship model for maintainers, differences between shipping kits vs onsite support, costs compared with traditional AV vendors, and challenges like aging capture hardware, audio/video troubleshooting, and sustainable funding. For show notes visit: https://www.talkingDrupal.com/551 Topics Module of the Week TFA Why Recording Matters Early Events and Growing Pains Post Production and Gear Limits Recording DrupalCon vs Camps Costs and Value Breakdown Pittsburgh Turning Point Hubs and Mentoring New Recordists Beyond Drupal Events Hands Off Goals Impact and Adoption Workflow Pain Points Content First Recording Maintainers and Volunteers Volunteer Stress Factors Funding and Platforms Drupal TV Origins Roadmap and Growth Wrap Up and Contacts Resources MOTW - Two-factor Authentication (TFA) - https://www.drupal.org/project/tfa TFA Email OTP Plugin - https://www.drupal.org/project/tfa_email_otp National Institute for Standards and Technology's Special Publication 800-63B section 3.1.1.2 "Password Verifiers" - https://pages.nist.gov/800-63-4/sp800-63b.html#passwordver Drupal Recording Initiative - https://www.drupal.org/project/dri DrupalCon Chicago Playlist - https://www.youtube.com/playlist?list=PLpeDXSh4nHjQpb2cHv9rgQv4lvq1-ZkC3 Guests Kevin Thull - Drupal Recording Initiative kthull Guest Host Bernardo Martinez - bernardm28 Hosts Nic Laflin - nLighteneddevelopment.com nicxvan Avi Schwab - froboy.org froboy Module of the Week with Avi Schwab- froboy.org froboy Two Factor Authentication - Two-factor authentication for Drupal sites. Drupal provides authentication via something you know – a username and password while TFA module adds a second step of authentication with a check for something you have – such as a code sent to (or generated by) your mobile phone. TFA is a base module for providing two-factor authentication for your Drupal site. As a base module, TFA handles the work of integrating with Drupal, providing flexible and well tested interfaces to enable your choice of various two-factor authentication solutions like Time-based One-Time Passwords (TOTP), SMS-delivered codes, pre-generated codes, or integrations with third-party services like Authy, Duo and others.

In Episode 549, Randy Fay and Stas Zhuk join us to discuss what DDEV is, recent improvements, and where it's headed. Module of the week is the DDEV Drupal Contrib add-on. Randy and Stas discuss priorities like reliability, consistent UX, add-ons discoverability, and new features including revamped ddev share with Cloudflare and rootless Podman support. They also cover coder.ddev.com, a cloud-based DDEV environment built on coder.com for easier onboarding and contribution, plus sustainability, community support, and challenges such as AI-driven PR volume and Stas's development constraints in Ukraine. For show notes visit: https://www.talkingDrupal.com/549 Topics Module of the Week - DDEV Drupal Contrib DDev Drupal Contri Overview Contrib Workflow Q&A Drush in Core Debate Add-on Registry and Contact Drupal AI Summit Plug What Is DDev Stas Origin Story Recent Releases and Priorities DDev Share and Podman Developer Experience Changes Database Upgrade Pain Points Coder DDev Cloud IDE Cloud DDEV Basics VS Code Remote Workflow Pair Programming Training Wins Docker Desktop Alternatives Onboarding Teams Faster Windows Support Reality Building Through War Roadmap Env File Fixes Beyond Drupal Adoption Addons Discovery Tools Funding Community Health AI Pull Requests Pressure AI Agents MCP Plans How To Get Involved Resources DDEV - https://ddev.com/ DDEV Add-on Registry - https://addons.ddev.com/ Introducing coder.ddev.com: DDEV in the Cloud - https://ddev.com/blog/coder-ddev-com-announcement/ About Stas Zhuk - https://ddev.com/blog/introducing-maintainer-stas/ Power Through Blackouts: How DDEV Community Helped Me in Ukraine - https://ddev.com/blog/power-through-blackouts-ddev-community-support/ Drush command in core - https://www.drupal.org/project/drupal/issues/3453474 Drush's Final Act - https://weitzman.github.io/blog/drush-final-act coder.com - https://coder.com/ Service hosting coder.ddev.com - https://www.hetzner.com/ Funding DDEV - https://ddev.com/blog/sustainability-for-ddev/ Gen AI DDEV newsletter note - https://ddev.com/blog/ddev-march-2026-newsletter/ Sharing Coder.ddev.com workspaces - https://github.com/ddev/coder-ddev/issues/80 Guests Stas Zhuk - stasadev Randy Fay - ddev.com rfay Hosts Nic Laflin - nLighteneddevelopment.com nicxvan John Picozzi - epam.com johnpicozzi Rod Martin - DrupalHelps.com imrodmartin Module of the Week with Martin Anderson-Clutz - mandclu.com mandclu DDEV Drupal Contrib - DDEV integration for developing Drupal contrib projects. As a general philosophy, your contributed module/theme is the center of the universe.

In episode #547, guest JD Flynn joins us to discuss why developers don't choose Drupal, focusing on Drupal adoption, discoverability, and outdated perceptions from Drupal 6/7. JD cites survey data showing low interest among non-Drupal developers, arguing Drupal's biggest problem is invisibility and that developers often pre-filter it due to PHP stigma and friction getting started. For show notes visit: https://www.talkingDrupal.com/547 Topics Welcome to Talking Drupal Meet JD Flynn Co Hosts Introductions Module of the Week: Native Observability Production Overhead Debate AI Patches and Etiquette Live Stream and Topic Setup Why Developers Skip Drupal Invisibility and Discovery Perception and Onboarding Friction Composer and Leaving the Island Perception Gap and PHP Stigma PHP Perception Versus Reality Why Developers Avoid Drupal Selling Drupal to Clients Instant Demos With Drupal Forge Discoverability in the AI Era Content Strategy Beyond Drupal PHP Stigma and Performance Community Effort and Live Streaming Marketing Drupal Out of the Box Wrap Up and Where to Connect Resources Why Developers Don't Choose Drupal (And What We Can Do About It) - https://www.fldrupal.camp/session/why-developers-dont-choose-drupal-and-what-we-can-do-about-it JD's stream - http://twitch.tv/jddoesdev Drupal is Great! Its Perception Might Not be. -https://picozzi.com/notebook/2025/jan/drupal-great-its-perception-might-not-be Drupal Forge - https://www.drupalforge.org/ Guests JD Flynn - Crepdrop dorficus Hosts Nic Laflin - nLighteneddevelopment.com nicxvan John Picozzi - epam.com johnpicozzi Rod Martin - DrupalHelps.com imrodmartin Module of the Week Correspondent Martin Anderson-Clutz - mandclu.com mandclu Native Observability brings real observability into Drupal. Trace requests, inspect execution, analyze performance, and explore runtime behavior — directly inside your application. No core patches. No external dependencies required to get started. Just install, enable, and start seeing what actually happens inside your system.

Today we are talking about the open data platform DKAN, what it's used for, and how it applies to Drupal with guests Liz Tupper & Dan Feder. We'll also cover Modern Drupal Dashboard as our module of the week. For show notes visit: https://www.talkingDrupal.com/545 Topics What Is DKAN Who Uses Open Data 20:08 DKAN Origin Story Why Drupal Fits DKAN From Distribution to Module DKAN 2 Rebuild and JSON Shift Async Jobs and API First How Teams Publish Data What a Dataset Really Is Metadata vs Data Access Why DKAN Left Drupal Org Migration Path to DKAN Four Harvesting and Data Store ETL APIs Visualizations and Bots Roadmap Data Store and AI Contributing and Where to File Issues Resources DKAN DKAN Drupal Module DKAN on GitHub Public sites using DKAN 2 DKAN channel on Drupal Slack JSON Form Widget Guests Liz Tupper - civicactions.com etupper Dan Feder - getdkan.org dafeder Hosts Nic Laflin - nLighteneddevelopment.com nicxvan John Picozzi - epam.com johnpicozzi Steve Wirt - civicactions.com Swirt MOTW Correspondent Martin Anderson-Clutz - mandclu.com mandclu Brief description: Have you ever wanted to have your Drupal site admins start with a fast, widget-based interface that surfaces key site metrics, system health, and operational insights? There's a module for that. Module name/project name: Modern Drupal Dashboard Brief history How old: created in Feb 2026 by Gaurav Kapoor (gaurav.kapoor) of werk21 in Berlin Versions available: 1.0.5, which works with Drupal core 10.3 and 11 Maintainership Actively maintained Security coverage Number of open issues: no open issues Usage stats: 4 sites Module features and usage With the module installed, site visitors with the new "Access modern dashboard" permission can access a React-based dashboard with widgets to provide insights on topics like: Content overview: total content count, published vs unpublished, and per content type breakdown. Users overview: user count per role (users with multiple roles are counted in each role), plus pie chart visualization. Additional Content (Entity overview): lists all entity types (content + configuration), shows counts, and provides direct "Manage" links. Modules overview: installed modules summary, including enabled/disabled and core/contrib breakdown. System & status: key environment details such as Drupal core version, PHP version, and database information. Health checks: displays Drupal requirement checks grouped by status (pass/warning/error) with a dedicated detail view. Each widget can be clicked to open a detail view of the extended data, making it easy for admins to dig into any area The widget-based architecture should also help to pull in data from other sources, potentially including things like analytics

No description provided.

Today we are talking about Mautic, marketing automation, and its history with Drupal with guest Ruth Cheesley. We'll also cover Mautic ECA as our module of the week. For show notes visit: https://www.talkingDrupal.com/541 Topics What Is Mautic? Self-Hosting and Data Ownership Who Uses Mautic + Personalization Mautic's History with Drupal How Drupal Integrate Mautic Orchestration in Mautic Privacy & Compliance: GDPR Tools, Consent, and Do-Not-Contact Controls Hosting Options Advanced Segmentation Points-Based Lead Scoring Validating Segments Using Points to Boost Common Mautic Adoption Pitfalls Getting Support The Future with AI AI and Open Source Maintenance Mautic Sustainability & Fundraising How to Contribute Resources Mautic Mautic Integration Advanced Mautic Integration Talking Drupal #343 - Marketing Automation with Mautic Managed hosting, 40% goes to the community Mautic/Drupal case study and presentation on that from our conference https://www.youtube.com/watch?v=r0SkfeHTLK8 https://mautic.org/case-study/inagro/ GDPR cleanup jobs to remove old data Anonymization tasks to comply with specific laws (eg CCPA) Anonymize IP setting Proposal to overhaul all things privacy and streamline experience for marketers - currently seeking funding, planning to ship in Mautic 9 Mautic contribution docs Testing PRs: inlcuding local setup guide Low/no-code tasks board Thanks Dev Ecosystems Guests Ruth Cheesley - ruthcheesley.co.uk RCheesley Hosts Nic Laflin - nLighteneddevelopment.com nicxvan John Picozzi - epam.com johnpicozzi Catherine Tsiboukas - mindcraftgroup.com bletch MOTW Correspondent Martin Anderson-Clutz - mandclu.com mandclu Brief description: Have you ever wanted to integrate Mautic marketing automation into your Drupal website, using ECA? There's a module for that. Module name/project name: Mautic ECA Brief history How old: created in Jun 2025 by Abhisek Mazumdar (abhisekmazumdar) of Dropsolid Versions available: 1.0.6 which works with Drupal 10 and 11 Maintainership Actively maintained Documentation - detailed README Number of open issues: 1 open issues, which is not a bug Usage stats: 3 sites Module features and usage With the module installed, your ECA models can respond to Mautic webhooks, and can also make use of new actions to give you CRUD capabilities (Create, Read, Update, or Delete) for contacts and segments within ECA Mautic ECA declares the Mautic API module as a dependency, and you need to use it to set up an API connection, and to define any webhooks you want to use in your models It's worth noting that the maintainers of Mautic ECA also seem to be involved with a number of other modules in the Mautic API ecosystem, including Mautic Personalization, as well as Mautic Content Provider, which can expose Drupal content for use in Mautic, for example to include in emails

Today we are talking about Acquia's Fully managed Drupal SaaS Acquia Source, What you can do with it, and how it could change your organization with guest Matthew Grasmick. We'll also cover AI Single Page Importer as our module of the week. For show notes visit: https://www.talkingDrupal.com/540 Topics Introduction to Acquia Source The Evolution of Acquia Source Cost and Market Position of Acquia Source Customizing and Growing Your Business Challenges of Building a SaaS Platform on Drupal Advantages of Acquia Source for Different Markets Horizontal Scale and Governance at Scale Canvas CLI Tool and Synchronization Role of AI in Acquia Source Agencies and Enterprise Clients AI Experiments and Content Importer AI and Orchestration in Drupal Future Innovations in Acquia Source Resources Acquia source Nebula Guests Matthew Grasmick - grasmash Hosts Nic Laflin - nLighteneddevelopment.com nicxvan John Picozzi - epam.com johnpicozzi Catherine Tsiboukas - mindcraftgroup.com bletch MOTW Correspondent Martin Anderson-Clutz - mandclu.com mandclu Brief description: Have you ever wanted to use AI to help map various content on an existing site to structured fields on Drupal site, as part of creating a node? There's a module for that. Module name/project name: AI Single Page Importer Brief history How old: created in Jan 2026 by Mark Conroy (markconroy) who listeners may know from his work on the LocalGov distribution and install profile Versions available: 1.0.0-alpha3, which works with Drupal core 10 or 11 Maintainership Actively maintained Documentation - pretty extensive README, which is also currently in use as the project page No issues yet Usage stats: 2 sites Module features and usage With this module enabled, you'll have a new "AI Content Import" section at the top of the node creation form. In there you can provide the URL of the existing page to use, and then click "Import Content with AI". That will trigger a process where OpenAI will ingest and analyze the existing page. It will extract values to populate your node fields, and then you can review or change those values before saving the node. In the configuration you can specify the AI model to use, a maximum content length, an HTTP request timeout value, which content types should have the importer available, and then also prevent abuse by specifying blocked domains, a flood limit, and a flood window. You will also need to grant a new permission to use the importer for any user roles that should have access. The module also includes a number of safeguards. For example, it will only accept URLs using HTTP or HTTPS protocols, private IP ranges are blocked, and by default it will only allow 5 requests per user per hour. It will perform HTML purification for long text fields, and strip tags for short text fields. In addition, it removes dangerous attributes like onclick or inline javascript, and generates CKEditor-compatible output. It currently supports a list of field types that include text_long, text_with_summary, string, text, datetime, daterange, timestamps and link fields. It also supports entity reference fields, but only for taxonomy terms. Listeners may also be aware of the Unstructured module which does some similar things, but requires you to use an Unstructured service or run a server using their software. So I would say that AI Single Page Importer is perhaps a little more narrow in scope but works with an OpenAI account instead of requiring the less commonly used Unstructured.

Today we are talking about EvolveDigital, What it is, and how it started in Drupal with guest Maya Schaeffer. We'll also cover Drupal CMS 2.0 as our module of the week. For show notes visit: https://www.talkingDrupal.com/539 Topics Comparing Drupal and WordPress Evolve Digital Summit Insights Marketing and Drupal Integration Evolve Digital and CMS Comparisons Summit Structure and Networking Speaker Selection and Outreach Balancing Content and Community Lessons from Different Cities Future Plans and New Formats Resources EvolveDigital Drupal CMS documentation Decoupling Content & Frontend Nika Karliuchenko, John Picozzi, Pete Navarra Drupal Canvas Webinar Guests Maya Schaeffer - evolvedigital.com mayalena Hosts Nic Laflin - nLighteneddevelopment.com nicxvan John Picozzi - epam.com johnpicozzi Catherine Tsiboukas - mindcraftgroup.com bletch MOTW Correspondent Martin Anderson-Clutz - mandclu.com mandclu Brief description: Do you want to start your next Drupal site using a variety of best practices, including Canvas for page layouts, or site templates for an opinionated architecture out of the box? Then the recently released Drupal CMS 2.0 could be just what you need. Module name/project name: Drupal CMS Brief history 2.0 release was created by phenaproxima less than a week ago, and requires Drupal 11.3 Maintainership Actively maintained Security coverage Test coverage Documentation guide linked in the show notes 145 issues on the development project, 24 of which are bugs Usage stats: No direct way to track, but drupal_cms_helper was added as a dependency late in the Drupal CMS 1.x cycle, so the fact that it has been installed 3,780 times likely indicates that Drupal CMS has been installed several thousand times at a minimum Module features and usage The biggest change in Drupal CMS 2 is the addition of Canvas for creating and managing layouts. We talked about Drupal Canvas in depth back in episode #518 so I won't go into too much detail here, but having it set up for you as an out-of-the-box feature is a big benefit Drupal CMS 1.0 included a carefully curated content architecture, including some optional recipes for additional capabilities. With version 2, the intent is for site templates to be the source of the content architecture. I'm sure we'll be hearing a lot more about site templates, including a marketplace where people can find them, in the coming and in particular with DrupalCon Chicago fast approaching Drupal CMS 2.0 also ships with much more sophisticated AI capabilities. There's a dedicated Canvas AI that can be used to generate and populate entire layouts, as well as generating code components, based on a user's prompt. And listeners may remember the demo in the Vienna Driesnote of using the Context Control Center to automatically create drafts of content updates when marketing information changes And of course, starting with Drupal core 11.3 means you'll get all the performance and other improvements in the latest version

Today we are talking about Integrations into Drupal, Automation, and Drupal with Orchestration with guest Jürgen Haas. We'll also cover CRM as our module of the week. For show notes visit: https://www.talkingDrupal.com/537 Topics Understanding Orchestration Orchestration in Drupal Introduction to Orchestration Services Drupal's Role in Orchestration Flexibility in Integration Orchestration Module in Drupal Active Pieces and Open Source Integration Security Considerations in Orchestration Future of Orchestration in Drupal Getting Involved with Orchestration Resources Orchestration N8N https://www.cve.org/CVERecord?id=CVE-2026-21877 https://www.cve.org/CVERecord?id=CVE-2026-21858 Drupal as an application Tools Orchestration ECA Maestro AI Flowdrop Guests Jürgen Haas - lakedrops.com jurgenhaas Hosts Nic Laflin - nLighteneddevelopment.com nicxvan John Picozzi - epam.com johnpicozzi MOTW Correspondent Martin Anderson-Clutz - mandclu.com mandclu Brief description: Have you ever wanted a Drupal-native way to store, manage, and interact with people who might not all be registered users? There's a module for that. Module name/project name: CRM - Contact Relationship Management Brief history How old: created in Apr 2007 by Allie Micka, but the Steve Ayers aka bluegeek9 took over the namespace Versions available: 1.0.0-beta2, which works with Drupal 11.1 or newer Maintainership Actively maintained, latest release just a day ago Security coverage: opted in, but needs a stable release Test coverage Number of open issues: 73 open issues, but all bugs have been marked as fixed Usage stats: 10 sites Module features and usage Listeners may remember some mention of the CRM module in the conversation about the Member Platform initiative back in episode 512 As a reminder, something other than standard Drupal user accounts is useful for working with contact information for people where you may not have all the criteria necessary for a Drupal user account, for example an email address. Also, a dedicated system can make it easier to model relationships between contacts, and provide additional capabilities. It's worth noting that this module defines CRM as Contact Relationship Management, not assuming that the data is associated with "customers" or "constituents" as some other solutions do At its heart, CRM defines three new entity types: contacts, contact methods, and relationships. Each of these can have fieldable bundles, and provides some default examples: Person, Household, and Organization for contacts; Address, Email, and Telephone for contact methods; and Head of household, Spouse, Employee, and Member for relationships Out of the box CRM includes integrations with other popular modules like Group and Context, in addition to a variety of Drupal core systems like views and search As previously mentioned CRM is intended to be the foundational data layer of the Member Platform, but is also a key element of the Open Knowledge distribution, meant to allow using Drupal as a collaborative knowledge base and learning platform

Today we are talking about Patching Drupal, Composer, and Composer Patches 2.0 with guest Cameron Eagans. We'll also cover Configuration Development as our module of the week. For show notes visit: https://www.talkingDrupal.com/536 Topics What is Composer Patches 2.0 Exploring Community Dynamics in Composer Patches The Genesis of Composer Patches The Decision to Use GitHub Broadening Composer Patches Beyond Drupal The Evolution to Composer Patches 2.0 Understanding Workflow Complexities Refining User Experience in 2.0 New Features and Enhancements in 2.0 Navigating Controversial Changes in 2.0 The Role of Dependency Patches Introducing patches.lock.json Best Practices for Patch Management Transitioning to Git Patching Exploring New APIs in Composer Patches 2.0 Understanding Capabilities and Events Transitioning to Composer Patches 2.0 Future of Composer Patches and Community Contributions Resources Announcing Composer Patches 2.0 Recipe issue for config devel Docs Patch man page Guests Cameron Eagans - cweagans.net cweagans Hosts Nic Laflin - nLighteneddevelopment.com nicxvan John Picozzi - epam.com johnpicozzi Andy Giles - dripyard.com andyg5000 MOTW Correspondent Martin Anderson-Clutz - mandclu.com mandclu Brief description: Do you maintain modules that provide configuration files? There's a module that can help manage them. Module name/project name: Configuration Development Brief history How old: created in Apr 2014 by chx, though recent releases are by Joachim Noreiko (joachim) Versions available: 8.x-1.11, which works with Drupal 9.3, 10, and 11 Maintainership Actively maintained Security coverage Test coverage Number of open issues: 36 open issues, 7 of which are bugs Usage stats: 2,391 sites Module features and usage The module really provides three useful features. First, it can ensure specific configuration files are automatically imported on every request, as though the contents were pasted into the core "single import" form Second, it can automatically export specific configuration objects into files whenever the object is updated. You provide a list of filenames and the module will derive the objects that need to be exported. Finally, it provides a drush command that can be used to generate all the necessary configuration files for a specific project. You put a list of the files into the project's info.yml file, and then with a single command a fresh copy of all the specified files will be generated and placed directly into the project's configuration folder. For obvious reasons this is not something you should ever have enabled in production, so definitely a best practice to pull this in using the require-dev composer command

Join Johanna and Jess as they dive deep into their experiences and insights working with Drupal in the nonprofit sector. Learn about their early careers, the evolution of Drupal's development, the significance of community in nonprofit tech, and the origins and importance of the Nonprofit Summit at DrupalCon. Discover how their community initiatives foster collaboration and support among nonprofit technologists, and get a glimpse into the upcoming summit details. Perfect for anyone interested in Drupal, open-source technology, and nonprofit organizational challenges. For show notes visit: https://www.talkingDrupal.com/cafe012 Johanna Bates Johanna Bates (they/them, hanpersand on drupal.org) is co-founder and co-principal of DevCollaborative, a company that builds accessible and sustainable Drupal and WordPress sites exclusively for nonprofit organizations. Johanna began their formal tech career at WGBH in Boston in 2000 as a front-end developer. They have been building Drupal sites since 2004, and have been co-moderating NTEN's Nonprofit Drupal Community and its monthly chats for over a decade. Johanna was involved in early Nonprofit Summits at NYCcamp starting back in 20-teens 2015, and helped bring the Nonprofit Summit to DrupalCon North America in 2017. Jess Snyder Jess Snyder (jesss on drupal.org and Drupal Slack) is Director of Web Systems for WETA, the flagship public media station for Washington, DC, and has over 20 years of experience in website development. Jess is an organizer for NTEN's Drupal Community of Practice as well as Drupal GovCon. She also co-chaired the triumphant return of the Nonprofit Summit to DrupalCon Portland 2024 and its sequel at DrupalCon Atlanta 2025. When not Drupaling, Jess sits on the Board of Directors for the National Academy of Television Arts and Sciences. Topics Meet the Speakers: Johanna and Jess Johanna's Journey in Nonprofit Tech Jess's Path in Public Broadcasting The Importance of Community in Nonprofit Tech Organizing Nonprofit Summits Challenges and Changes in Drupal The Value of Open Source for Nonprofits Comparing Drupal and WordPress Concerns About JavaScript in Content Editing Importance of Accessibility in Content Management Guardrails for Content Editors The Nonprofit Summit: Origins and Evolution Summit Format and Community Building Sponsorship and Event Details Getting Involved in the Nonprofit Drupal Community Conclusion and Final Thoughts Guests Johanna Bates - hanpersand Jess Snyder - jesss

Today we are talking about The Drupal At-Large Board Seat, What the job entails, and some common misconceptions with guest Fei Lauren. We'll also cover Token Browser as our module of the week. For show notes visit: https://www.talkingDrupal.com/533 Topics Understanding the Drupal Association at Large Board Seat Responsibilities and Experiences of a Board Member Challenges and Insights from Serving on the Board Community Representation and Accountability Skills and Qualities for Aspiring Board Members Navigating Board Member Responsibilities Community Perception and Board Care Global Community Engagement Challenges and Impact of Board Decisions Encouraging Non-Technical Contributions Reflections and Future Plans Election Process and Imposter Syndrome Resources Board of directors working groups Board of directors Guests Fei Lauren - feilauren Hosts Martin Anderson-Clutz - mandclu.com mandclu Nic Laflin - nLighteneddevelopment.com nicxvan MOTW Correspondent Nic Laflin - nLighteneddevelopment.com nicxvan Brief description: Have you ever wanted an improved token browser that loads quickly and doesn't have a depth limit? There's a module for that. Module name/project name: Token Browser Brief history How old: created in Nov 2025 by Andy Marquis (apmsooner) https://talkingdrupal.com/505 Versions available: 1.0.0 which works with Drupal core 11.3 or newer Maintainership Actively maintained Security coverage Test coverage Number of open issues: 2 open issues, 1 of which is a bug Usage stats: 3 sites Module features and usage The Token Browser module provides a rebuilt version of the standard token browser. Notably, it only renders the first level during the initial request, and then requests deeper levels as needed using all the latest HTMX improvements in Drupal core 11.3 It's worth noting that the initial version requires an alternative theme function be attached to form elements where you want to use the new Token Browser, so it doesn't actually replace the standard version Also, there seems to be an issue where the HTMX library doesn't load on cached pages, which is the one open issue. I pinged Andy about it and it sounds like he has a fix in the works. Finally, this module is similar to an older module called Fast Token Browser, but that module was never updated to work with versions of Drupal newer than 7, and relied on jQuery for its AJAX functionality