When a decoupled project begins one of the hardest parts that I’ve found is setting up a local environment to simulate all of the necessary components. How will the CMS be served? How will the decoupled front end be displayed? What about the dev server for rendering previews? Can I still call it headless or is decoupled the only appropriate word?
There is a better way! In this session I will be walking you through a setup that I use that incorporates separate servers for a Gatsby static site, a Drupal CMS site, and a development server running on NodeJS. Best of all, because it’s container based, it’s extremely portable and can be reused for multiple projects! Ready to learn more?