XperienCentral R47 forms the foundation for a significantly improved rich text editor. With this upgrade, essential preparations are made to ensure the smooth implementation of the new editor in the future. These changes mostly take place behind the scenes and are not yet directly visible.
Additionally, R47 includes various security updates, bug fixes, and minor improvements that contribute to a more stable and efficient platform.
Accessibility Improvements
Accessibility is an important focus within XperienCentral. In this release, a new feature has been added to further support compliance with WCAG guidelines for your website. Lead images can now be provided with alternative text, which can also be used as a caption. This functionality was previously available for image elements and has now been extended to lead images.
Basic Formatting in Login Screen
In R47, it is now possible to apply basic formatting to the announcement, which can be edited via My Settings (in the top right corner of the interface). Simple formatting, such as bold and italic, is now supported. The same applies to the company_name setting, which can be edited via the Setup tool. These adjustments contribute to better readability of the information on the login screen.
Audit trail
The audit trail now also displays changes in modular content elements and modular metadata (from both modular content types and modular metadata of pages). Previously, changes to these components were not visible in the audit trail.
GraphQL API Enhancements
Properties of modular content of the type Tag were previously not returned by the GraphQL API. The GraphQL API is primarily used for headless applications. By supporting tag properties in the GraphQL API, this information can also be utilized in headless applications.
To simplify finding content items displayed in these headless applications, it is now also possible to search for GraphQL IDs in the advanced search functionality.
Permission for Inline Editing of Page Sections
In R47, a new permission has been added for inline editing of page sections. Inline editing means that a page section can be modified directly on the page where it is used, without needing to open it first via Advanced Search or the page sections tree widget.
By default, this permission is enabled, which corresponds to the behavior before R47. When the permission is disabled, page sections can only be edited after explicitly opening them. This prevents editors from accidentally modifying a page section without realizing it is used on multiple pages.
Bug Fixes
Finally, this version includes several bug fixes. A complete overview of these adjustments can be found in the changelog of this release.
Comments
0 comments
Please sign in to leave a comment.