Kontent by Kentico: Versioning

Akshay Sura - Partner

21 Jan 2022

In this video, we walk through how Kontent Headless CMS stores versions of your content items and how to compare these content versions.

Transcript

Note: The following is the transcription of the video produced by an automated transcription system. 

Hi, this is Akshay Sura. Today we'll be talking about versioning, versioning of content is a good way to keep track of things you've done in the past, going back and seeing the differences, as well as if you are doing languages as well. It gets complicated in terms of how content is produced over time. We just want a way to go back and take a look. Maybe you want to revert to a previous version or look into exactly what changes were made by whom in order for, you know, to track things down. So, when we look at a piece of content, you always have the option. So, as you notice, like when it's in the published state, which is the final state, you can create a new version so every time you want to make a change. But at the same time, you can look at the existing changes. So, if you go to compare versions you have, so if I remove, compare and just go through it from when this content was first created, as you can notice, there's nothing, nothing there. Then we added some piece of content. We updated something on there and then it goes back to the draft state. We updated something and then the state changed. So, this is a good way to see not just the content, which was modified, but also the states and by whom. Right. So, we are in review. We're in published. And also, it's a good way for you to check the version compare. So, the version compares the neat features.

So, if I go back to here, when we first created the content to the last time we went into review or maybe the last time we updated it, the only thing that changed is from Jan., we would change it to January. But if I go between these two pieces of content, you could see we went from a blank piece of content to adding content. So, imagine over a period of time when you've made some changes, it's easy to look through who's made the changes? What states did the content go through? And it kind of helps you a little bit. So, versioning is super, super important to keep track of, especially when you have a lot of content authors who are making changes if you find a version. So, for instance, I want to go back to this version where we just did January. I can easily restore through that version. And yes, you know, you're going to lose some data. But as you can see, when you say, I want to revert back to that specific version, it creates a new version, reverts it back. So then now I can go through my workflow again in order for you to process through, go all through the checks and balances of the workflow and ultimately getting into publishing. I hope this was useful. Versioning is super easy, and as many content authors are working with the content, it becomes a really neat tool for you to verify, check how things are going, what was modified and collaborate much better. Thank you again.


If you have any questions, please get in touch with me. @akshaysura13 on Twitter or on Slack.

Sign up to our newsletter


Tags:

Composable DXP
Headless CMS
Jamstack
Kontent

Share on social media

Akshay Sura

Akshay is an eight-time Sitecore MVP who has spent more than a decade working exclusively on Sitecore projects.

In addition to his work as a solution architect, Akshay is also one of the founders of SUGCON North America 2015, SUGCON India 2018 & 2019, Unofficial Sitecore Training, and the Sitecore Slack.

Akshay founded and continues to run the Sitecore Hackathon. As one of the managing partners of Konabos Consulting, Akshay will continue to work with clients to lead projects and mentor their existing teams.


Subscribe to newsletter