Rich Text Editor
docs.gitlab.com
docs.gitlab.com
We also discussed your question around embedding it. Right now, rich text editor is available in: Wikis, Issues, Epics, Merge requests, and Designs. The focus is to add it to more places in GitLab. There are no active discussions around open sourcing the rich text editor as a separate component though the source code is available.
We are gathering feedback here if you want to directly contact the folks working on this feature: https://gitlab.com/gitlab-org/gitlab/-/issues/379045
You can track progress on all the rich text editor work here: https://gitlab.com/groups/gitlab-org/-/epics/10378
(Semi-tangent: I believe the reason so many people dislike WYSIWYG editing is that they've only experienced bad WYSIWYG editing)
> There are no active discussions around open sourcing the rich text editor as a separate component though the source code is available.
Maybe you're missing the chance to make a dent here.
There's obviously a reason you built your own component: You didn't find anything satisfactory already on the market.
By providing a great solution everyone can just go and use, besides gaining you the usual open source good will, you could also increase Gitlab-Markdown's popularity. That sounds like it could be a bit of free marketing, in places you wouldn't usually otherwise reach.
Not sure if this is convincing or passes your cost/benefit analysis, but I wonder if it's something you've considered.