Product changelog

If you've already started using the new personal API keys for Management API, you can now remove the deprecated API key using the Remove key button.

The deprecated API key remains available and valid until April 30, 2023. We recommend you switch to the new personal API keys before that date.

We've updated the regular expression for web URLs validation so that it now supports longer top-level domain names (TLDs). You can now use it to validate also URLs such as https://oxford.education or www.safelife.lifeinsurance.

If you're already using the Web URL pattern for validation, you'll see it's automatically changed to Custom pattern after this release. This is to keep the old pattern for you and prevent a breaking change. You can always change the validation to the updated Web URL pattern by selecting the option anew.

Preview URL patterns in the project settings are now sorted primarily by the enabled option, then by the content type name. This helps you find the active preview URLs quickly, as they're not hidden amongst the inactive URLs anymore.

Kontent.ai now validates element default values in content types. 

Thanks to that, you'll clearly see when you set a default value that doesn't meet the element's limitations. This helps to keep your content model clean and up to date. If you need to, you can still save your content types regardless of the warning.

This update doesn't include default values changed via Management API.

You can now send us your feedback directly. In Kontent.ai, just click the heart icon in the bottom left corner and select Send your feedback.

When you use a taxonomy term in a content item and someone deletes the term, it's now clearly visible. Up until now, deleted terms just disappeared. Newly, deleted terms are shown in red as “Deleted taxonomy term”. This applies also to taxonomy elements' default values.

When publishing a content item with deleted terms, you'll see a friendly warning, similarly as with deleted assets or linked items.

We've expanded the content type validation. It's no longer possible in the Kontent.ai app to save a content type with deleted assets, content items, or taxonomy terms in default values. This helps you keep your content model clean and up-to-date.

There's also new validation for the guidelines element. To prevent confusion, you now can't save a content type with deleted assets in guidelines.

This update doesn't include the Management API validation. We'll release that separately on October 26.

When you publish a content item with linked content, you can select its linked content items and publish them at the same time. We've made some changes to the way the selection works.

By default, the list of the linked content items is expanded one level deep. You can expand the list to any level necessary. This gives you more control over the content you're publishing.

When you work on content items, you'll now see a short label telling you whether any of your elements currently contain a default value.

Having multiple components in a content item is an essential part of content modeling. But at the same time, it might be a bit overwhelming to navigate such content items. To quickly scan through collapsed components, you can now have a look at their text preview. This gives you an idea of what's inside the component and if it's what you're looking for.

Ever wanted an easy way to find all places a content type is used in? It's easy with content items but what about components?

Say hello to the new filter! In the list of content types, you can now filter out all content items with components of the given content type.

You can use this when making changes to a content type but want to check the affected content first. Combined with the content items filter, the new option empowers you to find all places where the given content type is used.

When using markdown shorthands to format and structure text, you can now quickly revert the automatic markdown conversion by hitting the backspace key. This is another way to undo markdown conversion in addition to using CTRL + Z (or ⌘ + Z).

Hit the backspace key if you accidentally use a wrong markdown shorthand or want to keep the text as it was, effectively skipping the conversion.

Ever needed to quickly write things like 2⁴ = 16 ⟺ log₂(16) = 4, or H₂O? Now you can use keyboard shortcuts for superscript (Ctrl + Shift + .) and subscript (Ctrl + Shift + ,) that make writing expressions like that one a breeze. Check out more keyboard shortcuts.

If you're publishing a content item in non-default language and the item contains non-localizable elements, you can now choose to publish the item's default variant together with the non-default variant in a single action.

With this small improvement, you can easily keep your non-localizable elements up-to-date in your published content.

You can now set a custom codename for a content group directly in the Kontent UI. This way, you can make sure that codenames always meet your web development needs.

To enhance the security of your content when cloning projects, the subscription to which you clone needs to offer the same features as the original project's subscription.

For example, if you want to clone a project that has secure access enabled for Delivery API, the new project's subscription must support secure access as well. Same goes for Management API.

User listings in your project and subscription now show only active users by default. If needed, you can still apply filters to see deactivated users as well.

This is to make your user management clearer, as only active users count to the user quota of your subscription.

When you change an item's workflow and there's only one workflow the item can move to, Kontent now disables the dropdown and selects the workflow for you automatically. 

It works the same when you convert a component to a content item and there's only one workflow available.

If you have 15 or more components in a content item, they no longer expand automatically after you open the item. This speeds up the process of opening the content item so you can edit it sooner.

Consistent content labeling is important. With the new Not in filter, you can quickly find unlabeled content items.

