Joshuami

A couple months back I wrote about the new recipe unpacking feature in Drupal. The post received a fair bit of attention and was requested as a session at the Bay Area Drupal Camp (BADcamp). I continue to look for ways to leverage AI for something useful, so I decided to ask it to help me create Reveal.js slides.

A client recently needed to audit a number of documents (mostly PDFs) that were unexpectedly appearing in Google search results. The easiest way to identify documents that needed to be archived was to review unused media. Media that was not referenced by field or embedding.

I've picked up a few more bits of knowledge that distilled into these presentations since originally writing this post. Needless to say, I have more than 10 recommendations at this point. To that end, I'm revisiting this important topic as of August 2025.

Tour was deprecated in Drupal 10 and removed in Drupal 11.0. I was fine with that as I had not used it before, but I recently needed a tour for an upcoming launch of an intranet. Tour kinda blew my mind with its easy setup and out of the box look and feel.

With the release of Drupal 11.2, the Recipes feature gets an important new capability. You can now "unpack" recipes after they are run so that your composer.json will have the direct dependencies from the recipe rather than a dependency on the recipe itself.

The Web Content Accessibility Guidelines (WCAG) Version 2.1, Level AA is now the technical standard for state and local governments’ web content and mobile apps within the United States.

Dries post and AI and CMS platforms covers a lot, but I want to take a deeper dive into the two strategic priorities he outlines.

Drupal CMS is filled with modules that are considered best practice for most websites.