What's new in Content Hub ONE
We are constantly working to improve the experience of business users and developers who integrate the Content Hub ONE experience with their e-commerce websites or apps.
Here are the latest release notes:
- Rich text editor expansion: we've introduced an expanded view for our rich text editor, giving you more space to work in, for a more efficient writing experience.
- Enhanced reference calls: we previously improved the list endpoints for content and media items by adding support for lists of IDs. We’ve further enhanced this feature, so reference content and media item details are now requested in a single call. This optimization gives you a streamlined experience while browsing, letting you access the desired information efficiently and without delay.
- Authentication flow: we've refactored and improved our authentication flow to prevent the "Cannot resolve tenant" error.
Technical limits: to ensure performance and quality for all users, in this release we introduced technical limits.
Quantity Limit Content type ID and name 40 characters Field ID and name 40 characters Help text for fields 100 characters Content and Media item name and short text fields 1000 characters Content and Media item description and long text fields 50000 characters Error and warning text highlights: with the recent additions of various technical limits, we wanted to make it easier to differentiate between the errors that prevent you from saving (such as those caused by exceeding a technical limit), and the warnings about issues that allow you to save but prevent you from publishing (such as leaving a required field blank). For this reason, error text and highlighting are now red, and warning text and highlighting are amber.
- Preview API support for search, filtering, and sorting: the Preview API now supports filtering and sorting based on a range of system and user-created field types, including date time, number, Boolean, and short text fields. The Preview API now also supports filters that include nested OR and AND operators. This was previously only available for the Delivery API.
- Technical limits: to ensure performance and quality for all users, in this release we introduced technical limits. We have set a limit of 1,000 characters for short text fields, including the name fields for content and media items. For the description fields of these items, we set a higher limit of 50,000 characters. Content types have been given a smaller limit of 40 characters for their content type name and ID, and for their field name and ID.
- Code blocks in rich text fields: to support content creators, we're introducing a code block element for rich text fields. This lets you insert and edit blocks of pre-formatted code in the text. We currently support CSS, Javascript, JSON, Typescript, and HTML.
- Support for list of IDs in media list endpoint: we’ve made the content and media list endpoints more efficient by adding support for lists of IDs. Now, instead of needing multiple calls to fetch the details of a list of media or content items, you can get everything you need with a single, combined call.
- Added name text box to manage content/media item form: previously, you could change the name of a content or media item by updating the field at the top of the corresponding page. To make things clearer, we’ve add a Name field to the page form. Changing the value of either field now causes the other field to update automatically to match it, as shown here:
- Content type and media item deletion flow: to make things easier, you can now delete content types, media items, and content items directly from their respective detail pages. The only exceptions are media items that have been or are about to be published, and content items if there are existing items of that type.
- Technical limits: to ensure performance and quality for all users, in this release we introduced technical limits. Due to a limitation in the React library, use of the term "ref" in field names is not allowed, so you will see a warning when using this text during field creation.
- Up arrow on number field: clicking the up arrow on number fields now works as intended.
- Swagger schema updates: we've made some updates to our Swagger documentation to improve its usability. To make the documentation easier to navigate, we’ve simplified many resource names and removed unnecessary information.
- Technical limits: we've introduced technical limits to ensure high performance and quality of service. As part of this, we've set a limit of 100 content types per Content Hub ONE instance.
- In-app documentation support: we know how important it is to have access to the right information when you need it. That's why we've added links to our documentation and related API endpoints on the OAuth Client and API keys pages, so you can easily find what you're looking for.
- Streamlined content deletion: deleting content items is now easier and more intuitive than ever. You can delete your items from any page, except when they've been published or while publishing is in progress.
- More relevant search results: we've improved the sorting options for search results to show the most relevant content first, so you can find what you're looking for quickly.
- Improved data structure display: sifting through API responses to find content and media items is now easier. You can review the structure of your data with the new and improved JSON preview display on content and media detail pages.
- Faster login times: we're always working to improve the performance of our application. We've recently made the user login process faster, so you can get to work more quickly.
- Better Swagger experience: first, we've improved the order and descriptions of our APIs. This means that you can now find the information you need more easily and quickly.
- Better sorting and filtering: our APIs now support sorting by relevance, making it easier to find the information you're looking for. Also, the Preview API now supports filtering on date-time and number fields for content and media items, as well as AND and OR operators. This makes it easier to preview your data and ensure that it's accurate.
- Enhanced custom IDs: content items with custom IDs now accept hyphens, underscores, or periods, making it easier to name your content items in a way that makes sense to you.
New data modeling limits: For optimal performance, we have introduced some new limits. This will help to ensure that our platform is running smoothly and efficiently, and that you have the best possible experience.
Quantity Limit All tenants. 250,000 media items The help text of fields. 256 characters Media item description fields. 256 characters Rich-text fields. 200,000 characters Reference and media fields. 50 items Short text fields. 256 characters Long text fields. 50,000 characters Content types. 50 items All tenants. 100,000 content items
- Media transformation: both the Delivery API and the Preview API now support media transformation, giving you a great deal of control over the appearance of your media items.
- Reserved field IDs: additionally, several field IDs are now reserved, meaning they cannot be used for content types. This helps to ensure ongoing stability as you build your data model.
Better account information pane: now you can see important information about your account, such as tenant and organization details, by simply clicking the Profile icon.
- List display for Content Management API: custom fields are no longer included when displaying lists of content items and reference dialog boxes. This helps to simplify your lists and make it easier to find the information you need.