The Benefits Of A Headless CMS
Shutterstock
There are a number of benefits of storing and managing content and design within a CMS, but this does mean that the purpose of the content is limited to a particular channel. For example, if you build a website within your content management system, it’s not going to be easy to offer this content to native mobile apps or third-party content users. For most organizations, a single piece of content can be used across Web, mobile, tablet, social media and other connected smart devices, commonly known as the IoT (internet of things). Business users are looking to publish content updates and affect all sites and applications that use this content.
To solve this problem, many organizations are turning to systems that provide a "headless CMS" style of implementation.
With a headless CMS, the CMS is responsible for publishing content and media only; layout, presentation and front-end technology are the responsibility of the development teams that consume content and use as required. With the headless CMS, content is published that is available to any application via API data services. This is commonly known as content as a service (CaaS).
This sounds like a simple solution (and it is) to ensure content is available to any channel and that it is de-coupled from the design.
There are a number of benefits to the headless CMS approach other than content de-coupling:
• The CMS implementation is cleaner. The CMS tool is purely storing content and isn’t cluttered with stuff that’s relevant to business users and other stuff that’s development only.
• With little technical involvement required in the CMS, it’s also a lot quicker for business teams to create new functionality. For example, if a marketing department wishes to create a new series of product mini-sites, it can go straight into the CMS and start creating the content immediately without having to wait for developers to build CMS-based templates.
">Traditionally, the role of the content management system (CMS) is to publish text, multimedia, documents, metadata and structure information (typically the content of an application), as well as visual layout assets and client-side code (generally referred to as design).
Shutterstock
There are a number of benefits of storing and managing content and design within a CMS, but this does mean that the purpose of the content is limited to a particular channel. For example, if you build a website within your content management system, it’s not going to be easy to offer this content to native mobile apps or third-party content users. For most organizations, a single piece of content can be used across Web, mobile, tablet, social media and other connected smart devices, commonly known as the IoT (internet of things). Business users are looking to publish content updates and affect all sites and applications that use this content.
To solve this problem, many organizations are turning to systems that provide a "headless CMS" style of implementation.
With a headless CMS, the CMS is responsible for publishing content and media only; layout, presentation and front-end technology are the responsibility of the development teams that consume content and use as required. With the headless CMS, content is published that is available to any application via API data services. This is commonly known as content as a service (CaaS).
This sounds like a simple solution (and it is) to ensure content is available to any channel and that it is de-coupled from the design.
There are a number of benefits to the headless CMS approach other than content de-coupling:
• The CMS implementation is cleaner. The CMS tool is purely storing content and isn’t cluttered with stuff that’s relevant to business users and other stuff that’s development only.
• With little technical involvement required in the CMS, it’s also a lot quicker for business teams to create new functionality. For example, if a marketing department wishes to create a new series of product mini-sites, it can go straight into the CMS and start creating the content immediately without having to wait for developers to build CMS-based templates.
https://www.forbes.com/sites/forbestechcouncil/2017/11/22/the-benefits-of-a-headless-cms/
Tidak ada komentar