Content modeling isn’t an exact science, and there will always be pioneers, as well as companies, that use anti-patterns for their advantage.Most companies don’t make their content models public. Look into the examples of what others have successfully used and draw ideas for your own solutions.
Moving from traditional CMS platforms into Kontent.ai, it may seem that there are features missing. Where are quotes, charts, and other visuals? Where can I remove an article from the navigation?
Separating form and content is difficult if editors are used to having control over both. Try incorporating a taxonomy to help them shape the look and feel of the content. This way, you don’t need to allow too many disruptive changes, yet enable authors to choose what they need.
It’s not unusual to have the top 3 articles displayed on your home page. That can be driven via traffic analytics based on click-throughs, time spent reading, or they might even be curated. What's the best approach to model it in Kontent.ai?
Create relationships between articles and their authors to show who wrote what. The easiest way to do this is by modeling your articles and authors as separate content types.After a few setup steps, you use a dedicated linked items element to link authors to articles they wrote and create a relationship between the authors and their articles.
Online forms are everywhere. Contact forms, newsletter sign-ups, quote requests, surveys, order forms, and so on. Opposed to most traditional web CMSs, headless CMSs focus on content. You typically won’t find a form builder within them, giving you the power to set it according to your needs.
When a person’s job is to update content that others send them, there is always space for improvement. This example elaborates how a good content model streamlined a previously manual process of updating person profiles.
Locations can relate to your offices, cafes, bus stops, smart beacon placements, moving businesses, and so much more. The difference is the accuracy and additional parameters that are needed for each of these applications.
As your content grows bigger, you benefit from organizing your content into smaller groups such as releases. You create these groups by tagging your content. You can then plan your releases, see what's scheduled for each release, and perform bulk operations like publishing or changing workflow.
Traditionally, headless is primarily used for content. It can be a website, a mobile app, or even printed materials. It can be public texts, internal memos, or even UI copy for apps or games. Sometimes, though, you might need to have configuration schemes editable easily by business people.
based on that structure into your articles.
See how it all works on the example of social media posts like tweets inside articles.
44 minutes
Manager / Developer
