Darren Jacoby

<p>Easily configure the WordPress admin interface and application state using a single config file.</p>
<ul>
<li>Simplify the WordPress admin interface.</li>
<li>Place WordPress application state in a config file.</li>
</ul>
<p><a href="https://github.com/darrenjacoby/intervention" rel="nofollow ugc">Intervention on GitHub</a></p>


Intervention

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

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

Intervention vs WordPress GitHub Sync