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.

Mervin Praison

<p><strong>PraisonAI Git Posts</strong> is a revolutionary WordPress plugin that enables file-based content management with Git version control integration. Store your posts, pages, and custom post types as Markdown files while maintaining full WordPress compatibility.</p>
<h4>Key Features</h4>
<ul>
<li><strong>File-Based Content Management</strong> – Store all content as Markdown files</li>
<li><strong>No Database Writes</strong> – Pure read-only approach for content</li>
<li><strong>Git Version Control</strong> – Track changes with full Git integration</li>
<li><strong>Dynamic Post Type Discovery</strong> – Automatically registers post types from directory structure</li>
<li><strong>Custom URL Routing</strong> – Beautiful URLs for any post type (e.g., <code>/recipes/song-name</code>)</li>
<li><strong>YAML Front Matter</strong> – Rich metadata support</li>
<li><strong>Caching System</strong> – Built-in performance optimization</li>
<li><strong>Auto-Update Detection</strong> – Content updates automatically when files change</li>
<li><strong>WordPress Compatible</strong> – Works with themes, plugins, and filters</li>
<li><strong>Developer Friendly</strong> – Clean, extensible architecture</li>
</ul>
<h4>Perfect For</h4>
<ul>
<li>Developers who prefer Git workflows</li>
<li>Teams collaborating on content</li>
<li>Sites requiring version control</li>
<li>Static site generators transitioning to WordPress</li>
<li>Content stored in version control repositories</li>
</ul>
<h4>How It Works</h4>
<ol>
<li>Create a <code>content/</code> directory at your WordPress root</li>
<li>Add Markdown files with YAML front matter</li>
<li>Plugin automatically discovers and loads content</li>
<li>Create new post types by simply adding directories</li>
</ol>
<h4>Example Post</h4>
<p>    `markdown</p>
<p>title: “My Post Title”<br />
slug: “my-post-slug”<br />
author: “admin”<br />
date: “2024-10-31 12:00:00”<br />
status: “publish”<br />
categories:<br />
  – “General”<br />
tags:</p>
<p>  – “example”</p>
<p>Your content here</p>
<p>Write your content in <strong>Markdown</strong> format.<br />
    `</p>
<h4>Requirements</h4>
<ul>
<li>WordPress 5.0 or higher</li>
<li>PHP 7.4 or higher</li>
<li>Git (optional, for version control features)</li>
</ul>
<h3>External Services</h3>
<p>This plugin connects to external services for certain features:</p>
<h4>GitHub API</h4>
<p><strong>What it is:</strong> GitHub’s REST API (https://api.github.com) is used for version control and collaboration features.</p>
<p><strong>When it’s used:</strong> The plugin connects to GitHub API when you:<br />
– Enable GitHub OAuth authentication<br />
– Create or manage pull requests<br />
– Sync content with a GitHub repository<br />
– View pull request details and changes</p>
<p><strong>What data is sent:</strong><br />
– Repository information (owner, name)<br />
– Authentication tokens (OAuth)<br />
– Commit messages and file changes<br />
– Pull request data</p>
<p><strong>User consent:</strong> GitHub features are optional and only activated when you configure GitHub integration in the plugin settings. No data is sent to GitHub unless you explicitly enable and configure GitHub features.</p>
<p><strong>Service information:</strong><br />
– Service provider: GitHub, Inc.<br />
– Terms of service: https://docs.github.com/en/site-policy/github-terms/github-terms-of-service<br />
– Privacy policy: https://docs.github.com/en/site-policy/privacy-policies/github-privacy-statement</p>
<h3>Development</h3>
<ul>
<li>GitHub Repository: https://github.com/MervinPraison/PraisonAI-Git-Posts</li>
<li>Report Issues: https://github.com/MervinPraison/PraisonAI-Git-Posts/issues</li>
<li>Author Website: https://mer.vin</li>
</ul>
<h3>Credits</h3>
<p>Developed by MervinPraison</p>


PraisonAI Git Posts

Load WordPress content from files (Markdown, JSON, YAML) without database writes, with Git-based version control.

Content Version for Git vs PraisonAI Git Posts