Spell checking is disabled for rich text fields

[dandv]

I've just installed Strapi with npx create-strapi-app my-project --quickstart and created a Content Type for an Article, with a content Rich Text field. While editing it in Chrome 77, I'm surprised to see that spell checking is disabled. Do I need to enable a setting somewhere? We're considering Strapi to manage our blog posts (served via Gatsby), and spell checking is an essential function.

[dandv]

After using the rich editor some more, I've noticed there are no scrollbars, no synchronized scrolling, and generally, the experience could be much better if Strapi integrated the excellent StackEdit markdown editor, and side-by-side editing was the default.

Any thoughts on that? There's a very easy adoption path with stackedit.js, which can be bound to text areas, or the Rich Text editor can be StackEdit.

[soupette]

@dandv we are aware that the current WYSIWYG could be improved. However we are under active development of others features like the dynamic-zones. However, we the release of the beta.17 we have added a new feature which allows you to develop inside the administration panel so changing the current WYSIWYG has never been easier so you can easily the StackEdit markdown editor to your project.

Feel free to DM me on Slack if you need guidelines on how to do it.

[soupette]

BTW, here's a link on how to change the WYSIWYG.