What's New Since the Last Leap Week

Speaker 0: In Directus 10.8 we released a powerful new theming engine. Previously you were limited to adding your own CSS on top of the data studio to make yours. You now have the flexibility to customize colors, fonts, spacing, and much more across Directus using our new theme interface. Being able to white label Directus has always been important. Bringing your brand and aesthetic to the forefront really make Directus feel like your own tool.

Building on the excitement of our marketplace announcement, you can now develop and share themes as an extension. Now you can do more than just make direct us your own. You can share your designs and help others get creative too. We're excited to see the themes you bring to the marketplace. Thank you all for joining me in this exciting chapter.

Your vision, your directness, ready to dazzle. The canvas is fast. The palette is rich, and the possibilities, endless.

Speaker 1: As well as managing databases, Directus also helps you manage your files. As part of that, we offer media transformations via URL. Here's an image of 2 people on a beach. Notice that they're slightly off center, which is fine, until you start to crop the image via your app. Here the image is being cropped off from the center, but these two people are being chopped off.

In Directus 10.9, we introduced focal points. You can now specify the point for Directus to treat as the center. You can do this via the data studio or the files API. Now, the subjects that matter in your images can always be visible. You can combine this with our automation features to determine what the point of interest should be.

We hope you enjoy working with focal points, a small change with big impact.

Speaker 2: Before when requesting content versions, this is the data structure the data API return. And with relational fields, note that there is a create, update, delete array for each item. This is correct. It is what will happen when this version gets promoted. But it's different to what you may expect from an item when not using content version or using the main version.

This does made it hard to implement live preview as you had to account for 2 different data structures. In directors 10.10, we will store this data structure. But when you request a content version, we will standardize the data structure before returning it. So the return data is now the outcome if you were to promote the item. Here, we have an example of both a one to many and a many to many relationship.

In the one to many comments example, we are both updating an item and deleting related comments. The new output doesn't contain the deleted comment and returns the full item including any changes made in the content version. Likewise, in the many to many page blocks example, a block is being created and another deleted. The return data from a content version is now the same structure you expect, including the outcome of any changes. Now you can implement live preview with a standard and predictable data structure.