Version control is a non-negotiable part of any serious development project, but widespread adoption of this technique in the world of WordPress has been somewhat spotty to date. While the platform’s core has used Subversion for some time, sites out in the wild are often put together with little or no version control in place. VersionPress arrived on the scene in 2014 with a vision of bringing an integrated WordPress version control solution to the masses. It’s been making steady progress in that direction ever since, and the software’s recent transition into a free open source project marks an interesting inflection point in its development. With version 3.0 of VersionPress hot off the press, now is a great time to review progress to date, introduce its core functionality, and consider the future of the project as a whole. Let’s start with an overview of what it’s trying to achieve. What Problem Is VersionPress Trying to Solve? The VersionPress homepage does a solid job of summing up the basic problem the software is designed to address: WordPress is a cinch to use generally, but a huge number of site owners are carrying out irreversible changes on live
Share This