Discussed a bit on slack, wrt. potential new features that will not be possible with TinyMCE (at least without paying), namely:

Markdown support
Mermaid support
Cross-referencing (e.g. hashtag style refs to other datalab entries [believe there's an issue somewhere]).

cc @PeterKraus, @jcumby

There's then several other features that I've seen used that the new editor will need to support:

Tables
Images
Colours

The latter of which goes slightly beyond the markdown "spec" (or at least my understanding of it).

Some options I've looked at:

SlateJS: https://docs.slatejs.org/ with vue plugin https://github.com/Guan-Erjia/slate-vue3 (listed in the slate docs)
QuillJS: https://quilljs.com/ with VueQuill (https://vueup.github.io/vue-quill/) and various plugins for .md, mermaid etc. (https://github.com/quill-modules, https://github.com/quill-modules/quill-mermaid-chart)

There are quite a few others, but not many that are actively maintained.

The main issue will be migrating the fields that currently use TinyMCE to a new format, as currently we store a fairly verbose chunk of HTML of the WYSIWYG output. It would be nice to store something like Markdown instead, but migrating might be tricky, so we may need to keep two versions knocking around and still allow editing via TinyMCE, depending on how these libraries render the TinyMCE output.

Perhaps something Ben x2 could look into over September?

Migrate away from TinyMCE #1232

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions