Khokan Sardar

<p>WordPress full-site-editing structure — patterns, templates, template parts, global styles, and navigation — lives in the database. Moving <em>some</em> 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.</p>
<p><strong>SiteCargo</strong> 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.</p>
<p>It is currently a <strong>WP-CLI tool</strong> (an admin user interface is on the roadmap).</p>
<h4>How it works</h4>
<ul>
<li><strong>Export</strong> the entity types you choose into a self-describing bundle (a folder containing a manifest, one JSON file per entity, and the referenced media).</li>
<li><strong>Diff</strong> a bundle against a target site to preview exactly what would be created, updated, or left unchanged — without writing anything.</li>
<li><strong>Apply</strong> 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.</li>
</ul>
<h4>Supported entity types</h4>
<ul>
<li>Patterns (<code>wp_block</code>)</li>
<li>Templates (<code>wp_template</code>)</li>
<li>Template parts (<code>wp_template_part</code>)</li>
<li>Global styles (<code>wp_global_styles</code>)</li>
<li>Navigation menus (<code>wp_navigation</code>)</li>
</ul>
<p>Only templates/parts that have been customized in the database are exported; unedited theme-file templates already ship with the theme.</p>
<h4>External services</h4>
<p>This plugin does <strong>not</strong> 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.</p>


SiteCargo

Selectively promote WordPress full-site-editing structure and content between environments — without a full database migration.

Craig Gomes

<p>Classic Menus for Block Themes restores the legacy menu management system, allowing you to create and manage multiple menus alongside block-based WordPress themes. This plugin re-establishes the “Appearance > Menus” page and integrates classic menus with the Site Editor.</p>
<p>Features:<br />
– Manage multiple classic menus alongside block-based navigation.<br />
– Easily switch between block-based and classic menu systems.<br />
– Use custom menu IDs or names for flexibility in displaying menus across the site.</p>
<h3>License</h3>
<p>This plugin is licensed under the GPLv2 or later. For more information, see <a href="https://www.gnu.org/licenses/gpl-2.0.html" rel="nofollow ugc">GPL License</a>.</p>
<h3>Author</h3>
<p>Developed by Pixelvise: https://pixelvise.com</p>


Classic Menus for Block Themes

Short Description: Re-enable the legacy menu management system alongside block-based WordPress themes.

SiteCargo vs Classic Menus for Block Themes