tiptap VS taiga-ui

Hey HN, Philip here, Co-founder at Tiptap (https://tiptap.dev/).

We just shipped an upgrade to our DOCX import and export capabilities, including new extensions, new endpoints, better formatting handling, and custom node support. This may be for you if your product deals with Microsoft Word files in any way.

We rebuilt our DOCX handling pipeline to give developers more control and flexibility:

- Import endpoint: Converts .docx to Tiptap JSON, accurately handles complex formatting (lists, tables, inline styles).

- Export extension: Generates .docx from your editor content, including custom nodes.

- Custom node support: Map internal components (e.g. callouts, embeds) to standard DOCX structures.

- Style control: Define exactly how DOCX output should look to match your app’s UI.

- Frontend or backend: Run conversion wherever it makes sense for your setup.

- Image upload handling: We give you hooks to manage storage your way.

What's still on the roadmap:

1) Import and export of DOCX headers and footers

2) Import and export DOCX pagination

3) Import and export comments, version history, and suggestions

Developer Docs: https://tiptap.dev/docs/conversion/import-export/docx

Product Website: https://tiptap.dev/product/conversion

We’d love your feedback! If you’ve struggled with document conversion (or just want to nerd out a bit), let us know your thoughts and experiences.

Show HN: Tiptap Editor 3.0 Beta is out.

Hi HN! Philip here from Tiptap (https://tiptap.dev/). We're excited to announce Tiptap 3.0 Beta, a major upgrade built with and for the open source community. It's still extension-based, still unopinionated, but we've tackled some of the biggest developer headaches:

Enhanced TypeScript support:

Hi, Philip here from Tiptap. We just released a new set of open source UI components for [Tiptap](https://tiptap.dev/), our headless text editor framework.

These are handcrafted React components that integrate directly with Tiptap’s headless core, things like toolbars, dropdowns, formatting buttons, upload controls, etc. They’re MIT licensed and fully optional. You can use them as-is or customize every part.

There’s also a CLI that sets everything up for you: project scaffolding, recommended defaults, and a working example.

This is for folks who like the flexibility of Tiptap but don’t want to start from zero every time they need an editor UI. It doesn’t change how Tiptap works – just gives you a faster way to build on top of it.

Start here:

Thanks! I built the editor using Tiptap (https://tiptap.dev/) which doesn't support Markdown out of the box. However, since it can detect Markdown shortcuts (#, ##, >, etc.), it should be possible to convert a markdown file into rich text, and then when done writing and editing convert it back into markdown, while limiting formatting options only to ones that are available for both. I think Joplin (https://joplinapp.org/) does something similar.

I'll think about this for sure, especially since I've been thinking of making it possible to save and read local files. If you'd like to try Gorby, send me an email and I'll be happy to give you a free license code :)

While Storyblok and Builder.io offer full-page editing experiences with structured CMS capabilities, Tiptap takes a different approach. It’s not a traditional page builder but rather an embeddable headless editor built on ProseMirror. This means that instead of giving you a predefined UI to work with, it provides the underlying logic, leaving you in full control of the interface, interaction and level of functionality you want to provide in your page builder.

There are paid tools available. For example, the Tiptap rich text editor is free to use, but some advanced features and APIs are paid for. For example, the cursor editor heavily relies on AI capabilities, so it requires payment for use.

Novel is an open-source Notion-style WYSIWYG editor with AI-powered autocompletion. This built on top of TipTap. Tiptap is the headless and open source editor framework. Integrate over 100+ extensions and paid features like collaboration and AI agents to create the UX you want.

For more, visit the official TipTap website. Did you learn something new from this article? Let me know in the comments! 🎉

Tip Tap Library

Once I completed the backend, I wanted to interact with my service through a comfortable UI. Angular 19 had just come out with stable signals and other cool features, so I decided to use it for the frontend. I didn’t want to spend too much time designing UI components, hence I decided to use a component library that provides pre-built, customizable components. This allowed me to focus more on the core functionality and user experience. The library i choose is Taiga UI.

Our team already has a stock of welcomed projects, especially in the Angular ecosystem, such as Taiga UI, ng-polymorpheus and Web APIs for Angular to name a few. We take them very seriously because they are not pet projects or hobbies (although we love them as if they were). Therefore you can expect our documentation to be easy to navigate, examples to be plentiful and communication to go effortlessly.

The best component library by far in terms of default design (& not using TailwindCSS) i have encounter with is Taiga UI (its so eye-catching)

You can also check out TaigaUI https://taiga-ui.dev/ they also have an awesome component framework.

If you aren’t acquainted with Taiga and randomly stumbled upon this text, let me introduce Taiga UI — a powerful set of components for Angular, which is used in dozens of Tinkoff’s products and projects! In the following sections I will briefly unpack the overall achievements related to this multifaceted library.

https://taiga-ui.dev/ Taiga UI (free)

You could copy this service in your project: https://github.com/Tinkoff/taiga-ui/blob/main/projects/cdk/services/destroy.service.ts

There's beautiful Taiga UI library for awesome devs: https://taiga-ui.dev

Our library Taiga UI contains hundreds of useful components, directives, and services. The code maintainability is a pivotal issue for our UI Kit library. That is why we always try to write as little code as possible and look for native solutions.