would someone have a suggestion about this? Thanks a lot https://graphcool.slack.com/archives/C0MQJ62NL/p1495897291703723

@sdubois It's not necessarily safer but storing the content as Markdown might be a whole lot easier and reduce the complexities you'll run into.

okay thanks. I'm not quite sure though if that would allow enough styling flexibility.

You should escape some html tags (for example <scripts>, or only allow some tags b, i, p, em etc ...)

You can use html inside markdown for sure 😉

ah thanks @notrab @leopradel! Yes totally forgot html can go in markdown

@sdubois I'm working on a similar project using Draft.js as the editor. I store each node (Text, Image, Heading) as an entity within the graph itself as related items with a type and position. This allows me to safely pass the nodes back to the editor as props. But I can also parse and form the nodes into HTML through the render function too. Working with authors and editors I've found you can never trust what they are doing, so this provides the safest path.

@jjaybrown98 that sounds great! Is that proprietary or are you open-sourcing? I think a demo integrated with Graphcool would interest a lot of people, could even be featured in partnership with Graphcool maybe.

the draft.js integration can be open sourced. But the CMS itself is proprietary as it will be part of our publishing pipeline at LADbible

OK sounds good. Do you have a timeline and know where you intend to open-source?

prob not in the short term, we're still building it out

OK, I guess this is your github? https://github.com/TheLADbibleGroup

yeah that's it