Not natively, you’re right, but you can create a separate content type (for example “HTML widget”) that would include a long text field. You could then embed that into the Rich Text field.
I think it would take quite a bit of development and staff time to migrate or start using the rich text editor. We have just finished the hard sell on changing from HMTL to Markdown and I’m not sure our web editors are up for another change.
I’d still be interested in hearing from Contentful staff on the possibility of allowing Grammarly.
No, spell check wouldn’t work in the long text field that held the code, but you’d likely just have HTML/code/etc in there–nothing to spell check, per se.
I do appreciate recommending alternative solutions and we have looked at moving to rich text fields but having spell checking in long text/markdown fields would be helpful regardless. I think my (and other’s) frustration is that it’s an expected feature for creating content, this have been an asked for many times, and there haven’t been any substantial updates about it.
100% agree with Kyle - this is a serious omission and makes life extremely difficult for those of us using markdown. Using RT is not always an option when dev time is concerned. Be great to even know if this is on the roadmap in any form?