type
status
date
slug
summary
category
tags
password
icon
Medium Tages
Markdown Cheat Sheet for Absolute Beginners (Bookmark This!)
You just discovered Markdown and everyone says it's "simple," but you're staring at asterisks, hashes, and brackets wondering where to start. Your coworker casually mentions they write everything in Markdown. Your favorite tutorial blog is written in it. GitHub READMEs use it everywhere. But when you try to learn it, the documentation feels overwhelming.
Here's the truth: Markdown is genuinely simple—but only if someone shows you the essentials without the noise.
This cheat sheet will become your most-bookmarked resource. I'm going to show you exactly what you need to know: visual examples, side-by-side comparisons, and a downloadable reference you can keep forever. No fluff, no complex edge cases—just the practical syntax that will serve you every single day.
Let's turn you into a confident Markdown user in the next 8 minutes.
What is Markdown (and Why Should You Care)?
Markdown is plain text formatting that converts to HTML. That's it. You write with simple symbols like
**bold** and it renders as bold. No buttons, no toolbars, no proprietary software.Here's why beginners fall in love with it:
It works everywhere: GitHub uses it for README files. Reddit uses it for comments. Discord, Notion, Stack Overflow, Jupyter Notebooks, countless blogs—they all support Markdown. Learn it once, write anywhere.
It's future-proof: Markdown files are plain text. They'll open on any device, any operating system, 50 years from now. Try opening a Microsoft Word file from 1995—good luck. Your Markdown files? They'll always work.
It's portable: Copy your text from Notion, paste it into GitHub, move it to your blog. Markdown travels without breaking. No "formatting lost" nightmares.
You already know the basics: Ever put
*asterisks* around text in a chat to emphasize something? That's Markdown thinking. You're closer than you realize.The quick win: Learn just seven syntax rules and you'll handle 90% of your formatting needs. Seven. That's less than memorizing keyboard shortcuts in Microsoft Word.
Ready? Let's dive into those seven rules.
The 7 Markdown Syntax Rules You'll Use Every Day
Master these seven formatting rules and you'll handle 90% of your writing needs. Each one takes 30 seconds to learn. I'll show you the syntax, what it looks like when rendered, and when to use it.
1. Bold and Italic Text
The Syntax:
Renders As:
- bold text
- italic text
- bold and italic
When to use it: Bold grabs attention for important points. Italic adds subtle emphasis. Think of bold as shouting, italic as leaning in to whisper.
💡 Pro Tip: Use**double asterisks**for bold and*single asterisks*for italic. Some people use underscores (__bold__or_italic_) but asterisks are more common and work everywhere.
Common mistake: Putting spaces inside the asterisks breaks the formatting.
** text ** won't work. Keep it tight: **text**.2. Headings (Creating Structure)
The Syntax:
Rule of thumb: Use one
# for your document title, ## for main sections, ### for subsections within those sections. Most documents never need more than three heading levels.Example structure:
⚠️ Common mistake: Don't skip levels. Going from##straight to####confuses readers and breaks navigation. Always go in order.
Why this matters: Headings create your document's skeleton. They help readers scan, skip to sections they need, and understand your structure at a glance.
3. Lists (Bullets and Numbers)
The Syntax:
For nested lists, indent with 2 spaces:
Renders As:
- Main point
- Nested point
- Another nested point
- Back to main level
💡 Quick trick: You can use-,*, or+for bullet points—they all work. Stick with-for consistency (it's the most common convention).
Another trick: For numbered lists, you can just use
1. for every item and Markdown will auto-number them. This makes reordering easier:Still renders as 1, 2, 3.
4. Links
The Syntax:
Real examples:
Best practice: Use descriptive link text that tells readers where they're going. Don't do this:
❌
Click [here](url) for documentationDo this instead:
✅
Read the [Python documentation](url) for detailsWhy? It's better for accessibility (screen readers), better for SEO, and more helpful for readers scanning your content.
💡 Email links: Usemailto:in the URL to create clickable email links:[Contact me]([email protected])
5. Images
The Syntax:
Real example:
The crucial difference: That
! exclamation mark at the start makes it an image. Without it, you just have a regular link.= displays the image
[text](url)= creates a clickable link
Alt text matters: The text inside
[ ] is your alt text. It shows if the image fails to load and helps visually impaired readers using screen readers. Always write descriptive alt text.Good:
![Screenshot of terminal showing npm install command]Bad:
![image1] or ![pic]6. Code (Inline and Blocks)
This is where Markdown really shines for technical writing.
Inline code (for short snippets):
Renders as: Use the
print() function to display output.Code blocks (for multi-line code):
Renders as:
💡 Language highlighting: Add the language name after the opening triple backticks for syntax highlighting. Popular options:python,javascript,java,sql,bash,html,css,json
Example with JavaScript:
The language identifier gives you beautiful color-coded syntax highlighting.
7. Blockquotes
The Syntax:
Renders As:
This is a quote or callout.
It can span multiple lines.
Use blockquotes for:
- Actual quotations from sources
- Important callouts or warnings
- Highlighting key takeaways
- Notes or tips that need emphasis
Nested quotes:
Most people rarely nest quotes, but it's there if you need it.
5 Mistakes Every Beginner Makes (Fix Them Now)
I've taught hundreds of people Markdown. These five mistakes come up every time. Save yourself hours of frustration by learning them now.
Mistake #1: Forgetting Blank Lines
The problem: Paragraphs and sections run together when you don't add blank lines between them.
Example:
❌ Wrong:
✅ Right:
Why it happens: In plain text, hitting Enter once just continues the paragraph. Markdown needs that blank line to know you want a new paragraph or section.
The fix: Always add blank lines before and after headings, between paragraphs, and around lists, code blocks, and blockquotes.
Mistake #2: Spaces in Bold/Italic Syntax
The problem: Putting spaces inside the asterisks breaks the formatting.
❌ Wrong:
** text ** or * text *✅ Right:
**text** or *text*What happens: Markdown sees the spaces and thinks you're not trying to format—it displays the asterisks literally: text
The fix: Keep formatting markers tight against the text. No spaces between asterisks and the text you're formatting.
Mistake #3: Forgetting the ! for Images
The problem: Writing
[Image](url) creates a link to the image, not an embedded image.❌ Link (not what you want):
[Logo](logo.png) → Logo✅ Image (embedded):
 → displays the actual imageWhy it happens: Links and images have almost identical syntax. That one little
! makes all the difference.Memory trick: The exclamation mark is you exclaiming, "Look at this image!"
Mistake #4: Inconsistent List Indentation
The problem: Nested lists break or look wrong because of improper indentation.
❌ Wrong (only 1 space):
✅ Right (2 spaces or 1 tab):
The fix: Always indent nested items with 2 spaces (or 4 spaces, or 1 tab—be consistent). One space is too little and breaks rendering on many platforms.
Mistake #5: Not Testing Across Platforms
The problem: Your Markdown looks perfect in your editor but breaks on GitHub or Medium.
Why it happens: Different platforms use different Markdown "flavors"—slight variations in what's supported.
The fix:
- Preview your Markdown before publishing (most editors have preview mode)
- Test on your target platform (write in staging, preview before going live)
- When in doubt, stick to the Essential 7—they work everywhere
Essential Tools for Writing Markdown
These free tools will make your Markdown workflow 10x easier. I use these daily—they'll save you time and frustration.
Best Markdown Editors
Typora (Mac/Windows/Linux)
- What makes it special: WYSIWYG editor—see formatted text as you type
- Free/Paid: Trial available, one-time purchase
VS Code (All platforms)
- What makes it special: Free, powerful, built-in preview (Ctrl+Shift+V)
- Free/Paid: Completely free
Dillinger (Online)
- What makes it special: No installation needed, works in any browser
- Free/Paid: Free
Notion (All platforms + web)
- What makes it special: Combines Markdown shortcuts with rich features
- Free/Paid: Free plan available
Try It Yourself: 5-Minute Challenge
Ready to test your new skills? Complete this challenge and you'll know you've mastered the basics.
Your Challenge
- Open an editor: Go to Dillinger.io (no signup needed)
- Create a document with:
- ✅ One H1 heading (your document title)
- ✅ Two H2 headings (two main sections)
- ✅ Bold text in at least one sentence
- ✅ Italic text in at least one sentence
- ✅ A bulleted list with 3 items
- ✅ One external link (to any website)
- ✅ One inline code example
- ✅ One code block with language highlighting
Example Challenge Solution
Here's what it might look like:
Set a timer for 5 minutes and try it now. If you can create this document without looking back at the syntax, you've mastered the basics. Seriously—put this article aside and test yourself.
What Will You Create?
The beauty of Markdown is its simplicity. No complex software. No licensing. No formatting headaches. Just you, plain text, and the ability to write anywhere, anytime, on any device.
You're now part of the Markdown community—millions of developers, writers, and creators who've chosen simplicity and portability over proprietary tools.
Drop a comment below: What's the first thing you'll write in Markdown? A README? Notes? Documentation? I read every comment and love seeing what people create!
Found this helpful? Share it with someone learning Markdown. Bookmark it for future reference. Come back whenever you need a quick syntax reminder.
Happy writing! 🚀
Looking for more beginner-friendly tutorials? Follow for guides on GitHub, web development, and productivity tools that make your life easier.
Related:
上一篇
Why Developers Love Markdown (And 5 Reasons Developers Love Markdown)
下一篇
Easydict: The Ultimate macOS Translation Tool for Multilingual Work
Loading...
