2. Typical Workflow
EVENTS STATES ACTIONS
“Author” creates •Set access control
Restricted to authors and
or updates NEEDS REVIEW editors
article •Notify editors
NEEDS WORK •Notify author
“Editor” updates •Set access control
Visible to world, editable
or reviews PUBLISHED by editors
article •Notify author
Inspired by http://drupal.org/node/156317
7. Transitions
Article is created and needs review
Article is reviewed and needs work
Article is updated and needs review
Article is reviewed and published
Article is created and published immediately
9. Well, it is
It’s less a technical problem than it is a people
problem.
Spend plenty of time planning your workflow.
Keep it as simple as possible.
Planning should involve the people who will
actually use the workflow.
14. What else can you do?
Create views of content needing review or work
Create an “unpublished” state that is only
available when content is published
17. Drupal 6 / 7
Actions and Triggers (events) in core for as of v6
Write your own for version 5, 6 or 7
They are the logical future for many hook-related
methods
Rules module
Hinweis der Redaktion
Before you start...
Sketch out your workflow. Work it out on paper before you implement it.
Who should have access at various states in the flow?
What events should occur as the workflow changes?
If time allows, create the workflow and actions. Otherwise, show the existing.
Take some time to talk these points over with everyone. Really emphasize planning.