6. Publishing companies often run
many different sites
Managing content across all sites
becomes complex
Complexity slows you down
BIG PORTFOLIO
7. Organizations work differently with content
Content should be shared across
properties and channels
Content needs be stored carefully
CONTENT IS KING
8. Time to market is crucial
Agility is key
...applies to both your
editorial and engineering teams
FAST MOVING
9. How to build a content platform that
encourage agility and flexibility?
How to cater for different workflows?
How to move content between systems?
CHALLENGES
21. “We are working to expand the definition
and specification to encompass the
growing family of applications that
support HTTP-based, multi-master
replication.”
www.replication.io
22. HTTP API and replication protocol
from CouchDB
Revision and conflict model
is inspired by Git
THE PROTOCOL
25. Provides revision support
for all content entities
Tracks entity revisions like Git
Delete operation creates new revisions
multiversion.module
26. Provides a RESTful JSON API
Endpoints for entities, comparing revisions,
starting/stopping replications etc.
Drush plugin for running replications
relaxed.module