3 ms·
At this time, it is kind of wild that handling rich text content editing is so hard on the web. It is understandable, but a bummer, that really good content too
by pfooti 11y ago
At this time, it is kind of wild that handling rich text content editing is so hard on the web. It is understandable, but a bummer, that really good content tools (google docs, office 365, medium) do not open source their editors. There are some good tools (textbox, aloha, hallo, quill) and some decent legacy ones (ck, mce), but nothing that is clearly a go-to tool that handles rich text, structured text (tables and lists), operational transforms, and sanitizing input well. It's always like: choose two.
Kudos to ProseMirror for tackling this. I can't wait to see how this works out. Also, it is kind of nice to have a way to contribute monetarily; I don't have the time (or expertise) to really contribute code. I would, given the need.
- thangalin 11y agoHere is a list of browser-based editors: https://bitbucket.org/djarvis/world-politics/wiki/Editor https://bitbucket.org/djarvis/world-politics/wiki/Editor Although ProseMirror isn't listed, the page provides a decent summary of various editors and reasons why they are unsuitable for certain types of in-browser editing. Kudos indeed!
- socceroos 11y agowebODF is a nicely done ODF editor. Owncloud uses this in their own online document editing addon. http://www.webodf.org/ http://www.webodf.org/ The other really good one (which has been around for a while) is OX Documents: https://www.open-xchange.com/en/ox-documents https://www.open-xchange.com/en/ox-documents
- anilgulecha 11y agoGuardian's scribe is another very good example of keeping the view separate from the model. The model produces clean data, which is the same across browsers.