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

We've been using this plugin for almost a year to sync the Roots docs written in Markdown to GitHub.
This plugin is regularly maintained and updated, the author is very responsive and open to contributions, and it's reliable.
👍



Helps power the Roots docs

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

Billy Wilcosky

<p>Wiki Blocks lets you add collaborative wiki content with full version control. Users can suggest changes, review version history, and merge updates with proper permission controls.</p>
<h4>Key Features</h4>
<ul>
<li><strong>Gutenberg Block Integration</strong>: Seamlessly adds the wiki block type</li>
<li><strong>Version Control</strong>: Complete history of all changes with user attribution</li>
<li><strong>Collaborative Editing</strong>: Users can suggest changes that are reviewed before acceptance</li>
<li><strong>Permission System</strong>: Granular control over who can suggest, browse, and merge changes</li>
<li><strong>Modern UI</strong>: Clean, responsive interface with modal dialogs</li>
<li><strong>Accessibility</strong>: Full accessibility support with keyboard navigation and screen reader compatibility</li>
</ul>
<h4>How It Works</h4>
<ol>
<li><strong>Add a Wiki Block</strong>: Insert the Wiki Block into any post or page</li>
<li><strong>Initial Content</strong>: Set the initial content that becomes the first version</li>
<li><strong>User Suggestions</strong>: Logged-in users can suggest changes with summaries</li>
<li><strong>Version History</strong>: Browse all versions with excerpts and full content views</li>
<li><strong>Review & Merge</strong>: Administrators or authorized users can merge suggestions into the live version</li>
</ol>
<h4>Permission Levels</h4>
<ul>
<li><strong>Suggest Changes</strong>: Control which user roles can submit suggestions</li>
<li><strong>Browse History</strong>: Manage who can view version history</li>
<li><strong>Merge Versions</strong>: Restrict who can accept changes as the new live version</li>
<li><strong>Login Requirements</strong>: Optionally require login to browse versions</li>
</ul>
<h4>Use Cases</h4>
<ul>
<li><strong>Documentation Sites</strong>: Collaborative documentation with version tracking</li>
<li><strong>Knowledge Bases</strong>: Community-driven content with review process</li>
<li><strong>Policy Pages</strong>: Controlled content updates with approval workflow</li>
<li><strong>Educational Content</strong>: Student contributions with teacher oversight</li>
<li><strong>Team Wikis</strong>: Internal knowledge sharing with permission controls</li>
</ul>
<h3>Translation</h3>
<p>This plugin is translation-ready and includes a POT file for internationalization. To contribute translations:</p>
<ol>
<li>Download the POT file from <code>/languages/wiki-blocks.pot</code></li>
<li>Translate using a tool like Poedit</li>
<li>Save as <code>wiki-blocks-{locale}.po</code> and <code>wiki-blocks-{locale}.mo</code></li>
<li>Submit translations to the plugin repository</li>
</ol>
<h3>Support</h3>
<p>For support, feature requests, or bug reports, please visit the <a href="https://wilcosky.com/contact" rel="nofollow ugc">plugin support page</a>.</p>
<h3>Credits</h3>
<p>Developed by <a href="https://wilcosky.com" rel="nofollow ugc">Billy Wilcosky</a></p>
<p>Built with WordPress best practices and modern web standards.</p>
<h3>License</h3>
<p>This plugin is licensed under the GPL v2 or later.</p>
<h3>Privacy</h3>
<p>Wiki Blocks stores version history and user contributions in your WordPress database. This data includes:</p>
<ul>
<li>Content versions and change summaries</li>
<li>User attribution for changes</li>
<li>Block-specific settings and permissions</li>
</ul>
<p>No data is sent to external servers. All information remains within your WordPress installation.</p>
<h3>Security</h3>
<p>Wiki Blocks follows WordPress security best practices:</p>
<ul>
<li>All user inputs are sanitized and validated</li>
<li>Nonces are used for all AJAX requests</li>
<li>SQL queries use prepared statements</li>
<li>Output is properly escaped</li>
<li>Permission checks are performed on all actions</li>
</ul>
<h3>Performance</h3>
<ul>
<li>Optimized database queries with proper indexing</li>
<li>Efficient asset loading with cache busting</li>
<li>Minimal impact on page load times</li>
<li>Responsive design for all devices</li>
</ul>
<h3>Accessibility</h3>
<ul>
<li>Full keyboard navigation support</li>
<li>Screen reader compatible</li>
<li>High contrast mode support</li>
<li>Reduced motion preferences respected</li>
<li>Semantic HTML structure</li>
<li>ARIA labels and descriptions</li>
</ul>
<h3>Development</h3>
<p>Wiki Blocks is built with:</p>
<ul>
<li>PHP 8.0+ compatibility</li>
<li>WordPress coding standards</li>
<li>Modern JavaScript (ES6+)</li>
<li>Responsive CSS with Flexbox/Grid</li>
<li>Accessibility-first design principles</li>
</ul>
<h3>Roadmap</h3>
<p>Future versions may include:</p>
<ul>
<li>What you suggest</li>
</ul>
<h3>Contributing</h3>
<p>Contributions are welcome! Please:</p>
<ol>
<li>Follow WordPress coding standards</li>
<li>Include proper documentation</li>
<li>Test thoroughly before submitting</li>
<li>Use meaningful commit messages</li>
<li>Respect accessibility guidelines</li>
</ol>
<h3>Donate</h3>
<p>If you find this plugin useful, consider supporting its development:</p>
<ul>
<li><a href="https://buymeacoffee.com/billyw" rel="nofollow ugc">Donate</a></li>
</ul>
<p>Thank you for using Wiki Blocks!</p>


Wiki Blocks

Add wiki Gutenberg blocks to any page/post with version control and user collaboration features.

WordPress GitHub Sync vs Wiki Blocks