Advertise on podcast: Talking Drupal

Today we are talking about Drupal Advocacy, Non-Code Contribution, and the future with guest Tiffany Farriss. We'll also cover Better Social Sharing Buttons as our module of the week. For show notes visit: https://www.talkingDrupal.com/575 Topics Tiffany New DA Role Sustaining Drupal Next 25 Time Box And Priorities Three Bucket Strategy Fixing DA Finances Transparency And Trust Trust Through Transparency What Advocacy Solves Why Reputation Lags From Scattered To Focused Beyond The Drupal Bubble Problem First Storytelling Proof Over Promotion Scaling Non Code Contributions Funding Drupal Sustainability Success Metrics Resources Drupal Advocacy Program Guests Tiffany Farriss - association.drupal.org farriss Hosts Nic Laflin - nLighteneddevelopment.com nicxvan John Picozzi - epam.com johnpicozzi Tim Sharp - tea-sharp MOTW Correspondent Martin Anderson-Clutz - mandclu.com mandclu Brief description: Have you ever wanted to let visitors share your content on social media, without loading any tracking scripts or third-party JavaScript? There's a module for that. Module name/project name: Better Social Sharing Buttons Brief history How old: created in Aug 2018 by Joery Lemmens (flyke), though recent releases are by Shelane French (shelane) Versions available: 5.0.0, which works with Drupal 10.1, 11, and 12 Maintainership Actively maintained, latest release in July, adding Drupal 12 support Security coverage Number of open issues: 17, 5 of which are bugs against older branches Usage stats: 8,347 sites Module features and usage Supports 16 services, including Facebook, X, LinkedIn, Bluesky, Reddit, Pinterest, WhatsApp, Telegram, and email, plus handy extras like print and copy link Each button is just a plain link to that service's share URL, opening in a new tab. No trackers, no external API calls, no ad servers That's a nice win for performance, and for privacy and GDPR, since nothing third-party loads until a visitor actually clicks You can place it as a block, as a pseudo field on nodes or paragraphs, or call it from Twig with Twig Tweak The global settings form lets you enable services and drag them into order, and each block instance can override that list, the icon set, and the sizing The module comes with two icon sets: colored squares, which become round if you set the radius to 100%, or flat icons you can color with a CSS fill. The colored set also exposes CSS custom properties, so you can re-brand it from your theme The icons are minified SVGs in a single sprite, so they load once no matter how many buttons are on the page There's also a per-node submodule: enable it per content type, and editors with the right permission get a checkbox to turn sharing on or off for individual nodes Under the hood it's nearly all Twig, one template partial per service, with just a little JavaScript for copy link, print, and Bluesky. Copy link even uses an aria-live region to announce the confirmation to screen readers The block uses the current page's URL and title, so it works on user and term pages too, while the field version shares the node's own URL and title Developers can tweak what gets shared with an alter hook on the block's items Caveats: Facebook Messenger needs a Facebook App ID, and Metatag is recommended so services get proper Open Graph previews, and if a service changes its share URL format, the module needs an update Back in episode #548 we covered Social Media Links, and the two look similar: both give you a block of social network icons, with a choice of icon sets. But they solve opposite problems. Social Media Links is "follow us": it links out to your own profiles, using URLs you configure in the block or a field. Better Social Sharing Buttons is "share this": it builds each link on the fly from the current page's title and URL. So plenty of sites could use both

Today we are talking about the UN, Open Source, and Drupal with guests Tim Lehnen & Henry Poole. We'll also cover Live Update as our module of the week. For show notes visit: https://www.talkingDrupal.com/574 Topics What Is UN Open Source Week Why Open Source Fits UN Goals Who Attends and What Tech Is There Conference Audience and DPI DPG Drupal as a Digital Public Good UN Uses Drupal at Scale Why Attend and What to Gain Upstream First Contracting Open Procurement Curriculum Reaching Procurement Conferences Steering Spend Upstream Funding Open Source Legally Talking Louder Beyond Drupal Digital Sovereignty Explained Governance Values Matter Fixing Funding Perception Community Next Steps Closing Resources Appalachia Omar Mohsine Digital public infrastructure - DPI Digital public good - DPG ShareIT act Agencies need to use open source PDF: https://www.govinfo.gov/content/pkg/COMPS-17951/pdf/COMPS-17951.pdf Ditap NCMA Sovereign tech agency Palantir blog Eva black - Four opens FSF - Four freedoms Drupal's open web manifesto https://www.drupal.org/association/open-web-manifesto https://openwebsitealliance.org/charter.html#open-web-manifesto Guests Henry Poole - civicactions.com henry-poole Tim Lehnen - drupal.org hestenet Hosts Nic Laflin - nLighteneddevelopment.com nicxvan John Picozzi - epam.com johnpicozzi Tim Sharp - tea-sharp MOTW Correspondent Martin Anderson-Clutz - mandclu.com mandclu Brief description: Have you ever wanted parts of your Drupal pages, like blocks, views, or notifications, to update in real time without a page refresh, and without having to stand up extra infrastructure to do it? There's a module for that. Module name/project name: Live Update Brief history How old: created in Sep 2026 by Alessandro Feijó (afeijo) of Mindcore Versions available: 1.0.0-alpha6, which works with Drupal 11 and 12 Maintainership Actively maintained, latest release just a week ago No security coverage yet, since it was just created and only has alpha releases Test coverage Documentation: a detailed README, plus a roadmap doc and a built-in demo page Number of open issues: none Usage stats: 14 sites Module features and usage Live Update positions itself as a generic real-time event layer for Drupal: modules publish events to named channels, and browsers subscribed to those channels update just the affected part of the page Out of the box it uses plain HTTP polling back to Drupal, every 5 seconds by default, so it works on pretty much any host with no extra services The transport is pluggable, though. Set it to automatic and it'll try WebSockets first, then an experimental Server-Sent Events submodule, then fall back to polling For site builders, the base module adds an "Update this block live" checkbox to any block in the block layout, no code needed There's also a whole suite of submodules: live-refreshing Views displays, single-entity updates, user presence blocks like "who's viewing this page", a notification bell with toasts, queue progress monitoring, remote JSON API tables, and an admin dashboard with an event monitor One I think editorial teams will like: Live Update Form, which warns you when someone else is editing the same content you are For developers, publishing is one line, a liveupdate_publish() helper or an injectable service, and on the front end you can either use data attributes in your markup or subscribe through a small JavaScript API Every channel is access-controlled, and modules can weigh in on who's allowed to subscribe through by implementing hook_liveupdate_channel_access() Under the hood, events are stored in their own database table with an optional time-to-live, and expired ones get cleaned up on cron. Polling clients just ask for anything newer than the last event ID they saw There's a solid set of Drush commands too, including one to publish a test event straight from the command line, which is handy for debugging Caveat: this is very new and still alpha, so I'd treat it as one to watch and experiment with rather than deploy into production today And if polling isn't enough for you, there's a companion project, Live Update Go: https://www.drupal.org/project/liveupdate_go It's the push transport Live Update is designed around. A small Drupal module, plus a standalone gateway written in Go that gives browsers a native WebSocket connection Drupal stays in charge: it checks channel access, hands the browser a short-lived signed token, and sends signed events to the gateway, which fans them out to connected clients You run the gateway as its own service, with systemd or Docker, behind a TLS reverse proxy. The README is very clear that you shouldn't try to launch it from PHP It can scale horizontally using Redis or Valkey pub/sub, one gateway can serve multiple Drupal sites with isolated tenants, and if it ever goes down, Live Update falls back automatically and switches back once it recovers Same maintainer, created at the start of October, and also alpha, with an alpha1 release and one reported site so far