For example, if you need to find items that aren't labeled by a taxonomy called Continents, you'd select ∅ Not in Continents from the list of filters.

Guidelines in content items are now collapsed by default to make more space for what matters most – creating your content. You can always expand or collapse the guidelines as needed.

We've added information about the workflow of your content items to two new places:

• A content item's revision list
• An item's detail in the editorial calendar

When linking content items in rich text or linked items elements, the content list will be prefiltered to the collection of the parent content item.

This little change helps you select from the content that's relevant to what you're editing and save time.

When editing content types, you'll see to which workflows the content type is limited. You can change the limitations in workflow settings.

Also, in Project settings > Workflow you now see the number of content items used by each workflow. This number counts for items in all languages.

When inserting images to a content item, the last visited folder is now remembered so there's no need to click through the asset library again and again. Less time searching for assets, more time being creative.

You'll be no longer unsure about the way your content items are sorted. When you search for content items, you'll now see clearly in the search bar information on how the items are sorted. Moreover, if you set the list to custom sorting, for instance by name, you'll see a reset button to get back to the default sorting by relevance.

Kontent now makes selecting the right collection easier. When creating a new content item, you'll see the collections you use the most on top. Moreover, when you filter out content items in the content list and then create a new item, Kontent recommends you the collections relevant to your filter setup. And, last but not least, when you create a new content item from within the linked items element, Kontent selects the parent item's collection for you.

You can now sort your assets by title, creation date, and file size. When you select a sorting option, Kontent remembers it and will sort your assets the same also the next time you visit the asset library. You can also sort assets in the dialog for inserting an asset into a content item. Here, however, Kontent doesn't save your sorting options.

Restoring an older version of a published content item just got easier: you can do it directly and don't need to create a new version of the item first – the item gets to its first workflow step automatically.

Similarly, when you want to restore an archived content item from an older version, you can now do it directly without needing to restore it from its latest version first.

The list of collections in project settings now has filtering – that means it's easier for you to find the collection you need. What's more, we moved the Create button to the top so when you need to create a new collection, you now no longer need to scroll all the way down to the bottom of the list.

Your project environments just got a boost. With environment swap, you can now mark your non-production environments as production. This effectively swaps the production and non-production environments, giving you a way of pushing content model changes from an environment to production without migration.

After the swap, developers need to update their apps to use the new production's project ID and API keys. The former production environment will continue to work without interruption.

You can now expand nested linked items up to the 7th level of nesting when editing a content item. This is possible for items within the rich text element and linked items element.

With your asset library growing each day, it’s easy to lose track of what’s actually in it. Advanced asset management gives you the tools you need to stay on top of your assets.

Create an asset taxonomy based on your needs to organize assets by regions, teams, descriptive tags, and more. Find relevant assets without any hassle and make asset management a breeze!

Get in touch with us or check out our pricing page for more details.

In your subscription details, you'll now find a list of all users invited to the projects under your subscription. With this user overview, you can quickly:

• Find specific people by their name, role, or project they're in.
• Change user roles, including their access to content in specific environments, collections, and languages. 
• Activate or deactivate users in all projects under your subscription.
• Verify how many more users you can invite.

In newly created projects, the predefined workflow steps (Draft, Published, and Archived) will now come with the default Project Manager role. This means that items in these steps can only be handled by the Project Manager role unless specifically set otherwise.

To allow working with the workflow steps to anyone in the project, choose All roles instead.  

This applies to all new projects created after July 21, 2021.

The page tree in Web Spotlight can now be pinned in place. The change then takes effect across all your projects and web browsers. You can expand the page tree by clicking on a page tree icon at the top, or by clicking on the sidebar itself.

In your environments, you can now choose which users should be active and which roles these users should have in each environment. Users with the Project manager role still have access to all environments.

The Project manager role is now global for your whole project. When assigning this role to users, you need to assign the role to all languages and all collections. You can still create a custom role with the desired permissions and access restrictions.

If you assigned the Project manager role to a user and limited it to a specific collection or language, we'll migrate the role assignment for you.

When moving items between collections, you now always see a list of item variants that will be affected by the move. This helps you do a quick check and provides hints if you cannot move the item.

When you view your assets, you can see who created and last updated the asset.

For example, if you need to change the asset but don't have the means, now you know who to contact so they can adjust the asset for you.

Content details sidebar can now be pinned in place so it does not show after each item visit. The change then takes effect across all your projects and web browsers. After activating the pin, sidebar stays hidden in both content item and Web Spotlight editor. Sidebar will be opened only when used for confirmation of the following actions: workflow step change, assigning contributors, creating task, setting due date, and adding/changing notes.

