Up until this year, fully decoupled Drupal was a single category of decoupled Drupal architecture that reflects a full separation of concerns between the presentation layer and all other aspects of the CMS. The progressive decoupling paradigm lies on a spectrum the less of the page dedicated to JavaScript, the more editors can control the page through Drupal's administrative capabilities. This JavaScript might be responsible for nothing more than rendering a single block or component on a page, or it may render everything within the page body. In progressively decoupled Drupal, a JavaScript framework is layered on top of the existing Drupal front end. In this case, a decoupled approach becomes required. Sometimes, JavaScript is required to deliver a highly interactive end-user experience. Because the benefits are real, this is still how most new content management projects are built. This is Drupal as we have known it all along. Traditional Drupal remains an excellent choice for editors who need full control over the visual elements on the page, with access to features such as in-place editing and layout management. In traditional Drupal, all of Drupal's usual responsibilities stay intact, as Drupal is a monolithic system and therefore maintains complete control over the presentation and data layers. The different flavors of decoupling Drupal exist due to varying preferences and requirements. As I've written previously, the three most common approaches to Drupal architecture from a decoupled standpoint are traditional (or coupled), progressively decoupled, and fully decoupled. I want to revisit some of the established ways to decouple Drupal as well as discuss new paradigms that are seeing growing adoption.
0 Comments
Leave a Reply. |