Downloaded 38 times
![Source: Leo Laporte’s announcement (4ktch.in/twittv-leo)
“[It’s] faster and easier to create new sites. Web design
styles change faster than high fashion, so it's nice to be
able to update the site without re-doing all the hard
work on the backend.”](https://image.slidesharecdn.com/futureofthecms2015-12-03invisionwebinar-151207160929-lva1-app6891/85/The-future-of-the-CMS-53-320.jpg)
Uploaded byInVision App
The future of the CMS
The document summarizes Todd Ross Nienkerk's presentation on decoupled content management system (CMS) architecture. Some key points: - A decoupled CMS separates the content storage and delivery mechanisms, allowing content to be delivered to various channels through APIs instead of being tied to specific frontends. - Decoupling a CMS makes sense when organizations want to adopt cutting-edge frontend technologies, separate upgrades from redesigns, eliminate tension between design and CMS constraints, or publish content to multiple channels. - Case studies of organizations like TWiT that have moved to a decoupled CMS architecture are discussed, highlighting benefits like faster website updates, easier app development, and encouraging community contributions.
More Related Content
The future of the CMS
- 1.
- 2. InVision webinar |December 3, 2015 The Future of the CMS Decoupled architecture, multiple frontends, and content as a service
- 3. Todd Ross Nienkerk DigitalStrategist and Partner Four Kitchens @toddross todd@fourkitchens.com
- 4. I want youto rethink how we manage, publish, and consume content.
- 5.
- 6.
- 7.
- 8.
- 9.
- 10.
- 11.
- 12.
- 13.
- 14.
- 15.
- 16.
- 17.
- 18. Adopt cutting-edge frontend technologies Decouplingmakes sense when you want to…
- 19. Backend safe repeatable known solutions, expected results Frontend safe repeatable knownsolutions, expected results BORING
- 20. Frontend bleeding-edge tech richest experience highrisk, high reward Backend bleeding-edge tech richest experience high risk, high reward DANGEROUS
- 21. JUST RIGHT Frontend bleeding-edge tech richestexperience high risk, high reward Backend safe repeatable known solutions, expected results
- 22. Separate upgrades from redesigns Decouplingmakes sense when you want to…
- 23. Redesign New CMS UpgradeCMS Redesign Redesign Upgrade CMS Redesign Upgrade CMS Coupled Time
- 24. Upgrade CMS Redesign New CMS Redesign UpgradeCMS Redesign Time Decoupled separates upgrades and redesigns
- 25. Redesign New CMS Angular ReactPolymerBackbone Ember Upgrade CMS Time Decoupled helps you keep pace with frontend tech
- 26. iOS app RokuRedesign NewCMS iOS redesignWeb redesign Upgrade CMS Time Decoupled allows multiple frontends and experiences
- 27. Eliminate tension between adesign and your CMS Decoupling makes sense when you want to…
- 28.
- 29. Two philosophies of designingfor a CMS
- 30. CMS first • Theusers’ needs are important, but there are many ways to satisfy them • The design can be changed to align with the natural behavior of the CMS • The end result is easier and cheaper to maintain
- 31. Design first • Theusers’ needs are paramount and non-negotiable • The design must be executed as-is • This may involve hacking the CMS or creating a complicated codebase, which affects maintainability
- 32. Neither philosophy is wrong,and decoupling can satisfy both
- 33. Centralize your content Decouplingmakes sense when you want to…
- 34.
- 35.
- 36.
- 37.
- 38.
- 39.
- 40.
- 41.
- 42. Publish to manyfrontends and experiences Decoupling makes sense when you want to…
- 43.
- 44.
- 45.
- 46. Integrate multiple backends orservices Decoupling makes sense when you want to…
- 47.
- 48. Make your contenteasily accessible via an API Decoupling makes sense when you want to…
- 49.
- 50.
- 52. Why TWiT wentheadless
- 53. Source: Leo Laporte’sannouncement (4ktch.in/twittv-leo) “[It’s] faster and easier to create new sites. Web design styles change faster than high fashion, so it's nice to be able to update the site without re-doing all the hard work on the backend.”
- 54. Source: Leo Laporte’sannouncement (4ktch.in/twittv-leo) “Having a complete API would make it easier to do apps. The app, just like the website, would have access to everything there is to know about TWiT, in a simple, accessible fashion.”
- 55. Source: Leo Laporte’sannouncement (4ktch.in/twittv-leo) “By making the API public, we encourage members of our audience to create new things, things we might never have thought of. You could even design a website you like better. Abstracting the content from the presentation seems like a big win.”
- 56. Source: Leo Laporte’sannouncement (4ktch.in/twittv-leo) “By keeping Drupal simple and avoiding additional third- party modules, we can make a more secure and reliable backend that will be much easier to upgrade when future versions of Drupal arrive.”
- 57. • TWiT’s casestudy: 4ktch.in/twittv-leo • 4K’s blog post: 4ktch.in/twittv-4k • API documentation: docs.twittv.apiary.io • You can consume content the same way TWiT’s website does! • Saucier: github.com/fourkitchens/saucier • Our open-source Node.js framework for building decoupled Drupal sites
- 58. Decoupling makes sensewhen you want to… • Adopt cutting-edge frontend technologies • Separate upgrades from redesigns • Eliminate tension between a design and your CMS • Centralize your content • Publish to many frontends and experiences • Integrate multiple backends or services • Make your content easily accessible via an API
- 59.
- 60.
- 61. We must designfor experiences, not just devices
- 62. Frontend technologies are accelerating,and CMSs can’t keep pace
- 63. Rise of WMSs(Website Management Systems) and services like Squarespace
- 64. Return of (small)static websites
- 65.
- 66.
- 67. Thank you! All contentin this presentation, except where noted otherwise, is Creative Commons Attribution-ShareAlike 3.0 licensed and copyright Four Kitchens, LLC.
- 68. Credits • The followingicons are from the Noun Project and are licensed Creative Commons BY 3.0: Dog-walking illustration based on an icon by Pavel Nikandrov; Laptop icon by B. Agustín Amenábar Larraín; Tablet icon by Pham Thi Dieu Linh; Smartphone icon by George Agpoon; Media icon by Garrett Knoll; Text icon by Julien Miclo; Chat icon by Dolly Vu; Document icon by Nimal Raj. • Drupal is a registered trademark of Dries Buytaert. • The assets listed above, as well as any assets specifically noted on a slide, are exempt from this presentation’s Creative Commons BY-SA 3.0 license.