In the modern digital landscape, delivering content effectively across multiple channels and platforms is crucial for businesses. I am pretty sure everyone knows what a headless CMS is.

However when you think of a headless CMS and what Sitecore offers in this space, you think of XP, XM Cloud or maybe Content Hub One.

Not Sitecore Content Hub – it’s just a DAM!!!

Spoiler – It’s more than a DAM

That is unfortunately a common misconception, however one I feel that after explanation, it’s can become clearer on what Content Hub is.

The above image has been around for a few years but I think it explains Content Hub quite simply. The platform sits in middle, data is ingested on the left and used on the right.

I recently wrote about CMP here and how combining DAM with CMP you have an unbeatable ecosystem that can solve any problem.

This blog explores how to utilize Sitecore Content Hub and CMP for headless content delivery. Basically could it be a headless CMS!

Understanding Headless Architecture

Headless content management refers to the decoupling of content management from content delivery. In a headless setup, the back-end (content management) operates independently of the front-end (user interface).

This allows developers to build user interfaces using the latest front-end technologies while managing content in a centralized system.

Why is Content Hub ideal for headless content

Data Access

Sitecore Content Hub provides a RESTful API and a GraphQL layer for accessing data. Either will allow developers to pull content from the it how they like.

The APIs are well-documented, with endpoints for various content types, making it easy to fetch the necessary data.

Do you really need a full page builder

If you have very structured pages that do not change layout. Content Hub allows users to build content quickly and easily ready to be consumed by the downstream channel.

Content editors don’t need to worry about what goes where, they create and publish – That’s it.

What about if I do want to structure the content

Sitecore Content Hub is so versatile you could easily give content editors this functionality.

Basically it requires a data structure to hold the order and links to the content items. This is done by free modelling a new item in the schema – for this example we could call it ContentPage that makes a many to many child relation to a CMP content item.

Then a component to allow users to set the structure. This is done by building a react component with drag and drop. Users create a new ContentPage and add in the content items – then drag them into their order.

As the user changes position it updates the order on the parent and then ContentItem can be retrieved using the API or GraphQL for the structure.

Variations and Versions

I wrote last year about Content Hubs variations and versioning facility. This is baked into the product and if a great way of controlling and linking content.

Conclusion

I have demonstrated above the power that Sitecore Content Hub can offer.

It’s more than a DAM and could be used to deliver content to any channel. Combined with CMP, build your own content structure manager and you have a simple headless CMS.

Content management and orchestration are complicated platforms and this blog was to show you could manage your assets, content and structure in one platform.

Embracing this approach can help organizations stay ahead of the curve in today’s fast-paced digital environment.