Although not visible to site visitors, the Rocket Software Drupal instance makes excellent use of the Workbench suite of modules. The Drupal community may find this interesting because it shows the flexibility and customization that is possible when using Workbench.
By using Workbench, Rocket was able to allow its marketing team members of individual brands/product families to contribute content based on the site’s section, while allowing for the core web team to centralize content publishing responsibilities. This helped Rocket maintain consistent top-down branding throughout all areas of the site, and accommodated brand-specific language and messaging where appropriate. Workbench provides robust content workflow options for Drupal. Out of the box, Drupal provides a set of flags for content, such as whether it is published, belongs on the front page, or is sticky. These are simple on or off indicators. Either content is published or it isn’t, is sticky or it isn’t, is flagged for the front page or it isn’t, etc.
Organizations that use Drupal as their solution, these flags, and specifically the published flag, quickly become incomplete solutions. Organizations need to be able to control who is responsible for what content, draft new versions of content without it being published, and easily view these drafts as well as older versions of the content. Workbench provides all of these solutions through an intuitive mechanism for assigning content to sections, and these sections can be associated with specific roles and users within Drupal. Content moderation can also be split up into multiple roles, such as a role solely for editing content, a role solely for authoring content, and a role solely for moderating content (moving content between published and unpublished states). Workbench quickly converts Drupal into a robust content publishing platform well-equipped for diverse marketing teams such as those at Rocket.
The Drupal community may also be interested to know that the Rocket Software Drupal site uses taxonomies to divide and organize site content across 15 different brands, replacing the need for 15 different sub-sites.