What Actually Makes Markdown So Popular?

Markdown was created by John Gruber and Aaron Swartz in 2004 with one goal: make writing for the web as natural as writing a plain text email. It succeeded far beyond expectations.

Today, GitHub, GitLab, Reddit, Stack Overflow, Notion, Obsidian, and hundreds of other platforms support Markdown natively. When you write a GitHub README, you're writing Markdown. When you format a Reddit post with bold text and bullet points, that's Markdown too.

The beauty is in the readability. A Markdown file is completely understandable even without rendering it. Try reading raw HTML — it's a mess of tags. Raw Markdown reads almost like the final document.

The Core Syntax Every Writer Should Know

You don't need to memorize every Markdown feature. Most content can be written with just these essentials:

That covers around 90% of what most writers and developers ever need. The remaining 10% — tables, footnotes, definition lists — you can pick up as you go.

How Markdown Converts to HTML Under the Hood

When a Markdown processor encounters your text, it reads it line by line and applies a series of transformations. Headings starting with # become <h1> tags. Text wrapped in ** becomes <strong>. Lists become <ul> or <ol> elements.

Here's the interesting part: the conversion happens in a specific order, and that order matters. Code blocks are processed first to prevent their content from being accidentally formatted. Then headings, then inline elements like bold and italic. If processors didn't follow this sequence, a code block containing **text** might accidentally render as bold instead of literal asterisks.

Real-World Use Cases With Indian Examples

Markdown Flavors — Standard vs GFM vs Others

Here's something that trips up a lot of people: there isn't one single Markdown standard. The original spec by John Gruber covers the basics, but different platforms extended it in different ways.

GitHub Flavored Markdown (GFM) is probably the most widely used extension. It adds tables, task lists, strikethrough text, and fenced code blocks with syntax highlighting hints. If you've used GitHub, you've used GFM.

CommonMark is an attempt at a strict, unambiguous Markdown specification. Platforms like Reddit and Stack Overflow use variants of it. Most modern converters support a superset that includes both standard Markdown and the most useful GFM extensions.

When to Use Markdown vs When to Write HTML Directly

Markdown is excellent for content — blog posts, documentation, README files, notes, and anything text-heavy. It's not great for complex layouts, custom styling, or interactive elements.

Write in Markdown when your content is primarily text with basic formatting. Convert to HTML when you need to publish on the web. Write HTML directly when you need precise control over structure, custom classes, or complex component markup.

The two aren't mutually exclusive. Many developers write their content sections in Markdown and their layout structure in HTML. Some static site generators like Hugo and Jekyll let you mix both in the same file.

Markdown in Multiple Languages

Markdown works with any language and any script. Here's how the concept is known globally: