Drupal Content Packages Module Introduces Git-Based Editorial Workflow

New tooling in the Drupal ecosystem introduces a Git-based approach to managing structured content through a module called Content Packages, designed to align editorial workflows with code and configuration deployment processes.

The module was developed following an implementation experiment by Alex Urevick-Ackelsberg, CEO of Zivtech, who described challenges in manually publishing large volumes of content, including HTML and media assets, to a Drupal site. The approach explored AI-assisted tools to analyse existing content migration workflows and propose an alternative based on local content creation and Git-driven deployment.

Content Packages enables selected Drupal content to be stored as canonical package files with YAML front matter. These files can be version-controlled in Git, reviewed through pull requests, and deployed across environments using a repeatable workflow. The system supports validation, import, export, and comparison of package files against Drupal entity states, with UUID-based upsert operations preventing duplication across environments.

Additional features include diffing package files against live content, detecting drift between stored packages and entity values, and exporting content sets with recursive references. The module also supports packaging content and associated assets into ZIP or JAR archives with integrity metadata such as SHA-256 hashes and dependency graphs.

The module is designed for managing selected content rather than full-site synchronisation. It does not replace existing Drupal solutions such as migration frameworks or broad entity synchronisation tools, instead focusing on controlled, reviewable content sets that move through the same lifecycle as code.

Technical requirements include PHP libraries for Markdown processing and archive handling, along with optional integrations for modules such as Media and Paragraphs. The project is currently in an alpha release stage and is not covered by Drupal’s security advisory policy.

The approach reflects a broader shift toward local-first content authoring and structured deployment workflows in Drupal environments, particularly for teams managing repeatable or version-controlled content across multiple environments.

Further details and documentation are available on the project page.