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.

kdiweb

<p>Posts can be grouped in many ways in WordPress but there is no direct version control system. This plugin offers a lightweight solution if you want version control for a group of posts.</p>
<p>To make this work you define a keyword for each version control group you want to create. Then use that keyword as a prefix in the post name of each post in that group. The plugin will sort out the latest post automatically and label the rest as outdated.</p>
<p>It also let’s you have a URL that will always point to the latest post of that version control group. That way you can give out the URL to others and be sure that your visitors will always be viewing the most recent post.</p>
<p>This plugin will automatically:</p>
<ul>
<li>Define if a post is part of a version control group. </li>
<li>Search and locate the latest post by publish date.</li>
<li>Label the older posts of the group as outdated.</li>
</ul>
<p>This is especially practical for bloggers that often revisit older subjects and have to do the linking with the updated posts manually. Or if you are like me and publish material that has versioning applied to it (ex. software) through a blogging platform.</p>
<h3>Usage</h3>
<p>First thing you should do is visit the plugin’s options page (“Settings” -> “Post Version Control”).</p>
<p>There you will find two fields:</p>
<ol>
<li>
<p>The keyword list field, where you enter all the keywords you want to track seperated from each other by a comma and a space “, “. Each of them defines a different version control group.</p>
</li>
<li>
<p>The path for the latest posts URL. By default the path is “/current”. So if we have a keyword named “ajax” the URL: http://www.myblogaddress.com/current/ajax will point to the latest post of the “ajax” group.</p>
</li>
</ol>
<p>To link a post to a version control group of posts all you need to do is enter the keyword of that group as a prefix to the post_name of that post. So in the group “ajax” mentioned earlier all posts in that group should start with the “ajax-” prefix. An example list of that group of posts might be:</p>
<ol>
<li>ajax-first-post</li>
<li>ajax-updated-version</li>
<li>ajax-latest-news</li>
</ol>
<p>..and so on.</p>
<p>The plugin will automatically look through your posts of the same group and label the older ones by inserting an <!– outdated –> tag. This is replaced by the content of “outdated.html” in runtime. This is an example of how you can style your outdated tag. Just insert it along with your other styles:</p>
<p><style></p>
<p>p.outdated{<br />
  border: dashed 1px #f00;<br />
  background: #eee;<br />
  color: #f00;<br />
  text-align: center;<br />
}</p>
<p>p.outdated a {<br />
  color: #f00;<br />
}</p>
<p></style></p>
<p>Uninstalling should be pretty easy too. The only left overs are the <!– outdated: … –> comments in the old posts content which of course are ignored when viewing the webpage. If you don’t mind that you don’t have to do anything else apart from de-activating the plugin through your WordPress administration.</p>
<h3>License</h3>
<p>This work is released under the terms of the GNU General Public License:<br />
http://www.gnu.org/licenses/gpl-2.0.txt</p>


Post Version Control

Automatic version control for posts with the same prefix in the post_name

Version Control Your Content vs Post Version Control