Today we are talking about Drupalcon Rotterdam, Canvas and evaluating modules. We'll also cover Revision Graph as our module of the week. For show notes visit: https://www.talkingDrupal.com/573 Topics DrupalCon Rotterdam recap AI summits and training FrankenPHP app servers Driesnote highlights Advocacy and WordPress Rosetta Sprint and MCP Canvas multilingual and headless 3Frameworks And Voiceover Canvas And SDCs Headless And Signage Drupal 12 Beta Testing Rector And Deprecations PHP 8.5 Requirements Rethinking Module Evaluation AI And Commit Scale Module Discoverability 0Distributions Versus Recipes Resources Wordpal Core metrics Hosts Nic Laflin - nLighteneddevelopment.com nicxvan Martin Anderson-Clutz - mandclu.com mandclu Tim Sharp - tea-sharp MOTW Correspondent Martin Anderson-Clutz - mandclu.com mandclu Brief description: Have you ever wanted to see a node's revision history drawn like a Git graph, with each translation as its own branch? There's a module for that. Module name/project name: Revision Graph Brief history How old: created in Sep 2019 by Shibin Das (D34dMan) of Factorial Versions available: 4.0.0, which works with Drupal 11 and 12, and 3.1.1 for Drupal 10 and 11 Maintainership Actively maintained, 4.0.0 landed in mid-August after two alphas the same week Security coverage Test coverage Documentation: a solid README plus in-depth technical and revision-model docs in the repo Number of open issues: zero open issues Usage stats: 242 sites Module features and usage With the module installed, every node gets a Revision Graph tab, right next to the core Revisions tab One row per revision, one lane per language, so you can see when a translation branched off and how it's evolved since Each dot tells you two things: a solid ring means that revision was live at some point, a dashed ring means it's a draft that never was, and a filled center means it's what that language is serving right now It works with Content Moderation if you have it, showing your workflow states as text badges with whatever names your site uses, and adapts cleanly when you don't Reverts, and edits made from the published version while a draft is pending, show up as forks instead of a straight line Under the hood: Drupal doesn't actually store which revision a new one was derived from, so the module adds a small base field that records it at presave Older revisions don't get backfilled, on purpose, since reconstructing that would mean guessing. Those edges are inferred, and the graph draws inferred edges differently from recorded ones, so it never implies more precision than it has So on an existing site, make sure you run drush updb after enabling it Ships a distinct color for all 95 language codes Drupal knows, so it looks good out of the box, but you can override a lane's color or the fallback palette in config The graph loads in pages as you scroll, so long histories render quickly, and it's keyboard navigable, ARIA-labelled, and works in forced-colors mode Great for editorial teams on multilingual sites, and handy for compliance or auditing when you need to answer "what was live, and when?" Caveats: it's nodes only, and for obvious reasons a user will need the "view all revisions" permission to see the graph