The information you see in your audit log events has been rearranged for better readability.

Use the new {Collection} macro in your preview URLs to differentiate between collections. For example, if you're using collections for multiple regional websites, you can use the new macro to tell your app which website to preview.

Review changes in your content model using the audit log to see who changed what and identify root causes of incidents. The audit log is a journal of changes related to content types and snippets and includes additional details about the action and the changed content.

Ensure the right people work on the right content by assigning their roles to specific collections. With collections, you can set up individual departments and teams and divide your content in a way that makes sense to your organization.

You can give your users different roles for each collection and language, or specify a fallback role for any new collections or languages that you might create.

If you're using collections, you'll see a new Collection column in Content & Assets. The column will help you orient faster in your list of content items. You can still hide columns that you don't use or don't want to see.

You can now move content items to another collection in bulk through the bulk actions.

Web Spotlight introduces a new feature for your content authors: in-context editing. Edit your website content within the preview context without having to switch between the editor and preview.

Furthermore, you can now easily activate or deactivate Web Spotlight for your project in the Kontent's project settings. Note that you need to have Web Spotlight activated for your subscription first.

Web Spotlight, our brand new tool for Kontent.ai focused on website management, is now available. Feel free to request the activation of this feature on your project and watch the magic happen.

The expiration of content lets you schedule when content items move to the Archive state, automatically removing them from your websites and applications. This eliminates the overhead of manually removing items when they become obsolete, such as at the end of a campaign or after a planned event.

You can now invite multiple new users and existing users at the same time in the invitation dialogue. We've also improved several things under the hood to make the overall inviting experience smoother and faster.

When editing your content items, you can now add tasks, update due dates, notes, and contributors using the quick actions at the top. 

We've also changed the way you move items between workflow steps to make it more convenient. This will save you time when updating assignments.

You can now create content without the risk of overwriting the work of your colleagues. We took care of conflict prevention on the content item element level.

For example, this means you don't need to wait for a colleague to finish writing the body of an article if you want to adjust metadata for the same content item. Watch our webinar for a demo.

You can now search for items using an exact phrase without getting partially matched items.

You can now use a Manage environments permission to let users in your project work with environments. For example, this can be useful if you want to give your developers complete control over your non-production environments.

You can now use two new macros while defining preview URLs for your content types. The new {Codename} macro resolves to the codename of a content item and the {ItemId} macro resolves to the internal ID of a content item.

Environments provide a way to make changes in isolation from your production project. Use environments to prepare changes for your production project in a safe place. Your developers then take care of propagating those changes to production.

You can now browse content items in a hierarchical form using the new Relations tab.

You can now assign multiple roles in different languages to invite users with language-specific access to your project.

If you have multiple items in the Archived workflow step and you need to start working on them again, you can now select these items in your content items list and move them to the first step your role can work with using the Restore action.

You can now create and assign tasks within content items to delegate responsibilities and track progress of your content creation.

Your projects will now contain a new default workflow step named Archived, which comes after the Published step. After you unpublish an item, you'll find it in the Archived step. Unpublished and archived content will no longer be mixed up with items in the Draft and other workflow steps in your content list. If you later decide that you need to work on an archived item again, you can restore it to the first available step.

You can now share your active filters in the content item listing with your colleagues via link.

The permissions to Create a new version and Unpublish were split. The permissions can be assigned separately to the roles in your project via the Published workflow step. Make sure to verify who can unpublish content in your project and limit the permission only to select roles.

You can now use markdown shorthands to create headings and lists when editing text in the rich text editor.

You can now save filters in the content item listing so that you can find the right content even more quickly and don't need to select the filters again every time.

You can now add comments to all content elements in all workflow steps. That also applies to custom elements and published content items.

When you need to create a similar type that has a lot of content elements, you can now create a copy of the content type and save some time.

Comparing revisions of content items is now significantly faster for larger items with a lot of rich text elements.

Names of content items can now contain up to 200 characters (instead of original 50) to better support more descriptive titles.

You can now configure what columns will be shown in the content item listing in your project. Hide those columns that you don't use or don't want to see.

You can now discard unpublished changes made to your content so they don't clutter your project when a user accidentally creates a new version.

You can now select a scope that will be used for searching within content. You can choose to search either within content item names only or within all content elements of your content items.

You can now delete projects in your subscriptions. Be careful, though, deleting a project is irreversible as all project data are removed. If unsure whether you can delete a project, you can always archive it instead.

 You can now add images to the Guidelines element to advise your content editor more effectively when they're creating content.