Separate Froala editor style access

We're looking for a way to fix a problem we are seeing with styles and the Froala editor usage in page builder and in rich text fields in XbyK. When a user has access to the rich text field on a content type, they have the ability to choose options in the Froala editor that apply css classes to elements on the page. For example, a simple image with rounded corners. This looks great in the editor, but when you go to the site, the Froala editor styles are not included in the packages because that page is not a page builder enabled page so the rounded corners don't exist.

Is there a separate package or file we can include to include the OOTB Froala editor styles so we don't have to replicate them every time? I know we can modify the editor config. I know we can modify our own CSS. Those are options. I know styles may possibly be different from one site to another. If the Froala editor has those styles as part of the editor, and they are simple styles, then why not have a seperate library that we can include that is outside of the Admin interface? We don't need all of the page builder styles, just the Froala editor styles.


Environment

  • Xperience by Kentico version: [31.2.0]

  • .NET version: [10]

  • Execution environment: [SaaS]

Tags:
Page Builder v31.2.0 CSS JavaScript
0

Answers

To response this discussion, you have to login first.