Ben Balter

James DiGioia

<p><em>A WordPress plugin to sync content with a GitHub repository (or Jekyll site)</em></p>
<p><a href="https://scrutinizer-ci.com/g/mAAdhaTTah/wordpress-github-sync/build-status/master" rel="nofollow ugc"></a> <a href="https://scrutinizer-ci.com/g/mAAdhaTTah/wordpress-github-sync/?branch=master" rel="nofollow ugc"></a> <a href="https://scrutinizer-ci.com/g/mAAdhaTTah/wordpress-github-sync/?branch=master" rel="nofollow ugc"></a></p>
<p>Ever wish you could collaboratively author content for your WordPress site (or expose change history publicly and accept pull requests from your readers)?</p>
<p>Looking to tinker with Jekyll, but wish you could use WordPress’s best-of-breed web editing interface instead of Atom? (gasp!)</p>
<p>Well, now you can! Introducing <a href="https://github.com/mAAdhaTTah/wordpress-github-sync" rel="nofollow ugc">WordPress  GitHub Sync</a>!</p>
<h4>WordPress  GitHub Sync does three things:</h4>
<ol>
<li>Allows content publishers to version their content in GitHub, exposing “who made what change when” to readers</li>
<li>Allows readers to submit proposed improvements to WordPress-served content via GitHub’s Pull Request model</li>
<li>Allows non-technical writers to draft and edit a Jekyll site in WordPress’s best-of-breed editing interface</li>
</ol>
<h4>WordPress  GitHub sync might be able to do some other cool things:</h4>
<ul>
<li>Allow teams to collaboratively write and edit posts using GitHub (e.g., pull requests, issues, comments)</li>
<li>Allow you to sync the content of two different WordPress installations via GitHub</li>
<li>Allow you to stage and preview content before “deploying” to your production server</li>
</ul>
<h4>How it works</h4>
<p>The sync action is based on two hooks:</p>
<ol>
<li>A per-post sync fired in response to WordPress’s <code>save_post</code> hook which pushes content to GitHub</li>
<li>A sync of all changed files triggered by GitHub’s <code>push</code> webhook (outbound API call)</li>
</ol>


WordPress  GitHub Sync

We've been using this plugin for almost a year to sync the Roots docs written in Markdown to GitHub.
This plugin is regularly maintained and updated, the author is very responsive and open to contributions, and it's reliable.
👍



Helps power the Roots docs

A WordPress plugin to sync content with a GitHub repository (or Jekyll site)

Vishal Paswan

<p>Version Locker lets you lock specific plugins and themes to their current version. Once locked, they won’t update automatically or manually until you unlock them.</p>
<p>Useful for keeping your site stable when you have customized plugins, client sites, or production environments where you need control over when things update.</p>
<h3>What It Does</h3>
<ul>
<li>Lock individual plugins to prevent updates</li>
<li>Lock individual themes to prevent updates</li>
<li>Block all plugin updates at once (global killswitch)</li>
<li>Block all theme updates at once (global killswitch)</li>
<li>Block WordPress core updates (global killswitch)</li>
<li>Quick toggle locks on/off without page reload</li>
<li>Bulk lock or unlock multiple items</li>
<li>Email alerts when locked items try to update</li>
<li>Search and filter your plugins and themes</li>
<li>Activity log showing who locked what and when</li>
<li>Works on Multisite (each site has its own locks)</li>
</ul>
<h3>How It Works</h3>
<p>The plugin uses WordPress filters to hide update notifications and block update attempts. It doesn’t modify any plugin or theme files.</p>
<h3>Credits</h3>
<p>Thanks to <a href="https://profiles.wordpress.org/nemai/" rel="nofollow ugc">Nemai Naskar</a> for testing and feedback on 1.2.2.</p>


Version Locker

Lock plugin and theme updates to prevent accidental or automatic updates. Simple, secure update control for WordPress.

WordPress GitHub Sync vs Version Locker