fidzu : cms

Every login on a BOA account is a key of one kind, and the ring holds six of them: your own panel login and your oN.ftp shell open everything; a colleague's login to the Ægir panel holds one of two roles, Client, which can do with a site what you can short of deleting it, backups and the admin login link included, or the new Site operator, the valet key of the control panel, which verifies, clones, migrates, flushes caches and runs updates on the Client's Drupal and Backdrop sites and cannot reach a copy of the database, the admin account or the delete button, not even from the Backups tab; and a colleague's shell login comes as one of two, files and themes, or whole codebases with Composer and Drush. Every task records the login which queued it. Drush is the database, so the codebase key belongs with the Client role and never beside a site operator, and the roles are a list shipped with BOA, re-asserted every night, readable to the permission on one page.

18 Sep 2026 12:36am GMT

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.

17 Sep 2026 6:00pm GMT

Prices, specifications and proof buried in body copy are hard to compare, filter or reuse across pages, feeds and AI answers.

Drupal content modeling stores those facts as fields, connects related records with entity references and leaves prose for explanation. Maciej Lukianski walks through buyer-question audits, product and service field tables, migration stages and coverage reports that turn one edit into every output.

17 Sep 2026 1:18pm GMT