Enabling Collaborative Content Reviews
Enabling Collaborative Content Reviews
Efficiently manage editorial workflows so content and campaigns are delivered consistently within corporate branding standards to drive loyalty with customers over time.
Drupal for Web Experience Management: Enabling Collaborative Content Reviews.
Drupal provides the most simple, yet powerful platform for Digital Marketers to create meaningful and impactful Web Experiences for their customers. Creating these experiences often requires extensive collaboration through review and approval workflows across disparate marketing functions and even external partners. Web Experience Management solutions powered by Drupal empower Digital Marketing organizations to efficiently manage editorial workflows so that content and campaigns are delivered consistently within marketing and corporate branding standards that maintain loyalty and affinity with customers over time.
Web Experience Management on Drupal provides robust content staging workflow capabilities based on persona offering the fastest learning curve for new users which translates into a faster time to market for new content, campaigns, or even new product launches.
When we log in as a Staff Writer, she has access to do certain things such as create content, but not necessarily the ability to push it live. The content first needs to be approved by an editor or marketing to approve ahead of time.
Here we go into the writers workbench view where she has certain items available. She can create particular content types like blogs, questionnaires and even polls. First, let’s select some content and create a news item. We enter a title for the new news item and set the language to English.
Now we copy write new material into the WYSIWIG editor. While the writer is entering this new content, on the right side of the page you can see new Semantic content recommendations for a 3rd party service appear in real time. This includes related images from public or private sources or even articles or links to embed. The writer hits apply all and now the content is hyperlinked to additional content sources for the audience. Similarly, it can also auto suggest keyword tags.
The writer can then easily upload rich media by choosing a document from their desktop. Here they pull up a logo, which has been optimized and resized with built in digital asset management capabilities. We can also add a note for the editor or optimize SEO easily by embedding an alternate page title.
The writer now saves a draft and we see a preview here in light pink indicating that the content has not yet been published. However, the Draft preview is shown just as end-users will see it when published, but it’s only visible to users with the appropriate roles on their account. At the top of the page is a status tool bar indicating this is still draft content. The writer can then flag this draft as review required eventhough they can’t publish it directly themselves. So we click “needs review” and a notification is automatically sent to the next person in the chain such as another editor, brand manager, or marketing reviewer.
Now we switch to a different user who happens to have multiple roles applied. If we look at his profile, we can see he is an editor, administrator, and publisher. He therefore has additional permissions on the toolbar above as well as a different set of tabs on the content workbench including a needs review tab. In this case, Drupal could trigger email notifications, or tweets, or even chat messages to let him know that he has content to review.
Once notified, if he trusts the writer implicitly, he can just click publish without a review. But he wants to take a quick look, and sees an edit he wants to make. By clicking on edit draft, and make some changes to the text itself or any other edits.
Since this users role also includes editor rights, he has additional content controls. He could include it as part of the XML sitemap, turn comments on or off, schedule a publication date, or even set a page alias for advanced SEO parameters. He could also add additional keywords.
Notice the background is still pink indicating the page still hasn’t been published. Now that the editor has created a new revision, it’s easy to see the changes between his version and the writers version, indicated here in green. He could then set it to published or or go for additional review as the next step in the workflow. He can also look at the moderation history, so now that a change has been created to the content, it’s easy to go back and view or revert back to the older content as required. The pink background indicates this version is unpublished. When he decides to publish the new version, the background changes from pink to green indicating its gone live on the site.
Thanks for viewing this video on Drupal for Web Experience Management: Enabling Collaborative Content Reviews. Get in touch with Acquia today to learn more about our hosting, support, training, and other value added cloud services. And be sure to view our additional videos on Drupal for Web Experience Management.