Article version control
From Textbook
Overview
What we are talking about here is the ability to go back a version or two to capture a previous version of a given article you write in the event your current one becomes less than desireable for some reason. See this thread as just one example of where such a feature would have been helpful.
As zem points out, the programming is not that hard to do (when you have the time), it's reflecting the changes in the admin interface that can be the bear to wrestle. Hence, most planning at this point should be around the expected workflows and the interface appearance. Getting this down helps the devs do their stuff easier.
Workflows and Mockups
Add em' here!
