4 ms·
We use QuillJS https://quilljs.com/ https://quilljs.com/ for our projects, as a drop-in component to allow our users to edit rich-text fields. Works great for o
by jherskovic 4y ago
We use QuillJS https://quilljs.com/ https://quilljs.com/ for our projects, as a drop-in component to allow our users to edit rich-text fields. Works great for our CRUD apps; I am not a front-end person, but it's simple, does what we need, and seems to work in multiple browsers without issues.
Am I missing something?
- lewisjoe 4y agoYou don't need to migrate. QuillJS is enough for almost 98% of rich-text editing usecases out there. These options just improve over the document model and relevant document manipulation APIs - which won't be a requirement until your product's core is an editor.
- jherskovic 4y agoAwesome, clear answer. Thanks!
- misterS 4y agoWe use Quill, too, we only need rudimentary features, though. Its maintenance status is... questionable, although my information is out of date (see last paragraph). * Github: https://github.com/quilljs/quill/ https://github.com/quilljs/quill/ * It's latest release was 2019-09-09 – which is _ages_ in term of a JS library. * There's tons of open issues, the maintainer was (or still is) rather quiet. * It's pretty much a one-man-show. Although now that I look at it, the last few months a second contributor appeared. * Apparently there is a v2 in the works, but nobody know when it is due nor what its status is. * There were issue that asked whether the project was abandoned. The issues went unanswered, and then were deleted. To be fair: development seems to have picked up again. There were sporadic commits at the end of 2021, and I now see that there are a few this year, too.