Internet users are accessing web information across a variety of formats and devices. Managing all these touch points and creating brand and messaging consistency is a growing concern.
Headless CMSs address this problem by providing a content API and a single control point for managing all of the content while allowing the various sites and apps to handle templating and design.

There are side effects to sharing content between touch points, most of which are good, a few of which may be “bad” for your situation, and some of which are simply different. Managing content and developing websites with a headless CMS requires a mindset shift.

Because it can be a big shift in mindset, it makes sense to try things out before committing to a headless CMS. Luckily, there are several free and/or open source headless CMSs that you can try out, such as Directus, Cockpit, and Netlify CMS. You can even use the WordPress API to try out WordPress as a headless CMS. [285]


Comments are closed.