You may have heard that it is not possible to customize a headless CMS because its code sits in the Cloud? Fortunately, this is not the case with Kentico Cloud. Read on to learn more about our upcoming Extensions feature!
If you can't customize your headless CMS, content editors have to live with the default content authoring experience, which can be limiting. Content editors may be confined to using assets from external repositories like DAM, and writing content in Markdown syntax. Luckily our upcoming Extensions feature in Kentico Cloud will let you customize the experience!
What are Kentico Cloud Extensions?
Having a flexible and open API is a must in the world of specialized microservices and headless CMS, allowing developers to communicate with other services to build appealing digital experiences. For example, you can build powerful search into your website with Algolia and Kentico Cloud. This is one way you can look at headless CMS integration or extension capabilities through API.
Another way is to look at the ability to extend capabilities of the headless CMS itself, meaning to extend the default content authoring experience. And, this is where the Kentico Cloud Extensions framework comes in handy. It will allow you to connect with other best-of-breed tools no matter whether that's DAM, PIM, or any other. With Extensions, you will be able to provide your customers with a truly unique and differentiated content authoring experience.
Your API-first CMS should make it easy to connect multiple solutions into a single comprehensive digital experience platform. Kentico Cloud Extensions will make it possible through custom editing elements.
Hmm, custom editing elements sound promising. But what can they actually help content editors with? Long story short, there are limitless possibilities. Let's have a look at several useful examples of custom editing elements.
As long as the external service or system provides a public API to access its specific items, or to enrich/adjust the written content, you will be able to build a custom element to use it.
- Integrating external image and media repositories - the element allows you to search and select assets from external services and repositories like Flickr (see showcase below), DAM, and others.
- Integrating with AI tagging service - the element performs automated tagging by extracting keywords and other information from image assets.
- Integrating with product catalog - the element searches external product catalogs, PIM systems, and tight specific product with your content.
Other Examples of Custom Elements
- Markdown editor - a custom editing element allows content editors to write content in a lightweight markup language, with plain text syntax that can be easily converted to HTML, and many other formats. This is especially useful when you plan to distribute the same content to multiple channels that require different formats.
- YouTube video preview - displays an embedded YouTube video preview based on the defined video URL.
- Geo location selector - defines geo location by selecting a point in the displayed map.
- Color picker - defines a color (e.g. a product color) by selecting one of the predefined colored blocks.
- Country and state selector - auto-populates a list of states based on the selected country.
How Will You Use Extensions?
As you can see, Extensions will provide developers with enough power to connect Kentico Cloud with best-of-breed tools. Developers will be able to create different custom editing elements, which can be seamlessly integrated into the whole content authoring process.
We would love to hear what you think about Extensions, and how you would use them. Leave us a comment below, or send us an email to email@example.com. Your feedback helps us create a product that customers love.
For updates and further information on when Extensions will be available, check out the Kentico Cloud Roadmap.