Here's how Drupal can help in providing and managing the modern digital experience with a Distributed Content Management System.

1. Understanding Distributed
Content Management System

2. Index
● Understanding the concept of distributed content management
system?
● The distribution management of content
● Case 1:Publishing workflows for individual websites
● Case 2:Sharing content out - Centralized content on a distributed web
platform
● Case 3: Sharing content in - Decentralized websites as points of origin
● Case 4: Multichannel brand content
● Case 5: Content delivery to validated audiences

3. Need of a Distributed Content
Management System
● Heading an organization with the complex content creation and
publication needs while, also keeping a track of the content can be a
difficult task.
● Networked storage and exchange of data allow content to be
distributed across a network making the task of content
management all but impossible to deal without a CMS.

4. Understanding the Concept of Distributed
Content Management System?
● Let’s take an example of a news organization of One India News. It
has different regional websites.
● Similar to many media institutions, the website channels are split
into multiple categories (let’s say 5) and each of those categories
further houses a number of sub-sections

6. ● Each of those regional websites are handled by a number of different
editors for each category and channel.
● Assortment of vote cards, topic cards, photo collage - you can see
how quickly the web presence gets complex!

7. Distributed Management of
Content
Management of Distributed Content
Deals with the workflow involved in
the content creation with a
decentralized approach
Deals with existing content from a
variety of sources, involving input
(from other websites/sources), output
(to other websites) or both.
Can eliminate the time and
opportunity for error introduced
when users enter content in
multiple places
Goals are generally around efficiency
and control.
The Distributed Management of Content

8. Use Case 1: Publishing Workflows For
Individual Websites
● Publishing workflows must be tailored not only to the media houses
but to each channel and team that’s in charge of their regional website.
● Content to be published on the homepage of the website will likely
require significantly more oversight than in the humor or offbeat
channel.

9. Use Case 2: Sharing Content Out
Sharing Content Out - Centralized Content On A Distributed Web Platform
● In some cases, it may be easiest to just hyperlink to that content in its
original location; however, consider, a news story of national
importance published on the main website. That story may be
reposted in its entirety in all the other regional websites.
● Copying and pasting becomes a less efficient option when the content
is further distributed - more so when you consider the possibility of
edits and possible unpublishing.

10. By extending the same technologies that allow websites to receive events
from a central calendar, we can enable content managers to publish
events to the calendar from within the same website they usually
manage. (The same content approval and publishing workflow
considerations apply, of course.)
Use Case 3: Sharing Content In
Sharing Content In - Decentralized Websites As Points Of Origin

11. Use Case 4: Multichannel Brand Content
● Single-source content syndication also provides an opportunity
for media companies like One media looking to promote their
brand across multiple mediums.
● Many companies choose to employ standalone, all-in-one news
providers such as ANI, rather than integrating a category for each
of the news providers.

12. “By programmatically receiving the content from a content repository the
organization can eliminate the risk of delayed news and lose the audience.”

13. ● A common approach is to segregate guest editor content into different
regional “portals” - websites that require editor to create accounts and
login to see the information for their country or part of the world.
● To overcome the challenge of validating these accounts, companies
often integrate with an Identity Provider (IdP) such as SAML 2.0 Single
Sign On easy configuration active
support, in Drupal website.
Use Case 5: Content Delivery To Validated
Audiences

14. At the far end of the Distributed Content Management spectrum are systems
that need to publish consistent, controlled content to websites with no
possibility for discrepancies across multiple sites.
The modular design of the Drupal architecture allows both stand
alone and distributed realizations so that the system can be deployed
in a variety of applications.

15. Connect with us, drop a mail at hello@opensenselabs.com or tweet us
@OpenSenseLabs.

16. THANK YOU