A recap of Drupal Developer Days 2026, including the release of Config Ignore 3.4.
Last week was the annual Drupal Developer Days, and as always it was a fantastic event.
Look behind the curtains and see how beautiful things happen.
A recap of Drupal Developer Days 2026, including the release of Config Ignore 3.4.
Last week was the annual Drupal Developer Days, and as always it was a fantastic event.
A behind-the-scenes look at how we tackled the challenges of end-to-end testing in a Drupal and Next.js project, using Docker, JSON-RPC, and GitHub Actions to streamline the process.
“We’ll add the tests later”. Most of us have said this at some point in our software development career. But then “later” never arrives.
Ideally you would export the config and commit it in git before and during experimenting with recipes or changing configuration with AI. But core already has an API to create config checkpoints, we can expose it to the UI and let you the site builder use it: Introducing Config Checkpoint UI
Last week I attended the Drupal Dev Days in Leuven and many of the sessions and also conversations in the hallway and the contribution room were about Drupal CMS and AI.
During Drupalcon we sprinted on config contrib modules
The last two weeks the dust settled after an energetic and productive Drupalcon. Now there is a new stable release for all of the three most popular contrib modules Nuvole maintains: Config Filter, Config Split and Config Ignore.
Beware of subtle behavior change with Drupal 9.3+ and Config Split 1.x
For those unfamiliar with it, Config Split is a Drupal module developed by Nuvole, which splits the configuration when it is exported and merges it back together when it is imported. It is useful in many scenarios but best tailored to having some configuration only in some environments (for example the Devel module only in development environments).