GitHub Flavored Markdown (GFM) Guide: Tables, Task Lists & Code Blocks
A complete guide to GFM extensions over standard CommonMark. Master tabular markdown, fenced code languages, strikethroughs, and checklists.
Key takeaways
- GitHub Flavored Markdown (GFM) is a formal extension of CommonMark, adding tables, task lists, strikethrough, and autolinks.
- GFM tables use pipes (|) to separate columns and hyphens (-) with optional colons (:) to control text alignment.
- Interactive task lists can be created using - [ ] for pending items and - [x] for completed tasks.
- Always specify the language identifier after the opening backticks (```typescript) to enable accurate syntax highlighting.
Companion utility
Try Markdown Previewer & Live HTML Converter
Use the browser utility for the same task, then return here for the implementation details.
1. Why GitHub Flavored Markdown (GFM) Was Created
Standard Markdown was originally designed for writing web articles with simple paragraphs, headers, and lists. However, when software teams began using Markdown for README files, issue trackers, and pull requests, they needed tables, checklists, and fenced code blocks with language indicators. GitHub formalized these extensions into the GFM specification, which is now the industry standard for developer documentation.
2. GFM Table Syntax and Alignment Tricks
Creating tables in GFM is straightforward with pipes (|) and hyphens (-). You can control text alignment using colons: - Left-align (default): :--- - Center-align: :---: - Right-align (great for numbers and currency): ---:
| Utility | Status | Execution Environment |
| :--- | :---: | ---: |
| Crontab Generator | Active | 100% Client-Side |
| UUID Generator | Active | Web Crypto CSPRNG |
| SQL Formatter | Active | In-Browser V8 |Rana Jawad
Principal Systems Architect at ToolNara. The guides focus on browser runtime behavior, standards, and engineering trade-offs.
View author profile