Download as PDF, PPTX
Uploaded byPantheon
Content as a Service: What to Know About Decoupled CMS
The webinar discusses the advantages of decoupled Content Management Systems (CMS) and features case studies from Twit.tv, Four Kitchens, and Pixo. It highlights the transition from monolithic architectures to decoupled systems, emphasizing better workflows, easier upgrades, and the ability to use a mix of modern development tools. The presentations underscore how decoupling empowers teams by allowing independent workstreams and enhancing the design process.
More Related Content
Similar to Content as a Service: What to Know About Decoupled CMS
Content as a Service: What to Know About Decoupled CMS
- 1. CONTENT AS ASERVICE: WHAT TO KNOW ABOUT DECOUPLED CMS PANTHEON WEBINAR WITH FOUR KITCHENS AND PIXO
- 2.
- 3. Pantheon.io 3 Speakers Josh Koenig Co-Founder& Head of Developer Experience Pantheon Mike Minecki Director of Technology Four Kitchens Brandon Bowersox- Johnson Chief Technology Strategist Pixo
- 4. Pantheon.io 4 Agenda ‣Why DecoupledCMS? Josh Koenig, Pantheon ‣Case Study #1: Mike Minecki, Four Kitchens ‣Case Study #2: Brandon Bowersox-Johnson, Pixo ‣Discussion and Q&A
- 5.
- 6. Pantheon.io 6 Monolith vs.Decoupled Monolith Templates & Themes Display Logic Editorial UI Admin UI VS. Decoupled
- 7. Pantheon.io Decoupled 7 • CMS JS App User Request Hybrid • CMS Single Page App User Request SinglePage • CMS Native Mobile App User Request Native • Decoupled Front End CMS User Request CMS2 CMS
- 8.
- 9. Pantheon.io 9 Speakers Brandon Bowersox- Johnson ChiefTechnology Strategist Pixo
- 10. June 11, 2015 TWiT.tv Drupal& Node.js = Content as a Service
- 11. Agenda • About us •About TWiT.tv • Why Content as a Service? • Architecture • Workflow • Final Thoughts
- 12. We make BIGwebsites fourkitchens.com @fourkitchens
- 13. The TWiT.tv NetcastNetwork with Leo Laporte features the #1 ranked technology podcast This Week in Tech, along with over 20 other top-ranked online shows.
- 17. Why TWiT.tv wanteda Content as a Service architecture
- 18. Decouple upgrades Cost ofDrupal upgrade stifled redesign attempts
- 19. Better API forapp developers Active community of developers currently using RSS feeds.
- 20. Exiting and proven technology Adesire to innovate and iterate.
- 21.
- 22. Architecture • Node.js • Drupal7 • Custom encoding server (named Elroy) • Cachefly for static assets.
- 23. Architecture walkthrough Publishing andviewing a podcast on the new TWiT.tv
- 24.
- 25.
- 26.
- 27.
- 28.
- 29.
- 30.
- 31.
- 32.
- 33.
- 34.
- 35.
- 36.
- 37.
- 38.
- 39. Drupal architecture • Drupal7 • RESTful Module • Very little custom Drupal code
- 40. Node.js architecture • Saucier- Our headless framework • Node.js • Express for routing • Dust templates • Redis for caching
- 41.
- 42. API mockups Get frontend and back end teams working early
- 43.
- 44.
- 45. Built in APIconsole
- 46.
- 47. Acts as aproxy
- 48. Design in thebrowser A dream come true
- 49.
- 50.
- 51. Design in thebrowser
- 52. Design in thebrowser • Responsive loves design in the browser • Workflow with Drupal is always clunky • Decoupling made the process seamless
- 53.
- 54.
- 55. Decoupled empowerment • Redesignswon’t require a CMS upgrade • Independent work streams • Best of breed tools • More natural modern design process
- 56.
- 57.
- 58.
- 59.
- 60.
- 61.
- 62.
- 63.
- 64.
- 65.
- 66. Old Way • CMStheming • Limited team • Develop in CMS • Costly upgrades • Choose the best FE tools • FE devs ≠ CMS devs • Start without a CMS • Simpler CMS upgrades Goals
- 67.
- 68.
- 69. cms.uic.ed u Site uic.edu Content as aService CMS JSON
- 70.
- 71. Pattern Lab • Atomicdesign • Test drive responsive layouts • Assemble elements into pages • More at patternlab.io
- 74. Benefits • Able topick and add best tools • Front end team starts right away • Test drive components
- 75.
- 76. Decoupled WordPress • Minimalcustom code • Component-based content structure • WordPress JSON API
- 79. Benefits • Less-customized CMSeasier to upgrade • More focused authoring experience • Content available as JSON
- 80. CMS + PatternLab Outpost
- 81. Outpost • Lightweight PHPapp • Feeds JSON from WordPress or Drupal into Pattern Lab templates • More at getoutpost.org
- 82. Outpost 1. Handles visitorrequests (Symfony HTTP...) 2. Fetches JSON content (Guzzl) 3. Caches responses (Stash) 4. Dev tools for logging, debugging
- 83. Content Objects • FeedJSON into PatternLab • Encapsulate JSON into objects
- 86.
- 87. Result • Fell inlove with our CMS again • Built great FE with the best tools • FE dev team and timeline not tied to CMS • Unleashed content authoring • Easier upgrades over time
- 88.
- 89.
- 90.