3 ms·
This is really good. I can right off my head come up with interesting possibilities based on this standard. #1) All major rich text libraries (Prosemirror, Qui
by lewisjoe 8y ago
This is really good. I can right off my head come up with interesting possibilities based on this standard.
#1) All major rich text libraries (Prosemirror, Quill, Draft, Slate, Trix & more) out their now have their own capabilities and their own JSON representation. But exporting content across these editors is a pain. You either have to use HTML or Markdown, both of which have formatting loss.
#2) This means when you develop an app around document creation you are essentially locked down with either the libraries' data model JSON, or end up writing migration code and parsers if you want to switch.
#3) What if word processors have an option to export their content into such a JSON representation, such that parsing or rendering these content in browsers wouldn't involve us working with HTML
Challenges:
What if view information like line-endings and pagination are part of the model? Coming up with a JSON standard for such cases would be very difficult / impractical?
- michaelmior 8y agoI think this sounds good. Of course it only really becomes good if different projects start adopting it. Hopefully some of the libraries you listed are taking notice.