- cross-posted to:
- [email protected]
- [email protected]
- [email protected]
- cross-posted to:
- [email protected]
- [email protected]
- [email protected]
Exactly which flavours of Markdown are targeted/required by this specification?
Basically a combination of GFM with a few extensions such as definition lists!
Very weird style. Inconsistent heading styles. Four tilde code blocks? That’s totally nonstandard. Why?
Thanks for the feedback! The style choices are intentional and all valid CommonMark:
-
Heading styles: Setext (
===/) for H1/H2 makes major sections visually prominent in plain text, while ATX (##) is used for deeper levels. This hybrid approach optimizes readability in the raw source. -
Four tildes: Tildes are valid CommonMark delimiters, just less common. They’re chosen because code often contains backticks (shell commands, string literals), so tildes avoid visual clutter.
The core philosophy is that Markdown should be readable as plain text, not just after rendering. These choices prioritize scanning structure in a text editor. That said, it’s definitely an opinionated style—not for everyone!
I like the heading styles! The tildes are unusual but the reasoning is sound!
code often contains backticks
I’ve never seen code contain three backticks though.
I guess your heading logic kind of makes sense but tbh I still hate it.
-
Because Hong.