Today we are talking about PHP, Open Source, and Sustainability with guest Elizabeth Barron. We'll also cover AI Image Classification as our module of the week. For show notes visit: https://www.talkingDrupal.com/572 Topics What is the PHP Foundation Language Health Challenges Paid Core Developers Release Infrastructure Foundation Role and Perception Docs and Onboarding Elizabeth Open Source Journey Future of PHP Ecosystem Listener Elephant Question Ecosystem Security Hub Advisory Board Limits Modernizing Mailing Lists Foundation Awareness Push PHP Ambassadors Strategy State of PHP Survey Five Year Vision Community Hour Podcast php.net Design Refresh Resources The PHP Foundation Derek Rethans xdebug Infrastructure https://github.com/derickr Drupal advocacy Link to community hour podcast Php 8.5 Contribute to php article Guests Elizabeth Barron - thephp.foundation elizabethbarron Hosts Nic Laflin - nLighteneddevelopment.com nicxvan John Picozzi - epam.com johnpicozzi Tim Sharp - tea-sharp MOTW Correspondent Martin Anderson-Clutz - mandclu.com mandclu Brief description: Have you ever wanted the images in your Drupal media library to be automatically given alt text, a rich description, and a set of tags, using AI? There's a recipe for that. Module name/project name: AI Image Classification Brief history How old: created in Sep 2025 by Artem Dmitriiev (a.dmitriiev) of 1xINTERNET Versions available: 1.1.1, which requires Drupal 11.2 or newer Maintainership Actively maintained, latest release and commit just two weeks ago Security coverage Number of open issues: 9 open issues, 4 of which are bugs Usage stats: No usage data reported Module features and usage This recipe applies core's image media type recipe, then adds a description field and a tags field to image media, with tags in a new "Image Classification" vocabulary Editors get a "Generate Alt Text" button right on the image field, using the Field Widget Actions module, with a prompt written like an accessibility expert: under 100 characters, no "image of", flag logos and graphics On save, a vision model writes a description of up to eight sentences: colours, photo versus illustration, people, mood, and key objects, using the media name for context Tagging is chained off that description rather than the image itself, picking or creating up to five short, general terms, and reusing similar existing tags where it can It also adds bulk actions to the media admin view, so you can run description and tagging across an existing library, not just new uploads Description and tag filters are added to the media library, including the widget, so editors can search for "sunny summer day" right in the image picker The stated bigger goal is making images discoverable by RAG and other AI search, so good descriptions become a foundation for future AI features. In fact, this recipe is a dependency for the Canvas AI Image Search recipe, which is still a work in progress Under the hood, images get scaled to 400px wide and converted to PNG before they're sent to the model, which keeps things faster and cheaper One caveat: your site needs an AI provider with a default "chat with image vision" model, and the recipe checks for that when it's applied Also worth a look: the description prompt asks the model to describe people's age, gender, and ethnicity, and even name them if it can, so you may want to review that prompt for your privacy policies, and adjust accordingly Like any recipe, it provides a robust starting point for some compelling features, and every prompt and setting can be tweaked after you apply it Lastly, I wanted to mention that in today's Driesnote in here in Rotterdam, Dries demoed being able to use MCP to search images on his own site. A recipe like this could help you make sure the images in your media library have sufficient metadata to make that work reliably

Today we are talking about GovHub, Drupal in Government, and Why Governments Love Drupal with guest Jasmyne Epps. We'll also cover Convivial Gov Site Template as our module of the week. For show notes visit: https://www.talkingDrupal.com/571 Topics GovHub Origins and Goals Feature Requests and Governance Why Government Chooses Drupal Team Structure and Release Cadence Accessibility and Compliance Strategy Hosting Model and Multisite Structured Content and Microcontent Syndication and Emergency Alerts Orchard Design System Explained Training and Onboarding Editors Gov Talks Conference Logo Specs and Releases Ticket Prioritization PRICE QA Workflow with Tugboat Handling Traffic Spikes Drupal 11 Performance Talk Drupal 11 Upgrade Gotchas Getting Users Excited Translation Strategy Limits Why Government Loves Drupal Resources GovHub The Bug Stops Here — The State of Georgia Shifts Left (GovCon 2025 presentation with Jasmyne Epps and James Sansbury) Accelerating an ambitious migration and development project (GovHub + Tugboat migration story) Logo page Public facing knowledge base Orchard design system (P)Rice (P)olitics - (R)each - (I)mpact - (C)onfidence - (E)ffort Luma Guests Jasmyne Epps - jasmyneepps.com jasmyneepps Hosts Nic Laflin - nLighteneddevelopment.com nicxvan John Picozzi - epam.com johnpicozzi Amber Matz - tugboatqa.com [amber himes matz](https://www.drupal.org/u/amber himes matz) MOTW Correspondent Martin Anderson-Clutz - mandclu.com mandclu Brief description: Have you ever wanted to stand up a polished, accessible government website in Drupal (with components, content types, SEO, and cookie consent all wired up) without writing any code? There's a site template for that. Module name/project name: Convivial Gov Brief history Created in March 2026 by Morpht, the shop behind the Convivial family — with Ivan Zugec leading the maintainer team. Versions available: 1.3.3, which works with Drupal 11 Maintainership Actively maintained: release just last week, on September 16th Security coverage Test coverage: functional tests for install and validation, plus a kernel requirements test. Documentation there's a full handbook over at docs.morpht.com, and a live demo at gov.convivial.io Open issues: none? Site template features and usage Like the Haven site template we talked about a couple of weeks ago, Convivial Gov gives you a curated stack plus demo content, and in this case hands you a robust, ready-to-customize government site. Because it's built on Drupal CMS, you get all the latest Drupal tooling: Canvas for visual page building, Single Directory Components, and Recipes. The front end is Morpht's Morphos theme, built on Tailwind and DaisyUI, so you get dark mode, multiple colour palettes, and a big library of editor-friendly components out of the box. It's worth mentioning that using the Morphos theme on a production site requires a paid license The provided components are sorted into six buckets: container, content, child, element, background, and behavior. They include fun ones like scroll reveal and a colour palette switching behavior The content model is broad. You get seven content types: Page, Section, Article, Publication, Resource, Topic, and Audience. And, they come with a stack of teaser and card view modes to display them. The whole point is no-code: a site builder can compose sophisticated pages in Canvas without ever touching a template. One thing to watch: the default timezone is Australia/Sydney out of the box It's also worth comparing Convivial Gov to another site template called Local. Both dropped in March 2026, both are Canvas-based Drupal CMS site templates for the public sector, and both lean on ECA for automation — so there's real common ground. The difference is scope and mechanism. Local, from Annertech, is narrowly purpose-built for local councils and community-service directories: it ships a specific service information architecture — Service and Service Landing content types — with ECA wired so section pages stay in sync when service pages get published or updated, taking its cues from the gov.uk design system. Convivial Gov goes the other way — it's design-system-led and general-purpose, a broad component library and content model meant for any government, agency, or marketing site rather than one particular workflow.

