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 I maintain that Markdown is a downstream product of software distribution and reuse being difficult. It makes sense in a world where the user of the data will not have ready use of the tools used to author it, or full fidelity viewers. It's sort of the XLS of the software world.
@neauoire @mirth That's pretty much the official origin. It was intended to be a plain-text markup that could be read as either formatted output supporting the basics (text styles, lists, simple tables), or as plain text with the visible markup making sense. If you wanted anything more complex, you were supposed to go to HTML or something suited to complex formatting.