WP Document Revisions — Document Management and Version Control for WordPress
TL;DR: WP Document Revisions is a document management and version control plugin for the popular content management system, WordPress. Think of it as an open-source and more intuitive version of the popular Microsoft collaboration suite, Sharepoint.
WP Document Revisions is a document management and version control plugin. Built for time-sensitive and mission-critical projects, teams can collaboratively edit files of any format — text documents, spreadsheets, images, sheet music… anything — all the while, seamlessly tracking the document’s progress as it moves through your organization’s existing workflow.
WP Document Revisions is three things
- A document management system (DMS), to track, store, and organize files of any format
- A collaboration tool to empower teams to collaboratively draft, edit, and refine documents
- A file hosting solution to publish and securely deliver files to a team, to clients, or to the public
Powerful Collaboration Tools - With great power does not have to come great complexity. Based on a simple philosophy of putting powerful but intuitive tools in the hands of managers and content creators, WP Document Revisions leverages many of the essential WordPress features that, for more than eight years, have been tested and proven across countless industries — posts, attachments, revisions, taxonomies, authentication, and permalinks — to make collaborating on the creation and publication of documents a natural endeavor. Think of it as an open-source and more intuitive version of the popular Microsoft collaboration suite, Sharepoint.
Document History - At each step of the authoring process, WP Document Revisions gives you an instant snapshot of your team’s progress and the document’s history. It even gives you the option to revert back to a previous revision — so don’t fret if you make a mistake — or receive updates on changes to the document right in your favorite feed reader.
Access Control - Each document is given a persistent URL (for example, yourcompany.com/documents/2011/08/TPS-Report.doc) which can be private (securely delivered only to members of your organization), password protected (available only to those you select such as clients or contractors), or public (published and hosted for the world to see). If you catch a typo and upload a new version, that URL will continue to point to the latest version, regardless of how many changes you make.
Enterprise Security - Worried about storing propriety or sensitive information? WP Document Revisions was built from the first line of code with government- and enterprise-grade security in mind. Each file is masked behind an anonymous 128-bit MD5 hash as soon as it touches the server, and requests for files are transparently routed through WordPress’s time-tested URL rewriting, authentication, and permission systems (which can even integrate with existing enterprise active directory or LDAP servers). Need more security? WP Document Revisions allows you to store documents in a folder above the
public_html web root, further ensuring that only those you authorize have access to your work.
Customization - WP Document Revisions recognizes that no two teams are identical, and as a result, molds to your firm’s needs, not the other way around. Need to track additional information associated with a document? Departments, editors, issues, sections, even arbitrary key-value pairs – whatever you can throw at it, it can handle. Development and customization costs are further minimized by its extensive plugin API, and the WordPress Custom Taxonomy Generator makes it easy for even the uninitiated to add custom taxonomies to documents. Need an audit trail to track check-ins and check-outs? User-level permissions based on the document’s state or another custom taxonomy? Support for third-party encryption? Check out the WP Document Revisions Code Cookbook for sample code. Looking for even more advanced control of your workflow? WP Document Revisions will detect the popular workflow plugin Edit Flow, if installed, and will automatically pull Edit Flow’s advanced workflow management tools into WP Document Revisions. Simply put, virtually every aspect of the plugin’s functionality from workflow states to user-level permissions can be fully customized to your team’s unique needs.
Future Proof - Switching costs a concern? WP Document Revisions is built with tomorrow’s uncertainty in mind. Equally at home in an in-house server room as it is in the cloud, moving individual files or entire document repositories in and out of WP Document Revisions is a breeze (history and all). And since the software is open-source, you can easily add tools to automate the process of moving to or integrating with future third-party systems.
- Support for any file type (docs, spreadsheets, images, PDFs — anything!)
- Securely stores unlimited revisions of your business’s essential files
- Provides a full file history in the form of a revision log, accessible via RSS
- Helps you track and organize documents as they move through your organization’s existing workflow
- Each file gets a permanent, authenticated URL that always points to the latest version
- Each revision gets its own unique URL (for example,TPS-Report-revision-3.doc) accessible only to those you deem
- Files are intuitively checked out and locked to prevent revisions from colliding
- Toggle documents between public, private, and password protected with a single mouse click
- Runs in-house or in the cloud
- Secure: filenames are hashed on upload and files are only accessible through WordPress’s proven authentication system
- Can move document upload folder to location outside of web root to further ensure government- and enterprise-grade security
- Documents and Revisions shortcodes, Recently Revised Documents widget
- Multisite and Windows (XAMPP) support
- French and Spanish language support (easily translated to your language)
- Integration with Edit Flow
Features Available via the Code Cookbook
- Audit Trail - creates check in / check out audit trail for all documents
- State Permissions - allows setting user-level permissions based on a custom taxonomy such as workflow state or other document status
- Third Party Encryption - example of how to integrate at rest encryption using third-party tools
- Rename Documents - changes all references to “Documents” in the interface to any label of your choosing
- State Change Notification - how to use document API to allow users to receive notification whenever documents change workflow state
- Bulk Import - how to batch import a directory (or other list) of files as documents
- file type Taxonomy - Adds support to filter by file type
- Track Changes - Autogenerates and appends revision summaries for changes to taxonomies, title, and visibility
- Remove Workflow States - Completely removes Workflow state taxonomy backend and UI
- Change Tracker - Autogenerates and appends revision summaries for changes to taxonomies, title, and visibility
- French - Hubert Campan
- Spanish - TradiArt
- Source Code (GitHub)
- Development version (Build Status)
- Code Cookbook
- User support forums
- Submit a bug/feature request
Questions? Comments? Many may have already been addressed in the WP Document Revisions FAQ, or feel free to simply leave a reply below.
Give it a try today:: Download WP Document Revisions from the WordPress Plugin Repository
WP Document Revisions was developed by a law student and a business student with a grant from Google, and in close coordination with and under the watchful eye of WordPress.org’s lead developers. 1 Special thanks to Jon Cave, Aaron Jorbin, Mitcho Erlewine, and Andrew Nacin for their guidance.
Update (6/12): Comments have been closed in favor of expanded support and discussion options. Additional documentation about the project can now be found in the Project Wiki. If you are interested in joining the project at any level of technical expertise, please see How to Contribute.
Neither relationship should imply a formal endorsement. ↩
If you enjoyed this post, you might also enjoy:
- Twelve tips for growing communities around your open source project
- Why open source
- Why WordPress
- How I re-over-engineered my home network for privacy and security
- Five best practices in open source: external engagement
- Four characteristics of modern collaboration tools
- 19 reasons why technologists don't want to work at your government agency
- Ten ways to make a product great
- 15 rules for communicating at GitHub
- How I over-engineered my home network for privacy and security
- Why everything should have a URL
Ben Balter is Chief of Staff for Security and Engineering at GitHub, the world’s largest software development platform. Previously, as a Staff Technical Program manager for Enterprise and Compliance, Ben managed GitHub’s on-premises and SaaS enterprise offerings, and as the Senior Product Manager overseeing the platform’s Trust and Safety efforts, Ben shipped more than 500 features in support of community management, privacy, compliance, content moderation, product security, platform health, and open source workflows to ensure the GitHub community and platform remained safe, secure, and welcoming for all software developers. Before joining GitHub’s Product team, Ben served as GitHub’s Government Evangelist, leading the efforts to encourage more than 2,000 government organizations across 75 countries to adopt open source philosophies for code, data, and policy development. More about the author →