End-users today look forward to highly interactive websites that are able to pop out results in a jiffy. Content needs to be made available at all touch-points in harmony. The Headless CMS architecture solved all of these problems by creating different layers for presentation and data. Because Drupal emphasizes on server-side rendering rather than client-side rendering, the decoupled architecture was conceived. A headless Drupal website has its advantages and disadvantages and is not meant for every kind of a website. Founder of Drupal, Dries Buytaert believes that progressive decoupling is a better approach as in this way we can get the best of both worlds – a client-side framework for uninterrupted workflow without compromising on the Drupal’s content management capabilities. Still wondering if the headless Drupal architecture is a good idea or not? Contact our experienced and certified Drupal developers to help make your decision easier.