Live data from Hacker News

Switching Rich Text Editors, Part 1: Picking Tiptap

ashbyhq.com

21–30 of 54 posts

Re: Switching Rich Text Editors, Part 1: Picking Tiptap

#21
post #13

This analysis that GitLab did was really valuable for helping me do my research on an editor architecture for my app. It almost reads like a blog post, it's an incredibly well-written issue. https://gitlab.com/gitlab-org/gitlab/-/issues/273238

And this is their current implementation, for those interested: https://gitlab.com/gitlab-org/gitlab/-/tree/master/app/asset...

Re: Switching Rich Text Editors, Part 1: Picking Tiptap

#22
post #16

Earlier quoted context omitted.

Are you sure that it's not something else interfering with TipTap? Their long demo https://tiptap.dev/examples/book which has 200,000 words was still very responsive.

That page just freezes the browser using Brave on Android.

Weird, works very responsively for me on Firefox Nightly on Android.

Re: Switching Rich Text Editors, Part 1: Picking Tiptap

#23
post #17

Very timely topic. For those of us looking for more flexible options, like for an online news publication that needs to show well placed and sized images and so on, I wonder what everyone is using that isn’t Wordpress but has the same sort of core functionality. Like for example if you wanted a Wordpress style story editor in rails is there an obvious option?

I came across react-page[1] the other day, it seemed like a reasonably powerful block editor but was too much for our purpose so I haven't actually used it.

[1]: https://github.com/react-page/react-page

Re: Switching Rich Text Editors, Part 1: Picking Tiptap

#24
Thanks for submission! Very timely. Been searching for a stable and flexible editor (or rather a tool to build such an editor) and Tiptap looks like a good candidate.

I was also considering Slate, but have found this rather annoying bug https://github.com/ianstormtaylor/slate/issues/4833, which is surprising as it doesn't look like some rare edge case, and breaks something that seems to be like basic functionality for an editor. Had to re-consider.

Re: Switching Rich Text Editors, Part 1: Picking Tiptap

#25
post #24

Thanks for submission! Very timely. Been searching for a stable and flexible editor (or rather a tool to build such an editor) and Tiptap looks like a good candidate. I was also considering Slate, but have found this rather annoying bug https://github.com/ianstormtaylor/slate/issues/4833 , which is surprising as it doesn't look like some rare edge case, and breaks something that seems to be like basic functionality f…

Slate’s poor Android support makes it a bad choice for anything but personal projects or when you can commit to only supporting English/ASCII input. Android appears to work okay for English input, but is completely broken for Chinese/Japanese/Korean or other languages that use composition or an input method editor.

Re: Switching Rich Text Editors, Part 1: Picking Tiptap

#27
post #26

What does Ashby actually do as a company? It might be my locked down corporate network but I can't find a description anywhere.

Really. I couldn't find it either for a good 10 minutes. I went through all the links painfully and got to careers and there they have some glimpse into their precious company.

>What we're building At Ashby, we’re on a mission to help professionals excel at their jobs with software. We believe current software is barely scratching the surface and the most promising productivity improvements haven’t materialized yet.

We’re starting with a suite of products that help talent leaders, recruiters, and managers excel at hiring. Prior to starting Ashby, our Co-Founder and CEO, Benji, experienced the limitations of current products first hand. This experience has created a relentless focus to solve recruiting’s toughest problems with powerful and delightful software.

Re: Switching Rich Text Editors, Part 1: Picking Tiptap

#28
> We took a chance that Slate would support more browsers and its API would remain stable (despite the maintainers strongly suggesting that both might not happen!). Unfortunately, our gamble didn't pay off, and the maintainers introduced significant breaking changes to the API and document model…

You have been warned…

Post reply on HN