Multisite Content Deployments for Media Organizations
0 likes592 views
Dick Olsson discusses the challenges media organizations face in deploying content across multiple sites, emphasizing the need for agility and effective workflow management. He proposes a content platform that supports flexible workflows and bi-directional replication to streamline content operations. The document outlines technical solutions utilizing Drupal, CouchDB, and RESTful APIs to improve content management and reduce time to market.
Multisite Content Deployments for Media Organizations
- 1. MULTISITE CONTENT DEPLOYMENT DICK OLSSON TWITTER: @dickolsson
- 2. Challenges for media organizations Content deployment scenarios A solution Demo AGENDA
- 3. Dick Olsson dixon_ on drupal.org @dickolsson on Twitter Drupal contributor Working at Pfizer Inc. WHO AM I?
- 4. Developer at NodeOne Big media clients around Scandinavia Lead Drupal Developer at Al Jazeera Media Network Live blogging News Programmes MY PAST
- 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
- 12. MERGE WORKFLOW Stage Edit 1 Edit 2 Edit 3 Prod
- 15. Content staging Content sharing Replication Syndication IT'S SORT OF...
- 16. WHAT DO WE WANT FROM A SOLUTION?
- 17. Loosely coupled system Freedom in choosing workflows Freedom in choosing apps and tools WHAT WE WANT ON A HIGH LEVEL
- 19. Revisions everywhere Bi-directional replication Conflict detection REST API WHAT WE WANT ON A TECH LEVEL
- 20. A SOLUTION
- 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
- 23. Drupal CouchDB Angular / PouchDB Hood.ie (or other systems using the protocol) REUSABLE PROTOCOL
- 24. Contrib: Multiversion Relaxed Web Services Core: Serialization Restful Web Services DRUPAL 8
- 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
- 27. Revisions everywhere Bi-directional replication Conflict detection REST API Multiversion + Relaxed = replication.io
- 28. DEMO
- 29. Flexible workflows for any organizational needs Freedom in choosing tools Loosely coupled systems decreases time to market CONCLUSIONS
- 30. THANK YOU! QUESTIONS? DICK OLSSON TWITTER: @dickolsson