Comment by TheRealPomax
2 months ago
GFM, because HTML in markdown should not be a parse error, and getting twenty different markdown "specs" to all agree on new syntax for bits they are obviously missing (like details, classed scoping, transclusions, etc) is not happening.
HTML in markdown has never been a parse error. Unless you're using something very broken.
https://daringfireball.net/projects/markdown/syntax#html
Except under GFM, html is explicitly part of the spec[1], not just "it's not a parse error, but that's because it's just text that doesn't fall in any predefined markdown syntax category", and good luck finding a WYSIWYG markdown editor that gets them right. The number of editors that completely break on <details> alone is disheartening.
[1] https://github.github.com/gfm/
I was actually thinking for going with GFM seems popular with many, despite the occasional strong opinions against it..