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.

Freemius

alex91ckua

The Deployer for Git (and <a href="https://deployer-for-git.com/" rel="nofollow ugc">Deployer for Git Pro</a>) are designed for developers who seek to simplify their website changes deployment. This tool seamlessly connects your WordPress site with various git repositories, enabling real-time updates and automated deployments directly from your commits. This plugin makes it easy — no FTP, no zipping files. Supports all popular services.

Deployer for Git


I had a client that has a bit unusual server setup so we had problems setting up GitHub Actions and making them work.The client has paid for the Pro version since our repositories are private.Everything worked like charm - after pushing my changes I simply went to wp-admin and clicked a button to pull the changes from GitHub.We have 3 repositories on that website.Then I realized that each repository has a special deployment link, so I created GitHub Action to do a GET request to that URL, and that worked like a charm, even behind the basic auth that the website uses.So now our changes get deployed automatically.Definitely a great and simple solution than setting up the pipelines which always cause problems on different platforms.Good job!



EDIT:I found 2 features I'd like to see in the next version:- An option to define the folder nameMy GitHub repository is not named the same as I'd like the plugin's folder to be named.Currently, there's no way to influence that.- The name of the last commit included in the log fileIt's rather hard to quickly confirm that all my last commits got deployed.Currently, it's almost 1am where I am, but the server is set to a different time zone so it's still yesterday.When I checked the logs, the date of the last entry was 1 day behind my current date.The reason I even checked the logs is because the browser has hashed my CSS so I couldn't see all the changes.Having the last commit message would help quickly confirming that everything was deployed properly.


Very useful plugin, works like a charm!


This is a fantastic plugin for theme or plugin development. It has proven to be helpful for our team's workflow. The free version functionality is excellent, but the Pro version is worth the upgade. Also the developer of this plugin is very responsive.


Very helpful for Plugin Development

Install and update plugins (and themes) hosted on your repo hosted on GitHub, Bitbucket, GitLab, or Gitea in a single click.

Static Page Publisher vs Deployer for Git