substance

Hi Mickael! Each content type consists of the following pieces: - Node (model) [1] - Component (visual representation) [2] - Converter (optional, used to map from and to XML/HTML) [3] The verbose output for heading1 you see is just the DOM projection of the data, which is custom and can be specified in the Component implementation [2]. Often you need to add extra markup and interactive elements, so that's why for Substance content (data) is not rendered 1:1 but through a custom renderer component. Please have a look at the examples [4], which includes minimal but functional implementations using most of the available concepts. [1] https://github.com/substance/substance/blob/master/packages/... [2] https://github.com/substance/substance/blob/master/packages/... [3] https://github.com/substance/substance/blob/master/packages/... [4] https:/

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. [1] https://github.com/substance/substance#beta-5

Old (veeeeeeery old) substance dev here. They are not AMD based (have a look here indeed https://github.com/substance/substance/blob/master/browser.j...) and about jQuery I’m pretty sure you can wrap it up as a Web Component pretty easily.

It is open-sourced? https://github.com/substance/substance/blob/master/LICENSE