What Is Markdown Syntax and How Does It Work?
Markdown is a plain-text formatting syntax created by John Gruber in 2004 that converts simple text characters into formatted HTML. A hash symbol becomes a heading, asterisks become bold or italic text, a hyphen becomes a list item. WikiPlus Markdown Editor at wikiplus.co lets you write Markdown and see the rendered result in real time — making it ideal for learning the syntax by immediately seeing each element's output.
The Philosophy Behind Markdown
Markdown was designed with one core principle: a Markdown document should be readable as plain text, without appearing to be marked up with tags or formatting instructions. A sentence like **this is important** is still readable as plain text — the asterisks suggest emphasis through their placement even before rendering. This contrasts with HTML (<strong>this is important</strong>) which is harder to read in its raw form, and with rich text editors (Word, Google Docs) where formatting metadata is hidden. Markdown files are stored as plain text (UTF-8 .md files), making them future-proof, version-control friendly, and readable without specialized software. This is why developers adopted Markdown for documentation — Git commit messages, README files, and issue trackers all work better with plain text than binary document formats.
Core Markdown Elements: Complete Reference
The essential Markdown elements with syntax: Heading 1: # Title. Heading 2: ## Section. Heading 3: ### Subsection (up to ######). Bold: **text** or __text__. Italic: *text* or _text_. Bold italic: ***text***. Strikethrough (GFM): ~~text~~. Unordered list: - item (or * or +). Ordered list: 1. item. Nested list: indent with 2–4 spaces. Horizontal rule: --- or ***. Link: [link text](https://url.com). Image: . Inline code: `code`. Code block: ```language on first line, ``` on last line. Blockquote: > quoted text. Table (GFM): | H1 | H2 | with | --- | --- | separator. Task list (GFM): - [ ] unchecked item. Footnote: text[^1] with [^1]: footnote content. These 20 elements cover virtually all Markdown writing needs. Try each in WikiPlus Markdown Editor at wikiplus.co and see the rendered output instantly.
Markdown Flavors: CommonMark, GFM, and Others
Markdown has several variants ('flavors') with slightly different rules and extensions. CommonMark is a standardized specification attempting to resolve ambiguities in Gruber's original description — it is the most widely adopted specification for new tools. GitHub Flavored Markdown (GFM) extends CommonMark with tables, task lists, strikethrough, and autolinks — it is the de facto standard for technical documentation. MultiMarkdown extends GFM further with footnotes, citations, tables of contents, and LaTeX math support — used in academic writing tools. Pandoc Markdown extends further still with additional academic and technical features. The key practical point: when writing for GitHub, use GFM syntax. When writing for a general Markdown-consuming tool, CommonMark is the safe default. WikiPlus Markdown Editor supports GFM, which covers both CommonMark and the GitHub-specific extensions.
Markdown in Different Platforms
Markdown is accepted by a wide range of platforms, each with slightly different rendering behavior. GitHub: GFM with GitHub's own CSS and some GitHub-specific extensions (code block rendering, issue/PR reference linking). Notion: Markdown input mode with Notion's block rendering — paste Markdown and Notion converts it to blocks. Ghost (blogging platform): native Markdown editor with a custom flavor. Jekyll/Hugo/Next.js (static site generators): Markdown files as page source, rendered at build time. Reddit: simplified Markdown for post and comment formatting. Discord: simplified Markdown for chat messages. Stack Overflow: simplified Markdown for questions and answers. For most of these platforms, GFM-compatible Markdown is the safest common denominator. Write in WikiPlus Markdown Editor, verify the preview, and export for the target platform.
Frequently Asked Questions
- What does Markdown look like? Show me an example.
- A Markdown document looks like this in plain text: # My Heading followed by a blank line, then paragraph text, then **bold words** and *italic words*, then a list starting with - Item one and - Item two. The same document rendered in HTML shows a large H1 heading, a normal paragraph with bold and italic words, and a bulleted list. The plain text version is readable even without rendering — this readability is Markdown's core design principle. Open WikiPlus Markdown Editor at wikiplus.co to type Markdown and see the rendered output side by side in real time.
- Is Markdown hard to learn?
- No. The ten most common Markdown elements cover 90% of everyday use and can be learned in 15 minutes: # for headings, **text** for bold, *text* for italic, - item for lists, 1. item for numbered lists, [text](url) for links,  for images, `code` for inline code, and triple backticks for code blocks. The remaining elements (tables, task lists, blockquotes) are learned as needed. WikiPlus Markdown Editor is ideal for learning because you see the rendered output of each syntax element immediately as you type it — trial and error produces instant feedback.
- Where is Markdown used in real life?
- Markdown is used everywhere in software development and writing: GitHub README files and issues (every developer repository has at least one .md file), documentation sites (most developer docs tools — MkDocs, Docusaurus, GitBook — use Markdown as the source format), note-taking apps (Obsidian, Bear, Notion all support Markdown input), static site generators (Jekyll, Hugo, Next.js MDX), blog platforms (Ghost, Hashnode, Dev.to), and communication tools (Slack, Discord, Reddit use simplified Markdown for text formatting). Markdown is the most widely used human-readable markup language in software contexts.