Many open source enthusiasts (practitioners, paragons, partisans, preachers and protagonists) will have heard of Drupal.
For those that haven’t, Drupal is an open source content management framework, as well as an extended community of developers, maintainers and business supporters.
Acquia Inc. is a software-as-a-service firm that provides enterprise-grade hosting, support and services for Drupal.
So that’s Drupal, but what is Decoupled Drupal?
Here’s a snapshot of what Buytaert is saying and you can read more at the above linked blog mention.
Three levels of coupling
Traditional Drupal architecture (coupled Drupal) is a monolithic implementation where Drupal maintains control over all front-end and back-end concerns. The ‘coupling’ in this sense, is Drupal’s hard-wired control relationships at both front and back.
Buytaert says that traditionally coupled traditional Drupal is ideal for traditional websites, that is – it will offer fast deployment (time to market) options and alleviate a content creator’s reliance on front-end developers.
“This involves a complete separation of concerns between the structure of your content and its presentation. In short, it’s like treating your web experience as just another application that needs to be served content. Even though it results in a loss of some out-of-the-box CMS functionality such as in-place editing or content preview, it’s been popular because of the freedom and control it offers front-end developers,” noted Buytaert.
Horses for courses
Buytaert says that the most critical to any decision to decouple Drupal is the must-have feature set desired for both editors and developers.
He asserts that in order to determine whether you should use a decoupled Drupal, it’s important to isolate which features are most valuable for your editors and developers.
Unfortunately he concludes, it’s a horses for courses situation and there is are no black-and-white answers here; every project will have to weigh the different pros and cons.