TinyMCE VS slate

i use this for textarea, it has all possible tools uncluding drag and drop files ... https://www.tiny.cloud/ Tiny MCE

TinyMCE is a web-based Javascript WYSIWYG editor that is platform-independent and was released as open source under LGPL.

On top of being able to view my blog posts in TinyMCE, you can also edit, create and save .whtml files representing these WYSYWIG documents. If you want to edit the file in a more code/text friendly format, I also have added Monaco Editor, which I consider almost like a mix between VS Code and Notepad. Monaco has language detection, line information & Prettier formatting options.

Text Editor: Quill and TinyMCE

Many of the available editors, like TinyMCE, work really well and are great for most projects. However, you might find one or the other editor a bit overloaded, too complicated or you just want to program your own WYSIWYG editor.

If all you need is paragraphs, links, italics, and bold, and you don't mind making the user type these tags themselves, you can technically accomplish this without a WYSIWYG: use a tag (text_area is the form helper), then simple_format() the output.

But obviously that kind of sucks. For your use case, Trix is fine, right out of the box.

My go-to WYSIWYG is TinyMCE: https://www.tiny.cloud/. It's very powerful and almost infinitely configurable.

More about it here: https://www.tiny.cloud

There's quite a few. I use TinyMCE : https://www.tiny.cloud/

You definitely need to give Slate (https://github.com/ianstormtaylor/slate) a try - the best editor framework I've used.

Slate: Looks very promising, but it's for React. (Someone has floated the idea of making it framework-agnostic, but the maintainers haven't committed to that goal yet.)

Thanks for submission! Very timely. Been searching for a stable and flexible editor (or rather a tool to build such an editor) and Tiptap looks like a good candidate.

I was also considering Slate, but have found this rather annoying bug https://github.com/ianstormtaylor/slate/issues/4833, which is surprising as it doesn't look like some rare edge case, and breaks something that seems to be like basic functionality for an editor. Had to re-consider.

Slate - A completely customizable framework for building rich text editors.

Slate.js is a highly customizable platform for creating rich-text editors, also known as WYSIWYG editors. It enables you to create powerful, intuitive editors similar to those you’ve probably used in Medium, Dropbox Paper, or Google Docs. These are quickly becoming standard features for many web apps, and tools like Slate make them easier to implement, ensuring your program won’t get bogged down in complexity.

Building complex, nested documents was impossible. Many editors were designed around simplistic "flat" documents, making things like tables, embeds and captions difficult to reason about and sometimes impossible. Demo GitHub

Ok good to know. Although, the Mention Example seem pretty complicated for what feels like such a simple task but still good to know about this in case I ever need it in the future

I've been using Slate heavily this year. I'm not a Slate developer, but I've read a lot of the source code, follow all the Github issues, etc., and I'm "owning an aging fork". As far as I can tell, the API instability mentioned elsehwere in this thread resulted from a nearly complete rewrite (inspired by immerjs) that launched in May 2020; for over a year since then, the API has been very stable, mainly because Ian Taylor, who wrote most of Slate, seems to have moved on to other projects (see https://github.com/ianstormtaylor/slate/graphs/contributors)... there's still a lot of work on Slate, but it's mainly by other people who are trying to preserve the vision that Ian laid out. I ended up forking only the React part of Slate, which is officially a plugin, and massively rewriting it to support virtualized windowing, so we can work with very large possibly complicated to render documents. I also added fairly generic realtime collaboration support. This is currently used in https://cocalc.com for WYSIWYG editing of Markdown documents. I also have plans to extend my use of Slate with windowing to Jupyter notebooks and other document types.

I chose Slate over Prosemirror because the source code of Slate is Typescript written in a clear modern style, and I was able to start reading any part of it and understand it easily, whereas I find Prosemirror's core source code more difficult (this may just be a reflection of my shortcomings). I spent a lot of time initially just reading Slate PR's claiming to fix bugs, then integrating the PR's into my fork, often in a way that makes sense for my project, but likely wouldn't in general (I left helpful remarks on Github).

Slate is an interesting project, and it is comparable to Prosemirror. However, development is structured very differently at present, and I think there's little funding behind Slate, whereas the author of Prosemirror seems to have done a good job encouraging sustainable donations. I think Ian Taylor, who mainly wrote Slate, also cofounded a company called Segment.io, which is a serious startup that was recently sold to Twilio, so I don't know what his motivations are...