Version

Speaker 0: Hello. We are so excited to welcome you to the very first Director Sleep Week. We have a truly global community, so wherever and whenever you are, hello. We have a fantastic week lined up. Over the next 5 days, we'll be sharing what's new and upcoming for Directus and possibly even some teasers of work that's been years in the making.

Now Directus isn't a new project with the first version built by our CEO and co founder Ben almost 20 years ago. Directus 9 then completely overhauled the project into what we use today And earlier this year, we released Directus 10 with a commitment to sustainable open source. There have been over 26,000,000 downloads of Directus and that's because of the hard work and enthusiasm of our core team, contributors, and community members. In fact, there's now over 10,000 of you in our Discord server and 23,000 stars on our GitHub repository. The last few months have seen us bring live preview to the Directus editor, release Directus real time, and create a brand new SDK with much improved developer experience.

Today we're releasing directors version 10.7 and to kick it off, we want to introduce content versioning. Content versioning is a huge update to how you and your team author and collaborate in the Directus editor, and I would love to hand it off to Azeri to tell you more.

Speaker 1: Until now, collaborating on content using Directus hasn't always been the easiest. We have comments and revision history with accountability. But actually collaborating has largely happened off platform. There was a small risk. You would hit save the changes after someone else and override work, and there was no good way to work on draft updates and saving without publishing.

We have taken great care to build content versioning in the director's way, being both super powerful while being unoppressive to your workflow. Rather than talk to you about it, let me show you. Here, I have an articles collection where I've enabled content versioning, and this is an item within that particular collection. And here, we have a pill or menu, which is the main entry point for us to go into content versioning. Here, we can create a new version.

I'll call it graph as the key, and mine graph as the name. Now I'll change the title, add a new cover image. And for the content, I will just follow it up with an enemies. Here, I can save the version, and we'll go back here. We can see the main icon is not updated at all.

But when I view my draft, I can see my latest changes with the new cover image and content. Over here, I can promote the version. When I see the changes by default, we'll select all the changes from your new draft. And when I click on the preview tab, we can see what would be changes that I will be promoting to. And if I would like to keep the same cover image over here, you can see I will go back to the old image.

But for the demo purposes, I'll choose true cover image and content to be updated with the title remaining as the same. And while promoting it, we can choose to delete, keep it, and now choose to delete it. Now once promoting, we can see the title remains the same with the cover image and content updated to the new one that I've just added. You can also use our new content versions API to do what we just did in the data studio. If you have content versioning enabled on the collection, accessing the item like normal will always get the main version.

To get a specific version, use the new version parameter with the key provided when you created the version. And over here, it will be the test. And this data is from the test content version for this particular item. To promote a content version, you have to first create a div, which will return a hash And provide that hash to the promo endpoint. Content versioning also exposes new events which can be used in Director's Ultimate.

That's both in Hook's extensions and in Flows. A cool tip is that once you combine content versioning and live preview, you can view non published changes in your pages before you sign it off. And that's content versioning. It's been

Speaker 0: a pleasure to work on this for you and back to Kevin. Content versioning was a feature built with our our amazing community. It's been in preview for a couple of months and we've loved having your feedback implementing many of the suggestions that you've made. You can get your hands on content versioning now by downloading the just released Directus version 10.7 which is now available on NPM and Docker Hub. That wraps up day 1 of Leap Week.

We hope you love where we've landed for content versioning, and there's plenty more to come this week. See you tomorrow.