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.

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

Wiki Blocks vs Post Version Control