Tag Archives: cms

Thoughts on CMS’s as Version Control Systems

I got myself to thinking about versioning content in a content management system.  It seems to me that when it comes down to it versioning of content is integral to the success of long term usability of a CMS.  As any website grows more and more users will need to have access to both create and maintain the content of a website.  But I was thinking that version control can server a better purpose then just helping with workflow.

Let’s apprise one of the weaknesses of the internet, permanence.  After I post this article on my website, the website would seem to be the same website, but looking at it from a different perspective you could consider it to be a “new edition”.  Much like a book, adding new information and reprinting it, you would have a new book as a different edition.  The problem with this analogy is that with books you can take the two editions and compare them side by side, but with a website the old edition is gone forever (kind of).  Comparing two editions of a book can show you exactly what changes have been made, while there is no way of knowing exactly what has changed on a website.

Now this is not entirely true, The Wayback Machine at the Internet Archive, continually scans the internet and saves old copies of information. RSS feeds have been adopted to allow subscribers to keep informed of changes made to the website.  And Wiki’s have sprung up in the attempt to allow content to be kept up to date and versioned.

What I would like to see is a standard for websites that allows the website itself to be versioned.  Make a website capable of being displayed as it was at a specific date and time.  Allow for milestones to be created for the content and the website as a whole.  Imagine having a draggable timeline above the website and being able to change the date you are viewing the website from.  This could even be extended to have a timeline per piece of content.

I am taking a lot of this idea from version control systems like CVS, SVN, or Git, but with one main difference.  Content should also be able to be predated to allow content to show up at future times as well.  Using version control as an embargo system is just one of the many advantages of thinking of a website as a viewpane on a timeline.

How long will it be until we create an internet of self archiving websites.  How long until we stop using technologies such as RSS and The Wayback Machine as stopgaps.  Let’s address this issue before it is too late, if it isn’t already.