As a result, the Drupal repository (back-end) and front-end systems are decoupled. The content is then accessed through Drupal APIs and presented in the front-end systems of an organization's choice. In this setup, Drupal is typically used for back-end storage and management of content. In a decoupled architecture, different systems are used to control the back-end content management and front-end content presentation. If an organization is using Drupal to manage a website or set of websites and doesn't plan to reuse the same content for other digital channels or devices, a traditional architecture may be the best option. The primary reason for using this approach is simplicity. The traditional approach provides all of the extensive content management features that have made Drupal one of the most powerful and widely used CMS platforms.
Content editors add or manage content through Drupal's authenticated back-end admin section, while visitors view the front-end content, templates, and design system presented by Drupal via an HTML rendering engine (Twig). In a traditional architecture, Drupal is used for both the front-end presentation of content and the back-end management of content. Drupal Architecture Options Traditional or Unified Drupal Competitors such as Pantheon and Platform.sh have also made efforts to support and promote headless. Its HIPAA-compliant cloud hosting is a great option for the centralized content repository often used in decoupled setups. Additionally, Drupal's evolution into an API-first platform makes it well-suited to leverage these newer approaches.Īcquia, the leading cloud platform for Drupal, has focused heavily on supporting headless and decoupled architectures in recent years. The introduction of decoupled and headless architecture options further extends this flexibility and enables Drupal to power even more dynamic digital experiences. While the traditional approach works well in many cases, healthcare organizations looking to expand their digital marketing and patient engagement efforts should consider the benefits of a decoupled approach.įlexibility is one of Drupal's core principles, and its modular structure allows organizations to build dynamic web experiences for their audiences. However, despite these efforts, most organizations still use Drupal in a traditional, unified setup. The Drupal community has been exploring non-traditional architecture options for almost a decade, including headless and decoupled. Each has its advantages and appropriate use cases.
In this article we provide an overview of the various architecture approaches and how they can benefit healthcare organizations (or any industry, for that matter).ĭrupal architecture generally falls into two main categories, traditional or decoupled. We are often asked about the different architecture options for Drupal.
0 kommentar(er)
