--- canonical: https://amplience.com/developers/docs/release-notes/2024/next-gen-locale-improvements/ title: Next Generation Authoring (Beta) flexible locale handling description: Flexible locale handling allows you to specify the locales that are shown by default audience: Business User image: https://cdn.media.amplience.net/i/ampproduct/next-gen-rich-text-images-fix-1?w=1200&h=630 image_width: 1200 image_height: 630 date_published: 2024-09-30 date_modified: 2026-04-09 --- # Next Generation Authoring (Beta)- new locale features, fixed issues **Release date: 2nd October 2024** In this release we've added some new features and made further improvements to [Next Generation Authoring](https://amplience.com/developers/docs/schema-reference/) (Beta), as we move towards a general availability release. We're responding to your feedback, addressing issues and incorporating new features. A new flexible locale handling feature allows you to specify the locales that are shown by default for a localized property. ## The new authoring experience To find out about the new authoring experience, start on the [What's new](https://amplience.com/developers/docs/schema-reference/) page. Next Generation Authoring includes an [enhanced "look and feel"](https://amplience.com/developers/docs/schema-reference/) which you get as soon as you switch it on, without any additional development. There are also many new developer features such as [customizable input fields](https://amplience.com/developers/docs/schema-reference/) and control over [form layout](https://amplience.com/developers/docs/schema-reference/), all of which are demonstrated in our [schema examples](https://amplience.com/developers/docs/schema-reference/). > **Info: Next Generation Authoring Beta release** > This release of Next Generation Authoring is classified as a beta release. During this beta phase you have the option to switch Next Generation Authoring on or off. We encourage you to [switch it on](https://amplience.com/developers/docs/schema-reference/) and start taking advantage of the benefits it has to offer. ## Flexible locale handling: the localized value set We've introduced a new [configurable component](https://amplience.com/developers/docs/schema-reference/) that is used with [field level localized](https://amplience.com/developers/docs/dev-tools/guides-tutorials/localization/) properties. It allows you to specify the locales that are shown by default for a property, and helps improve the authoring experience if you have multiple locales on your hub and only want to view and add values for certain locales. In your content type schema you can specify pinned locales for a property. The user can choose to view additional locales, but the pinned locales will always be shown by default and cannot be removed. You do not need to pin the master locale because this will always be shown. ### Localized value set example In the example shown below there are 7 locales available on the hub, but only the pinned locales: `en-GB` and `fr-FR`, are shown by default. If one of the pinned locales is hidden, using the locale filter at the top of the screen, then a message will be displayed. ![A content form with properties that use the localized value set component and have the en-GB and fr-FR locales pinned](https://ampproduct.a.bigcontent.io/v1/static/localized-value-set 'A content form with properties that use the localized value set component and have the en-GB and fr-FR locales pinned') For more details on using the new component with your localized properties see the [configurable components reference](https://amplience.com/developers/docs/schema-reference/) and [schema examples](https://amplience.com/developers/docs/schema-reference/). ## Resolved issues We've also resolved some issues that you've reported with the new authoring experience. Included in this release is a fix to the way markdown image links are displayed. Images are now shown in the rich text editor preview, so your markdown text will render in the same way as it did in the previous authoring experience. ![Images are now rendered in the rich text editor](https://cdn.media.amplience.net/i/ampproduct/next-gen-rich-text-images-fix-1?w=1880&fmt=png 'Images are now rendered in the rich text editor') In some circumstances, a schema containing a conditional was being displayed as a blank screen in the content form. This issue has now been fixed and we've updated our conditionals schema example. Our updated conditionals example shows how to show some alt text only when an image has been added. ![You can now do more with conditionals. Here a text field is shown only when an image has been added](https://ampproduct.a.bigcontent.io/v1/static/women-in-winter-hat 'You can now do more with conditionals. Here a text field is shown only when an image has been added') ## Keeping up to date To keep up to date with any outstanding issues that may have prevented you from taking advantage of Next Generation Authoring, take a look at the [FAQs](https://amplience.com/developers/docs/schema-reference/) page. This is updated frequently with information about known issues and recent fixes. We're also keen to receive your [feedback](https://amplience.com/developers/docs/user-guides/basics/dynamic-content/#send-us-your-feedback) about how you're finding the new authoring experience and any issues you find. ## Related pages [Next Generation Authoring](https://amplience.com/developers/docs/schema-reference/) [Out of the box features](https://amplience.com/developers/docs/schema-reference/) [Optimize your authoring experience](https://amplience.com/developers/docs/schema-reference/) [Schema reference: new features](https://amplience.com/developers/docs/schema-reference/) [Schema examples: new features](https://amplience.com/developers/docs/schema-reference/) [Configurable components](https://amplience.com/developers/docs/schema-reference/)