MSK Institute • Shikohabad
Loading Page Content...
Preparing courses, live labs, and learning resources.सामग्री लोड हो रही है, कृपया प्रतीक्षा करें...
Connecting serverPlease wait...
💻 Practical Labs🚀 Free Demo📜 Verified Certificates
Markdown Flavors & Specifications (CommonMark vs GFM)0%
Markdown Flavors & Specifications (CommonMark vs GFM)
Beginner12 min read•Updated: Jul 11, 2026
As Markdown grew from a small scripting utility in 2004 into the global standard for software documentation, different software programs began implementing their own syntax variations. These variations are known as Markdown Flavors.
To prevent chaos and ensure documents render identically everywhere, formal specifications like CommonMark and GitHub Flavored Markdown (GFM) were established.
Click to Zoom1. Why Did Flavors Emerge?
John Gruber's original 2004 Markdown specification was ambiguous about edge cases:
- What happens if you have an ordered list inside a blockquote without a blank line?
- How should four spaces inside an emphasis tag be parsed?
- What about tables, task lists, and syntax-highlighted code blocks? (None of these existed in original Markdown!)
Different developers built parsers in Perl, Python, PHP, and JavaScript, each resolving ambiguities differently. A file that looked perfect on one website broke on another.
2. The Three Major Specifications
Original Markdown (2004)
│
▼
CommonMark (2014) ───> Standardized formal specification with 600+ test cases
│
▼
GitHub Flavored Markdown (GFM) ───> CommonMark + Tables + Task Lists + Strikethrough + Autolinks
1. Original Gruber Markdown (2004)
- Minimalist baseline: Headings (
#), basic lists, blockquotes (>), simple links ([text](url)), and images (). - Lacks support for tables, strikethrough, syntax highlighting, or task checkboxes.
2. CommonMark (2014)
- Created by a group including Jeff Atwood (Stack Overflow co-founder) and John MacFarlane (Pandoc creator).
- Provides an exhaustive, unambiguous specification with over 600 automated compliance tests.
- Defines exact behavior for nested lists, whitespace handling, and delimiter balancing.
3. GitHub Flavored Markdown (GFM)
- A strict superset of CommonMark. It includes everything in CommonMark plus critical extensions demanded by developers:
- Tables: Using pipe (
|) and hyphen (-) syntax. - Task Lists: Clickable checkboxes (
- [ ]and- [x]). - Strikethrough: Double tildes (
~~text~~). - Autolinks: Plain URLs like
https://example.comautomatically become clickable links without brackets. - Fenced Code Blocks: Code blocks with triple backticks and language identifiers (```js).
3. Comparison Matrix of Markdown Flavors
| Feature | Original Markdown (2004) | CommonMark (2014) | GitHub Flavored Markdown (GFM) | ||
|---|---|---|---|---|---|
| Strict Grammar Spec | No (Ambiguous) | Yes (Formal RFC) | Yes (Extends CommonMark) | ||
| Fenced Code Blocks (```) | No (Indented only) | Yes | Yes | ||
| **Tables (` | ... | `)** | No | No | Yes |
Task Lists (- [x]) | No | No | Yes | ||
Strikethrough (~~) | No | No | Yes | ||
| URL Autolinking | No | No | Yes | ||
Alert Admonitions (> [!NOTE]) | No | No | Yes (GitHub Native) |
Click to Zoom4. Which Flavor Should You Use?
For 99% of modern web development, documentation, and technical writing, GitHub Flavored Markdown (GFM) is the industry standard. Nearly all major modern parsers (Remark, MDX, VS Code, Next.js) either support GFM by default or via official plugins.
Interactive Quiz
Multiple Choice Questions
Question 1
What was the primary motivation behind the creation of the CommonMark specification in 2014?
Question 2
GitHub Flavored Markdown (GFM) is built as a strict extension on top of which specification?
Question 3
Which of the following features is supported in GFM but was NOT part of the original 2004 Markdown specification?
Question 4
How does GitHub Flavored Markdown (GFM) format strikethrough text?
Question 5
In standard CommonMark, what syntax is used for fenced code blocks?
Next Lesson
Environment & Editor Setup (VS Code, Obsidian, Typora)
Continue learning with hands-on practice, examples, and exercises in the upcoming topic.
Related Lessons
| Previous Lesson | Next Lesson |
|---|---|
| Introduction to Markdown & Philosophy | Environment & Editor Setup (VS Code, Obsidian, Typora) |
Practice Quiz
Test your understanding of this lesson with 5 questions. Each question has one correct answer.