Our clients often come to Drupal with expectations about the features of a content management system (CMS). In many cases, Drupal handles the features they expect. However, not all editorial tools are a part of Drupal Core, and Drupal has addressed these tools with various contributed modules. As a result, Drupal’s editorial space generally lacks a consistent workflow and interface.
At DrupalCON San Francisco, Palantir.net outlined the opportunities we saw for improving content management workflow in Drupal 7. This presentation introduces the outcomes of that work.
Workbench incorporates contributed modules and has some new features of its own:
- [ ] Hierarchical permission inheritance by “Sections” not just content types
- [ ] Extensible workflow states
- [ ] Single repository for media management
- [ ] Modify live content without publishing changes immediately
Workbench provides a unified interface for managing content. In effect, Workbench hides Drupal from you and makes content management about your institution and your website, not about Drupal.
This module suite is expected to be released by the time DrupalCon starts on March 7th.
Video at archive.org.
People who maintain sites for large organizations and decentralize control of content will learn how Workbench can improve their control over sections of the site and who is responsible for each section.
People who maintain any site who want a simplified user experience for managing content will see how Workbench provides a user interface that is consistent and easy to access.