heartcoredev

Static Page Publisher allows you to deploy static landing pages to your WordPress site automatically via REST API.
Features: 
* Generate a secure access token for API requests. 
* Upload and deploy a base64-encoded ZIP containing your landing page. 
* Front page is dynamically replaced with uploaded content. 
* Easily view and share your API base URL for integration.
REST API Endpoints: 
* <code>GET /wp-json/static-page-publisher/v1/verify-token</code> — Verify if a token is valid. 
* <code>POST /wp-json/static-page-publisher/v1/update-landing</code> — Upload and deploy a base64-encoded ZIP as the new landing page.
Ideal for teams automating content deployment from Figma, design systems, or CI/CD pipelines.

Static Page Publisher

Deploy static landing pages via REST API and dynamically serve them on your front page.

Daniel Emunot

StageBridge gives you a complete staging workflow without leaving WordPress.
Core Features
<ul>
<li>Clone – Create a staging copy of your production site in a configurable subfolder, such as /staging/, or on a staging subdomain such as staging.example.com.</li>
<li>Sync – Pull current production files and database changes into staging.</li>
<li>Push – Push staging changes back to production with safe conflict protection by default.</li>
<li>Force overwrite – Optional push mode for cases where staging should intentionally replace production changes.</li>
<li>Backups – Create full, database-only, or files-only backups manually or on a schedule.</li>
<li>Restore – Restore from saved backups when you need to roll back.</li>
</ul>
Additional Features
<ul>
<li>Incremental file copying for clone, sync, and push operations.</li>
<li>Conflict-aware push protection for production files and common WordPress content tables.</li>
<li>Compressed file backups to reduce inode usage.</li>
<li>Automatic full safety backups before sync and push, with a per-operation checkbox to skip them when appropriate.</li>
<li>Subfolder or subdomain staging URL modes.</li>
<li>Staging admin bar indicator and frontend staging banner.</li>
<li>Same-tab switch buttons to reduce accidental editing in the wrong environment.</li>
<li>Search/replace for URLs and paths with serialized data support.</li>
<li>Password-protect staging with .htaccess / .htpasswd when supported by the server.</li>
<li>robots.txt handling for staging environments.</li>
<li>Email notifications for clone, sync, push, and backup events.</li>
<li>Live activity logs and persistent completion modals for long-running operations.</li>
<li>Configurable file exclusions for cache, backup, archive, and log files.</li>
<li>Automatic retries for temporary server errors.</li>
<li>Clean uninstall that removes plugin options and custom plugin tables.</li>
</ul>
StageBridge is intended for site owners, maintainers, and developers who need a practical staging workflow from inside WordPress.
<h3>Requirements</h3>
<ul>
<li>WordPress 5.9 or higher</li>
<li>PHP 7.4 or higher</li>
<li>ZipArchive PHP extension for file and full backups</li>
<li>mod_rewrite for optional staging password protection on Apache-compatible servers</li>
<li>Sufficient disk space for staging copies and backups</li>
</ul>
<h3>Privacy</h3>
StageBridge runs locally inside your WordPress installation. It does not send site data to an external service.
The plugin stores settings, logs, backup metadata, operation progress, and staging metadata in the WordPress database. Backup archives and temporary job files are stored on your server under wp-content/uploads/stagebridge/. Email notifications are sent through your WordPress site’s configured mail system.

StageBridge

WordPress staging workflow manager for cloning, syncing, pushing, restoring, and backing up sites from the dashboard.

Static Page Publisher vs StageBridge