Replies: 3 comments 4 replies
-
Without having looked into the options and what fits the use-case the best, from a consistency perspective, I'd go with the same stack as DA. That makes it easier to track issues, bugs, enhancements, onboarding from one to the other as necessary etc. |
Beta Was this translation helpful? Give feedback.
-
To help with the comparaison attaching stackblitz demos. prosemirror: https://stackblitz.com/edit/basic-prosemirror?file=index.ts lexical: https://stackblitz.com/edit/lexical-vanilla-js?file=src%2Fmain.ts TinyMCE: (MAS Studio implementation, WIP): https://github.com/adobecom/mas/blob/main/studio/src/rte-editor.js |
Beta Was this translation helpful? Give feedback.
-
some internal comparison https://wiki.corp.adobe.com/pages/viewpage.action?spaceKey=AEMSites&title=Rich+Text+Editor+-+Evaluation |
Beta Was this translation helpful? Give feedback.
-
Hey, for m@s project we had to go with some RTE choice and took TinyMCE as it was universal editor's one at that moment. Now it's very likely it will change to some other one at some point, and there are complaints about its usage of iframe (cc @yesil :) )
Aside from that, had a chat with @auniverseaway that has picked prosemirror for document authoring.
I've heard about quill, lexical, and i will learn about others as well i guess
we will have to develop a few more plugins soon, and i would like to poll if by any chance we could all agree on one RTE of choice. Beside the fact we may reach at some point a unified admin ui, developing plugins for RTEs takes time (ramp up & pure dev), and i guess we would benefit from not scattering our efforts.
Beta Was this translation helpful? Give feedback.
All reactions