Curious whether y’all considered Tiptap as a base for the editor, and if so why you decided against it?
(Tiptap is what we use for Manifold/Manifund and there are definitely some warts—eg markdown not being supported out of the box, though recently I think that’s changed—but mostly I’ve liked it.)
We couldn’t find any implementation of anything like a suggested edits feature for Tiptap-based editors and didn’t want to be in the position of needing to implement it from scratch. Lexical was almost in that position, but ProtonMail’s docs (which I think maybe they acquired) are built on lexical, have a suggested edits feature, and are open source with a compatible license.
Also Tiptap was in the position of needing to support a lot of really old legacy browser behaviors, and iirc lexical made a pretty explicit design decision to avoid a lot of that for the sake of having saner internal & external APIs.
In a lot of ways, Tiptap probably would have been better—it’s certainly much more widely used, at least if you measure by “how many meaningfully-sized organizations use it in their stack” rather than “how many editors that end-users run into on the web are based on one vs. the other” (Meta uses lexical, so that’d be kinda skewed). But with the rapid improvements of LLMs for coding, I’m generally less afraid of future risks from lack of support.
Curious whether y’all considered Tiptap as a base for the editor, and if so why you decided against it?
(Tiptap is what we use for Manifold/Manifund and there are definitely some warts—eg markdown not being supported out of the box, though recently I think that’s changed—but mostly I’ve liked it.)
We couldn’t find any implementation of anything like a suggested edits feature for Tiptap-based editors and didn’t want to be in the position of needing to implement it from scratch. Lexical was almost in that position, but ProtonMail’s docs (which I think maybe they acquired) are built on lexical, have a suggested edits feature, and are open source with a compatible license.
Also Tiptap was in the position of needing to support a lot of really old legacy browser behaviors, and iirc lexical made a pretty explicit design decision to avoid a lot of that for the sake of having saner internal & external APIs.
In a lot of ways, Tiptap probably would have been better—it’s certainly much more widely used, at least if you measure by “how many meaningfully-sized organizations use it in their stack” rather than “how many editors that end-users run into on the web are based on one vs. the other” (Meta uses lexical, so that’d be kinda skewed). But with the rapid improvements of LLMs for coding, I’m generally less afraid of future risks from lack of support.