Rich Text editors (often referred to as WYSIWYG editors) allow content creators to quickly markup/style content with easy to use buttons for things such as changing font size, bolding text, and inserting links or images. This freedom to markup/style content can also cause issues for companies when trying to keep a consistent and cohesive website with branding and styling guidelines. Changing formatting and inserting media makes it easy to violate branding guidelines, and do things the module isn't anticipating.

What's happening?

You now have the ability to customize the toolbar of rich text fields inside of custom modules created through the CLI by adding an enabled_features property to the fields.json file.

Why is this happening?

We have heard a lot of feedback from developers who wished to have this feature and we agree that this can help companies to reinforce brand and style guidelines when entering content onto their websites. It is another way for content creators and developers to further work together.

When is it happening?

This is available immediately and is enabled through the enabled_features property that can be added to the rich field’s attribute in your fields.json file. You can view more about this property in our documentation.

Can the Default Rich Text Module or Tag be configured as well?

At this time, this is only being rolled out for custom modules created through local development who utilize the rich text field. We are looking into expanding this functionality out to the default rich text module and tag as well but there is no timeline in place for this currently.

To discuss this change, please refer to our community post here.