Haris Amjed

<p>The Version Control Your Content plugin provides an alternative to the native WP <a href="https://wordpress.org/documentation/article/revisions/" rel="ugc">Revisions</a> feature using Git services.</p>
<h4>Requirements</h4>
<ul>
<li>A GitHub account. If you don’t have one, you can create one <a href="https://github.com/join" rel="nofollow ugc">here</a>.</li>
<li>A GitHub private repository. If you don’t have one, you can create one <a href="https://github.com/new" rel="nofollow ugc">here</a>.</li>
<li>(Optional but highly recommended) A GitHub fine-grained personal access token. If you don’t have one, you can create one <a href="https://github.com/settings/tokens/new" rel="nofollow ugc">here</a>.</li>
</ul>
<p>This plugin provides an option for version control in the following places for now:</p>
<ol>
<li>Block Editor (Gutenberg)</li>
<li>Classic Editor</li>
<li>Additional CSS in the Customizer</li>
<li>Default Settings pages in WP Admin</li>
</ol>
<p>On all supported pages, you will see a “Version Control” box, and you can activate or deactivate it for that page. It will also show you the real-time GitHub API usage in the top admin bar.</p>
<p>This solution will put minimal load on your server because there will be no database entries, no complex SQL operations, and only simple JavaScript-based API calls to external Git services.</p>
<h4>How it works behind the scenes?</h4>
<ol>
<li>When you submit any HTML form, such as saving a post, it captures the form data via JavaScript before sending it to the server backend.</li>
<li>It sanitizes the data and converts it to JSON format (if needed).</li>
<li>It sends that JSON or HTML data to your Git repository via a commit.</li>
<li>In this way, all your changes will be new commits in your Git repo in related JSON or HTML files.</li>
<li>In the commits box, a list of all commits will be shown. It will also provide an option to view the changes or revert to that version.</li>
</ol>
<h4>Planned Upcoming Features</h4>
<p>Currently, I have developed it for three views as described above, and the following features will be added in the future:</p>
<ul>
<li>Integration with page builders like Elementor, Divi, Beaver Builder, WPBakery, etc.</li>
<li>Integration with WooCommerce</li>
<li>Integration with BuddyPress</li>
<li>Integration with bbPress</li>
<li>Integration with WPML, etc.</li>
</ul>


Version Control Your Content

Provides an alternative to the native WP Revisions feature using Git services. Also works for Additional CSS and wp-admin Settings pages.

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)

Version Control Your Content vs WordPress GitHub Sync