📝 Lesson 2.1: Markdown Essentials
Markdown is the quiet superpower under every Obsidian note. It's a tiny set of typing habits that turn plain text into clean, formatted writing — no toolbars, no mouse, no lock-in. Learn it once here and you'll use it for the rest of your life, in Obsidian and far beyond.
📚 What You'll Learn
By the end of this lesson, you will be able to:
- Explain what Markdown is and why formatting-as-plain-text is so durable
- Write headings, bold, italic, highlights, lists, and task checkboxes from memory
- Create links, blockquotes, horizontal rules, inline code, and code blocks
- Switch confidently between Obsidian's Live Preview, Source mode, and Reading view
⏱️ Estimated Time: 50 minutes
🎯 Project: Take a messy, unformatted note and rewrite it into clean, readable Markdown.
In This Lesson
What Markdown Is (and Why It Wins)
Imagine you want a word to be bold. In a word processor you select it and click a
button. But that "bold" is now stored as invisible formatting locked inside a proprietary file. In
Markdown, you just type two asterisks around the word — **bold** — and the
app shows it bold. The formatting is the text. Nothing is hidden.
📖 Definition
Markdown is a simple, human-readable way to add formatting to plain text using a
few ordinary keyboard characters — #, *, -, [].
It was created in 2004 to be easy to write and easy to read even in its raw form. Obsidian
notes are Markdown files (.md), which is exactly why they'll still be readable in
twenty years.
Here's why this matters so much for the system we're building:
- It's readable raw. Even without Obsidian, a
.mdfile makes sense in Notepad or TextEdit. Compare that to opening a.docxin a text editor — a wall of gibberish. - It's fast. Your hands never leave the keyboard. Formatting keeps pace with thinking.
- It's portable. The same Markdown works in Obsidian, GitHub, Reddit, Discord, Notion, and countless other places. Learn it once, use it everywhere.
- It's future-proof. Plain text is the most durable format in computing. No company can take it away or change it under you.
**bold**"] --> B["Obsidian reads
the Markdown"] B --> C["You see
bold text"] B --> D["File on disk stays
plain readable text"]
🧠 Mindset
If a page of asterisks and hashes looks intimidating right now, breathe easy. You already know how to make a bullet list — you'd type a dash and a space, exactly what a paper list looks like. Markdown is mostly your existing instincts written down. By the end of this lesson the symbols will feel less like code and more like punctuation. Give it fifteen real minutes of typing and it clicks.
Headings & Text Emphasis
Headings — the skeleton of a note
A heading is a title for a section. In Markdown you make one by starting a line with one or more
# symbols followed by a space. More hashes = smaller, more nested heading.
# Heading 1 — the note's main title
## Heading 2 — a major section
### Heading 3 — a sub-section
#### Heading 4 — a smaller sub-section
Obsidian goes up to six levels (######), but in practice you'll rarely need more than
three. Headings do more than look big — Obsidian builds the note's Outline from them,
lets you fold sections under them, and even lets you link straight to a heading later
([[Note#Heading]]). Good headings are an investment that pays off constantly.
⚠️ Watch Out
You must put a space after the #. # Heading is a heading;
#Heading with no space is a tag (a different feature you'll meet in
Lesson 2.3). This trips up nearly every beginner. When your "heading" turns into a colored tag, a
missing space is almost always the reason.
Bold, italic, strikethrough, and highlight
These are the everyday emphasis marks. Wrap your text in the right symbols:
| You type | You get | When to use it |
|---|---|---|
*italic* or _italic_ |
italic | Gentle emphasis, titles, foreign words |
**bold** or __bold__ |
bold | Strong emphasis, key terms |
***bold italic*** |
bold italic | Maximum emphasis (use sparingly) |
~~strikethrough~~ |
Done, rejected, or outdated ideas | |
==highlight== |
highlight | Marking the single most important line |
The ==highlight== syntax is one Obsidian supports specifically (it's not part of the
original Markdown standard, but Obsidian and many tools add it). It renders like a yellow marker over
the text — perfect for the one sentence in a note you never want to lose.
✅ Pro Tip
You don't have to type these symbols by hand every time. Select a word and press Ctrl/Cmd + B for bold or Ctrl/Cmd + I for italic — Obsidian inserts the asterisks for you. Learning the symbols still matters (so you can read raw notes and type fast), but the shortcuts are there when your hands prefer them.
Lists & Task Checkboxes
Bullet lists
Start a line with a dash and a space (- ) to make a bullet. Obsidian also accepts
* or +, but a dash is the most common and readable choice — pick one and stay
consistent.
- Milk
- Bread
- Coffee beans
Numbered lists
Start lines with 1., 2., 3. — a number, a period, and a space.
Use these when order matters (steps, rankings).
1. Open Obsidian
2. Create a note
3. Start typing
💡 Handy trick: You can actually type 1. on every line and Markdown
will still number them 1, 2, 3 correctly when rendered. This means you can reorder steps without
renumbering by hand. Obsidian also auto-continues a list when you press Enter.
Nested lists
Press Tab (or add spaces) to indent a list item under another. This creates sub-points — a simple, powerful way to outline your thinking.
- Fruit
- Apples
- Bananas
- Vegetables
- Carrots
- Spinach
To un-indent, press Shift + Tab. Nesting works several levels deep and mixes bullets with numbers freely.
Task checkboxes — your notes become a to-do list
This is one of the most-loved features in all of Obsidian. Make a bullet, then add square brackets to turn it into a checkbox:
- [ ] An unfinished task
- [x] A completed task
A space between the brackets (- [ ]) is an empty box; a lowercase x
(- [x]) is a checked box. In Live Preview and Reading view these render as real, clickable
checkboxes — click one and Obsidian writes the x into your file for you. Your note has
quietly become a working to-do list, and because it's plain text, those tasks live right alongside the
context that created them.
💡 A glimpse of what's possible
Because tasks are just special bullets in plain text, a community plugin called Tasks
can later scan your entire vault and collect every unchecked - [ ] into one
live list, add due dates, and more. You don't need it yet — but know that today's simple checkbox is
the seed of a full task-management system. Foundations first.
Links, Quotes & Rules
External links (to the web)
To link to a website, put the visible text in square brackets and the URL in parentheses right after, with no space between them:
Read the [Obsidian help docs](https://help.obsidian.md) for more.
That renders as: Read the Obsidian help docs for more. The bracketed part is what the reader sees; the parentheses hold the destination. You can also paste a bare URL and Obsidian will make it clickable.
Internal links (to your own notes) — a first taste
Obsidian adds its own, even simpler link style for connecting your notes to each other: type two square brackets and the note's name.
I wrote more about this in [[Sleep Habits]].
These internal links (also called wikilinks) are the beating heart of Obsidian — they
turn your notes into a connected web. When you type [[, Obsidian pops up a list of your
notes to pick from. We're only mentioning them here so you recognize the syntax; we devote all
of Module 3 to linking, backlinks, and the graph. For now, just know the two shapes:
[text](url) goes out to the web, [[Note]] connects within your vault.
→ external website"] A --> C["[[Note Name]]
→ another note in your vault"] C --> D["Builds your web
of ideas (Module 3)"]
Blockquotes
Start a line with > and a space to create a quote block — indented, with a bar down
the side. Great for quoting a source, highlighting an important note, or setting text apart.
> The palest ink is better than the best memory.
> — a Chinese proverb
Everything on a > line becomes part of the quote. You'll see in the next lesson that
Obsidian builds its beautiful colored callout boxes right on top of this humble
blockquote syntax.
Horizontal rules
Three or more dashes on their own line (---) draw a horizontal divider across the page —
handy for separating big sections within a long note.
First topic wraps up here.
---
A fresh topic begins here.
⚠️ Watch Out
Three dashes make a divider in the middle of a note. But three dashes on the very first line of a note mean something completely different — they open a Properties (YAML frontmatter) block, which you'll learn in Lesson 2.3. Leave a blank line above your dividers and you'll never confuse the two.
Code: Inline & Fenced
Even if you never write software, "code" formatting is useful for anything you want shown in a monospace font, exactly as typed — file names, keyboard keys, commands, or a snippet you don't want the editor to "helpfully" reformat.
Inline code
Wrap a word or two in single backticks (` — the key above Tab on most
keyboards):
Open the `settings.json` file and change `theme` to dark.
That renders the wrapped bits in a distinct monospace style, set apart from the sentence. Perfect for referring to filenames or exact values without them getting mangled.
Code blocks (fenced)
For several lines of code or preformatted text, use a "fence" — three backticks on their own line before and after your block:
```
def greet(name):
print("Hello, " + name)
```
Everything between the fences is shown verbatim, in a neat box, with nothing interpreted as Markdown.
You can name the language right after the opening fence (like ```python) to get syntax
highlighting — colored keywords and strings. We'll explore that, plus math and Mermaid diagrams, in the
next lesson.
✅ Pro Tip
Code blocks are the safest way to paste text you want left exactly as-is — a URL with odd characters, an ASCII diagram, or example Markdown you want to show rather than render (this very lesson does that constantly). If Obsidian keeps "eating" your symbols, wrap them in backticks.
The Three Views: Live Preview, Source, Reading
Here's the question every newcomer asks: "Do I have to look at all these asterisks while I write?" Happily, no. Obsidian gives you three ways to view the very same note, and understanding them removes all the confusion.
| View | What you see | Best for |
|---|---|---|
| Live Preview (default) | Text looks formatted as you type; the symbols quietly appear only on the line your cursor is on | Everyday writing — the best of both worlds |
| Source mode | The raw Markdown, every symbol visible all the time | Precise edits, fixing tricky syntax, learning |
| Reading view | The fully rendered, finished page — no editing, no symbols | Reading, reviewing, or presenting a note |
Live Preview vs. Source: two ways to edit
Live Preview and Source mode are both editing modes — you can type in either. The
difference is how much raw syntax they show you. In Live Preview, a line reading
**important** displays as important while you write, and only reveals its
asterisks when your cursor lands on that line so you can edit them. In Source mode, you
always see **important**, symbols and all. Most people live in Live Preview and dip into
Source when something looks wrong and they want to see exactly what's on the line.
You toggle between these two editing modes in Settings → Editor → "Default editing mode," or per-note from the more-options (⋮) menu in the top-right of a note.
The pencil/book toggle: Editing vs. Reading
In the top-right corner of every open note is a small book/pencil icon. It flips the note between editing (pencil — where Live Preview or Source lives) and Reading view (book — the clean, final render). The keyboard shortcut is Ctrl/Cmd + E, and it's one worth memorizing — you'll bounce between writing and reading constantly.
(formatted while typing)"] A --> D["Source mode
(raw symbols shown)"]
💡 The mental model
Think of it as one document with three lenses. Reading view is the printed page. Source mode is the manuscript with all the editor's marks. Live Preview is the magic middle — the page that formats itself as you write. The file on disk never changes; only your view of it does. That's why nothing you do here can "break" your note.
🎯 Project: Rewrite a Messy Note
Time to make Markdown a habit, not a concept. Below is a raw, unformatted note — the kind we all actually write when thoughts tumble out. Your job is to rewrite it as clean Markdown in Obsidian, using every tool from this lesson.
🏋️ Format the "Weekend Plan" note
Objective: Convert plain text into a structured, readable note using headings, emphasis, lists, tasks, a link, a quote, and a divider.
Here's the messy source (create a new note and paste it in):
Weekend Plan
Big goal for the weekend is to finally organize the garage and relax a bit.
Garage stuff to do buy shelving from the hardware store, sort the boxes, throw out old paint, sweep the floor. The paint one is important dont forget hazardous waste rules.
Relaxing ideas watch that documentary, go for a run, call mom.
Quote I like: the secret of getting ahead is getting started.
Useful link https://help.obsidian.md
Instructions (about 15 minutes):
- (2 min) Make "Weekend Plan" a level-1 heading (
#), and add two section headings (##): "Garage" and "Relaxing." - (3 min) Turn the garage jobs and relaxing ideas into bullet lists.
- (3 min) Convert the garage jobs into task checkboxes
(
- [ ]) so you can tick them off. Mark one as already done with- [x]. - (2 min) Highlight (
==...==) or bold the hazardous-waste warning so it can't be missed. - (2 min) Put the quote in a blockquote (
>). - (1 min) Make the link a proper Markdown link with friendly text.
- (2 min) Add a horizontal rule (
---) between the two sections, then flip to Reading view (Ctrl/Cmd + E) and admire your work.
💡 Hint — the shape you're aiming for
# Weekend Plan
Big goal: **organize the garage** and relax a bit.
## Garage
- [ ] Buy shelving from the hardware store
- [ ] Sort the boxes
- [ ] Throw out old paint — ==follow hazardous waste rules!==
- [x] Sweep the floor
---
## Relaxing
- Watch that documentary
- Go for a run
- Call mom
> The secret of getting ahead is getting started.
Useful link: [Obsidian help docs](https://help.obsidian.md)
🧩 Stuck? Common fixes
- Your heading turned into a colored tag? You forgot the space after
#. - Checkboxes not clickable? Make sure it's
- [ ]with a space between the brackets, and view the note in Live Preview or Reading view. - Highlight not working? It needs two equals signs each side:
==text==.
✅ Project Completion Checklist
- The note has one
#title and two##section headings - Garage jobs are task checkboxes, with at least one checked
- The hazardous-waste line is highlighted or bold
- The quote is in a blockquote
- The link uses
[text](url)syntax and is clickable - A
---divider separates the two sections - You viewed the finished note in Reading view
🎯 Quick Quiz
Question 1: Which line correctly creates a heading in Obsidian?
Question 2: You want a clickable, unfinished to-do item. What do you type?
Best Practices for Writing in Markdown
✅ Do's
- Use headings generously. They give a note structure, feed the Outline, and become link targets later.
- Pick one bullet character (a dash) and one bold style (asterisks) and stay consistent across your vault.
- Leave blank lines between blocks — between a heading and a list, between paragraphs. Markdown loves breathing room.
❌ Don'ts
- Don't over-format. If everything is bold and highlighted, nothing stands out. Emphasis works because it's rare.
- Don't fight the editor. If symbols keep vanishing, you're probably in Live Preview with your cursor off the line — that's normal, not a bug.
- Don't forget the space after
#,-, and>. Nearly every "why won't this format" moment is a missing space.
📓 Learning Journal
Keep a learning journal inside your own vault — a perfect chance to practice today's Markdown. After each lesson, take a few minutes to write down:
- Key concepts you learned
- Techniques that clicked for you
- Questions or confusion points to revisit
- Ideas you want to try
- Your progress and feelings about learning this
✍️ This lesson's prompt: Write your journal entry for today using at least one heading, one bullet list, one task checkbox, one bold or highlighted phrase, and one blockquote. Then flip to Reading view. Which piece of Markdown felt most natural, and which one will you have to look up again?
📝 Lesson Summary
🎓 Key Takeaways
- Markdown formats plain text with a few keyboard characters, so your notes stay readable, fast, portable, and future-proof.
#makes headings (mind the space!),**bold**,*italic*,~~strike~~, and==highlight==handle emphasis.- Lists use
-and1.; tasks use- [ ]and- [x]for clickable checkboxes. [text](url)links to the web;[[Note]]links to your own notes (Module 3).>quotes,---divides, backticks make code.- One note, three views: Live Preview (format while typing), Source (raw symbols), Reading (final page). Toggle with Ctrl/Cmd + E.
🎉 What You've Accomplished
You've learned the entire everyday Markdown toolkit — the same syntax that powers Obsidian, GitHub, and half the writing tools on the internet. You took a messy note and gave it a clean structure, and you now understand why the symbols sometimes appear and sometimes hide. This is the literal language of every note you'll ever write in this course. Beautifully done.
❓ Common Questions at This Stage
Do I have to memorize all these symbols?
No — and you won't have to try. After a few days of writing you'll have headings, bold, lists, and tasks in muscle memory, which covers 90% of daily use. The rarer ones (highlight, strikethrough) you can always look up. Obsidian also offers Ctrl/Cmd-key shortcuts and a command palette so you rarely have to remember cold.
Why do the asterisks appear and disappear while I type?
That's Live Preview doing its job. It shows formatted text everywhere except the line your cursor is on — there it reveals the raw symbols so you can edit them. Move your cursor away and the line renders cleanly again. If you'd rather always see the symbols, switch to Source mode.
Is Obsidian's Markdown exactly the same as everywhere else?
The core is universal — headings, bold, lists, links, and code work identically across tools.
Obsidian adds a few friendly extras (like ==highlight==, [[wikilinks]],
callouts, and math) that some other apps don't support. Your notes stay portable; just know a couple
of the fancier bits are Obsidian-flavored.
🔭 Looking Ahead
You've got the essentials cold. Next lesson we go beyond basics: Obsidian's gorgeous callout boxes, real tables, syntax-highlighted code, math with LaTeX, footnotes, embedding images and other notes, hidden comments, and even Mermaid diagrams inside your notes. Your notes are about to get seriously powerful.
✅ Before the Next Lesson
- Complete the "Weekend Plan" rewrite and view it in Reading view
- Practice toggling editing/Reading with Ctrl/Cmd + E a few times
- Write your Learning Journal entry in Markdown
📚 Additional Resources
- Obsidian Help — Basic formatting syntax
- Obsidian Help — Advanced formatting syntax
- The Markdown Guide — basic syntax
🌟 Encouragement for the Journey
You just learned a skill you'll carry for decades — Markdown outlives apps, jobs, and trends. Every note from here on is written in a language you now speak. The symbols already look a little less strange, don't they? Onward to the fun stuff. 🔮