Sisanu

<p>If you use WordPress MS, the plugin gives you the possibility to copy the content and all related to a specific site created in the WPMS and deploy all that on another application that uses also WordPress MS. This plugin is for site admins (super administrators) of WPMS sites.</p>
<p>The purpose of this plug-in is to allow you to make changes in a “staging” environment and once you decide the site is ready to be published you can choose to deploy it to a “live” environment. Please note that this plugin has to be installed and activated on both application in order to have the deployment functionality.</p>
<p>Bug report, please go here: </p>
<p>http://www.phpcoder.ro/contact.php</p>
<h3>License</h3>
<p>This program is distributed in the hope that it will be useful, but<br />
WITHOUT ANY WARRANTY; without even the implied warranty of<br />
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.</p>
<h3>Version history</h3>
<p>0.1-alfa First testing alpha version.<br />
0.2-beta Beta version.</p>


Sisanu Site Deployment

This plugin adds an option page "PHP Site Deployment" under your admin menu. The plugin gives you the possibility to copy the content and al …

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.

Sisanu Site Deployment vs SiteCargo