Markdown Cheat Sheet for Faster, Cleaner Work Notes
Markdown is one of those tools that knowledge workers discover, immediately see the value of, and then forget half the syntax for within a week. The problem is not that Markdown is hard. The problem is that forgetting a single character in the middle of a note breaks focus enough to reach for Google — and by the time the tab is open, the thought is gone.
This cheat sheet is organized around the work you actually do, not alphabetical syntax lists. Keep it somewhere you can open in two seconds.
Structuring Notes With Headings
# H1 — Main title or document name
## H2 — Main section
### H3 — Subsection
In practice, most notes only need H2 and H3. H1 is usually the page title or note name. Use headings to separate topics, not to decorate.
Capturing Bullets and Numbered Steps
- Item one
- Item two
- Indented sub-item (two spaces before the dash)
1. First step
2. Second step
3. Third step
Use bullets for unordered lists and items where sequence doesn’t matter. Use numbers for steps, instructions, or ranked items.
Marking Action Items
- [ ] Task not done
- [x] Task completed
Task lists work in most Markdown-based note apps (Notion, Obsidian, Logseq, Linear, GitHub). Check your app — some require a specific toggle or plugin. This is one of the most useful work-note patterns: combine action items with owner initials if the list is shared.
Emphasizing Decisions and Key Points
**bold** — decisions, key metrics, important names
*italic* — terms being defined or lightly emphasized
~~strikethrough~~ — things that were considered but rejected
Adding Links
[Link text](https://url.com)
For meeting notes: link to the relevant document, ticket, recording, or source directly. A note that references “the proposal” is less useful than a note that links to it.
Quoting Statements and Sources
> This is a blockquote.
> Use it for direct quotes from meetings, research, or client messages.
Formatting Code, Commands, and File Names
`inline code` — for commands, file names, field names, or technical values
```
code block
for multi-line code, scripts, or config snippets
```
Inline code is useful for API keys (masked), field names in a CRM, file paths, or any value that should not be reformatted by the app.
Simple Tables (Where Supported)
| Column 1 | Column 2 | Column 3 |
|----------|----------|----------|
| Row 1 | Value | Value |
| Row 2 | Value | Value |
Tables work in GitHub, Notion, Obsidian, and most doc tools, but not in all plain-text environments. Test before relying on them. For comparison notes, decision matrices, or action-item tables with owners and deadlines, they are significantly cleaner than prose.
Horizontal Rules for Visual Separation
---
Use sparingly — to separate distinct sections in a long note, or to mark the end of meeting notes before follow-up actions begin.
When Markdown Does Not Help
- Brainstorming quickly — formatting slows the capture
- Voice notes or dictation workflows
- Collaborating with non-technical clients who use rich-text editors
- Tools with excellent keyboard shortcuts where formatting buttons are faster
A Minimal Starter Set for Most Teams
If your team is new to Markdown, standardize on six patterns only:
- Headings for structure
- Bullets for lists
- Checkboxes for action items
- Bold for decisions
- Links for references
- Blockquotes for direct quotes or key statements from meetings
These six cover 90% of practical note-taking without requiring anyone to learn the full syntax. Add tables and code blocks as the team gets comfortable.
Source: AFFiNE — Build Better Study Habits. Markdown syntax compatibility varies by application. Task lists, tables, footnotes, and other extended syntax may not work in all tools — verify in your specific note-taking app. For a comprehensive reference, see the Markdown Guide.