[development] Requiring node revisions

Karthik narakasura at gmail.com
Fri Jun 8 10:31:43 UTC 2007

On 08/06/07, Robert Douglass <rob at robshouse.net> wrote:
> So far, David has convinced me that we should make revisions
> automatically and all the time, and that we should work towards
> simplifying the UPDATE/INSERT workflow for nodes. Doing this, and
> simultaneously working on the interface and workflow for revision
> management, will allow us to become a next generation publishing tool.
> We gain:
> - a very straightforward of saving drafts (1)
> - the equivalent of Angie's revision moderation - in core (2)
> - easier programming API
> - less cluttered UI
> - improved preview workflow (3)

1, 2 and 3 can be implemented just as well without making revisions
mandatory. Easier programming API essentially involves removing an
UPDATE query - no more. Less cluttered UI implies removing a couple of
checkboxes. Derek's excellent ideas for improving the usability of the
'Publishing options' fieldset will mitigate most of them.


More information about the development mailing list