DDEV Contributor Training Examines Add-on Lifecycle and Workflow Distribution

Contributor training on DDEV add-ons examined how development teams can use add-ons as reusable workflow distribution mechanisms rather than limiting them to service integrations. The session, presented by Randy Fay and Stas Zhuk, covered the complete add-on lifecycle, including setup, testing, publication, and maintenance.

The training session was published on the DDEV blog on 28 April 2026. According to the post, the material explains how add-ons can package hooks, commands, scripts, and configuration into distributable units that help teams standardise operational processes across projects. Examples referenced in the session include automating database sanitisation during imports, installing Git hooks during project startup, and distributing boilerplate configuration files across multiple Drupal environments.

The session also reframed add-ons as infrastructure for sharing institutional workflows between projects and teams. Fay cited a presentation by Bill Seremetis at DrupalDevDays Athens 2026 describing add-ons as “a set of files: hooks + commands + scripts + config — it’s a distribution mechanism.” The example described an agency maintaining a single custom add-on across more than 100 Drupal projects to propagate workflow updates and operational practices consistently.

Practical guidance in the training covered the use of the ddev-addon-template repository for bootstrapping new add-ons. The template includes GitHub Actions continuous integration support and a tests/test.bats suite for automated testing. The session also demonstrated testing add-ons locally through ddev add-on get /path/to/your/addon, validating branch-specific builds using --version, and testing open pull requests with the --pr option.

The post explains that the core installation logic of an add-on is defined in install.yaml, which controls file placement and supports pre_install_actions and post_install_actions for running shell or PHP scripts during installation. Publication guidance in the session notes that repositories tagged with the ddev-get topic are indexed by the DDEV add-on registry, typically appearing within about 24 hours.

Additional references linked from the training include official add-on documentation, registry resources, maintenance guidance, and a technical walkthrough titled “Anatomy of an Advanced DDEV Add-on.” The source material focuses primarily on contributor workflows and operational practices rather than introducing new DDEV platform features or version-specific functionality.