The Complete History of Markdown

Markdown has become the de facto standard for writing on the web. From GitHub READMEs to academic papers, its influence is ubiquitous. But how did this simple formatting language come to dominate digital text?

The Problem: HTML was too heavy

Before Markdown, writing for the web meant writing HTML. If you wanted to bold a word, you wrapped it in <strong> tags. Creating a list required nested <ul> and <li> tags. This constant context-switching between human prose and machine structure was tedious and broke the flow of writing.

In the early 2000s, bloggers and writers sought a better way. They wanted a syntax that was readable in its raw form but could easily convert to valid HTML.

2004: The Birth of Markdown

In 2004, John Gruber, a tech writer and author of the Daring Fireball blog, teamed up with Aaron Swartz, a programmer and internet activist. Together, they released Markdown 1.0.0.

Gruber’s philosophy was simple:

“The overriding design goal for Markdown’s formatting syntax is to make it as readable as possible. The idea is that a Markdown-formatted document should be publishable as-is, as plain text, without looking like it’s been marked up with tags or formatting instructions.”

Swartz contributed significantly to the original Perl script (Markdown.pl) that parsed the syntax and converted it to HTML. They drew inspiration from pre-existing conventions used in plain text emails, such as using asterisks for emphasis.

Key Initial Features

The first version included simple formatting:

• *Italic* and **Bold** text.
• Lists using - or *.
• Blockquotes using >.
• Code snippets using backticks `.

The Wild West: Flavors Emerge

As Markdown grew in popularity, its limitations became apparent. The original syntax lacked support for tables, complex definition lists, mathematical equations, and footnotes.

Furthermore, Gruber’s original Perl script was ambiguous in certain edge cases, leading to inconsistent parsing across different implementations. Because there was no formal specification, developers started creating their own “Flavors” of Markdown to add missing features:

MultiMarkdown (2005)

Fletcher Penney released MultiMarkdown, adding crucial features for academic writing, such as tables, footnotes, and math support.

GitHub Flavored Markdown (GFM)

Perhaps the most influential variant, GFM introduced strikethrough, task lists (- [x]), autolinking of URLs, and fenced code blocks using triple backticks. GFM standardized how developers document code and remains the most widely used Markdown variant today.

The Push for Standardization: CommonMark (2014)

In 2014, a group of prominent developers (including Jeff Atwood and John MacFarlane) sought to formalize Markdown. The lack of a rigorous spec meant that parsing a nested blockquote on one platform might yield entirely different HTML on another.

They released CommonMark, a heavily defined, unambiguous specification for Markdown parsing. While Gruber objected to the formalization (leading them to drop the name “Standard Markdown”), CommonMark brought necessary stability. Today, parsers like markdown-it (used by MarkdownToPrettyPDF) strictly adhere to the CommonMark spec.

Markdown Today: The “Everything” Format

Today, Markdown is no longer just for blogging.

• Knowledge Management: Apps like Obsidian and Notion rely heavily on Markdown.
• Documentation: Static site generators like Next.js, Hugo, and Docusaurus build entire websites from Markdown files.
• Diagrams as Code: By extending code blocks, modern tools allow you to render Mermaid, PlantUML, and Graphviz diagrams directly from Markdown—bridging the gap between prose and visual architecture.

Markdown succeeded because it prioritized the human over the machine. By hiding the complex HTML markup behind intuitive text symbols, it allowed writers simply to write.