milkdown VS react-page

Page: https://milkdown.dev/

When it comes to community plugins, I don’t run a single one. The core plugins do what I need. I only miss two features, scrollable code blocks and support for WYSIWYG tables like in the Milkdown editor. To my knowledge, there are no community plugins for this, so I haven’t had any reasons to install such plugins. I guess I’m a quite basic Obsidian user.

To be honest, there are not many disadvantages. There are some annoyances. I personally miss a good way to build tables. A table-building solution like the one in Milkdown (visual Markdown editor used by e.g., Standard Notes) would be very welcome. I also miss horizontal scrolling in code-blocks and other such minor stuff. Since Obsidian is improving in a high pace, and hasn’t even reached version 1.0 yet, I can live with that.

When writing a list in the new Markdown Visual (which seems promising despite the misfortunate font choice), I am not able to indent a list item using tab, like you do in all other writing software. As I understand it, it is based on the Milkdown editor, which states in their shortcuts that it is Mod-[ or Mod-] to sink or lift items.

Sounds like you need a WYSIWYG editor. There are a bunch of them, but I like Prosemirror and Milkdown the most.

Milkdown is a WYSIWYG (what you see is what you get) editor. It's an open source project that integrates Markdown editor, components, and plugins.

HyperMD and Quill are pretty nice. The one I currently have my eye on is one called Milkdown (https://milkdown.dev)

Hi guys. Just made an editor wrapping around Milkdown, the WYSIWYG Markdown editor component. Here is the installation link:

This is really slick! A really fluid and intuitive interface.

We use https://react-page.github.io/ (also MIT licensed) extensively at my startup; it attacks the same problem, and it's been incredibly effective (and hackable!).

Generally speaking, owning your own CMS data, in your own database, with a well-documented JSON data format, and adding the ability to take any React component you've written (that itself may interact with your own data) and make it not only reusable as part of a content editing system but also WYSIWIG, opens up a huge number of opportunities - including adding your own logic to transform content before display.

https://builder.io is another alternative that's very effective at the adapting-custom-components-to-WYSIWIG side of things, but does keep the data in its own cloud storage.

I'm really excited to see innovation in this space, and I'll be following Puck closely!

A few days ago someone posted a link in an answer to a similar library to https://react-page.github.io/.

https://github.com/react-page/react-page is fully open source with a simple JSON data model and multi-language support; we’ve built various utilities for auto-generating content. Invest a few days in customizing CSS and you have a world-class WYSIWYG for your own design language. Highly recommend.

I maintain https://react-page.github.io/

If its just some rich content you want to edit, you can also use https://github.com/react-page/react-page which is a rich content editor, that i am maintaining. You can use it to edit and display content. The data itself can be stored as a json string and can be saved in your api, your firebase or your headless cms. I also tried to pair it with strapi, where I would share ReactPage‘s config and cell plugins both with a nextjs frontend and strapi admin panel. This is extremly powerful and flexible.

I came across react-page[1] the other day, it seemed like a reasonably powerful block editor but was too much for our purpose so I haven't actually used it.

[1]: https://github.com/react-page/react-page

a quick search turned up React Page — can anyone vouch for this or recommend anything else?