tiptap VS gitlab

The Editor: The core of our app is the editor. We need an easy to use and robust rich text editor, that supports all of the features we want such as: headings, lists, placeholders, markdown, color, images, bold italic etc… For this we will use @10play/tentap-editor which is a rich text editor for react native based on Tiptap.

If you want bell and whistles - https://tiptap.dev/

A WYSIWYG rich-text editor using tiptap2 and Element Plus for Vue3

You can build a Notion-like editor on top of https://tiptap.dev :-) Here is a demo of what such an editor might look like: https://demos.tiptap.dev/

Since Tiptap is headless, you have the freedom to design and develop the UI exactly the way you want.

The first link shows a discussion that started in July 2020, when Tiptap was only available in version 1. The new major version 2, which is a complete rewrite, was in development. The biggest drawback the GitLab engineers had was the lack of a test suite in Tiptap 1. That's understandable, because as a key component of your application, testing is necessary to ensure that you catch breakable changes. Tiptap 2 does just that. [1]

[1] https://github.com/ueberdosis/tiptap/tree/develop/tests

No good tool is built without using good tools, and Vrite Editor is no different. Before getting into WYSIWYG editors, I extensively researched available RTE frameworks, that could provide the tooling and functionality I was looking for. Ultimately, I picked TipTap and underlying ProseMirror — IMO, the best tools currently available for all kinds of WYSIWYG editors.

Nodejs has hocuspocus (built on prosemirror) (https://www.npmjs.com/package/@hocuspocus/server) using tiptap (https://tiptap.dev/), are there any similar alternative backends in Go?

Check this headless editor framework https://tiptap.dev/

If you're in need of a solid editor library for your next project, be sure to check out Tiptap. It's an open-source project, and we always appreciate feedback and contributions!

The buttons had to be absolutely positioned, which required both a custom TipTap extension and tapping deeper into the underlying ProseMirror (both libraries powering the Vrite editor).

(Side note: Issues are usually hash-prefixed like #1234 both on GitLab and GitHub. However, commit messages must not begin with a hash, they would be considered a comment and ignored. Therefore, GitHub has introduced the alternative prefix GH- and I've contributed a similar prefix GL- to GitLab a while ago.)

and its "oh, you want multi-arch, do you?" friend. While prosecuting this <https://gitlab.com/gitlab-org/gitlab/-/issues/339567> I learned that https://hub.docker.com/layers/multiarch/qemu-user-static/7.2... actually mutates the binfmt_misc in buildx's context in order to exec the static copy of qemu in it https://github.com/multiarch/qemu-user-static/blob/v7.2.0-1/...

and, that the buildx plugin itself has some qemu magick in it, which got addressed in a minor version bump but I couldn't track down the relevant GitHub issue this second (I've flushed it from my mind, only recalling that there were a lot of actors in that tire fire)

This is actually a follow-up refactor, the fix is here: https://gitlab.com/gitlab-org/gitlab/-/commit/abe79e4ec43798...

This made me curious. Having never read the gitlab code before, and on mobile, took all of about 30 seconds to find https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/ro...

Those are some pretty clean routes!