Hello, I’m new to the Strapi world. So far I am very impressed by it. I am eager to start offering clients development on Strapi and not have to use WordPress as a CMS.
One of my resistance from offering Strapi to clients is the behavior of the Default Rich Text Editor. The Strapi v4 default Rich Text Editor field needs improvements.
Just like v3 the default mode is set to markdown and when in preview mode the user can’t edit the content directly. There is the option to expand to have a side by side view of both modes, but it’s redundant. I’m curious why there was a decision for it to have this behavior?
One of the main uses for a CMS is to allow a non-coder the ability to edit the content of a website without having to deal with code. Although markdown is rather easy to understand, it’s still code and general users of the CMS shouldn’t have to see the markdown code.
Having a simple user-friendly Rich Text Editor WYSIWYG is important to any CMS.
Is there any plans to change the default behavior to start in preview mode and allow editing in that mode?
They essential said they are not prioritizing changing it at the moment. There is third party integrations available for the time being. They plan to work on changing the default rich text editor this year at some point.
There is feature request on this issue on their github repo. You can add to the discussion there:
Hello Everyone!!
As you mentioned before, Strapi Text Editor has a Markdown Mode, as well as a Preview Mode. Everything looks fine inside the Strapi Text Editor. The thing is that anytime I write something using html tags in the Text editor, the view on my browser is still showing the html tags. Does anyone know why the text appear with the html tags in my front view?
There is now an official CKEditor 5 integration as a Strapi Custom Field. It should be the most feature rich integration. The CKEditor team plans to make more updates to it.