SiteCargo

WordPress full-site-editing structure — patterns, templates, template parts, global styles, and navigation — lives in the database. Moving some of it from staging to production today means either a full database sync (which is destructive to production-only data like orders, users, and form entries) or tedious manual copy-paste.

SiteCargo packs exactly what you choose into a portable, reviewable bundle and applies it to another site with stable identity, ID remapping, and media handling — never touching the data you didn’t select.

It is currently a WP-CLI tool (an admin user interface is on the roadmap).

How it works

• Export the entity types you choose into a self-describing bundle (a folder containing a manifest, one JSON file per entity, and the referenced media).
• Diff a bundle against a target site to preview exactly what would be created, updated, or left unchanged — without writing anything.
• Apply the bundle to the target: standalone posts (patterns, navigation) are matched by a stable identifier so re-applying updates the same item instead of duplicating it; templates, parts, and global styles are matched by theme and slug. Numeric IDs baked into block markup (images, reusable-block and navigation references) are remapped to the target site, and referenced media is imported and de-duplicated by content hash.

Supported entity types

• Patterns (wp_block)
• Templates (wp_template)
• Template parts (wp_template_part)
• Global styles (wp_global_styles)
• Navigation menus (wp_navigation)

Only templates/parts that have been customized in the database are exported; unedited theme-file templates already ship with the theme.

External services

This plugin does not connect to any external service, send any data off-site, or phone home. Bundles are plain files on your own server that you move between environments however you like.