lexical VS Editor.js

Lexical (https://lexical.dev/) is really nice to use and doesn't use Prosemirror or CKEditor.

I've tried to get to grips with Lexical but found the docs pretty hard to follow. It definitely seems to offer pretty heaps of power, just unlocking that seemed tricky. We're hoping to use it for customer facing collaborative list product that allows for richer media (video, code blocks etc.)

Yes, it uses the Lexical framework internally, so markdown gets converted to an AST, then the AST gets serialized back.

Rich text editing doesn't imply pagination. Contenteditable is not abandoned. Lexical[1], Meta's framework for text editing relies on contenteditables.

[1]: https://lexical.dev/

lexical is a framework for building web based text-editors ... so yea it can do formatting but if you are using it to just do formatting you are very much using the wrong tool.

Haven't tried it out myself, but it's probably Lexical.

Svelte just got a lot more interesting! Dominic who is the creator of LexicalJs and InfernoJs (which is known to be insanely fast) has joined the svelte core team and is now working at Vercel full time! Here is the announcement on Twitter!

Finally there's Slate and Lexical which are super powerful in terms of customizability and extensibility. They're great options for when the editing experience plays a major role in the product.

I am supporting a project where lawyers, advisors can publish articles or news, to get more attention and clients. Initially it was made through TinyMCE, but they wanted not just HTML, but also a way of showing many pictures with interactions. I was seeking UI editor like Medium, and I guess best what I found was EditorJS and during checking its Awesome List there were several carousel plugins and I stopped on this.

We call it EmailBuilder.js – a powerful block-based email builder that takes the best parts of other open source libraries like Editor.js and email component libraries and puts them into an easy to use no-code builder.

I tried the "Doc", "Sheet" and "Slide" feature and each of them are incomplete and lacks most of the popular features. It would be better if the author uses existing solutions instead of implement them from ground up.

editor.js [0] for documents and Grist [1] for spreadsheet are some good examples.

[0]: https://editorjs.io/

Editorjs [https://editorjs.io/]

Use Gutenberg or a block editor like this (https://github.com/codex-team/editor.js) for a CMS. The WYSIWYG days are over.

Has anyone had any luck adding editor.js to your app? I've got a plain rails/stimulus/turbo/activeStorage app which needs a dynamic page builder and editor.js looks like it has promise. However it's a pretty specialized workflow and Im not sure if it jives well with the plain Rails ecosystem.

try this: https://editorjs.io/ might come handy, it's a very nice library and it's well maintained.