On Mon, Oct 1, 2012, Björn Sandberg <
adapti...@gmail.com> wrote:
>I just started looking into django-cms on behalf of a client with a fairly
>large page count (1000+). We are evaluating several different solutions,
>and as django is in common use elsewhere this is looking like a good
>solution. However, a proper workflow for publishing is essential, so until
>the current issues with the toolbar and moderation is resolved, I can't
>really recommend it for live deployment.
Hi Björn.
When we were in your position three or four years ago, moderation was part of our specification.
However, It was quite complicated to get working, so we decided just to do without it for the time being.
Some years later, our site is deployed with 1300+ pages and about 60 different web authors, and as it turns out, we haven't missed that functionality at all.
Now, even if it were easy, we wouldn't bother using it - why introduce a layer that just gets in the way and solves a problem that we don't actually have?
Our web authors work for different departments and office; they're in Groups. Each Group has permission to edit its own Pages ("has permission to edit this page and all descendants") - and that has worked perfectly well so far, with no need for moderation/approval mechanisms.
Obviously this might not work quite so well for a different organisation, but in our case it has been wholly adequate.
I also give a few trusted web editors extra permissions by adding them to a Group called "Lead web editors", just so that the power to cause damage by mistake is more limited, but probably you would want to do that sort of thing anyway.
Daniele