text VS tiptap

As for the editor, I hope it will not reformat the text, see the Nextcloud debacle: https://github.com/nextcloud/text/issues/593

Yes, but some 'central' agencies push for specific Markdown formats/use. E.g. Nextcloud [1] wants to use Markdown as a format, to save the output of their wysiwyg text editor. Everytime you open a Markdown file in nextcloud-text, it is 'formatted' correctly, according to the Commonmark specs, and _written_ back, without asking the user.

[1]: https://github.com/nextcloud/text/issues/593

With the text app you can open to edit them. I believe its this one https://github.com/nextcloud/text

But since you do have concrete PHP experience, you might find it easier to try to work on some of the open issues in one of the Nextcloud repositories. So for example, if you go to the 'Issues' section for the Text app, there are various tags on the issues, and you might be able to start out by helping out with those tagged "Need triage". (i used to triage bug reports for Emacs itself, which is what led me to write this guide to reporting bugs in GNU Emacs.)

It may very well be expected behaviour. See for instance this on Github.

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).