Today we are talking about Laravel, Marketing, and The PHP Foundation with guest Matt Stauffer. We'll also cover Formdazzle as our module of the week. For show notes visit: https://www.talkingDrupal.com/570 Topics What Is Laravel Writing Laravel Books AI and Technical Writing Laravel Versus CMS Drupal as Framework Integrating Laravel and CMS Laravel and Symfony Marketing Modern PHP Laravel Community Marketing Jigsaw and Onramp Drupal Marketing Lessons Onboarding Focus in Laravel Laravel BDFL Changes Onboarding And Docs Drupal Framework Perception What PHP Foundation Does Marketing PHP Vs Laravel AI Answers And Positioning Cross Ecosystem Collaboration Resources Jigsaw Onramp Native php Alpine Tailwind Vue Laravel herd php.new Blog post on how to contribute to php Laracon talk Kent C. Dodds The Last Software Engineer (how in the AI era, we need to all become Product Engineers) Guests Matt Stauffer - mattstauffer.com Hosts Nic Laflin - nLighteneddevelopment.com nicxvan John Picozzi - epam.com johnpicozzi Amber Matz - tugboatqa.com [amber himes matz](https://www.drupal.org/u/amber himes matz) MOTW Correspondent Bernardo Martinez - bernardm28 Brief description: This week's module is Formdazzle, a developer tool that makes theming Drupal forms easier. Drupal's Form API is a powerful abstraction, but when you want to target one specific field, label, button, or form wrapper, the default Twig template suggestions can be limited. The module works by taking information Drupal already knows about the form, like the form ID, element type, and element name, and using that to generate more targeted Twig template suggestions. For example, in a Drupal View with exposed filters, you may want to style the Reset button differently from the Submit button. By default, Drupal renders both buttons through the same input–submit.html.twig template, which makes it difficult to customize them independently. This module lets you assign different templates to individual form buttons—such as Submit, Reset, or Filter—based on their action, type, and other properties. This module has no configuration. Just enable the module and it starts working and look at the twig debug comments including extra template suggestions. Module name/project name: formdazzle Brief history How old: created in 13 September 2019 by johnalbin Versions available: ^10.1 ^11 ^12 Maintainership Actively maintained Last release was 1 September 2026, currently the module has two maintainers Stephen Mustgrave and John Albin. The module includes both test and security coverage. Usage stats: 3,956 according to drupal.org Module features and usage There's no configuration. Just enable the module and it starts working, including with Views exposed forms and Webform. Formdazzle automatically adds more specific theme suggestions based on the form ID, element type, and element name.

On today's show we are talking about Site Templates, What they do, and How you can use them with guests Tim Lehnen & Adam Globus-Hoenich. We'll also cover Haven as our module of the week. For show notes visit: https://www.talkingDrupal.com/569 Topics MOTW: Haven What Site Templates Are Canvas Components Included Promoting Templates Beyond Drupal Templates vs Distributions Who Benefits from Templates Template Types and Adoption Where to Find Templates Featured vs Installer List Free vs Paid Templates Recipes vs Templates Distributions and Themes Empowering Site Builders Exporting a Template Designing for Users Releases Without Upgrades Best Practices and AI How to Contribute Resources Webinar: Drupal Canvas and Agentic Content Management: What Enterprise Teams Need to Know Drupal Site Templates Tim's book - Fog & Fireflies Guests Tim Lehnen - @TimLehnen hestenet Adam Globus-Hoenich - @PhenaProxima phenaproxima Hosts Nic Laflin - nLighteneddevelopment.com nicxvan Stephen Cross - SecondSginalMedia.com [stephencross]](https://www.drupal.org/u/stephencross) Amber Matz - tugboatqa.com [amber himes matz](https://www.drupal.org/u/amber himes matz) Module of the Week Correspondent Martin Anderson-Clutz - mandclu.com mandclu Haven - Site Template - Designed for non-profit sites, this template features a bright, warm design that can be adapted for many use cases. It comes pre-confifgured with blog, projects and people profiles, as well as newsletter signup, donation add-ons and more.

Today we are talking about Drupal Performance, Rapid Development, and Drupal Canvas Maturity with our hosts. We'll also cover Microsoft 365 FullCalendar as our module of the week. For show notes visit: https://www.talkingDrupal.com/568 Topics Deprecating Module Theme Files Migrating Hooks to Classes Why This Change Matters Drupal Performance Gains Performance Audits and Lighthouse Automating Checks and Spreadsheet Rant AI Spreadsheet Cautionary Tale Privacy Concerns with AI Freelancer Pressure Rapid Change Reality Canvas Release Risks Community Support Needed AI For Documentation Canvas Production Readiness Canvas Architecture Debate AI For Voting Research LLM Bias And Sources Resources Rebrickable Webpagetest Lighthouse Tugboat Drupal canvas Guests Martin Anderson-Clutz - mandclu.com mandclu Hosts Nic Laflin - nLighteneddevelopment.com nicxvan John Picozzi - epam.com johnpicozzi Amber Matz - tugboatqa.com [amber himes matz](https://www.drupal.org/u/amber himes matz) MOTW Correspondent Martin Anderson-Clutz - mandclu.com mandclu Brief description: Have you ever wanted your users' own Outlook calendars to show up right alongside your Drupal content in a calendar view? There's a module for that. Module name/project name: Microsoft 365 FullCalendar Brief history How old: created just last month, August 19 2026, by fabianderijk of Finalist Versions available: 1.0.0, which works with Drupal 11 Maintainership Brand new — the first and only release is from last month, and the whole commit history is basically launch day Security coverage: brand new, so not yet Test coverage: yes, both unit tests and kernel tests Documentation: a genuinely thorough README — it walks through privacy, the config guard rails, and three different ways to customize event output Open issues: none yet, it's less than two weeks old Usage stats: Too new for a site count Module features and usage With this installed, it adds the signed-in user's Microsoft 365, or Outlook, calendar as an extra event source on a FullCalendar view — so their personal appointments sit right next to the Drupal content the view already renders It leans on the Microsoft 365 Connector module and its SSO submodule, plus the FullCalendar module. Each user must have signed in through Microsoft 365 SSO: anyone who hasn't just sees no events, which is a clean fallback It uses lazy loading, so it only fetches events in the date range the calendar is currently showing, not your whole calendar Privacy is baked in: anything marked private or confidential in Outlook is masked, so it shows up as just "Busy", with no title, location, or meeting link, unless the site builder deliberately turns masking off The response itself is per-user and marked private, no-store, so it never lands in a shared or CDN cache There's a clever server-side cache too: it stores the raw Graph response before masking, so a single fetch can serve several displays that each have different masking settings You get guard rails you can tune with Drush or an admin form: max events, max date range, cache lifetime, and a separate, shorter failure cache That failure cache is a nice touch — if there's no active Microsoft session, or Graph errors out, it caches the empty result briefly so a broken connection doesn't get re-polled on every single calendar click Under the hood it calls Graph's calendarView endpoint rather than /me/events, which means recurring meetings get expanded into their individual occurrences — exactly what a calendar grid needs Every event carries CSS classes for its status — busy, free, tentative, out-of-office, working elsewhere, cancelled — so you can style them however you want And if CSS isn't enough, there's a server-side alter hook and a JavaScript pre-build event for fully custom rendering. Nice detail: the hook is explicitly guarded so you can't use it to put back a title or location that masking just stripped out Clearly this will be more useful for edge cases, for example an intranet, but I think this is a really interesting example of the power of Drupal as an integration layer, or as some like to put it, the "glass" through which a user can interact with multiple systems

