Managing the Risks of Going Headless


Deciding to go headless for your project can introduce a lot of risk.

  • Working with disparate teams using different technologies
  • Recreating existing functionality in the new 'head'
  • Unnecessary abstractions
  • Single points of failure

In this talk I will go over some of the risks involved with headless projects and share some successful strategies Chapter Three has used to help mitigate those risks.

Session Track

Drupal Showcase

Experience Level


Drupal Version