The Hierarchy API now supports the locale parameter to allow you to retrieve hierarchy nodes with content localized for a particular locale.

Next Generation Authoring validation is now even easier to use. A new validation header allows users to navigate straight to validation errors in the authoring experience.

In Dynamic Content, an icon identifies any content that does not meet validation rules as a result of ignoring schema validation.

We've added documentation to explain how to integration Content Studio with your existing content workflow, and how you can manage content generated using the Content Studio API.

We've introduced a set of improvements to the way Next Generation Authoring handles validation. We've listened to your feedback and ensured that validation behaviour is now more closely aligned with the previous authoring experience, and added some improvements. A number of bugs have also been fixed.

Manifest files can be used to retrieve localized variations of image alt text from Content Hub. The Automatic alt text service must be set up for the hub.

Dynamic Content has a redesigned properties pane, featuring a new layout and more content properties.

Dynamic Content search for partial strings has been enhanced, and now allows users to enter search strings of less than 3 characters.

We've enhanced automatic alt text for developers and users.

You can now manage Personal Access Tokens in Dynamic Content.

The CLI tool now gives you greater flexibility for migrating content, with a new "Ignore schema validation" feature. With this feature you can quickly migrate content items, bypassing schema validation that may prevent content migration.

This release focuses on developers and includes updates to the schema editor to make it easier to take advantage of the new features in Next Generation Authoring. The alt text icon is also now shown by default on the media card when you add an image to your content.

This release of Dynamic Content brings improvements to the scheduling slot browser, helping you to find slots more easily when adding them to editions.

We've made some changes to the Hierarchy API and Filter API to provide developers with more flexibility when retrieving hierarchical content. Both APIs now support retrieving content using a delivery key as well as a content item id.

Stay up to date with our latest documentation changes including release notes, documentation updates and tips for getting the most out of the docs.