#
Markdown 101
← All reads
Staying current · 5 min read

What's new — and how to keep up

Markdown looks frozen in time, but its standards have a quiet, ongoing story. Here's what actually changes, and the short list of places worth watching.

Why "what's new" is even a question

Gruber's original 2004 description was deliberately loose — it explained the philosophy and gave examples, but left edge cases to each implementer's judgment. That freedom is why Markdown spread so fast, and also why the same document could render one way on a wiki and differently in another tool. Most of Markdown's "news" over the years has been the effort to tame that ambiguity without losing the simplicity.

The two names worth knowing

CommonMark is the closest thing Markdown has to an official standard. Launched in 2014 by a group including John MacFarlane (creator of the Pandoc converter) and Jeff Atwood (co-founder of Stack Overflow), it's a precise, unambiguous specification backed by a test suite of 500-plus cases. Its goal: any conforming parser produces the same output. It deliberately keeps its scope tight — headings, paragraphs, lists, links, images, emphasis, code, and blockquotes — and nothing fancier.

GitHub Flavored Markdown (GFM) is the dialect you meet most, given GitHub's scale. Formalized in 2017, it's a strict superset of CommonMark: every valid CommonMark document is valid GFM, and GFM adds a small set of extensions on top — most notably tables, task lists (- [ ]), strikethrough (~~text~~), and autolinks.

A short timeline
2004
Gruber releases Markdown with a Perl script, Markdown.pl, that converts it to HTML.
2014
CommonMark published — the first rigorous, unambiguous spec and test suite.
2016
The text/markdown media type is registered with the IETF (RFC 7763 & 7764).
2017
GitHub publishes the formal GFM spec, built as a strict superset of CommonMark.
Now
CommonMark is the baseline for GitHub, GitLab, Reddit, Discourse, Stack Exchange and more — refined steadily, with a 1.0 still pending.

The thing most "changes" come down to

When a tool says it supports "Markdown," it increasingly means CommonMark plus a few extensions of its choosing. So the practical question is never really "what's the latest version of Markdown?" — it's "which flavor does this tool speak?" Tables and task lists work on GitHub; paste them somewhere that only does plain CommonMark and they may show up as raw symbols. Even GitHub's own renderer adds things — alerts, math, diagrams, emoji shortcodes — that aren't in the formal GFM spec and won't travel elsewhere.

Rule of thumb
Core syntax travels everywhere. Anything beyond it — tables, checkboxes, math, diagrams — is a flavor. When in doubt, test where it'll actually be read.

Where to actually keep up

You don't need to follow Markdown like the news. A handful of primary sources tell you everything that's real (skip the third-party summaries):

§
The CommonMark Spec
spec.commonmark.org — the canonical, versioned standard
#
The GitHub Flavored Markdown Spec
github.github.com/gfm — the dialect you'll meet most
The CommonMark Forum
talk.commonmark.org — where open spec questions are debated
Gruber's original project page
daringfireball.net — the source, still online
The syntax you learned here is the part that never changes.
Back to lessons →
Sources: CommonMark Spec & CommonMark.org; GitHub Flavored Markdown Spec (github.github.com/gfm); GitHub Engineering Blog, "A formal spec for GitHub Flavored Markdown" (2017); Wikipedia, "Markdown" (RFC 7763/7764, adopting platforms). Linked sites are primary sources.