[HN Gopher] Launch HN: Tiptap (YC S23) - Toolkit for developing ...
___________________________________________________________________
Launch HN: Tiptap (YC S23) - Toolkit for developing collaborative
editors
Hi HN! We're Nick, Patrick, Philip, Sebastian, Sven, and Timo from
Titap (https://tiptap.dev/), an open source developer toolkit for
building collaborative editing apps. Our editor framework, based on
ProseMirror, is at https://github.com/ueberdosis/tiptap, and our
real-time collaboration backend, based on Yjs, is at
https://github.com/ueberdosis/hocuspocus. Building editor
interfaces like Notion or Google Docs in your web app takes a lot
of work and time. Our open source tools and cloud services let you
build collaborative content editing faster--in days or weeks,
rather than months or years. And this is just for the editor. If
you want real-time collaboration or other advanced features like
version history in your editor, the overall workload quickly
escalates--you will need a robust and serious backend
infrastructure that requires even more time to set up and maintain.
This doesn't make sense for most frontend developers or most
startups. We spent eight years as a digital agency developing
applications with complex content editing functionality. We learned
the hard way how limited the existing editors were. After building
Tiptap as a headless editor framework with an extension-based
architecture, we needed to allow multiple users to edit content
simultaneously, which got complicated. There was no simple solution
that could be integrated quickly. So we built that too. The Tiptap
editor is based on the JS framework ProseMirror, which is a good
foundation for editors. The learning curve for ProseMirror is steep
because it's complicated to understand and lacks simple APIs and
documentation. It takes a lot of code around ProseMirror to develop
a modern user experience. We've taken care of that for you. Tiptap
is headless, so it will work with whatever frontend or design you
have in mind--we make no assumptions about your UI. You can use it
to develop block-based editors like Notion, classic interfaces like
Google Docs, or whatever you need. It's also framework agnostic, so
you can use it with React, Vue, etc., or vanilla JavaScript. And
it's highly customizable through our extension architecture. We
also provide an API to access ProseMirror's internals through
Tiptap if you want to dig deep into the core. Adding real-time
collaboration to your editor is as easy as installing and
configuring an extension. Our collaboration backend, called
Hocuspocus, uses Yjs. This is a widely used implementation of CRDTs
(conflict- free replicated data type). Hocuspocus makes it easy to
set up a Node.js websocket server to handle communication between
multiple peers to synchronize data. Like the Tiptap editor,
Hocuspocus is designed to be extensible according to your needs.
Also, Hocuspocus can work independently of Tiptap with other
editors like Lexical or Slate. An earlier version of Tiptap got
discussed a couple years ago at
https://news.ycombinator.com/item?id=26901975. We've been enjoying
wider adoption since then. For example, Substack uses Tiptap for
their editor that allows creators to write content on substack.com,
and YC uses Tiptap in their Bookface forum (which is basically HN
for YC alums). With the Tiptap Cloud, we offer managed backend
services if you don't want to build and maintain every feature
yourself. For real-time collaboration, we provide a cloud
infrastructure with multiple datacenter regions where you can
deploy Hocuspocus. The Tiptap AI integration beta is a service
where you connect your OpenAI API key to our backend and install
the Tiptap editor AI extension to get AI writing experience in your
editor. Here's a demo: https://ai-demo.tiptap.dev/ We invite you
to explore Tiptap's capabilities in your app, contribute to its
open source development, and (hopefully!) join our welcoming
community. We'd love to hear what you've already built with Tiptap
or what's stopping you from creating something with it :-) We look
forward to all of your comments!
Author : philipisik
Score : 142 points
Date : 2023-08-01 15:24 UTC (7 hours ago)
| dimmke wrote:
| I use Tip Tap in SvelteKit and I like it a lot. I'm really glad I
| chose it over Lexical and other options. Congrats on the recent
| YC funding! Nice to see a player in this space that isn't from
| Facebook/React dominant.
|
| The only issue I have encountered with it that I haven't solved
| yet (I think there are multiple potential paths) is
| validating/sanitizing data with it.
|
| To parse the content and turn it into raw text requires
| instantiating TipTap and all the attendant plugins. So even if I
| want to do a server side check for something like minimum
| character count, I have to 'decode' the JSON etc...
|
| I know it's not the focus, but something that makes that easier
| would be nice. And something I could easily add to a Schema
| checker like Joi or Zod.
| danielvaughn wrote:
| I also liked it a lot, though I used it in React and had a bit
| of trouble with getting it to play nicely with useEffect.
|
| I see that as an issue with React though, not TipTap. It's a
| great editor and I love that it's headless.
| nbashaw wrote:
| Curious what issues you ran into?
| danielvaughn wrote:
| My memory is hazy since it's been a while, but I
| implemented collaborative editing in TipTap using YJS. This
| requires coordinating editor state with a socket interface
| and I had to use a bunch of useEffect trickery to make sure
| the state didn't get out of sync. I'm afraid I can't
| elaborate further, but I will say that I'd highly recommend
| TipTap if you want to build collaborative editing. Once I
| got it working, it worked perfectly.
| brigadier132 wrote:
| > I'm really glad I chose it over Lexical and other options.
| Congrats
|
| Do you mind expanding on this? I've been comparing the two and
| found the lexical data model easier to understand.
| dimmke wrote:
| I'm going to be honest, I did this evaluation several months
| ago and I don't remember all of the exact points. If I
| remember:
|
| * I did not like that it was an alternative to a different
| Facebook rich text editor (draft.js)
|
| * Very React focused (makes sense, it's a Facebook/Meta
| project) - even applying concepts. Here's an excerpt from
| their site: "If you've used React Hooks before, you can think
| of $ functions as being something that follows a similar
| pattern. These are functions that show their intent as to
| where they can or cannot be used."
|
| I don't want to use React Hooks or things designed to be like
| React Hooks.
|
| * Newer and less features/polished. Looking at their official
| project site, there's way less features already available.
| That means more custom code you have to write.
|
| * No standard schema/for formatting rich content
| egonschiele wrote:
| Have you tried using Lexical? I found it to be very buggy and
| ended up replacing it with Quill.
| JimDabell wrote:
| It doesn't include Lexical, but GitLab did a detailed
| comparison of rich text editors a while back and settled on
| Tiptap. Their write-ups are pretty detailed:
|
| https://gitlab.com/gitlab-org/gitlab/-/issues/231725
|
| https://gitlab.com/gitlab-org/gitlab/-/issues/273238
| patrickbaber wrote:
| Thanks for the links to the discussion, I wasn't aware of
| it. Seems like a nice long read and find out what others
| think about us. I will read it.
| steventey wrote:
| Tiptap is incredible! Built https://novel.sh/ with it and the
| extensiveness & API is _chefs kiss_! So proud of you guys and the
| YC funding is truly well-deserved! Congrats again!
| patrickbaber wrote:
| Thank you for contributing to our community with your pretty
| slick editor. We love seeing all these different UIs out in the
| wild. It's the goal with our headless approach to be as
| flexible as needed. I like your AI integration. This is all
| just the beginning of AI-based content editing.
| mercurialsolo wrote:
| Are these editors mobile responsive? Or is this something you see
| more as being used for desktop / cloud based editors?
| jitl wrote:
| Marijn, the ProseMirror author, does an excellent job building
| fully responsive frameworks. Out of the ContentEditable
| libraries I've tested, ProseMirror did the best on Android,
| which is the most challenging platform to support. His
| CodeMirror is by far the best code editor for mobile too.
| Monaco, the VS Code editor component, is pretty broken on
| mobile.
| timoisik wrote:
| I was just about to write the same thing. Adding here, the
| headless approach allows you to optimize your editor for
| mobile pages from a UI perspective.
| ngc6677 wrote:
| Note: https://github.com/yjs/yjs for collaborative "document
| edition, and user cursors"; has WebRTC, web socket, matrix.org
| backend
| eggbrain wrote:
| I think TipTap is really cool (and congrats on the launch!), but
| I hope you won't begrudge me a worry:
|
| I see from your home page and pricing page
| (https://tiptap.dev/pricing) that you've switched from wording
| that says "You are free to do whatever you want, TipTap is
| licensed under MIT" (with support for premium paid plugins), to
| TipTap being free* (no Credit Card required), and no mention of
| the MIT license.
|
| This makes me extremely worried that you are eventually going to
| go the TinyMCE / Froala / CKEditor route, which has made me very
| hesitant to now use these editors.
|
| I completely understand that WYSIWYG editors are extremely hard
| to maintain, but on the flipside I now am worried about all the
| projects I've added / started to add TipTap to. Can you help
| assuage this worry? Will the core plugin remain free and MIT
| licensed forever, and not reliant on some sort of usage model
| outside of premium plugins?
| timoisik wrote:
| The core of Tiptap (https://github.com/ueberdosis/tiptap) will
| remain free and under MIT license. Thanks for your feedback on
| the pricing page here!
| jitl wrote:
| Can you explain more about how Tiptap's concepts extend or
| replace ProseMirror's concepts?
|
| A few years ago I evaluated rebasing Notion's editor on various
| editor frameworks. ProseMirror came out at the top of my list,
| but I wasn't sure how to rank TipTap.
|
| Having more batteries included is good, but I've found that
| layers of abstraction can really get in the way. For example if I
| need to fix a bug with Android Gboard input, without a framework
| I can exactly control the DOM structure and input handling, but
| the downside is no one fixes the bug for me. With ProseMirror,
| I'd need to tunnel through 1 layer of abstraction and/or patch 1
| layer of abstraction. With Tiptap, maybe I'd need to fork-and-
| patch both you and ProseMirror? Each layer also increases our
| maintenance liability. If the ProseMirror author decides to
| retire or take the library in a direction that doesn't work for
| us, then we need to fork and maintain it. If both you and the
| ProseMirror do that, we have more code we need to maintain.
|
| Ultimately I decided adopting a library was too risky, and opted
| to improve our native ComtentEditable handling. Because our
| product's selling point is an editor, we want to control our own
| destiny.
|
| For others who can afford a library but still need to weigh the
| risks of that abstraction stack, can you share some insights?
| patrickbaber wrote:
| I can definitely see your point. How many layers do you really
| need to get a practical abstraction, and how many layers are
| too many moving parts?
|
| With Tiptap we are trying to make it easy to build modern
| editors. The demands on the usability of an editor are getting
| higher and higher because of tools like Notion. Building a tool
| like this from scratch is pretty hard. That's why we used
| Prosemirror as a solid foundation, but in our daily work of
| developing editors for our projects we came to the point that
| we really need an additional layer of abstraction to reduce
| recurring code that you don't want to write over and over
| again. Yes, with our layer we made some decisions about how an
| editor framework should behave, but with our extension-based
| architecture in Tiptap, which ProseMirror also has, you can
| extend both layers separately.
| practal wrote:
| I think if the editor is a core piece of your app, you cannot
| really outsource it. After looking at lexical, ProseMirror,
| CodeMirror, etc., I am currently rolling my own. Your comments
| from last year (https://news.ycombinator.com/item?id=31815209)
| are helping a lot with that!
| dimmke wrote:
| I'm not part of the TipTap team but I think I can help answer
| this.
|
| Think of it like this... you're basically only coupling
| yourself to ProseMirror. That's the schema you're storing in
| your database. TipTap is a set of libraries that you can use
| for your web app etc... but if you ever find it insufficient,
| you're free to role your own thing.
|
| ProseMirror has been around for a long time and is unlikely to
| be going anywhere, but having a company with VC funding using
| it as its base helps ensure that if ProseMirror got abandoned,
| it'd likely get picked back up by TipTap or some other
| interested party.
|
| Even if you're building your own editor, unless your editor has
| a need that ProseMirror's schema doesn't account for or solve
| it makes sense to use it.
| jamesjyu wrote:
| We've been happy users of Tiptap at Sudowrite, and recently
| finished converting 1M+ documents from Quill (with Firebase) into
| Tiptap (with self-hosted WS Hocuspocus), running admirably @ 50
| updates per second. Happy to answer questions on how it's been
| going.
|
| (psst, we're also hiring!)
| timoisik wrote:
| That sounds awesome! Would love to hear more about how you set
| up the migration.
| thecodrr wrote:
| We have been using Tiptap in production for more than a year in
| Notesnook[0]. Glad to see it finally launching here on HN!
|
| We have had quite a long and rough ride in search of a stable
| rich text editor. We began with Quill.js then migrated to TinyMCE
| and then finally settled on Prosemirror. Unfortunately,
| contenteditable is still absolutely horrible on web browsers,
| especially mobile ones.
|
| Tiptap is a good choice if you are looking for a framework
| agnostic and thin abstraction over Prosemirror. However, if you
| are primarily working with React you should go with Remirror[1].
| Tiptap's APIs are heavily inspired by Remirror (almost a
| duplicate in some places). Remirror takes the edge on the
| maturity and stability of the API and extensions. The sheer
| number of utilities offered by them to simplify Prosemirror's
| APIs is astounding. And trust me, you will need a lot of those
| utilities eventually. Prosemirror is not an easy API - really,
| really well designed but not easy.
|
| In the end, though, its Prosemirror that's doing all the heavy
| lifting. And no matter how many abstractions you put on it, you
| will have to get really, really close in with Prosemirror's
| internals. Tiptap or Remirror do not make that any easier or
| harder aside from the initial bootstrapping.
|
| [0] https://notesnook.com
|
| [1] https://remirror.io
|
| ---
|
| Edit: almost forgot this but the only real selling point of
| Tiptap is their extensive documentation.
| jitl wrote:
| Did you use Remirror? Both Remirror and Tiptap? Or you just
| investigated Remirror before landing on ProseMirror + Tiptap?
| thecodrr wrote:
| No. I found Remirror quite a while after Tiptap while
| searching for a more stable React Node View implementation.
|
| The good news, though, is that it's really simple to mix and
| match Tiptap and Remirror since both of them use Prosemirror
| internally.
| patrickbaber wrote:
| Thank you for your honest feedback. Our goal is to make
| ProseMirror with Tiptap even easier to use. The demand for
| modern content editing continues to grow. Tools like Notion
| have raised the bar. We don't want to hide ProseMirror, we want
| to complement it.
|
| We believe that a good editor needs not only a frontend, but
| also easy-to-use backend services that we try to integrate as
| seamlessly as possible. With our framework-agnostic approach,
| we support more than just React.
| egonschiele wrote:
| I wish the cheapest non-free tier was cheaper, but I totally
| agree that building an editor with all the features listed is
| very time consuming. I love that you are working to tackle this
| issue!
|
| If I had one request, it would be instead of making me jump from
| $0 to $150 a month, have a usage-based model similar to OpenAI or
| Firebase, with functionality so I could cap costs to say $15 a
| month.
| tiptapsebastian wrote:
| Thank you, this is valuable feedback for us and you're not the
| first to say so.
|
| To be honest, we're still thinking about pricing and I'm sure
| there will be updates in the (hopefully near) future.
|
| Personally, I'm a big fan of usage-based pricing because it's
| the fairest approach. We are also thinking about splitting the
| price tiers into different modules, e.g. for OpenAI
| integration, collaboration, maybe support and so on. I said
| "hopefully in the near future" above because it's going to be a
| huge amount of work for us to change that (for example, we have
| to change our payment provider) and we're currently focused on
| other things like implementing new features that our users are
| asking for most.
|
| What do you think about module-based pricing (in combination
| with usage-based pricing)?
| egonschiele wrote:
| Module-based would be ideal. For context, I'm building a
| writing app. I have basic functionality + OpenAI integration,
| but these things have been a huge pain:
|
| - collaborative editing
|
| - offline editing
|
| - faster loads with sw caching
|
| - git history
|
| - end-to-end encryption.
|
| It's taken me forever to build these, and the code's still
| not where I want it to be. If you had modules for these that
| I could pay for, I totally would.
| rubenfiszel wrote:
| > The Tiptap AI integration beta is a service where you connect
| your OpenAI API key to our backend and install the Tiptap editor
| AI extension to get AI writing experience in your editor. Here's
| a demo: https://ai-demo.tiptap.dev/
|
| Congrats, any plan on supporting code/monaco and autocompletion?
| We had to rebuild it ourselves on top of yjs and gpt4 for
| windmill.dev and would have happily built it on a service if it
| existed.
| patrickbaber wrote:
| Tiptap AI is still in it's early stages and we are constantly
| thinking about how to improve the DX and UX. Autocompletion for
| text is already working quite well. Our next goals are
| streaming support for all commands and providing a SDK. Tiptap
| is primarily a framework for text editing, but we'll definitely
| keep an eye on your use cases.
| TechBro8615 wrote:
| Congrats on the launch. I just want to say that I love the name
| :) It's fun, memorable, evocative of the product's purpose, and
| rolls off the tongue.
| JDLongley wrote:
| I've been using TipTap to build my side project
| https://liftnotesapp.com/
|
| The APIs and AST syntax have been very straightforward to work
| with. Congrats on the launch!
| thepaulmcbride wrote:
| Will schema versioning be coming to hoscuspocus or will this be
| locked behind a paywall? We've sponsored tiptap for a while now
| and I'd hate to be locked out of features because we need to self
| host.
| timoisik wrote:
| Schema versioning is something I would really like to see in
| Hocuspocus, but it is currently not scheduled. So it will be a
| while before we tackle this topic. Currently we are building
| version history so that you can have a Google Docs-like history
| of your documents. Version history will not be available in the
| freeplan.
| samcgraw wrote:
| Congrats Tiptap folks!
|
| I was just playing around with Tiptap last week and build a (very
| dumb) AI rephrasing app here: https://authored.co. Took a bit to
| get used to the ProseMirror API, but was a fun experience!
| TheProTip wrote:
| Currently using TipTap as a higher level abstraction on top of
| ProseMirror. Mostly for the React node view support which works
| very well. I try to implement most other stuff as straight
| ProseMirror plugins.
|
| Shameless plug for some ProseMirror FOSS ecosystem contributions
| I've recently made:
|
| A commit-based collab plugin that's far more performant under
| heavily active client loads than stock. I'm a fan of YJS, but not
| a fan of state-based CRDT layer on top of ProseMirror for my use
| cases. Wrote about this here:
| https://stepwisehq.com/blog/2023-07-25-prosemirror-collab-pe... .
|
| I also translated the core ProseMirror projects of model,
| transform, and test-builder to C# so you can build robust
| backends in a C# monolith. All tests on those projects have been
| translated as well. Wrote about this here:
| https://stepwisehq.com/blog/2023-07-17-announcing-prosemirro... .
|
| Hope to release more FOSS projects along the way; lot of taking
| from ProseMirror compared to what's given back IMHO(not targeted
| at TipTap which provides a lot of value). I've got some stuff
| geared towards minimizing keystroke-to-paint latency which I hope
| to write about soon. Ideally we will reach a point where we
| contribute funds to the ProseMirror project.
|
| Cheers!
|
| _ducks_
| patrickbaber wrote:
| Thank you for your open source contributions and in-depth
| articles. We think that the field of collaboration is still new
| and evolving. Because of the pros and cons of the different
| implementations, we think it might be a good idea to have the
| choice between libraries like Yjs and Automerge. Would you use
| it?
| TheProTip wrote:
| Would I use Automerge? Hopefully this isn't TMI :)
|
| I think it would need to clearly be worth the cost. I'm
| having a hard time imagining use-cases my users would have,
| and matter enough, that would necessitate it over the commit
| based backend..
|
| I spent quite a bit of time as an FTE building out a robust-
| ish and efficient Yjs backend POC. This included refactoring
| the ProseMirror Yjs bindings into a proper TypeScript
| project, and specializing them for some funky use-cases. At
| the end of it all my personal takeaways were:
|
| * State-based CRDT isn't great when you _want_ a central
| authority in the mix anyway and are fundamentally trying to
| work with operations
|
| * The exchange rate between ProseMirror's currency, steps,
| and some other replication strategies building blocks is too
| high
|
| * ProseMirror should add the concept of range-relocation to
| its mappings; this is a bit of an aside but it would help
| retain user intent when reconciling concurrent edits involved
| in block relocations
|
| As a concrete example for others imagine a knowledge base
| editor. You want allow certain users ONLY to comment and you
| want to enforce this on the backend. There are a number of
| ways this could be implemented but you may want the UX of
| optimistically allowing them to make that edit in the FE and
| then submit the ProseMirror steps to the backend. This will
| typically involve two fundamental ProseMirror steps(of which
| there are only a few) to set an attribute and set a mark on a
| node range.
|
| You can relatively easily inspect the submitted changes to
| verify only the allowed operations are occurring, and
| authorize the user for them.
|
| However Yjs just cares about syncing state so the documents
| end up equivalent, and its efficient diff format doesn't
| really have the info you'd need to determine what's going on.
| You'd need to have the actual document model loaded, and then
| diff the docs before/after to figure out exactly what
| happened. And/or patch into the Yjs binding diff algorithm
| which works surprisingly well but doesn't produce minimal
| changes and can often "over edit" the document model.
|
| So something that was relatively simple with ProseMirror
| steps has become a huge thing with Yjs. And for what?
|
| All that to say, Automerge is supposedly operation based so
| _in theory_ it sounds like a better route for use cases
| involving a central authority(which is most if I 'm
| speculating) and want to do extra processing on document
| operations.. But it'd need to bring a lot to the table to
| offset the time investment..
| warthog wrote:
| We started using Tiptap recently and was surprised that it was
| not a brand new solution! We like it very much so far
| meagher wrote:
| Since Tiptap is built on top of ProseMirror, do you contribute
| funds to support ProseMirror's development?
| patrickbaber wrote:
| Since the last few weeks we are focusing on the development of
| Tiptap. We definitely want to have a solid foundation, so we
| will support the projects we rely on. Without their work,
| Tiptap wouldn't be possible.
| jstummbillig wrote:
| [flagged]
| dang wrote:
| Whoa, can you please make your substantive points without
| breaking the site guidelines? You broke these:
|
| " _Converse curiously; don 't cross-examine._"
|
| " _Assume good faith._ "
|
| If you wouldn't mind reviewing
| https://news.ycombinator.com/newsguidelines.html and sticking
| to those rules, we'd be grateful. I took a quick look at your
| previous comments and didn't see any pattern of guideline
| breakage (thank you!), so this should be easy to fix.
| meagher wrote:
| I was just curious given that ProseMirror is used a lot and
| doesn't seem that well supported financially.
|
| > We are all constantly building products on other products,
| given a license that allows for that, without contributing
| work or money to the products.
|
| This type of attitude is pretty harmful for open source.
| Folks (especially companies) should support their key
| dependencies where they can.
| jstummbillig wrote:
| I don't think that is true but in any case: Honoring the
| license, which we are usually we particular around here,
| has to be enough on both ends. The license is up to the
| licenser. White knighting around it on an arbitrary per
| case basis is just awkward.
| jahewson wrote:
| What about Yjs?
| danielvaughn wrote:
| TipTap uses YJS under the hood for conflict resolution.
| patrickbaber wrote:
| Yes, our collaboration backend Hocuspocus uses Yjs.
|
| We know the technologies we rely on, but we also know how
| important it is to find a sustainable way to maintain an
| open source project. For a popular project that a lot of
| other people rely on, this means getting money for
| development. Since Tiptap is also open source, we can see
| how the big players are using our project, and sponsor tiny
| amounts or nothing. We try to do it better than they do,
| because open source is definitely in our DNA, as it was in
| our previous work as a digital agency, and now since a few
| weeks with our focus on Tiptap.
| bloomfieldj wrote:
| Woah, congrats on launching here!
|
| A friend of mine has been using TipTap extensively with his web
| app and convinced me to look into it a few months ago.
|
| Word doc imports and exports are a really important piece for me
| and I saw they're in the "Proof of Concept" stage of your idea
| pipeline.
|
| Do you have any idea when this'll be ready? I'd be happy to help
| test the feature if it can help!
| timoisik wrote:
| Top priorities are currently Collab + Version history in collab
| and improving AI integration. Word doc import and export is one
| of the next features we definitely want to tackle, but we don't
| have an exact timeframe yet. I would love to see what you are
| working on and how you would use word doc import and export.
| csallen wrote:
| You raised money. Does that mean you're going for a billion
| dollar exit? What does that path look like, exactly?
|
| Related, I recently started rebuilding the post editor on
| IndieHackers.com to use Tiptap. Enjoying it so far. I wish your
| documentation had a few more examples, and better English in some
| places. But its high quality was part of what attracted me to
| Tiptap in the first place. I'd love to see y'all continuing to
| iterate and improve on it!
| jackfischer wrote:
| We used TipTap to great effect in an old iteration of our product
| at credal.ai. It helped us create nuanced text tagging behavior
| without too much time investment. Would happily recommend it.
| YousefED wrote:
| Congrats on the YC funding and the launch! I've enjoyed building
| https://www.blocknotejs.org on top of TipTap / Prosemirror.
|
| fyi, BlockNote aims to be a bit more batteries-included (comes
| with UI and block-based editing) - in case headless text-editing
| libraries are a bit too much work / steep learning curve.
| patrickbaber wrote:
| Thanks! We've already found your great project and we're proud
| to have such a strong community. It's definitely a valid
| approach to include more batteries. We have been asked many
| times if we will provide a UI. Right now we're going the
| "headless path", building more features independent of the
| exact UI and backend services to improve the editor experience.
| qwertox wrote:
| About three years ago I was looking for an editor and while
| TinyMCE was the absolute best, its pricing model was as bad as
| CKEditor's, so I ended up testing Tiptap in a Vue project.
|
| It's really a great and flexible editor, with a couple of rough
| corners, but overall the only serious alternative to the above-
| mentioned editors. And since it has a sensible licensing model it
| is an overall good choice.
| patrickbaber wrote:
| As we continue to improve Tiptap, we would be interested in
| more details about the "rough corners". Do you have any
| examples?
| qwertox wrote:
| The main problem had to do with fields inside a custom
| component not updating the tree (document JSON?) properly.
| These components could be nested, they had each a title and
| another variable-content field into which other components
| could be nested into. The title was a div.contenteditable and
| I had a hard time getting it to sync with the tree, some
| components were never able to do this.
| https://imgur.com/a/qKg9UUs (SFW, apparently imgur has a new
| policy?)
|
| It might be somewhat similar to the "details" extension, but
| they were also drag and droppable. The drag and drop support
| was also somewhat subpar compared with TinyMCE, I ended up
| using vue.draggable.next to solve the issues, but this added
| a layer of huge complexity.
|
| Then there was an issue that the UniqueID is a Pro extension
| and it would have been required for properly storing the
| document. I now see that pro extensions are free, after
| registration, but I'm not sure if it was always like this, I
| think it was coupled to a GitHub sponsorship back then (maybe
| around August 2021). For a side project which would then sit
| at rest for some months this wasn't feasible. I think I
| implemented a custom UniqueId to get around this, but I
| haven't touched the project for over a year.
|
| About 2 months ago I was thinking about rewriting it in React
| and see if I could turn it into something, but I haven't
| found the time.
| ksajadi wrote:
| We use Tiptap with vanilla React and it's great. My only wish is
| for it to have collaborative support beyond JS. Currently support
| for YJS is very limited if you are not using or can't use JS for
| the server component.
| timoisik wrote:
| For now, you could run Hocuspocus as a separate service and
| write an extension that connects to your application. In our
| Cloud (https://tiptap.dev/cloud) we send webhooks, so you can
| process changes or store documents on your side as well.
___________________________________________________________________
(page generated 2023-08-01 23:00 UTC)