What Comes After Decoupled?
tobby
Decoupling your Drupal backend and frontend makes a lot of sense, but what comes next?
Decoupling, at its core, is all about Separation of Concerns. Let the backend CMS do what it does best; managing content, user authentication for editorial users and admins, and hook into community contributed modules and functionality. Then, let the frontend implementation do what it needs to do; display content and other data, provide a consistent and pleasant user experience, and allow for new design implementations without the need to alter the backend (or vice versa). Have a middleware that ties it all together, and transforms data into content along the way.
...and now you’ve done all this. But what comes next?
This session will explore some of the lesser known advantages of Decoupled Drupal, including:
- Managing the difference between content, data, and live updates
- Assembling cohesive content from multiple CMSes or data APIs; working with multihomed content systems
- How Drupal can place nicely in a larger content/data ecosystem
This session will also cover a list of the hottest technology, tools, and platforms that open the door to new possibilities.