The five Ws of decoupled websites
stevector
This session will introduce why many web teams chose to split the public-facing part of their site from content administration in Drupal. In a decoupled project, back-end and front-end developers can each use their preferred tools to accomplish their work. Decoupled projects have the potential to improve the performance, user experience, and value of public-facing sites.
Teams considering decoupled architectures may face an overwhelming number of choices, concerns over lost functionality from previous monoliths, and unfamiliarity with newer tools. But the reward can be worth the risk when projects are structured in a way to maximize the chance of success.
Learning Objectives
This session will introduce why many web teams chose to split the public-facing part of their site from content administration in Drupal.
Target Audience
This session is for developers and site owners considering decoupled architectures.
Prerequisites
Attendees will get the most out of this session by being familiar with the challenges of Drupal site building and theming.
Track
Development & Coding
Experience Level
Beginner
When & Where
Time:
Wednesday, 15 July, 2020 - 16:15 to 17:00
Room:
Hopin Sessions
If no timezone is set on your profile, time is displayed in UTC.
Update your profile's timezone
