A decoupled CMS is one where the CMS functions as the backend to store, keep,
and edit content but no longer necessarily provides that content's delivery. It is considered "headless" because
it means chopping off the front end framework from the Drupal backend storing the data.
A headless CMS usually provides content through an API, meaning that it may deliver content anywhere, on any device. You will often hear this particular strategy as 'API-first'.
API-first is an approach that begins with the RESTful API as the communication between the backend, headless CMS, and user devices such as sites, mobile applications, wearable, IoT apparatus, and much more.
The decoupled CMS strategy is embraced industry-wide and impacts more than just those using Drupal.
But if you have a Drupal site, you will want to understand more about headless Drupal, you may contact the SoftGrid's development
team for the same! In conventional setups, Drupal provides a means to store information, an administrative region to handle content,
and a way to display data. In a headless installation, the data display functionality is replaced using an API into the data.
Then, another framework uses that API to access format, deliver, and display the data.