I have brought this issue up on the Strapi Community Call from last month. The devs are aware of this issue.
You can watch the video of it here: Strapi Community Call February - YouTube
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:
opened 10:57PM - 08 Feb 22 UTC
issue: feature request
source: core:content-manager
source: core:content-type-builder
## Feature request
### Please describe your feature request
- [x] **I have… created my request on the Product Board before I submitted this issue**
- This is linked to https://portal.productboard.com/strapi/1-roadmap/c/37-wysiwyg-html-editor
- [x] **I have looked at all the other requests on the Product Board before I submitted this issue**
### Summary
The current and previous (v3) WYSIWYG editor are more so basic markdown editors and while markdown is awesome (since I'm writing this feature request in markdown :smile: ) I believe there is room for improvement and we could swap the default editor shipped with Strapi for something more feature rich and complete.
There is already community options in both v3 and v4 such as CKEditor 5, React MD, Toast UI, and Editor.js I do think we should ship something more feature complete then forcing everyone to install one of the community options.
If anything we could also make it easier to swap out our editor by standardizing methods to build new editors into the Strapi interface.
### Why is it needed?
Our current editor only supports the bare minimums in terms of markdown support (eg no tables, ect) and support for things like inline youtube video previews, ect are a bit more complex to handle properly.
Likewise not all non-technical content editors are familiar or like markdown. Likewise in many frontend frameworks a library is required to convert markdown to html. I believe it could be possible to handle this type of conversion server side and maybe caching those outputs (or pregenerating them).
### Suggested solution(s)
I don't believe selecting an html specific WYSIWYG editor is a good idea because ideally as not all uses for strapi will support html but I believe the best option is to pick an editor that instead uses a more json backed structure like [Editor.js](https://editorjs.io/) as we could either build in support in SDKs to convert this format to markdown, html, whatever basically and it fits with native strapi implementations (even doing things like lifecycle modifications to the content, ect would be very easy since we could natively interface with specific parts of the content)
Ideally whatever editor we choose should be opensource and preferably have a strong plugin system itself that we could leverage. I'm not saying Editor.js should be our choice but there is **a lot of editors out there** and I think it would be cool to explore this as a community and see what everyone thinks.
### Related issue(s)/PR(s)
https://github.com/strapi/strapi/issues/10706
https://github.com/strapi/strapi/issues/9770
https://github.com/strapi/strapi/issues/8662
https://github.com/strapi/strapi/issues/4586
https://github.com/strapi/strapi/issues/3865
https://github.com/strapi/strapi/issues/3114
https://github.com/strapi/strapi/issues/2950
https://github.com/strapi/strapi/issues/1291
https://github.com/strapi/strapi/issues/8004
https://github.com/strapi/strapi/issues/6051
https://github.com/strapi/strapi/issues/2505
https://github.com/strapi/strapi/issues/978
https://github.com/Roslovets-Inc/strapi-plugin-ckeditor5
https://github.com/kwinyyyc/strapi-plugin-wysiwsg-react-md-editor
https://github.com/fagbokforlaget/strapi-plugin-wysiwyg-toastui
https://github.com/melishev/strapi-plugin-react-editorjs