More and more enterprises are updating their content management technology from traditional full-stack CMSes to headless CMSes. While IT architects and developers praise this transition, it could leave people with less technical knowledge out in the cold.
From the point of view of digital marketers and content creators, headless CMSes appears to lack some features that they are accustomed to. At the same time, these CMSes expand their ability to manage experiences from a single website to multi-channel digital products. It’s no wonder that some people are a bit overwhelmed.
I made this transition myself, and I’m here to help you become friends with your new headless CMS. I’ll walk you through the opportunities that headless offers and give you a gentle nudge toward new ways of working with content and user-experience design.
In this post, you’ll learn how to maximise the value of your content with a new approach to management and content modeling. In the second post of this two-part series, I’ll help you expand your opportunities to curate content experiences across channels and optimise omni-channel user experience using the best tools on the market.
To maximize the value of your content, you’ll need to rethink your approach to content and work in cross-functional teams.
Monolithic CMSes and headless CMSes require different approaches to content management because they’re designed for very different end products. Monolithic CMSes—those traditional systems with front- and backends, such as Wordpress—are designed for managing web pages and websites; headless CMCes manage content across many digital channels, everything from websites to mobile applications to voice-control applications. Thanks to the decoupled nature of headless CMSes, you can ensure a coherent content experience across multiple channels.
Cross-functional teams help you take advantage of your headless CMS. By gathering everyone involved in creating digital experiences — from UX designers to editors to product owner — a system that works for everyone can be designed from the start.
Now that you are designing content for multiple channels, it’s important to structure that content into a content model that can be used repetitively across all channels. Creating a content model is an instrumental but often neglected UX design phase. It’s often left for developers to do because it resembles database design and is technically easy for them. But databases are used by an application, and computers don’t mind abstraction the way humans might. Therefore, structuring content is a bit more challenging than database design.
A successful content model is:
One approach to the content-modelling process is to take an existing piece of content and divide it into smaller, reusable pieces. You can then abstract these pieces for reuse. Once the content pieces are divided and abstracted, they’re referred to as structured content. This can be done by developers or, with Contentful, by non-technical team members.
Contentful enables anyone to structure content in the web app. An example might clarify things: Think about structuring a recipe. Recipes have a familiar structure; they require a title, introductory text, list of ingredients with amounts, and instructions.
You could design a simple structure — what Contentful calls a content type — by using:
Quick and simple. But there’s a better way to think about this content that will improve the digital experience, search engine visibility, increase business opportunities, and maximize the possibilities to utilize automation and AI.
Instead of entering the recipe content into one text field, create a content type for ingredients that splits the amount, unit and name of ingredient into three separate short-text fields. Step-by-step instructions should also have their own content type. Now, your recipe content type includes:
Why is this better? Have you ever tried cooking by looking at recipes on your smart watch or mobile phone? Normally you’ll spend more time scrolling up and down between ingredients and instructions than actually cooking.
But with this structure, readers can advance without scrolling backwards. This structure would also enable voice control and reduce the need to touch the phone altogether. It’s a much more hygienic approach to cooking, don’t you think?
Designing user experience and content for multiple channels might feel very overwhelming. If you have worked with websites for a long time, it might be challenging to let go of the thought that content equals a webpage. I have a helpful tip for you: as a potential end user of your content, try thinking about the channels that use your content as voice, not text. I have found this to be a useful way to rewire my very website-oriented brain to embrace the world of omni-channel content.