Thanks for your input. Mark
On Sun, Aug 24, 2014 at 6:22 PM, Stephen McDonald <[email protected]> wrote: > You might also be interested in this discussion from two years ago, where > I mostly described exactly the same workflow you need, and how it could be > implemented: > > > https://groups.google.com/forum/#!msg/mezzanine-users/4vr3IWT-8UM/ORcbKB_CNeAJ > > Nothing happened on that front though - but the intention to provide this > by default is certainly there, it will probably come to fruition when > someone wants it badly enough to contribute it :-) > > > > > On Mon, Aug 25, 2014 at 11:19 AM, Stephen McDonald <[email protected]> wrote: > >> Nothing like that exists in Mezzanine by default, but have a look at the >> following plugin: >> >> https://github.com/renyi/mezzanine-editor >> >> I've not used it before, so make no claims to its suitability. >> >> >> >> On Mon, Aug 25, 2014 at 11:04 AM, <[email protected]> wrote: >> >>> I am new to Mezzanine, but have worked with the Plone (a Python based >>> cms) a lot, and have developed several django based sites. I am curious if >>> Mezzanine will work for a new project that I am moving from Plone. >>> >>> The project is a US high school online newspaper. We have one unusual >>> requirement that many cms frameworks struggle with. I need a three step >>> workflow process for all content. The typical use case: >>> >>> step 1 - a Content Creator (ie anyone with an account on the site that >>> has been approved) creates a piece of content (article, photo, etc.) and >>> submits that piece of content for review. >>> step 2 - the content is reviewed by a Reviewer - usually a teacher or >>> staff member. If the article is approved by the Reviewer, it is submitted >>> to the Editors for publication, if not it is sent back to the Content >>> Creator >>> step 3 - an Editor, usually a student, reviews the submitted content >>> from the Reviewer, and either publishes the content, or sends it back to >>> the Content Creator for changes. >>> >>> Only published content is available publicly on the site. Of course, all >>> of these submissions and back and fort between the Content Creator, >>> Reviewer, and Editor is documented with comments and date stamps - ie a >>> history is kept. Also, emails and texts are sent to each person(s) in >>> theses roles when something changes, so everyone can react as soon as >>> possible >>> >>> The basic rule is that all content (and edits to that content) must >>> first be reviewed by a Reviewer (ie teacher or staff) before any student >>> sees the submitted content - a school district rule and not my version of >>> Big Brother. >>> >>> I searched the Mezzanine documentation for "workflow" and did not find >>> any references, so I am not sure what it is called in this project. Does >>> Mezzanine have the concept of workflow for content, and can it be easily >>> adjusted for this three step workfow process? >>> >>> Thanks, >>> >>> Mark >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Mezzanine Users" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> >> >> -- >> Stephen McDonald >> http://jupo.org >> > > > > -- > Stephen McDonald > http://jupo.org > > -- > You received this message because you are subscribed to the Google Groups > "Mezzanine Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Mezzanine Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
