Four Kitchens Presents: Future of the CMS
•
2 gostaram•614 visualizações
In our "Future of the CMS" webinar, Four Kitchens CEO and Co-Founder Todd Ross Nienkerk walks you through the options behind a modern, responsive, design strategy. Watch the video to learn about: * Decoupling your CMS * Multichannel publishing * Content-as-a-service * Future-proofing your project And more!
Recomendados
Recomendados
Mais conteúdo relacionado
Mais procurados
Mais procurados (20)
Destaque
Destaque (15)
Semelhante a Four Kitchens Presents: Future of the CMS
Semelhante a Four Kitchens Presents: Future of the CMS (20)
Mais de Four Kitchens
Mais de Four Kitchens (20)
Último
Último (20)
Four Kitchens Presents: Future of the CMS
- 1. August 10, 2016 The Future of the CMS Decoupled architecture, multiple frontends, and content as a service
- 2. Todd Ross Nienkerk CEO, Co-Founder, and Digital Strategist Four Kitchens @toddross todd@fourkitchens.com
- 3. I want you to rethink how we manage, publish, and consume content.
- 5. When decoupling makes sense Agenda 321
- 7. What “decoupled” means 1 32
- 12. Web Backend
- 16. When decoupling makes sense 31 2
- 17. Adopt cutting-edge frontend technologies Decoupling makes sense when you want to…
- 18. Backend safe repeatable known solutions, expected results Frontend safe repeatable known solutions, expected results BORING
- 19. Frontend bleeding-edge tech richest experience high risk, high reward Backend bleeding-edge tech richest experience high risk, high reward DANGEROUS
- 20. JUST RIGHT Frontend bleeding-edge tech richest experience high risk, high reward Backend safe repeatable known solutions, expected results
- 21. Separate upgrades from redesigns Decoupling makes sense when you want to…
- 22. Redesign New CMS Upgrade CMS Redesign Redesign Upgrade CMS Redesign Upgrade CMS Coupled Time
- 23. Upgrade CMS Redesign New CMS Redesign Upgrade CMS Redesign Time Decoupled separates upgrades and redesigns
- 24. Redesign New CMS Angular React PolymerBackbone Ember Upgrade CMS Time Decoupled helps you keep pace with frontend tech
- 25. iOS app RokuRedesign New CMS iOS redesignWeb redesign Upgrade CMS Time Decoupled allows multiple frontends and experiences
- 26. Eliminate tension between a design and your CMS Decoupling makes sense when you want to…
- 28. Two philosophies of designing for a CMS
- 29. CMS first •The users’ 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
- 30. Design first •The users’ 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
- 31. Neither philosophy is wrong, and decoupling can satisfy both
- 32. Centralize your content Decoupling makes sense when you want to…
- 37. Sara Me
- 38. Sara Me
- 39. Me Sara
- 40. Me Sara
- 41. Publish to many frontends and experiences Decoupling makes sense when you want to…
- 45. Integrate multiple backends or services Decoupling makes sense when you want to…
- 47. Make your content easily accessible via an API Decoupling makes sense when you want to…
- 49. Web Content hub Social media Native apps Feeds Smart TVsXbox Wear- ables Public API Public data Fan site
- 51. Why TWiT went headless
- 52. 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.”
- 53. Source: Leo Laporte’s announcement (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.”
- 54. Source: Leo Laporte’s announcement (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.”
- 55. Source: Leo Laporte’s announcement (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.”
- 56. •TWiT’s case study: 4ktch.in/twittv-leo •4K’s blog post: 4ktch.in/twittv-4k •API documentation: docs.twittv.apiary.io •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
- 57. Decoupling makes sense when 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
- 58. What’s next 1 32
- 60. We must design for experiences, not just devices
- 61. Frontend technologies are accelerating, and CMSs can’t keep pace
- 62. Rise of WMSs (Website Management Systems) and services like Squarespace
- 63. Return of (small) static websites
- 64. Questions?
- 65. Thank you!
- 66. Credits • All content in this presentation, except where noted otherwise and listed below, is Creative Commons Attribution-ShareAlike 3.0 licensed and copyright Four Kitchens, LLC. • The following icons 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.