ckeditor5 VS quill

Have you ever come across CKEditor 5? It's a great, easily customizable JavaScript rich text editor, which also offers collaboration features: https://ckeditor.com/ckeditor-5/

And if you want to check the newer version, CKEditor 5: https://ckeditor.com/ckeditor-5/demo/ https://github.com/ckeditor/ckeditor5

We recently switched to CKEditor at work, and they actually have a bold tag wrapper remover for their copy/paste plugin.

Edit: Link to CKEditor https://ckeditor.com/ckeditor-5/

To open my first pull request, I need to first create a fork. I'll use the excellent CKEditor 5 repo as my example that I'm contributing to. Note that none of this is specific to GitHub -- it would work the same with BitBucket or any other git host. My steps are:

I wrote this to address a GitHub issue for CKEditor (a rich text editor). See ckeditor#2737. Someone else wrote something in angular here.

Ontop of that this [issue](https://github.com/quilljs/quill/issues/3806) exists - which forces us to upgrade once primeNg lets us. Anyone knows a good alternative? I am done with quill and would love to use something more stable.

I started with Quill... wound up hitting lots of challenges. There are bugs/issues like, "don't add extra margin or it will be converted to extra spaces." I also struggled to embed Quill into an HTML form element, which I though would be easy.

Fair enough. Look maybe into more of a utility like Quill? https://quilljs.com/

I agree. Yes, you can. Quill is the example here.

Actually, back in 2015 when we started prototyping CKEditor 5, we started with this approach as well. Our goal from the beginning was to combine real-time editing capabilities with an engine capable of storing and rendering complex rich-text structures (nested tables, complex nested lists, other rich widgets, etc.). We quickly realized that a linear structure is going to be a huge bottleneck. In the end, if you want to represent trees, storing them as a linear structure is counterproductive.

So, we went for a tree model. That got many things in the engine an order of magnitude harder (OT being one). But I choose to encapsulate this complexity in the model rather than make it leak to particular plugins.

In fact, from what I remember, https://github.com/quilljs/quill/issues/117 (e.g. https://github.com/quilljs/quill/issues/117#issuecomment-644...) is a good example of issues that we avoided.

I also talked to companies that built their platforms on top of Quill. One of them ended up gluing together countless Quill instances to power their editor and overcome the limitations of the linear data model but is now looking for a way to rebuild their editor from scratch due to the issues (performance, complexity, stability).

So, yes. You can implement a rich-text editor based on a linear model. But it has its immediate limitations that you need to take into consideration.

I've always used Quill and always satisfied with it. It can be adapted to React Native as well. Despite the most popular RTE is Draft js it has some limitations on mobile.

NgPrime has this editor if you’re using it already for components. Or Quil could work

Quill

The few I have seen out there are flask-blogging, tiny-blog, and maybe quill?