Today we are talking about Security, Vulnerabilities, and how to avoid exposure with guest Dave Welch. We'll also cover Security Scanner as our module of the week. For show notes visit: https://www.talkingDrupal.com/567 Topics What Are CVEs CVE Lifecycle and Disclosure AI Era Security Challenges What CVE Program Excludes Patch Fast Reality Global Security Signals CVE Timing Judgment KEV Flags Explained CVE Updates Link Rot Who Decides CVE Sneaky Patch Dangers ADP Program Fixes Small Team Triage Vulnerability Tsunami AI Autonomous Security Future Legal Pressure Budgets Resources Psalm PHP Static Analysis Tool SARIF format PHP ecosystem Council of roots How AI Broke Open Source Security: End-of-Life Software Is the Most Exposed CVE podcast Vulncon PSIRT Guests David Welch - github: dwelch2344 dwelch2344 Hosts Nic Laflin - nLighteneddevelopment.com nicxvan John Picozzi - epam.com johnpicozzi JD Flynn - dorficus MOTW Correspondent Martin Anderson-Clutz - mandclu.com mandclu Brief description: Have you ever wanted a fast way to catch the security mistakes that slip into custom Drupal code — especially the code your AI assistant just wrote — before it ships? There's a module for that. Module name/project name: Security Scanner Brief history How old: created in July 2026 by Mayank Gupta (mayankguptadotcom) of Acquia Versions available: 1.0.0, which works with Drupal 10.3 and 11 Maintainership Actively maintained — created and shipped its first stable this summer, with steady development right through late July Security coverage Test coverage — and it's strong: unit and kernel tests, including a regression corpus built from real Drupal core advisories Documentation? In-depth README with a full check table and CI recipes, plus a CHANGELOG Number of open issues: 1 issue, not a bug Usage stats: 2 sites (it's brand new) Module features and usage Provide a Drush command, has no UI — you point drush security:scan at a module or any path, it reads the code statically, and prints a prioritized, OWASP-mapped list of things to review It's built for the age of AI-written code — the checks target the classes AI assistants keep reintroducing: routes with no access check, #markup and |raw XSS, missing CSRF tokens, unserialize() on untrusted data, hardcoded secrets Then there's an optional deep pass: with the Psalm static analysis scanning engine installed, it'll trace untrusted input across functions and files to catch cross-function issues. And it's honest about state — the report always says whether that deep pass ran, was skipped, or failed, so a failure never gets mistaken for a clean scan One nice detail under the hood: a tokenizer-backed "code map" that knows whether a match is real code, a comment, or a string — so it won't flag the word "unserialize" sitting in a doc comment. That kills the single biggest source of false positives The checks are regression-tested against real Drupal advisories (Drupalgeddon, Drupalgeddon2, the 2019 unserialize bug, etc) so a pattern that caused an actual CVE can't quietly come back in your custom code Output comes in three flavors: a readable table, JSON for CI and AI agents, and SARIF — which means findings show up as annotations right on your GitHub or GitLab merge-request diff instead of buried in a job log For adopting it on an existing codebase there's a baseline file — you fingerprint the findings you've reviewed, with a required reason on each, and they stop failing the build but never go invisible; every run still counts them It exits non-zero on error-level findings, so it drops straight into CI or a pre-commit hook And it's extensible — checks are Drupal plugins with a #[SecurityCheck] attribute, so any module can add its own or alter the ones that ship Big caveat, and the module says this itself: a finding means "review this," not "this is broken." Static analysis has false positives, and a clean scan doesn't prove the code is secure — access-control logic especially still needs human review I first heard about this module over beverages at Drupalcamp Asheville, so I know that this module was largely vibe-coded, after having an AI agent ingest every single Drupal security team CVE. So I like to think of this module as security pattern recognition tool, but of course it does even more

