Saltar al contenido
Radio Logo
PodcastsTecnologíaTalking Drupal

Talking Drupal

Talking Drupal Hosts
Último episodio

603 episodios

  • Talking Drupal

    Talking Drupal #578 - Rosetta

    13/11/2026 | 1 h 7 min
    Today we are talking about Better traceability, better debugging, and Rosetta with guest Jürgen Haas. We'll also cover Maestro as our module of the week.
    For show notes visit:
    https://www.talkingDrupal.com/578
    Topics
    What Is Rosetta
    Rosetta Building Blocks
    Standards and Where to Join
    Rosetta End Goal Question
    Unifying Workflow APIs
    Fail Gracefully and Version
    Scaling Module Integrations
    AI Agents as Another UI
    Tools Discovery Explained
    Dependencies and Determinism
    Hooks Glue Code Reality
    Tracing with OpenTelemetry
    Sensitive Data Guardrails
    Big Challenges and Help
    Tool API Adoption Status
    Defining Rosetta Success
    Resources
    One trace, inside and outside Drupal: a proposal for Rosetta
    Write a setting's rules once, in config schema, and use them for validation, forms and the published JSON SchemaMaestro
    Orchestration
    Dries blog post
    W3C open telemetry
    Drupal open telemetry
    Guests
    Jürgen Haas - lakedrops.com jurgenhaas
    Hosts
    Nic Laflin - nLighteneddevelopment.com nicxvan
    John Picozzi - epam.com johnpicozzi
    Emma Horrell - emma-horrell
    MOTW
    Correspondent
    Martin Anderson-Clutz - mandclu.com mandclu
    Brief description: Have you ever wanted to model a multi-step business process on your Drupal site, like a review and approval flow that routes tasks to different people, branches on their decisions, and can even hand steps off to AI? There's a module for that.

    Module name/project name: Maestro

    Brief history How old: created in Jun 2010 by Blaine Lang (blainelang) of Nextide, and is now co-maintained with Randy Kolenko (_randy)
    Versions available: 4.6.0, which works with Drupal 10.3 and 11, and 3.1.4, which also supports Drupal 9.4 through 11

    Maintainership Actively maintained, 4.6.0 came out last week
    Security coverage
    Test coverage
    Documentation: a handbook on drupal.org, plus a series of videos, including AI and agentic examples
    Number of open issues: 189 open issues, 55 of which are bugs, but many date back to the Drupal 7 and 8 branches, and half a dozen issues were closed just last week

    Usage stats: 785 sites

    Module features and usage Maestro's tagline sums it up: if it can be flow-charted, it can be automated with Maestro
    You build a workflow template in a visual drag-and-drop editor, and 4.6 adds a new ReactFlow-based editor as an alternative to the older diagram-js one
    Templates are made of tasks: interactive ones assigned to a user or role, plus non-interactive ones like If, And, Or, can set a process variable, batch functions, and spawn a sub-flow
    That gives you parallel approvals, serial steps, and dynamic routing, for example taking a different path depending on whether someone clicked Accept or Reject
    Each user gets a Task Console listing what's assigned to them, and tasks can be reassigned or delegated
    Under the hood, a background engine Maestro calls the orchestrator and does the work of advancing each process. You run it via a tokenized URL, cron, or drush maestro:orchestrate, and if it isn't running, nothing moves forward, so that's the first thing to set up
    Since 4.1 there's an AI task, built on the AI module, which can return a yes/no or true/false result that the next If task can route on, or store the response in a process variable
    There's also a Tool task for calling Tool API tools directly with no AI involved, and AI tools that let an agent list, start, and check on Maestro workflows
    New in 4.6, a trace view and trace archive let you see a snapshot of the process variables before and after each task, which is great for auditing or debugging
    For editorial and compliance teams, this is a natural fit for multi-stage content review, legal sign-off, or anything where you need a record of who approved what and when
    Maestro also has an ECA integration submodule: a Maestro task can fire an event for ECA to react to, and an ECA action can spawn a new Maestro process. We covered ECA in episodes #375 and #402
    Both ECA and Maestro let you visually model automation without code, but the mechanism is different. ECA reacts to events in the moment: something happens, conditions are checked, actions run, and it's done. Maestro is stateful: each process instance lives on for days or weeks, waiting for people to complete tasks, with the orchestrator advancing it in the background
    We haven't covered FlowDrop yet, but it's the newer option in this space, with an n8n-style graph editor where typed data flows from node to node, and it leans heavily into AI and data pipelines. It does have human-in-the-loop pauses, but Maestro's model is built around people and their task queues, while FlowDrop's is built around moving data through a chain of nodes
    The good news is they can work together: FlowDrop workflows can be published as Tool API tools, which Maestro's Tool task can call. And of course, the Rosetta initiative is all about reducing duplication of effort wherever possible, and making these solutions work seamlessly together
  • Talking Drupal

    Talking Drupal #577 - Off The Cuff 14

    05/11/2026 | 1 h 8 min
    Today we are talking about Drupal 12, Field UI and UX. We'll also cover DruBOM as our module of the week.
    For show notes visit:
    https://www.talkingDrupal.com/577
    Topics
    Drupal 12 Release Prep
    Release Cadence Debate
    Field UI Modal UX Issues
    Button Confusion
    Modal UX Patterns
    Evidence Based UX
    Muscle Memory Traps
    Jakobs Law Explained
    Listener Feedback
    PHP Vulnerability Breakdown
    Security Hygiene Automation
    Vendor Module Support
    Resources
    Drupal 12 Deprecation Status Summary
    Jakob's law Nielson
    Laws of UX
    Hosts
    Nic Laflin - nLighteneddevelopment.com nicxvan
    John Picozzi - epam.com johnpicozzi
    Emma Horrell - emma-horrell
    MOTW
    Correspondent
    Martin Anderson-Clutz - mandclu.com mandclu
    Brief description: Have you ever wanted a full inventory of everything your Drupal site is built from, checked against public security advisories, and exportable as a standard SBOM? There's a module for that.

    Module name/project name: DruBOM - Drupal Bill of Materials (SBOM)

    Brief history How old: created in Oct 2023 by Paolo Mainardi (paolomainardi) of SparkFabrik, and rewritten this fall
    Versions available: 1.0.0-beta4, which works with Drupal 11.3 and 12
    Maintainership
    Actively maintained, latest release and latest commit both just this past Sunday
    Security coverage: opted in, though there's no stable release yet
    Test coverage
    Documentation: an in-depth README, plus separate docs on the advisory sources and on scanning in CI
    Number of open issues: 4 open issues, none of which are bugs, and one of them is the plan for a stable release

    Usage stats: 9 sites

    Module features and usage SBOM stands for software bill of materials, a list of every component a site is built from, with its version, license, and source. Auditors, security teams, and customers are asking for them more and more
    DruBOM takes a snapshot that covers the PHP runtime and its extensions, Composer packages, Drupal modules and themes, asset libraries like jQuery and CKEditor 5, and npm, Yarn, and pnpm lockfiles in your themes and modules
    Anything it can't read shows up as a coverage gap. Gaps are always listed, never hidden
    Advisory checks are opt-in. You can check against drupal.org security advisories, the Packagist advisory database, OSV.dev for npm, and the PHP project's own advisories
    Packages from private repositories are never sent out, and you can list private npm scopes to keep them out of advisory checks too
    Findings that appear in the CISA or ENISA catalogs of known exploited vulnerabilities get flagged and go to the top of the list
    For each finding you can record a decision on whether your site is actually affected, called a VEX statement. A decision applies only to that exact package version and gets confirmed again after each new snapshot
    The admin dashboard under Reports has an interactive dependency map, so you can see which Drupal project brought in some deep npm package
    For CI, drush drubom:check can fail a pipeline when open findings hit a severity threshold, and the export is a standard SPDX 3.0.1 document ready for auditors
    Under the hood, it's all pure PHP now. The original version wrapped the Syft and Grype binaries, and the rewrite dropped them. Running drush updb saves your old reports as files before removing the old settings
    There's also a bin/drubom-scan script that builds the SBOM from the codebase files without running any of the site's code. That's useful when an auditor shouldn't have to trust the site, or after a suspected compromise
    Caveats: you need a private file system, and few security tools read SPDX 3 yet
    Update Status in core is the obvious comparison. Both tell you when something on your site has a security advisory, but Update Status checks drupal.org release data for Drupal projects only. DruBOM builds its inventory from lockfiles and the codebase, so it also covers Composer, npm, libraries, and PHP, and matches advisories against exact versions
  • Talking Drupal

    Talking Drupal #576 - Inside & Outside Drupal AI

    30/10/2026 | 1 h 19 min
    Today we are talking about AI, Drupal, and what's new with guests Dr. Christoph Breidert & Scott Falconer. We'll also cover Drupal AI Demo as our module of the week.
    For show notes visit:
    https://www.talkingDrupal.com/576
    Topics
    Inside vs Outside AI
    Agent Permissions and Scoping
    Drupal Org and GitLab Future
    Outside AI Examples Teaser
    Why CMS Still Matters
    Agent Swarms Expose Data
    Shadow IT And Liability
    CMS As Context Engine
    Content Governance At Scale
    Provenance And Regulation
    MCP And Client Integrations
    Rosetta Sprint Challenges
    Keeping Up With AI
    Resources
    Drupal AI Initiative: introducing Inside AI and Outside AI
    Guests
    Christoph Breidert - 1xINTERNET.com breidert
    Scott Falconer - managing-ai.com scott-falconer
    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 try out all of Drupal's AI features on a realistic site, and then pop the hood to see exactly how they're configured? There's a demo for that.

    Module name/project name: Drupal AI Demo
    https://new.drupal.org/ai/demo

    Brief history How old: project created on Oct 4, 2026 by Christoph Breidert (breidert), a Drupal AI Product Lead, with support from 1xINTERNET, FreelyGive, and Foster Interactive. The demo itself was revealed in the Driesnote at DrupalCon Rotterdam
    The demo runs on Drupal CMS with the Drupal AI modules, running on Drupal 11.4

    Maintainership Looks to be actively maintained
    Documentation: the project has a README that is really clear about what you can try and who has access to what
    Number of open issues: 83, 2 of which are bugs

    Module features and usage The demo is a site for Northmoor University, a fictional coastal university, with realistic programs, news, events, people, and images
    You launch your own copy for free through Drupal Forge. No install, no config, no credit card, and AI credits are included, courtesy of amazee.ai. Each demo instance lasts 30 days
    Features include AI search with cited answers, page generation in Canvas, content review, auto-classification, translation, image validation, image generation and alt text, AI disclosure labels, observability, and an MCP server so tools like Claude can work with the site's content
    Each feature has a step-by-step explainer page in an "AI Features" section, right in the demo site
    The best part is you have full admin access, so every agent, prompt, index, and view is right there to inspect, tweak, or rebuild on your own site
    Lots of the features are public recipes you can use today, like AI Answers, AI Image Alt Text, AI Content Classification, and AI SEO Optimizer
    The big caveat: the ai_demo project is really a placeholder. It's the README plus the issue queue. The actual build (content, theme, demo-specific recipes, deployment) lives in a private GitLab repo for Drupal AI Partners
    So the project's real job is feedback: issue templates for bugs, feature requests, feature-page fixes, and plans, each tagged by demo component. Fixes show up the next time you launch a new copy
    The build was a big community effort: from August to late September, more than 100 contributors, 1,442 commits across 54 projects, and 616 merged MRs, adding roughly 596,000 lines of code
    Back in episode #529 we covered the AI Ecosystem Recipe, and both are about getting the Drupal AI stack in front of you fast. The difference is mechanism: the recipe applies the AI modules to your own site for you to configure, while the demo is a fully-baked, hosted instance with content and prompts already tuned, so you can not only try out but also reverse-engineer a working setup
  • Talking Drupal

    TD Cafe #021 - Meet Tim Sharp

    26/10/2026 | 51 min
    In a Talking Drupal Cafe conversation, Stephen Cross chats with recent Talking Drupal Guest Host, Tim "Tea Sharp," a relatively new Drupal user at Appalachian State University, starting with a light discussion about a 3:00 PM drink before digging into Tim's path from sustainability science and design through nonprofit work, WordPress site building, and finally Drupal in higher ed. Tim describes learning Drupal 7, discovering Views, and then helping his team manually consolidate hundreds of departmental subdomain sites while migrating to Drupal 10 using a product approach and a shared distribution initially built with Lullabot. He discusses training and documentation for non-technical site managers, professional development through DrupalCon Atlanta and Drupal Camp Asheville, interest in Drupal AI for tasks like alt text generation, and aspirations to keep speaking, contribute more, and improve module discoverability and documentation.
    For show notes visit:
    https://www.talkingDrupal.com/cafe021
    Topics
    Finding Talking Drupal
    From Sustainability to Design
    Pandemic Pivot to Web
    WordPress Site Builder Era
    Discovering Drupal at App State
    Drupal 10 Rebuild and Consolidation
    Team Structure and Iteration
    AI in Drupal Workflows
    Upgrade Blockers Cleared
    Aspiring Drupal Speaker
    Raycast Productivity Talk
    Stage Fright Reframed
    Posting Beyond Comfort
    Finding a Username
    Joining Talking Drupal
    Better Module Discovery
    Open Source Burnout Lessons
    Why More TD Cafe
    Final Encouragement
    Tim Sharp
    Tim is a self-taught Web Developer at Appalachian State University in Boone, North Carolina. At App State, he works with a team of developers to support over 300 websites. Tim is passionate about community organizing and recently became a co-organizer of Drupal Camp Asheville.
    Stephen Cross
    Stephen is the founder of Talking Drupal and Drupal Developer.
    Guests
    Tim Sharp - tea-sharp
    Stephen Cross - stephencross
  • Talking Drupal

    Talking Drupal #575 - The Drupal Advocacy Program

    22/10/2026 | 1 h 7 min
    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
Más podcasts de Tecnología
Acerca de Talking Drupal
Talking Drupal is a weekly chat about web design and development by a group of people with one thing in common: We Love Drupal. With hosts John Picozzi, Nic Laflin, and Martin Anderson-Clutz
Sitio web del podcast

Escucha Talking Drupal, sobre la marcha y muchos más podcasts de todo el mundo con la aplicación de radio.es

Descarga la app gratuita: radio.es

  • Añadir radios y podcasts a favoritos
  • Transmisión por Wi-Fi y Bluetooth
  • Carplay & Android Auto compatible
  • Muchas otras funciones de la app