As I was finishing up my blog post on the Economics of Claude Code I got to the point where I was ready to post it to the Zivtech.com #Drupal site and then I realized I was going to have to post a whole lot of content on my own, including a bunch of html and image files. I really didn't want to do that, and the "laziness is the mother of invention" thing really works at such an amazing level in this new AI world. So... I had #Codex and #Claude investigate the current Drupal content migration landscape and come up with a better way for me to create all the content on my local Drupal site and then use git to move the site live.
Introducing: Content Packages
From the module description page:
Content Packages provides a Git-friendly workflow for managing selected Drupal content as canonical package files with YAML front matter. It is designed for teams that want important editorial, documentation, demo, or starter content to move through the same review and deployment process as code and configuration.
A package file can be validated, imported into Drupal, exported back from Drupal, and diffed against the current Drupal entity state. Imports upsert by UUID so the same package can be replayed across environments without creating duplicate content.
Use Content Packages when you want:
- Selected content entities stored in Git.
- Content changes reviewed in pull requests.
- Repeatable demo, starter, documentation, or seed content.
- Local-first content authoring that can be replayed on another Drupal environment.
- Content drift detection between Git package files and Drupal entity values.
- Bundle-specific package mappings through package type plugins.
- Selected recursive content graphs exported as reviewable ZIP or JAR archives.