Today we are talking about Drupal, AI, and learning to use it responsibly with guest Mike Anello. We'll also cover Entity Mesh as our module of the week. For show notes visit: https://www.talkingDrupal.com/566 Topics Course overview Fast moving modules Inside vs outside AI No code approach Keeping curriculum current Essentials vs add ons Chat Claude Code setup Inside vs Outside AI Rules and Provider Calls Guardrails in Drupal UI Model QA and Testing Local Models and Costs Token Budgets and Logging Course Use Cases Overview RAG and Vector Basics Class Schedule and Pricing AI Predictions and Wrap Resources New DrupalEasy class: Responsible Drupal AI Basics Training at orlando amazee ai Jrockowitz losing my skill AI module ecosystem AI browser provider (LLM in Google Chrome) amazee.ai Private AI Provider Derecho Guests Mike Anello - drupaleasy.com ultimike Hosts Nic Laflin - nLighteneddevelopment.com nicxvan John Picozzi - epam.com johnpicozzi JD Flynn - dorficus MOTW Correspondent Martin Anderson-Clutz - mandclu.com mandclu Brief description: Have you ever wanted a way to analyze and visualize the ways in which the content on your Drupal site is interlinked? There's a module for that. Module name/project name: Entity Mesh Brief history How old: created in Jan 2025 by Jorge Tutor (gedur) of Metadrop Versions available: 2.1.0 and 2.0.3, both of which work with Drupal 11 Maintainership Actively maintained, latest release last month, and a commit just yesterday Security coverage Test coverage Documentation? Project page is pretty descriptive Number of open issues: 13 open issues, 4 of which are bugs, but 2 of those were marked fixed in the past week Usage stats: 437 sites Module features and usage With Entity Mesh installed, the module will analyze the rendered output of your nodes using a chosen account, looking for links to other content That means it will find not just links in entity relationship fields, but also links within formatted text, menus, and more The results can be visualized in a D3.js 3D visualization, displayed as a table, or exported as a CSV The report also exposes a set of Views-style filters, to help you narrow down to the specific set of information you want to understand Entity Mesh analyzes the DOM of your rendered nodes, looking for links, iframes, and images. Internal paths are further analyzed and categorized, for example based on whether the specified path redirects, is broken, points to something that is access-denied, and so on From a marketing perspective, that allows you to understand the paths available to navigate from a source page to a target page, the content linked to or from a specific page, and will also augment the content deletion confirmation form to advise the user of any existing links to the content being deleted There are obvious SEO advantages to being able to find redirect chain, broken or access denied links, and there are GDPR compliance implications for being able to identify iframes that might load third-party cookies The project page also mentions that this module could be very useful to run after a content migration, for QA The actual analysis of your site content be triggered by drush, an admin form, or by cron, and you can set limits on the size of the batch to run, because of the weight it puts on your site by rendering every node it analyzes The current versions Entity Mesh also depend on the Entity Registry and Entity Render Context modules, that have essentially the same maintainers, so if there's only part of Entity Mesh that you really need, you could also give those a look Back in episode #321 we covered Entity Usage, and there are some definite similarities, but also some differences. While they both provide reporting on content relationships, Entity Usage does so by examining structured field values at save time. So, the information gathered is different, and collects data that can be displayed in views or custom code.

Today we are talking about Open Source sustainability, becoming your own content creation machine, and how drupal influenced some of that with guest Jeff Geerling. We'll also cover AI Metering as our module of the week. For show notes visit: https://www.talkingDrupal.com/565 Topics Jeff's Timekeeping Icebreaker Jeff's Drupal Origin Story From Drupal to Hardware Tinkering Staying Motivated on YouTube What Conferences Are Really About DrupalCon Memories and Community Why Jeff Moved to Hugo PSA Tornado Warning Detour Keeping Up with Drupal CMS PHP Perception Shift Fast Drupal Setup COVID Streaming Boom Picking Video Projects Decommissioning Builds YouTube Algorithm Risk Vintage Time Server Creator Starter Tips Supporting Maintainers Books and Crohns Local Control Trends AI Workflow Boundaries Timing Obsession Kind Drupal Culture Guests Jeff Geerling - jeffgeerling.com geerlingguy Hosts Nic Laflin - nLighteneddevelopment.com nicxvan Mike Anello - drupaleasy.com ultimike JD Flynn - dorficus MOTW Correspondent Mike Anello - drupaleasy.com ultimike Brief description: AI Metering module - helps keep track of your users' AI token usage on the site. Includes cost estimation, token limits, and local LLM fallback options. Module name/project name: AI Metering Brief history How old: created in June 1 2026 by Jérôme Tchania (codeitwisely) Versions available: 1.0.1 Maintainership Actively maintained - yes Co-maintained by Carlos Ospina (camoa) Security coverage - yes Test coverage - yes Documentation - yes Number of open issues: 9 open issues, 4 of which are bugs against the current branch Usage stats: Sites: 78 Module features and usage Obtains token costs for all modules from LiteLLM Can be configured to send email when the token limit is being approached. Per user and per role reports. LLM fallback to Ollama

