By natalie_wright on

The following blog was written by Drupal Association Signature Hosting Supporter, Acquia. 

The rapid evolution of diverse end-user clients and applications has given rise to a dizzying array of digital channels to support.

Websites in the past were built from monolithic architectures utilizing web content management solutions that deliver content through a templating solution tightly “coupled” with the content management system on the back-end.

Agile organizations crave flexibility, and strive to manage structured content across different presentation layers consistently in a way that’s scalable.

Accomplishing this efficiently requires that teams have flexibility in the front-end frameworks that dominate the modern digital landscape. That’s why decoupled and headless CMS is taking off. That’s why you’re here. But now you need the right technology to support the next phase of the web and beyond.

Download this eBook on headless and decoupled CMS

Comments

MusicB’s picture

MusicB commented

thanks sir

Praveen999’s picture

Praveen999 commented

I have just recently joined Drupal Community, started to study and hopefully work in drupal. Drupal 7 is more coupled and Drupal 8 is Decoupled, correct me if I am wrong.

esteban.arias’s picture

esteban.arias commented

I would say that they are both coupled by default, but you can set them up in a decoupled way by configuring it appropriately.

MillarP’s picture

MillarP commented

How does one go about doing that exactly?I can't find anything in the documentation talking about a decouple Drupal apart from a discussion group trying to work out how to do this.

esteban.arias’s picture

esteban.arias commented

Heya Millar,

Setting up a decoupled Drupal will be different depending on the kind of data you will be serving to your frontend.

If you will only be doing a headless Drupal for a marketing site which is only edited by a small group of content editors, then you can use a combination of JSON views with a small set of filters per view to serve your data. But if the project has to do with Personally Identifiable Information, then you must setup a headless which takes authentication into consideration (and maybe OAuth) so it will be a little more complex of a setup than before.

I am not an expert myself, but I have setup 3 decoupled Drupal sites so far. I can say that over time you will get familiarized with the contributed modules you can use to setup APIs, and every implementation will vary on a per-project basis (and depending on D7 or D8 too).

Please look at this article which has an actual example of a setup in Drupal 8: https://www.adcisolutions.com/knowledge/how-create-headless-drupal-site

jonesrussell42’s picture

jonesrussell42 commented

The built-in method to go headless in Drupal 8 is to use it's REST capabilities. See the official documentation to get started.

Alternatively, you can use the JSONAPI module. 

gulfwebdesigns’s picture

gulfwebdesigns commented

hi Natalie, absolutely good stuffs and keep it up! bookmarked this on Pocket as well! 

itsnadeem’s picture

itsnadeem commented

Drupal has Restfull webservice module and JSON API module. now both are available in Drupal Core. we can use these modules to achieve Decouple Drupal