Considering a Headless CMS: Five Benefits of a Decoupled Architecture

Checklist

May 9, 2019

TABLE OF CONTENTS

Intro

In the publishing and digital media space, traditional CMSs such as Wordpress or Drupal provide a lot of functionality out of the box. These CMSs allow a business to easily build a content repository, along with the presentational aspects that are necessary to display and interact with that content.

Traditional CMSs house all of the logic to create, edit, store, and display content. Support for features such as pages, templates, themes, custom data types, and more can make traditional CMS platforms very appealing when getting content distribution off the ground. Additionally, plugin and extension marketplaces can add rich new features with little to no development effort.

Traditional CMS

What is a Headless CMS?

So what’s a headless CMS and how is it different? A headless CMS is one where the CMS only deals with content creation, leaving the presentation of that content to other components in the system. The CMS only exposes its data through an API, effectively decoupling presentational aspects from content creation.

Headless CMS

Transitioning from a traditional CMS architecture to a headless one requires some effort. However, there can be several benefits:

Five Benefits

Distribution to More Channels

Allows easily adding new systems to handle distribution to different channels. These can be traditional web channels for desktop or mobile, or even more exotic platforms such as social destinations (Facebook, Snapchat, Instagram), apps, wearables, voice assistants, OTT, etc.

Quicker and Easier Development

By decoupling distribution channels from one another, it allows them to evolve independently. This means development teams can focus on delivering a vision without the distractions and synchronizations needed in a centralized app.

Platform Resilience and Longevity

Because each distribution channel is isolated from the CMS, they become simpler, needing to handle fewer edge cases. This also allows newer developers to jump into a distribution channel component easily and make less mistakes as data dependencies are more apparent. This makes the overall architecture easier to evolve and maintain.

Better Performance

With each distribution channel being highly focused and specialized, it allows more fine-tuning, potentially leveraging channel-specific APIs and frameworks. In addition, because components are explicitly separated from one another, it makes measuring API calls for performance bottlenecks easier.

Opportunities for Integration with Different Data Sources

In a headless CMS setup, it becomes fairly simple to integrate the CMS content API with other APIs, combining them to provide a richer data set. For example, geodata, weather data, or even other third-party services could be combined with content to provide a more compelling experience.

Traditional CMS platforms are a fantastic way to get started in the publishing and digital media space. However, they may hamper the evolution of a digital media brand. Embracing a headless CMS or decoupled architecture is a good step towards removing the ceiling on the possibilities for content creation and distribution.

About Levvel

Levvel helps clients transform their business with strategic consulting and technical execution services. We work with your IT organization, product groups, and innovation teams to design and deliver on your technical priorities.

Content creation and publishing can be tricky. Our Digital Media team helps your brand shine and take the guesswork out of building and managing a digital publishing platform tailored to your needs. We empower media companies, publishers, and content providers to build digital brands. We enable incredible digital experiences and build tools and infrastructure to power them. For more information, contact us at hello@levvel.io.

Authored By

Ralph Khattar

Senior Engineering Manager

RECOMMENDED CONTENT

Everything You Need to Know About the California Consumer Privacy Act (CCPA) and How to Be Compliant

Blog

Architecting a Digital House of Brands

Guide

Video Series: The Future of Digital Media—Tools and Trends Shaping the Industry

Blog

Meet our Experts

Ralph Khattar
Senior Engineering Manager

Ralph Khattar is a Senior Engineering Manager in the Digital Media vertical. Before joining Levvel, Ralph worked at AOL as a technology leader and oversaw the architecture of the content platform for multiple large media brands, delivering billions of page views per month. He has also overseen the merging of several systems when Verizon acquired AOL and merged with Yahoo. Ralph brings experience in building large, sophisticated systems that can scale to handle the demands of businesses of any size.

Related Content

Everything You Need to Know About the California Consumer Privacy Act (CCPA) and How to Be Compliant

As of June 2018, the state of California passed a new privacy law that could lead to more consequences for US-based companies than the European Union’s General Data Protection Regulation (GDPR). Here's what you need to know and how to be compliant.

Blog

Feb 07

Architecting a Digital House of Brands

As content companies grow by either creating new internal brands or acquiring external brands, management of the portfolio can become a headache.

Guide

Aug 14

Let's chat.

You're doing big things, and big things come with big challenges. We're here to help.

Access the Checklist

By clicking the button below you agree to our Terms of Service and Privacy Policy.

levvel mark white

Let's improve the world together.

levvel-mark-mint

© Levvel 2020