Today we are talking about Maintaining NodeJS, Patternlab, Writing Books, and Open Source with guest Brian Muenzenmeyer. We'll also cover AI Webform Generator as our module of the week. For show notes visit: https://www.talkingDrupal.com/564 Topics Brian Open Source Origins Pattern Lab Node Journey Maintaining and Moving On Writing Approachable Open Source Who the Book Is For Beyond Code Contributions All Things Open Book Signing Choosing Conferences to Attend Pitching Open Source at Work Misconceptions and Starting Small Avoiding Maintainer Burnout Handling AI Noise and Low Effort PRs DCO and Licensing Basics Better Communication and Reviews Node and Drupal Lessons Optimism for Open Source Future Resources Brian Muenzenmeyer https://brianmuenzenmeyer.com https://approachableopensource.com/ https://bsky.app/profile/brianmuenzenmeyer.com https://www.linkedin.com/in/brian-muenzenmeyer-91a77554/ https://www.renderatl.com/schedule upcoming https://nodeconf.eu/program upcoming spectrum of engagement https://approachableopensource.com/blog/2025-open-source-pace-layers/ change in contention https://brianmuenzenmeyer.com/posts/2018-i-maintainer/ burnout https://approachableopensource.com/read/the_spectrum_of_engagement/ https://approachableopensource.com/read/the_four_files_of_any_open_source_project/ LICENSE Hodag Cryptid https://en.wikipedia.org/wiki/Hodag https://www.rhinelanderchamber.com/about-the-hodag/ You should write a book All contributors spec Talk at all things apart DCO Developer Certificate of Origin Open source law policy and practice Sustain OSS Guests Brian Muenzenmeyer - brianmuenzenmeyer.com Hosts Nic Laflin - nLighteneddevelopment.com nicxvan John Picozzi - epam.com johnpicozzi Bernardo Martinez - bernardm28 JD Flynn - dorficus MOTW Correspondent Jacob Rockowitz - jrockowitz.com jrockowitz Brief description: AI Webform Generator enables site builders to create a Drupal Webform, or update an existing one, from plain-English instructions. It sends the request through the site's configured Drupal AI provider, validates the returned Webform definition, and saves the resulting form. Review the generated change before using the form. Module name/project name: AI Webform Generator (ai_webform_generator) Brief history Created on 2 July 2026 by chaitanyadessai (Chaitanya R Dessai). The current stable release is 1.0.2, released on 3 July 2026, and supports Drupal ^10 || ^11. Maintainership Appears actively maintained: Drupal.org lists an update on 24 July 2026. Maintainers: zeeshan_khan and chaitanyadessai. (Specbee) Security coverage: Yes. Stable releases are covered by Drupal's security advisory policy. Test coverage: Yes. Version 1.0.2 includes unit, kernel, and functional tests for prompt building, JSON validation, settings, route access, Webform building, and optional CAPTCHA elements. Documentation: Yes. The project page and module README cover requirements, configuration, usage, security considerations, and supported field types. Issues: 1 open issue, with 0 open bug reports (7 issues total). Usage stats: 1 site reports using this module. Module features and usage Creates complete Webforms and updates existing Webforms in place from natural-language prompts. Supports common Webform elements, including text, email, telephone, number, date, select, checkbox, radio, range, password, hidden, and managed-file elements. Validates the AI response before applying the Webform definition. Uses the existing Drupal AI provider configuration; API keys are not stored in this module's configuration. Provides configurable model, temperature, output-token, and per-user request limits to balance output quality and provider spend. Requires trusted users with both the generator permission and ordinary Webform edit access when changing an existing form. AI-Generate Notes, Review, and Recipe (used for testing) https://github.com/jrockowitz/drupal_playground/tree/main/recipes/drupal_playground_webform_ai AI-Generated Assessment Technical: The module separates AI generation, prompt building, JSON validation, and Webform construction into Drupal services. It uses the site's configured Drupal AI provider, validates a limited allowlist of Webform element types before saving, and exposes model, temperature, output-token, and per-user request-limit settings. Access and error handling: Generation requires its own permission, and updating an existing Webform also requires normal Webform update access. A per-user flood limit constrains provider spend; failures are logged, with detailed upstream errors shown only to generator administrators. Code quality: Version 1.0.2 uses strict types and separates form, service, validation, and persistence responsibilities. It includes unit, kernel, and functional coverage for core behavior. This assessment is a code review of the released module, not a security audit. Implementation: The module creates new Webforms and updates supported fields of existing Webforms in place, but saves the generated definition immediately without a preview, diff, or approval screen. Usefulness: The module is useful for quickly drafting straightforward Webforms and iterating on common field changes when a site builder reviews the result. Complex, highly customized, or regulated forms need especially careful manual review before publication. How to use it: Configure a chat-capable provider, select an existing Webform or choose to create one, describe the fields and validation in plain English, submit the request, and then review the saved Webform. For example, create a disposable contact Webform and ask the generator to add a required telephone field while preserving the existing fields. AI-generated source code: The module's runtime use of AI and its code style cannot establish whether its source was AI-generated or AI-assisted. Its public project metadata does not make an authorship claim, so this is unknown. Possible improvements: Add a preview/diff and explicit approval before saving; broaden support for advanced Webform structures and handlers; add optional, privacy-conscious prompt and response audit logs; and expand regression coverage for complex Webform updates. Next steps for adopters: Restrict generation to trusted roles, begin with a low request limit, test representative prompts outside production, and review every generated field, validation rule, confirmation message, and permission before publishing.

How should development teams adopt AI without sacrificing code quality or collaboration? In this Talking Drupal Cafe, Stephen Cross is joined by Mike Miles and Jim Birch to discuss practical strategies for integrating AI into Drupal development teams. They explore AI coding assistants, team policies, code review, agent workflows, governance, and real-world lessons from using tools like Claude Code and GitHub Copilot in production environments. For show notes visit: https://www.talkingDrupal.com/cafe020 Topics Why AI Matters Now Team Introductions From Experiments to Workflows Standards and Guardrails Skills and Automation Examples Taming Verbose AI Code Adoption and Tool Choices Governance and Training Measuring Productivity Gains Keeping Up Without FOMO AI for Editors and Site Features Red Teaming and AI Security Jim Birch Jim Birch is Director of Engineering and AI Practice Lead at Kanopi Studios, where he leads engineering teams and oversees the company's responsible adoption of AI. Jim is also a Drupal CMS committer, and Recipes Initiative Coordinator, and is a Google Cloud Certified Generative AI Leader. Michael Miles Mike Miles is a technical leader and speaker with more than 20 years of experience in web engineering, open-source development, and digital platform delivery. As the Director of Web Development at MIT Sloan, he leads the team responsible for the development, maintenance, and growth of the school's public digital properties. Mike regularly speaks at technical conferences on topics including modern web development, Drupal, technical leadership, testing, delivery practices, and practical AI adoption. He is also one of the organizers of New England Drupal Camp. Stephen Cross Stephen Cross has been a Drupal developer for over 20 years and founded Talking Drupal in 2013. As founder of Second Signal Media, he combines his passion for open source and media production to share conversations that help the Drupal community learn and grow. Guests Michael Miles - mikemiles86 Jim Birch - thejimbirch Stephen Cross - stephencross Resources Courses https://anthropic.skilljar.com/ https://academy.openai.com/pages/courses Skills https://kanopi.github.io/cms-cultivator/ https://kanopi.github.io/delivery-record/

