4 ms·
This is great -- lack of a standard that was actually used (unlike CommonMark) was one of my main issues with Markdown (http://ericholscher.com/blog/2016/mar/15
by forsaken 10y ago
This is great -- lack of a standard that was actually used (unlike CommonMark) was one of my main issues with Markdown (http://ericholscher.com/blog/2016/mar/15/dont-use-markdown-for-technical-docs/ http://ericholscher.com/blog/2016/mar/15/dont-use-markdown-f...) -- It's really great to see GitHub leading in this department, and it gives me hope that one day we might actually have Markdown that is portable between implementations.
- SEJeff 10y agoPerhaps you missed Jeff Atwood (codinghorror)'s standardized markdown spec, which is about as close as you'll get: http://commonmark.org/ http://commonmark.org/
- forsaken 10y agoYea, I mention commonmark in the post, and referred to it in the "standard that was used" part -- commonmark is great, but wasn't widely adopted. Updated my original post to be more clear.
- zellyn 10y agoThis is actually very closely based on CommonMark, according to the article.
- jotux 10y agoThe github spec is literally CommonMark with extensions. https://github.github.com/gfm/ https://github.github.com/gfm/ http://spec.commonmark.org/0.27/ http://spec.commonmark.org/0.27/