Someone asked me why I don't implement markdown support to the wiki engine instead of painstakingly typing down html tags. I think the reason that I never felt like markdown was worth it, was that the editor I use makes writing html somewhat frictionless, maybe if I lost this, I'd consider adding a parser.
Markdown support adds a thick layer of junk to a SSG, maybe the trick is just to improve html support to the editor you use, and keep the site simplier.
@neauoire implement some flavour of Tonedown?
https://wiki.feelingof.com/tonedown/
The (meh, but heavily commented) reference impl is line 86 to 256 here:
https://github.com/feelingofcomputing/wiki/blob/main/build/build.coffee
But generally, making your own to-html macro lang is a lovely little thing to do.
@spiralganglion that looks neat, although it makes the decision of `** or __`, which I would probably do without.
Org-mode has is right I think:
*bold*
/italic/
_underline_
+stroke+
@neauoire yeah, that weirdness is for backwards compatibility with markdown.
org-mode seems so nice on paper.
@spiralganglion It is even better on screen. I use both org-mode and Markdown daily, but I only ever swear at Markdown.
Devine Lu Linvega
Ivan Reese
Konrad Hinsen
256k