DrupalCamp Atlanta 2016: CMS Future: Decoupled, multichannel, & Content as a Service (Todd Nienkerk)
Content! It’s everywhere! It’s on websites and apps. It’s displayed on computers, televisions, and watches. It’s heard on phones, radios, and screen readers. How can you keep pace with the rapidly changing landscape of content management and publishing?
In this session, you’ll learn how media companies, publishers, universities, and nonprofits are adapting and thriving — all while keeping their content centrally managed and easy to update. We’ll discuss:
How decoupling your CMS — separating the management of content from the presentation of content — makes it easier and cheaper to support new technologies and devices, all while providing a better experience for users, developers, and designers.
How multichannel publishing allows you to distribute your content to any website or device with minimal changes.
Why a content-as-a-service approach will help you collect, manage, and distribute your content from a single, easy-to-manage location — and foster a community of content contributors and app builders.
We’ll close with a couple of Four Kitchens case studies that demonstrate these techniques:
TWiT.tv: How we relaunched This Week in Tech as a decoupled Drupal site with an exposed API that allowed their fanbase to directly access content and build their own apps.
NBC: How we relaunched NBC.com, The Tonight Show with Jimmy Fallon, and Saturday Night Live as decoupled Drupal sites and built an API that shares content across multiple NBC brands, devices, and apps. Plus, a bonus demonstration of our Amazon Echo app: How we made an app that responds only to human speech.
Learn more: http://drupalcampatlanta.com/2016/sessions/future-cms-decoupled-multichannel-and-content-service
In this session, you’ll learn how media companies, publishers, universities, and nonprofits are adapting and thriving — all while keeping their content centrally managed and easy to update. We’ll discuss:
How decoupling your CMS — separating the management of content from the presentation of content — makes it easier and cheaper to support new technologies and devices, all while providing a better experience for users, developers, and designers.
How multichannel publishing allows you to distribute your content to any website or device with minimal changes.
Why a content-as-a-service approach will help you collect, manage, and distribute your content from a single, easy-to-manage location — and foster a community of content contributors and app builders.
We’ll close with a couple of Four Kitchens case studies that demonstrate these techniques:
TWiT.tv: How we relaunched This Week in Tech as a decoupled Drupal site with an exposed API that allowed their fanbase to directly access content and build their own apps.
NBC: How we relaunched NBC.com, The Tonight Show with Jimmy Fallon, and Saturday Night Live as decoupled Drupal sites and built an API that shares content across multiple NBC brands, devices, and apps. Plus, a bonus demonstration of our Amazon Echo app: How we made an app that responds only to human speech.
Learn more: http://drupalcampatlanta.com/2016/sessions/future-cms-decoupled-multichannel-and-content-service