5 ms·
OMG. I was just about to start my own Markdown parser because I needed custom elements and I was finding too hard to work with existing "customizable" Markdown
by andrerpena 4y ago
OMG. I was just about to start my own Markdown parser because I needed custom elements and I was finding too hard to work with existing "customizable" Markdown parsers.
Also, I needed a React renderer for React-Native and I was also about to write my own.
By the looks of it, I will be able to just use Markdoc.
Thank you Stripe!
- Duhck 4y agoWe use Remark, and given the ability to leverage AST, its pretty much limitless in terms of customization
- kposehn 4y agoI was in the same boat, wanting to migrate away from Jekyll+Liquid. Very glad they released this.
- atonse 4y agoAny reason why this would be better than liquid? Genuinely curious because we’re about to adopt liquid.
- SneakyTornado29 4y agoWow! Was thinking of doing the same because I wanted to include custom HTML elements suck as boxed block quotes in my Markdown documents. So does this solve the problem?
- tannhaeuser 4y agoHey, if you really want to customize markdown with your own elements and their rendering/templating, check out SGML [1]. It's made for exactly this type of flexible and extensible document apps/sites, even allows custom Wiki syntax rules. [1]: http://sgmljs.net http://sgmljs.net
- kyawzazaw 4y agoA bit of a tangential question. What kind of project or business that you run that you need it? How much hours do you estimate it would have taken you?
- fastball 4y agoFor my startup, which is built around Markdown notecards[1], we've been using markdown-it, which it seems is also being leveraged by the Markdoc project. So far I've written a couple of extensions for markdown-it and haven't really had any issues. [1] https://supernotes.app https://supernotes.app