Content hub

A content hub is a central repository of content. This concept has become more popular since the introduction of headless content management systems since these aim to act as a central place to store content (without its design) used for multiple digital experiences (DX). In many cases these are external facing DX use cases, but a content hub can also be used for internal content to serve up information to staff, in that case it can also be referred to as a knowledge hub and it crosses over into the area of knowledge management. A content hub aims to act as a ‘single source of truth’.

A more traditional Web CMS can also act as a content hub if it has a proper set of APIs that allows you to access the content in the repository. A CMS used as content hub should be able to integrate with a variety of enterprise systems, bringing together content from repositories of different functional areas of the business such as content creation, creative design and commerce teams across departments like sales, product development and marketing. It should be able to integrate with technologies such as DAM, CRM, PIM/ecommerce and PLM systems, knowledge bases as well as other CMS. Ideally information should not be copied from these systems but be accessible by referencing it. Once content is accessible via a content hub, your organization is able to create digital experiences in many form factors through the API layer of the content hub, without the need to request content from multiple systems.

Example use cases

  • Flexible creation of websites and related digital experiences when combined with tailored templates
  • Personalized content based on audience’s location and language
  • Content hubs for medical content relating to remote monitoring and care, involving analytics, surveys, messaging and telemedicine
  • Accurate information for remotely guided maintenance and repair actions for the automotive industry

Key benefits

  • Store all relevant corporate or digital experience information in a single content repository
  • Separate content from design, enabling multichannel use
  • Allow granular access rights management for each function and department
  • Reduce time spent on searching correct or updated information