Help Us Improve Tiptap: Share Your Feedback #7351
Replies: 6 comments 12 replies
-
|
The documentation around Node, Mark and other primitive sucks. there is no clear explanation of different use cases. You need to go through existing tiptap extension to figure out how to do stuff. |
Beta Was this translation helpful? Give feedback.
-
|
Loving Another suggestion: add a built-in way to mark/label streamed text (via Thanks for the great work; keep crushing it! 🚀 |
Beta Was this translation helpful? Give feedback.
-
|
Please make AI toolkit cheaper and acessible without going through the Sales team. Especially for AI toolkit features that do not depend on Tiptap cloud like Review changes should be part of the |
Beta Was this translation helpful? Give feedback.
-
|
I would love for list nodes to still have capability to be dragged and dropped as individual nodes. They're nested right now so grouped together when trying to drag around. I am going to look at re-doing this myself with a custom extension and can send over if interested. |
Beta Was this translation helpful? Give feedback.
-
|
Pages is really impressive, but there isn’t much documentation about what’s possible. We’re building a product whose main use case is turning written entries into printed books. We’re not relying on Pages to format content for print, but we do like the idea of letting users write inside a paginated editor so it feels closer to the final result. Right now, two things stop this from feeling seamless:
|
Beta Was this translation helpful? Give feedback.
-
|
I know you specifically said this is for OSS topics, but I can not stop my self from mentioning a few of these since I do not know how else to give some of this feedback.
Overall though, I love Tiptap and what you have done! I have been a user for a few years now and will continue to be one! |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hey Tiptap community,
We want to make Tiptap better over the next year, and the most valuable input for that comes from the people actually using it in real projects.
I’d love to hear your honest feedback on things that are currently not working well or are causing friction for you. In particular, I’m interested in:
Pain points & blockers
Bugs, edge cases, or limitations that slow you down or make certain use cases hard or impossible.
Documentation gaps
Parts of the docs that are unclear, misleading, outdated, or simply missing.
API & code quality feedback
Areas where the API feels awkward, inconsistent, or harder to use than it should be.
Project & DevRel experience
How we handle issues, PRs, discussions, releases, and communication in general. What works well, and what doesn’t?
A quick note on scope: this discussion is intentionally focused on the open-source core of Tiptap. Pricing or paid extensions aren’t the main topic here. We want to understand what you need from the OSS side to confidently build and ship your apps. Our goal is to empower developers to extend and customize Tiptap themselves when needed, while keeping the core solid, well-documented, and pleasant to work with.
This is not a promise to immediately implement everything or to prioritize individual feature requests. The goal is to identify patterns, recurring problems, and areas where we can meaningfully improve the project for everyone.
If you have feedback, please reply to this thread. Concrete examples, links to issues, or short explanations of your use case are especially helpful.
Thanks for helping us make Tiptap better.
And since we’re close to the end of the year: we wish you a peaceful Christmas time with your family and friends, and a great start into the new year.
Beta Was this translation helpful? Give feedback.
All reactions