Drupal traditionally handles both content management and front-end rendering as part of its core functionality. Decoupled Drupal, in contrast, uses Drupal only for the content management, and does front-end rendering completely outside the Drupal ecosystem.
You can, and it’s called progressive decoupling -- leveraging parts of Drupal's rendering engine alongside your decoupled applications.
Attendees will leave with an understanding of the following:
The pros and cons of progressively decoupling your site
Leveraging progressively decoupled blocks in Drupal regions
Configuration management between blocks and ReactJS applications
xposing Drupal data to the ReactJS app using RESTful means.
With these tools, intermediate Drupal developers can combine the takeaways from this session into a fantastic experience for both end users and site developers.
Drupal Engineer & Themer at Kanopi Studios
Acquia Certified Developer - Frontend Specialist
I have been working with Drupal since 2010, initially as a Drupal Themer using contrib modules, HTML, CSS, and JS, while over time gaining more backend knowledge of custom module development, Linux, PHP, and GIT. At Kanopi, I work on Drupal support projects on both front- and back-end, developing new features for existing websites, keeping the websites up to date, and fixing bugs in the existing sites.