Drupal’s content moderation sucks because…<br />A Drupalcon 2010 lightning talk by:<br />Jeremy Stoller(jstoller)Senior Graphic ArtistExhibit Development DepartmentCalifornia Science Center<br />Fighting for a better user experience in the Drupal issue queue.<br />Christopher Nwani(cnwani)Print & Design ManagerMarketing DepartmentCalifornia Science Center<br />
The Situation<br />Large institutions require all content to go through an approval process—including edits to already published content.<br />Even small sites benefit from the ability to edit published content in a draft state, without un-publishing it first.<br />Many websites (or content types) require more than a two-state publication workflow. <br />
The Problem<br />Drupal only allows for a binary publication state and associates this state with the entire node, making even simple content moderation workflows difficult to implement.<br />
The Solution<br /><ul><li>Replace the binary “Published” state with a multi-state selector.
Associate this state with revisions, rather than nodes.</li></li></ul><li>State Groups<br />
State Groups (associated with content types)<br />