Obsidian for Beginners: 6 Keys to Markdown (2/6) — How to Use the Obsidian App for Notes
Based on Linking Your Thinking with Nick Milo's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.
Use double brackets ([[note]]) to create clickable links that also show up as connections in Obsidian’s Graph view.
Briefing
Markdown isn’t mainly about looking fancy—it’s a practical way to keep ideas portable and connected, so notes don’t get trapped inside a single app. The core payoff is that Obsidian can turn simple Markdown syntax into durable relationships: links tie concepts together directly, tags group them by theme, and lightweight formatting makes notes easier to scan without forcing you into a rigid editor.
The walkthrough starts in Obsidian with creating a new note, then pasting a cheat sheet of the “six keys” to Markdown. The first key is the link. Typing bracket-bracket triggers Obsidian’s note picker, and selecting a note (for example, “note star”) creates a clickable connection. That link isn’t just visual—it shows up in Obsidian’s Graph view as a relationship, reinforcing the idea that Markdown syntax can build a network of thinking rather than isolated text.
The second key is the tag, introduced with hashtag-based labels like “concept.” As the user types “#concept,” Obsidian auto-completes matching tags, and adding tags to multiple notes makes them retrievable as a group. A command-click on a tag brings up search results containing every note with that label, turning tags into a fast way to filter and navigate a personal knowledge base.
With linking and tagging established, the remaining four keys focus on formatting that improves readability while staying out of the way. Italics come from single asterisks around a phrase, used to emphasize a point. Bold uses double asterisks on both sides, useful for drawing attention to important nouns. Lists are created with a hyphen followed by a space; Obsidian automatically recognizes the list structure as items are added.
Finally, headers organize notes into a clear hierarchy. Using a hashtag plus a space creates headings, with six levels available (from the top-level title-like header down through smaller subheaders). The walkthrough demonstrates how quickly notes can be made more structured—turning sections like “Adversity Paradox” into a readable outline and adjusting subheader levels (e.g., header three) to match how the content should be chunked.
The closing message ties the mechanics back to knowledge work: formatting bars aren’t the point because the goal is to externalize ideas into a place that can be revisited and expanded. Markdown keeps the focus on thinking and writing, while links and tags act as “relationship builders” that help the system support recall later. The emphasis is incremental improvement—adding a few tags, tightening headings, and building lists over time—so the notes become easier to navigate and the mind gets more “reps” through repeated interaction with the material.
Cornell Notes
Markdown in Obsidian is presented as a portability-and-connection system, not a styling exercise. The six keys are: links ([[note]]) for direct relationships, tags (#tag) for grouping and retrieval, italics (*text*), bold (**text**), lists (- item), and headers (# Title through six levels). Links appear in Obsidian’s Graph view, while tags can be command-clicked to pull up all notes containing that label. The practical takeaway is that formatting stays lightweight and out of the way, letting writing and idea expansion remain the main activity. Incremental edits—adding tags, headings, and list structure—build familiarity and improve recall through repeated use.
How does Obsidian turn a simple Markdown link into a navigable knowledge connection?
What’s the difference between links and tags for organizing ideas?
How do italics and bold work in Markdown, and when are they useful in note-taking?
How are lists created in Markdown inside Obsidian?
How do headers work in Markdown, and what do the six levels mean in practice?
Why does the absence of a formatting bar matter for the note-taking workflow described here?
Review Questions
- Which Markdown key would you use to create a direct relationship between two specific notes, and how does Obsidian surface that relationship?
- When would you choose a tag over a link in a personal knowledge management system?
- What syntax creates a header, and how can you control the header’s size or hierarchy level?
Key Points
- 1
Use double brackets ([[note]]) to create clickable links that also show up as connections in Obsidian’s Graph view.
- 2
Apply tags with hashtags (#tag) to group related notes and retrieve them quickly via tag search.
- 3
Format emphasis with single asterisks for italics (*text*) and double asterisks for bold (**text**).
- 4
Build structured content with simple lists using a hyphen and space (- item), letting Obsidian handle the list formatting.
- 5
Organize notes with headers (# Heading) and choose among six levels to create a readable hierarchy.
- 6
Keep formatting lightweight so the main focus stays on writing, externalizing ideas, and revisiting them for growth.
- 7
Improve the knowledge base incrementally by adding tags, headings, and list structure as notes evolve over time.