3 ms·
A big part of that, I think, is which flavor of Markdown? Github? Pandoc? The OG from Daring Fireball? You'd also probably need an extension to Markdown that l
by thomascgalvin 4y ago
A big part of that, I think, is which flavor of Markdown? Github? Pandoc? The OG from Daring Fireball?
You'd also probably need an extension to Markdown that links it to a style sheet, so there's yet another dialect.
And then you'll want metadata, so ... which format do you support? Hugo's? Jekyll's? Something else?
Turning Markdown into HTML is (often) trivial. Turning it into a web page is often not.
- Schroedingersat 4y ago> Github? Pandoc? The OG from Daring Fireball? The most popular one that doesn't do something extremely stupid, with a piece of version info in the http header mime type in case it's a mistake. > You'd also probably need an extension to Markdown that links it to a style sheet, so there's yet another dialect. Absolutely not. Let the user have a local style sheet to render it how they want with 1-4 sensible defaults much like FF reader mode. > And then you'll want metadata, so ... which format do you support? Hugo's? Jekyll's? Something else? None of the above. Just the markdown. > Turning Markdown into HTML is (often) trivial. Turning it into a web page is often not. Don't turn it into a webpage then, we already have those. Just render some markdown.
- v3ss0n 4y agoCommonmark is most proper specs