maksonlee

<p>Content Version for Git stores editable WordPress content snapshots in a configured GitHub repository. It versions posts, pages, terms, and optionally media metadata and original media files. Editors can preview, diff, and restore previous versions from the WordPress admin.</p>
<p>The plugin writes and reads Git objects through the GitHub API. It does not keep a local Git repository and does not call the git CLI.</p>
<p>Features include:</p>
<ul>
<li>Automatic Git versions for normal post and page saves.</li>
<li>Side-by-side content diffs and field diffs.</li>
<li>Full restore and content-only restore modes.</li>
<li>Deleted Resources view for posts, pages, and tracked media.</li>
<li>Restore deleted posts/pages as new drafts and deleted media as new attachments.</li>
<li>Optional media metadata and file tracking.</li>
<li>Manual import of existing posts, pages, and media.</li>
<li>Version store dashboard with branch, latest commit, tracked file count, and GitHub version store status.</li>
<li>Direct GitHub API commits without a local Git worktree.</li>
</ul>
<h3>External Services</h3>
<p>This plugin connects to GitHub when the “Enable GitHub version store” setting is enabled and a repository URL, branch, and personal access token are configured.</p>
<p>When enabled, the plugin writes Git commits directly to the configured GitHub repository using the GitHub API. Commit data may include post/page content, metadata, term references, media metadata, and media files if media tracking is enabled.</p>
<p>The GitHub version store is disabled by default. No data is sent to GitHub unless a site administrator enables and configures it. Without the GitHub version store, this plugin does not keep durable local Git versions. GitHub’s terms and privacy policy apply:</p>
<ul>
<li>https://docs.github.com/en/site-policy/github-terms/github-terms-of-service</li>
<li>https://docs.github.com/en/site-policy/privacy-policies/github-privacy-statement</li>
</ul>


Content Version for Git

GitHub-backed version history for WordPress posts, pages, and media.

litefeel

<p><em>A WordPress plugin to allow you writing on GitHub (or Jekyll site).</em></p>
<p>Some code for this plugin comes from <a href="https://github.com/mAAdhaTTah/wordpress-github-sync" rel="nofollow ugc">WordPress GitHub Sync</a>, thanks.</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>Well, now you can! Introducing <a href="https://github.com/litefeel/writing-on-github" rel="nofollow ugc">Writing On GitHub</a>!</p>
<h4>Writing On GitHub does three things:</h4>
<ol>
<li>Allows content publishers to version their content in GitHub</li>
<li>Allows readers to submit proposed improvements to WordPress-served content via GitHub’s Pull Request model</li>
</ol>
<h4>Writing On GitHub 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>


Writing On GitHub

Awesome plugin

A WordPress plugin to allow you writing on GitHub (or Jekyll site).

Content Version for Git vs Writing On GitHub