Customizing built in rich text widget

All the details are in the docs

• Rich text editor configuration
• Rich text editor plugins
• Rich text editor customization

If you are having trouble finding something in the documentation, use the AI chat widget in the bottom right corner of the docs pages. Ask it a question about a topic and it will like to the sources of information it provides.

Thanks Sean. I have read through the docs, and spoken with AI, and nothing indicates that we might be able to create custom properties for the rich text widget. I was hoping someone here might have some other insight.

Maybe I'm misunderstanding what you mean when you write "custom properties". Can you link to something in the Froala docs or examples that show how you see custom properties working?

Widgets can have properties so the content editor can configure them. I want to give the rich text widget some custom widget properties so the editors can make adjustments that will be reflected in the rich text editor view when it outputs the content.

Ahh!

You want to extend the existing Rich Text widget! That is possible and you can follow the docs on extending a widget.

For example, if you wanted to wrap the rich text widget in some specific design or layout you can adjust the rendering of the view file for your extended widget and then render the existing widget inside your new markup.

The extended widget can have as many custom properties as you want and you aren't limited to just supplying a custom properties class and a view - you can use a full view component. Just take a look at the FallbackFormWidget in the Kentico Community Portal.

But with this method, I am still creating a new widget which would result in 2 rich text widgets. One with extended properties, one without. I want to extend or override the existing one, so I only have one rich text widget in existence.

There is no way to add properties to the built-in widgets (or any widget provided through a NuGet package) without extending them to create a new widget.

My recommendation is to extend the built-in rich text widget and apply widget redirections to your <editable-area> or <widget-zone> tag helpers to exclude the built-in one.

Widget and section restrictions are a good practice anyway and they are easier to adopt at the beginning of a project than later on when marketers have used all kinds of combinations of widgets and sections across the various pages.