Thank you for sharing this on HN. Just wanted to add our introduction blog post, which may clarify some of the questions asked here.<p><a href="https://medium.com/@_mql/build-your-own-editor-with-substance-7790eb600109" rel="nofollow">https://medium.com/@_mql/build-your-own-editor-with-substanc...</a><p>And some usage examples:<p>Scientific Writing
- <a href="http://substance.io/lens" rel="nofollow">http://substance.io/lens</a>
- <a href="https://github.com/Coko-Foundation/pubsweet-core" rel="nofollow">https://github.com/Coko-Foundation/pubsweet-core</a>
Spreadsheet Software
- <a href="https://stenci.la/demo/sheets/iris" rel="nofollow">https://stenci.la/demo/sheets/iris</a>
Digital Archives:
- <a href="https://medium.com/@_daniel/publish-interactive-historical-documents-with-archivist-7019f6408ee6#.337wsufou" rel="nofollow">https://medium.com/@_daniel/publish-interactive-historical-d...</a>
Can somebody give any use case that make this project or draft.js interesting compared to all the other WYSIWYG editors available (tinyMCE, CKEditor and so on...)?<p>Especially since the generated HTML of the editor is very verbose and doesn't respect semantic (header1 isn't translate as h1 but a div with a super long id. Why?)<p>And what is so terrible about contentEditable? I spent a few minutes with it a few month ago and it felt great (and works on old version of IE), just lacking some library on top of it to give the end user a way to fully control everything.
Huh. I have actually been looking for <i>precisely this</i> --- I was going to go with the Guardian's Scribe, but I might investigate this instead.<p>Unfortunately it looks like it's JQuery and AMD modules, and I'm a Polymer and browserify shop, so it may just not be feasible. [sad face]
They're going down the route of not using contentEditable, which I think is a great move. I was a little bit disappointed when I saw Facebook's Draft.js didn't do the same. It's more work up-front to get something functional, but it's a better pattern for building text editors on the web.
Nice! Glad to see mobile support is on the roadmap [1]. So many browser rich editors seem to be virtually unusable on touch devices, it's the first thing I check now.<p>[1] <a href="https://github.com/substance/substance#beta-5" rel="nofollow">https://github.com/substance/substance#beta-5</a>
Very exciting project, specially the support for custom document schemas.<p>If the authors are around, I'd love to hear what was their thinking regarding implementing focus and selection, with regards to the inconvenients outlined by the author of ProseMirror here:
<a href="http://marijnhaverbeke.nl/blog/prosemirror.html#general-approach" rel="nofollow">http://marijnhaverbeke.nl/blog/prosemirror.html#general-appr...</a><p>In a nutshell, ProseMirror chose to keep contentEditable in order to have browser-level support for spell-checking, screen-readers, RTL, etc.<p>What are the tradeoffs exactly?<p>Thanks.
Just published an example that shows realtime collab capabilities:<p><a href="http://substance.io/examples/collabwriter/" rel="nofollow">http://substance.io/examples/collabwriter/</a>
This looks really interesting - it's very encouraging to see it being used in real projects of quite disparate types. It bodes well for the maturity and flexibility of the model.
For something like this I usually like to see a demo before I invest time in trying it out but the demo link is broken... Seems like something I might want to explore though!!
With the next release we will package the ability to have editors based on document slices (aka prjections): <a href="https://cloud.githubusercontent.com/assets/284099/13857486/6be94134-ec7a-11e5-96de-b216b0a3ad06.gif" rel="nofollow">https://cloud.githubusercontent.com/assets/284099/13857486/6...</a>