Talking Drupal

Join Baddy Sonja Breidert, a preconfigured CMS solutions expert, and Dr. Christoph Breidert, a Drupal solutions architect, as they dive into the transformative power of preconfigured CMS solutions for businesses. They discuss building effective Drupal systems, overcoming customization challenges, and selling these solutions to clients. The conversation also touches on the importance of work-life balance and community engagement in technology, making it a treasure trove for developers and business leaders alike.

Today we are talking about Config Actions, The Panels Favorite Drupal Modules, and Drupal Contribution. We'll also cover Transform API as our module of the week. For show notes visit: www.talkingDrupal.com/459 Topics New Config Action: Place Block Favorite Contrib modules Slack channels Preparing for Drupal 11 Drupal events Resources Config Action Place Block Front End Editing Drupal Module Gin Admin Theme Migrate Boost Keysave Navigation Matt Glaman Smart Date Code Blog Post Hosts Nic Laflin - nLighteneddevelopment.com nicxvan John Picozzi - epam.com johnpicozzi Martin Anderson-Clutz - mandclu.com mandclu Baddý Sonja Breidert - 1xINTERNET baddysonja MOTW Correspondent Martin Anderson-Clutz - mandclu.com mandclu Brief description: Have you ever wanted to expose your Drupal site's data as JSON using view modes, formatters, blocks, and more? There's a module for that. Module name/project name: https://www.drupal.org/project/transform_api Transform API Brief history How old: created in Sep 2023 by LupusGr3y, aka Martin Giessing of Denmark Versions available: 1.1.0-beta4 and 1.0.2 versions available, both of which work with Drupal 9 and 10 Maintainership Actively maintained, in fact the latest commit was earlier today Security coverage Documentation: in-depth README and a full user guide Number of open issues: 14 open issues, 3 of which are bugs, but none against the current branch Usage stats: 2 sites Module features and usage After installing Transform API, you should be able to get the JSON for any entities on your site by adding "format=json" as a parameter to the URL To get more fields exposed as JSON, you can configure a Transform mode, using a Field UI configuration very similar to view modes You can also add transform blocks to globally include specific data in all transformed URLs, in the same way you would use normal blocks to show information on your entity pages. The output of transform blocks is segmented into regions, Where Drupal's standard engine produces render arrays that ultimately become HTML, Transform API replaces it with an engine that produces Transform Arrays that will ultimately become JSON Where Drupal's standard JSON:API supports more or less exposes all information as raw data for the front end to format, Transform API allows for more of the formatting to be managed on the back end, where it will use Drupal's standard caching mechanisms, permission-based access, and more Transform API also supports lazy transformers, which are callbacks that will be called after caching but before the JSON response is sent You can also use alter hooks to manipulate the transformed data

Guest John Albin Wilkins discusses integrating Next.js with Drupal, covering topics like server requirements, content updates, server-side rendering, performance, and editorial experiences. The podcast explores challenges in decoupled Drupal, GraphQL usage, evolution of Layout Builder, responsive images, and a humorous anecdote about a trivial patch award in Drupal development.

Join Alexander Varwijk as he discusses Drupal architecture, common site building questions, and solutions with Drupal. Topics include starting a new site or feature, extending vs forking, contributing new modules, and preferences for Headless. Learn about the Revolt event loop, managing update hook differences, module categorization, real-time chat integration, client preferences, and King Dutch's online community contributions.

Randy Fay and Andrew Berry discuss DDEV's rapid growth and sustainability. They cover funding, future plans, and how to get involved. The podcast explores DDEV's features, challenges, and the importance of community participation in maintaining DDEV.

AI expert Mike Miles discusses top 5 AI uses for Drupal: idea generation, code debugging, content generation; emphasizes code review and skill evaluation. MIT Sloan's approach to content generation, future of AI in Drupal as a supportive tool, and AI tools in development explained.

Brian Perry, Drupal API Client expert, discusses the benefits of Drupal API Client, its role in normalizing JSON API, agnosticism in JS frameworks, and the use of TypeScript. They touch on creating instances, module applicability, potential core integration, and the roadmap. The episode also covers the Iconify Icons module and its features for adding icons to Drupal sites.

Guest Josh Miller from Urban Institute discusses their Drupal usage, challenges with AI bots, technical hosting solutions, and nonprofit innovations. They explore Access Unpublished module, local development tools, and Drupal GovCon. Urban Institute focuses on data visualization and interactive experiences.

Delve into web design and development with a focus on StarShot and Experience Builder. Explore the evolution of Drupal, the Default Content Module, and transitioning to CI CD pipelines. Learn about empowering site builders, enhancing user-friendliness, and balancing code purity. Discover the impact of Star Shot on Drupal Core and potential inclusion of Experience Builder. Revolutionize site launches with Star Shot and emphasize community engagement.

Today we are talking about Drupal Marketing with version numbers, what competitors are doing, and Learning to Just Saying Drupal with guest Ivan Stegic. We'll also cover Trash as our module of the week. For show notes visit: www.talkingDrupal.com/451 Topics What is the premise of Just Say Drupal Why do you think it is important to drop the version number Where do you suggest we drop verison numbers In sales, if you don't mention version, how do you talk to clients Why could using version numbers be detrimental What do you suggest we call Drupal 7 Have you spoken to the Drupal marketing team At Drupalcon they unveiled a new Brand Guide What do you think of Drupal Starshot Where do we go from here Resources Ten7 Blog - Just Say Drupal https://ten7.com/blog/post/just-say-drupal https://justsaydrupal.org Drupal issue Drupal Brand Guide Drupal.org Issue Starshot https://www.drupal.org/starshot https://www.hojtsy.hu/blog/2024-may-13/drupal-11-deep-dive-watch-recording-present-your-own-free-slides https://herchel.com/articles/thoughts-drupals-new-starshot-initiative https://mglaman.dev/blog/starshot-recipe-cook-ambitious-drupal-applications Drupal tooling Guests Ivan Stegic - ten7.com ivanstegic Hosts Nic Laflin - nLighteneddevelopment.com nicxvan John Picozzi - epam.com johnpicozzi Matthew Grasmick - grasmash MOTW Correspondent Martin Anderson-Clutz - mandclu.com mandclu Brief description: Have you ever wanted your Drupal site to have a trash bin for content entities, so they wouldn't be immediately deleted from the database? There's a module for that Module name/project name: Trash Brief history How old: created in Feb 2008 by rötzi, though recent releases are by Andrei Mateescu (mah-teh-sku) (amateescu) of Tag1 Versions available: 3.0.3, compatible with Drupal 9, 10, and 11 Maintainership Actively maintained, release less than two months old Security coverage Test coverage Number of open issues: 7 open issues, 3 of which are bugs against the current branch Usage stats: 1899 sites Module features and usage Once the module is installed, you choose which entity types on your site should use the new trash storage For all the configured entities, deleting a piece of content moves it into the new trash storage, along with a timestamp set for when it went into the trash You can configure whether or not the trash should be automatically purged on a periodic basis, and if so how often that should happen It seems that there are some entities for which the Trash module currently excludes its functionality, such as users, comments, taxonomy terms, and so on. The note in the code indicates that more testing is needed, so any of our listeners who wants to trash entities for any of these types could try out patching the TrashSettingsFormand on a local copy and provide feedback based on how things work The ability to restore deleted content is a request I've heard a number of times, so this could be a really useful module for making Drupal work in ways that certain teams expect