I am trying to port a fairly simple website to Backdrop. In that site, I use Field Extra Widgets which is a tiny utility module that simply adds two options for the edit form of fields: "hidden" and "read-only". This is for cases where one needs for example to provide a default value for a field, but wants to either prevent users from changing it when creating/editing the content or hide it out of their way (so that the form is not cluttered).
I am confident that I can port this module to contrib so that I can use it in this specific Backdrop-converted site, but I believe that such a tiny feature would be of value to core (it will be another thing to brag about Backdrop 1.5.0 in the DrupalSouth talk I might give ).
So, do I port it in contrib and see if we can merge it in core at some point in the future? ...or do I (please) get some guidance to add these small but very useful features in core now(-ish)?
Recent comments
Thank you both for your suggestions. Yeah, I'll give TinyMCE a try... better than trying to fight that behemoth CKEditor 5. The TinyMCE page says it can "co-exist with CKEditor" which is...
Specific tags to work in CKEditor 5
The specific tags I need are "<ruby>" and "<rt>" Wow, yeah, that's a pain with CKEditor5. A custom plugin, for sure, but no clue, what the code has to look like...
Specific tags to work in CKEditor 5
I think maybe the problem is with CKEditor stripping the tags - it can be more aggressive than what you would expect from the text format settings. I copied your examples into an example page...
Specific tags to work in CKEditor 5