Today we are talking about Drupito, its Business model, and Marketplaces with guest Ashraf Abed. We'll also cover Generate (Social Media) Image as our module of the week. For show notes visit: https://www.talkingDrupal.com/563 Topics Meet Drupalito and the Mission Platform Layers and Roadmap Pricing and New Markets Marketplace Success Stories Exportability and Vendor Lock In Growing the Drupal Ecosystem Derivatives and Recurring Revenue Rebuilding on Drupedo Funding Drupal Association Global Community Check In Migrating Sites to Drupedo Marketplace Vision Shift Maintenance and Incentives Safe Updates Blue Green Testing Mindset for Templates Official Marketplace Collaboration Agency Revenue and Partnerships Niche Derivatives and Pricing Launch Plans and Vetting Resources Code that ships Hosts Nic Laflin - nLighteneddevelopment.com nicxvan John Picozzi - epam.com johnpicozzi Ashraf Abed - drupito.com ashrafabed Avi Schwab - froboy.org froboy MOTW Correspondent Avi Schwab - froboy.org froboy Brief description: Have you ever wanted Drupal to generate dynamic social media images using tokenized node data, similar to the share images on GitHub repos or Reddit threads? There's a module for that Module name/project name: Generate (Social Media) Image Brief history How old: Created by tfranz of Germany on 22 April 2022 Versions available: 1.x-dev, 2.0.0-beta2, published a few weeks ago by our own Martin Anderson-Clutz Maintainership Minimally (although now slightly more actively) maintained No Security coverage (yet) Passing GitLab CI tests Well fleshed out README for docs Number of open issues: 8 open issues, 0 of which are bugs against the current branch, but there are lots of feature requests Usage stats: 1 site reports using this module Module features and usage GSMI requires an image style that uses a "Text Overlay" effect — this comes from the Image Effects module and lets you burn tokenized (or static) text onto an image. Normally, when Drupal generates an image style derivative, there's no entity in scope — it's just processing a file — so a token like [node:title] would resolve to nothing. GSMI's real contribution is the glue: when it builds a derivative for a specific node, it swaps in the node-resolved text before generating the image. That's what makes entity-aware tokens work inside an effect that otherwise only sees global tokens. Once the image style exists, GSMI's settings form lets you pick a source image field on the node — an image field or a media-reference field — plus a fallback image for when that's empty. From there it generates the styled derivative from that source image, for any node of any content type that has the field. Finally, GSMI exposes its own token — [node:generate-style], with optional style/field overrides — so you're not locked into the one global style/field pair configured in the settings form. I used that to drop the generated image into Metatag's og_image field for the Session content type on the MidCamp site, getting us dynamically generated session images.. A couple of gotchas we hit setting this up: Text Overlay's layout options have some bugs, and not filling out all of the options will result in an image library error. The bigger one: GSMI names the generated derivative file after the source image's filename — extension included — not after whatever format the image style actually outputs. If you try to convert an image to WebP you might get a WebP image with a JPG extension. BUUUUT - LinkedIn still doesn't support WebP (at least as per their documentation, so it's still in 2026 not safe to use WebP for a universal og:image. https://www.linkedin.com/help/linkedin/answer/a521928

Today we are talking about Supporting Open Source, Acquia, and The Acquia Fair Trade Initiative with guest James Sims. We'll also cover Image Effects as our module of the week. For show notes visit: https://www.talkingDrupal.com/562 Topics Fair Trade Initiative Explained How the Program Started Why Fair Trade Matters Adoption and Open Framework Agency and Freelancer Benefits Partner Funded Giving Who Can Be Makers Tracking Participation Tax Deduction Questions Community Shaped Program Money Counts Too Early Challenges Timeline And Launch Sustainability Built In How To Get Involved Defining Success Origins Of Fair Trade Resources Acquia Fair Trade Initiative Taste of chicago Giordanos Lou's pizza Five For The Future Image Convolution Playground Guests James Sims - rcjmselp85 Hosts Nic Laflin - nLighteneddevelopment.com nicxvan John Picozzi - epam.com johnpicozzi Avi Schwab - froboy.org froboy MOTW Correspondent Avi Schwab - froboy.org froboy Brief description: Have you ever gone to edit an image style in Drupal, looked at the list of filters, and said "give me more! I want more!". Have you said "I'd like to mirror, filter, and convolute an image in Drupal - all at the same time". If so, you're in luck. Let me introduce you to our module of the week: Module name/project name: Image Effects Brief history How old: Created by Drupal user mondrake of Italy on 17 September 2015. It's also the successor to the ImageCache Actions module, which was created all the way back in 2008. Versions available: It has a 4.0.0 version available with Drupal 10 and 11 support, and a 5.0.0 version for Drupal 11.3 and above. Maintainership Actively maintained Security coverage Test coverage Documentation It has a full README with details about the available image styles and whether they are supported by the GD or ImageMagick PHP libraries. Number of open issues: 35 open issues, 3 of which are bugs against the current branch. (The current branch has only been out a few months, and many of the open issues against prior branches seem to still be relevant.) Usage stats: 35,196 sites report using this module, with most still on the 3.x or 4.x branches. (its predecessor, ImageCache Actions, still has over 25,000 active installs) Module features and usage The module is pulled in just like any other, with composer require and then enable via drush or the UI. Once it's installed there is a very basic settings page, but most folks won't use much on there. The power of Image Effects comes when you go to Config > Media > Image Styles and then edit an Image Style. Once Image Effects is enabled, you'll see over two dozen additional effects in the list. These effects range from simple to complex. Interestingly, many of the effects that were so amazing 15 years ago are now doable with CSS. Still, there are some incredibly powerful filters. Side note: I'd strongly recommend Aubrey Sambor's recent talk from Drupal Camp Asheville, "You Don't Need JS for That", and her prior talk "Color in CSS" to learn a ton of things you didn't know about CSS effects. The basics like Color Shift, Contrast, Mirror, Rotate, and more are there if you'd like to do these natively. More advanced filters like Sharpen, Blur, and Convolute let you make more complex modifications to images. "Convolution" is the process of applying n-dimensional matrixes to images to create effects such as blurring, sharpening, and edge detection. Try it out on https://anna.engineering/Image-Convolution-Playground/src/ Lastly, you can create advanced image styles with ImageMagick arguments, create Text overlays using the power of Drupal tokens, or even develop your own Image Effects guided by the incredibly detailed DEVELOPING.md file included with the module.