Under Community Review

We will review this as part of our Experience Space UI extensibility roadmap. 

Allow custom CSS styles for rich text in Experience Space

We need to add custom css classes to rich text content in content manager.  Our editors routinely apply custom css classes to WYSIWYG content in CMS.  The custom css classes will drive how/when the specific content is displayed in the website.

In classic view, we are able to edit this file: [Tridion Root]\Tridion Sites\web\WebUI\Editors\Base\Configuration\FormatAreaStyles.css.  The custom css class names will appear in the "Style" dropdown:

Screenshot of Tridion Sites classic view with the 'Style' dropdown menu open, showing a list of custom css class names such as btnDefaultLrg, btnGrayMed, and h1-pseudo.

However, the feature is no longer available in the Experience Space now. So PLEASE include the feature in Experience Space.

Merry Zhong

  • Without FormatAreaStyles or equivalent method of customization will make Experience Space unusable. We use it to add features to allow editors to apply custom table style classes, custom functionality for Footnotes, Custom Icons in rich text and translation markup. How do  you plan to support customization in Experience Manager without FormatAreaStyles?

  • This is such a critical feature for accessibility -- the pseudo classes enable us to keep the headings in semantic order but visually style them in a way that meets our designer and editor needs. Please restore this critical feature so that we can continue to reach WCAG 2.1AA compliance and create accessible content for our many users.  Thank you!!