Drupal: Everything you need to know about the open-source CMS

You can use Drupal both as a traditional and a headless platform.

The main difference

With a traditional CMS, the front and back of a website are intertwined. The CMS dictates the appearance and design of the frontend of the website.

In a traditional CMS situation, opening up the content to wearable or native apps is only possible if the CMS also offers an API and if the CMS keeps the content and styling separate.

A headless CMS no longer dictates the styling or design — it merely unlocks the content. In a headless setup, you manage all your content in one separate system and then load it everywhere at the same time (by means of API links).

Drupal as a traditional CMS

A traditional CMS consists of a frontend and a backend. In the backend, you create new content or amend existing content. This is a secure area that only the administrator has access to. This content is displayed on the frontend — the part that website visitors can see and use — by means of a theme or template.

In a traditional CMS, the backend and frontend are seamlessly connected and dependent on each other. When you make an adjustment in the backend, the frontend code changes immediately. That comes with a big advantage: you can use your CMS to manage both the content and the design of your website (or several websites, if you're using a multisite setup). However, this interdependence can also limit the flexibility of design and access to other media.

Advantages of a traditional Drupal Platform

• For simple websites, you're best off using a traditional CMS because the extra features of a headless CMS are unnecessary;

• An intuitive editorial experience thanks to the integration between backend and frontend;

• The potential to open up content to other media and apps remains, thanks to the built-in Drupal API;

• For a platform that anticipates a lot of user input, a traditional CMS is the right choice.

Drupal as a headless CMS

Drupal headless is a smart solution for companies with an omnichannel approach. A traditional CMS is fully integrated into the frontend of the website. As soon as you make changes in the CMS, the code of the site immediately changes and the edits are visible to visitors. The backend and frontend are seamlessly intertwined.

With a headless CMS, things work differently. You manage and publish all your content from a central environment. The presentation layer is detached from the CMS and the content is managed in a separate environment.

This separate environment is connected to the presentation layer through an API link. For example, the content is displayed in the backend, frontend-specifically. This way, you can simultaneously publish information on a website, smartphone app, and smartwatch app. Each frontend processes the information individually so that the content is immediately optimised everywhere.

More advantages of headless Drupal CMS

For simple websites, a traditional CMS is sufficient. But for companies that are looking for more flexibility, scalability, and freedom, headless Drupal CMS adds value. This is especially true for a streamlined omnichannel strategy.

Along with easy management of multiple frontend environments, there are more advantages of headless:

• Fast and strong visual websites – If you use a lot of videos and animations, the user experience should have no limits. A lot of attention for the frontend in combination with headless CMS is the right solution;

• Flexibility – With a headless CMS, you can respond quickly to new developments. If you're growing quickly, you can easily adapt your headless CMS so that you can consistently serve your target group well;

• Safe for sensitive data – The content can only be retrieved via the API. It is often not possible to write back data. This makes it easier to secure the entire system.

Can't decide between traditional or headless CMS? With Drupal, you can use a combination of the two. This allows you to unlock traditional CMS content through an API for other channels such as an app or self-service portal.

Drupal’s versatility is also reflected in the fact that it can be used as a digital experience platform (DXP). DXP is a technology that has been gaining more and more fame since 2018. But what exactly is a DXP?

A DXP is a central platform that helps you reach the target group on a large number of touchpoints and where you can increasingly focus on the target group’s experience — i.e., the content you offer and their interaction with it, the medium, and the target group’s situation.

Think of specifically tailored content and interaction options, with a distinction between websites, mobile apps, portals, and much more. The great thing about DXPs is that everything comes from one source. As a result, you no longer depend on the often suboptimal cooperation of multiple separate systems. Drupal, with headless CMS at its core, works wonders as a DXP thanks to its architecture and operation with APIs.

Make your Drupal experience unique for everyone

Consumers are increasingly looking for personalised experiences. If you address users with content that is irrelevant to them, you'll lose them in a heartbeat.

Internet giants like Amazon, Spotify, and Netflix are already fully committed to providing personalised experiences. This might be buying advice, personalised playlists, or viewing tips.

But contrary to popular belief, this personalised approach is not only for the chosen few. By managing all content from a central system, you can provide a seamless customer experience that connects multiple touchpoints. This makes it easy for the consumer to follow a transmedia journey designed just for them.

Software like Drupal is constantly evolving. The most recent version of Drupal is Drupal 10, but the release of Drupal 11 is coming in late 2024.

You should ideally use a version of Drupal for which updates are still being released. This way, you can safeguard the quality and security of your platform.

Drupal 7 will continue to be supported until 5 January 2025. Drupal 8 and 9 are no longer supported.

The end date of support for Drupal 10 is still unknown, but as Drupal 11 will soon follow Drupal 10, Drupal 10 may still be supported until the end of 2026.

Do you have any questions about Drupal and the impact it can have on your organisation? Our Drupal experts are happy to guide you through them.