Switching Rich Text Editors, Part 1: Picking Tiptap
1–10 of 54 posts
Re: Switching Rich Text Editors, Part 1: Picking Tiptap
#2I just added tiptap to our new app last week, it was a great experience compared to all other RTE libraries I've used, would highly recommend it.
Re: Switching Rich Text Editors, Part 1: Picking Tiptap
#3> "To us, Prosemirror stood out as the most powerful solution. We wouldn't have needed any third-party dependencies (except for a React integration) and would have been able to define our document schema from the ground up. We didn't go with it because it took a lot of code to get started (even the official ProseMirror guides state this) and defining our custom schema, while powerful, was not worth the effort since we didn't have many custom requirements."
Custom schema is not just powerful but also essential for cross platform rich text editing/rendering. For example most rich text editors that work really well on the web is almost always broken in some way in a native android/ios app. Why? usually we ignore the schema and dump a black box json/html as rendering format and then deal with editing issues with that format when we actually port the app to mobile platforms.
For me it makes sense to just go with markdown or a very customizable rich text schema if it's worth it - so that rich text editing works smoothly across platforms.
Re: Switching Rich Text Editors, Part 1: Picking Tiptap
#4We were using Slate at Spectrum[0] back in 2017/2018, eventually switched to DraftJS due to cross-browser issues but that was honestly equally frustrating to use and support across many browsers.
In hindsight, we should've just had a GitHub-style markdown editor: https://mxstbr.com/thoughts/tech-choice-regrets-at-spectrum
It sounds like the situation has improved since then! I'll definitely try Tiptap if I ever need to build another RTE.
Re: Switching Rich Text Editors, Part 1: Picking Tiptap
#5Ah, the joy and horror of rich text editors. I completely understand the selling points and the attraction, but I gave up on 'm for my projects. Not saying that OP must do the same, though.
I eventually settled for plain text in a simple textarea, with basic possibilities for markup by allowing Markdown. No more struggling with different browsers, no struggling with how the RTE looks and feels, no incompatibility issues with the underlying database, etc.
Still not saying everybody has the same use case as I have (no code website system), but I wouldn't trade my current peace of mind for even the best looking RTE.
Re: Switching Rich Text Editors, Part 1: Picking Tiptap
#6We were using Slate at Spectrum[0] back in 2017/2018, eventually switched to DraftJS due to cross-browser issues but that was honestly equally frustrating to use and support across many browsers. In hindsight, we should've just had a GitHub-style markdown editor: https://mxstbr.com/thoughts/tech-choice-regrets-at-spectrum It sounds like the situation has improved since then! I'll definitely try Tiptap if I ever need…
I guess that's pretty hard to get right on the first try though. Use WYSIWYG and you have to deal with all the complexity and risks that involves; use markdown with some quality-of-life features on top any you may turn off users who expect a Microsoft Word experience. Depending on the app that isn't an easy decision.
That said, I haven't had to make that decision for a long time. Markdown editors have become noticeably friendlier, perhaps the difference isn't that big anymore and I'm out of date?
Re: Switching Rich Text Editors, Part 1: Picking Tiptap
#7I've been using Tiptap for my little brand design app (https://baseline.is) and it's been awesome to work with. The guys over at Überdosis are constantly working on it making it even more powerful and you can easily bend it to your will, which is very necessary in my case since I'm using it as a part of a design tool.
I would definitely recommend it to pretty much anyone since you can adapt it to your needs.
Re: Switching Rich Text Editors, Part 1: Picking Tiptap
#8Ah, the joy and horror of rich text editors. I completely understand the selling points and the attraction, but I gave up on 'm for my projects. Not saying that OP must do the same, though. I eventually settled for plain text in a simple textarea, with basic possibilities for markup by allowing Markdown. No more struggling with different browsers, no struggling with how the RTE looks and feels, no incompatibility iss…
I try to argue for this approach as much as possible but it rarely gets through to product people.
Re: Switching Rich Text Editors, Part 1: Picking Tiptap
#9This post is actually a great way to review any library. But there are two things I’d add:
> While Google is useful, ranking in Google Search is a popularity contest, not a quality test. To be exhaustive, we started with the initial list of libraries we found back in 2019 and used the references to other libraries in their documentation to find more.
In this case NPM and GitHub search are great for this. You can also sort by many important attributes and filter by keywords.
The other point that was unaddressed is to actually read the source code. Is the source easy to understand? Depending on the library the source code might be an important source of documentation.
Re: Switching Rich Text Editors, Part 1: Picking Tiptap
#10i had no idea what ashby was or how they were using tiptap, so i clicked on the logo at the top of the page - and i still have no idea what ashby is, or how they are using tiptap!