Markdown shows up everywhere a writer works now. Notes apps use it. Blogging tools use it. Even simple text editors quietly support it in the background. If you write for a living, or even just for yourself, you have probably seen a stray asterisk or pound sign and wondered what it does and whether you need to learn it.
Here is the short answer: you don’t need to learn all of it. Most guides to Markdown are written by developers, for developers, and they list every symbol the format supports. A writer doesn’t need every symbol. A writer needs six.
I’ve spent the last five years building and refining my own writing workflow across notes, drafts, and finished pieces, and Markdown has been part of that setup the whole time. Rohan Ratnayake has been exploring and writing about Digital Writing Workflows & Craft for years, bringing research, cultural context, and clear explanations to readers. What I’ve noticed, working inside these tools day after day, is that writers who try to learn Markdown like a piece of software end up frustrated. The ones who learn it like a small set of habits pick it up in an afternoon and never think about it again. This piece is built around that second approach.
What a Writer Actually Needs From Markdown
Most Markdown documentation is organized around what the software can render: tables, footnotes, task lists, strikethrough, code blocks, definition lists, and more. That list keeps growing because Markdown has been extended by dozens of different tools over the years, each adding its own features.
But a writer isn’t building software. A writer is trying to get a thought out of their head and onto the page in a shape that makes sense. The real question isn’t “what can Markdown do?” It’s “what does a draft actually need?”
A draft needs a few things, and only a few:
- A way to mark where a new section starts
- A way to mark a word or phrase that carries extra weight
- A way to break one idea into separate pieces
- A way to hold someone else’s words apart from your own
- A way to point a reader somewhere else without breaking the sentence
- A way to mark a shift in scene, tone, or time without writing a whole transition sentence
That’s six needs. And it happens that six marks answer them directly, with nothing left over. Everything else in Markdown exists to solve problems that belong to code, spreadsheets, or web pages, not to a person drafting an essay, a newsletter, or a chapter.
The Six Marks That Cover Almost Everything
Below is the full set, explained the way a writer thinks about them rather than the way a manual would list them.
Heading: Marking Where a Section Starts
When I outline a piece before writing it, each major point becomes its own section. A heading is just a pound sign followed by a space and the section title, like # Section Title. One pound sign marks a top-level section, two mark a sub-section, and that’s as deep as most drafts ever need to go.
Headings matter because they let you see the shape of a piece without reading every line. When I’m revising a long draft, I’ll often collapse it down to just the headings to check whether the order of ideas makes sense. That’s hard to do with plain paragraphs stacked on top of each other. A heading turns a wall of text into a map.
Emphasis: Marking a Pull-Out Thought
Every writer has moments where one word or phrase needs to land harder than the rest of the sentence. Emphasis handles that. Wrapping a word in single asterisks makes it italic, which reads as a lighter stress, closer to how you’d say the word if you leaned on it slightly while speaking. Wrapping it in double asterisks makes it bold, a heavier, more visual stress.
I use italics far more than bold in actual drafting. Bold tends to shout, and a page full of bold words stops meaning anything. Italics, used sparingly, work more like a raised eyebrow than a shout. The rule I follow is simple: if you’d naturally stress the word while reading the sentence out loud, it earns emphasis. If you wouldn’t, leave it plain.
List: Breaking One Idea Into Its Parts
Some ideas don’t want to be a paragraph. They want to be laid out side by side so a reader can scan them. That’s what a list does. A dash or asterisk at the start of a line creates a bullet point. A number followed by a period creates a numbered list, which signals a sequence or a ranking rather than a flat set of items.
Lists are useful for a writer specifically because they force you to separate ideas that might otherwise get tangled into one long sentence. If you find yourself writing a sentence with three “and”s in it, that’s usually a list trying to escape a paragraph.
Quote: Holding Someone Else’s Words Apart
When I’m citing a source, referencing something someone said in an interview, or pulling a line from an email to react to, I don’t want that text to look like it came from me. A greater-than sign at the start of a line creates a block quote, visually setting the text apart from the surrounding draft.
This is what a block quote looks like once it renders — indented and visually separated from the writer’s own sentences around it.
This matters more than it seems. A reader’s eye needs a signal that says “this next part isn’t the author talking.” Without that signal, quoted material blends into the writer’s own voice, and readers lose track of who is actually saying what.
Link: Pointing Somewhere Without Breaking the Sentence
Writers reference other things constantly — a source, a related piece, a tool, a definition. Without a clean way to link, you either paste a raw web address into the middle of a sentence, which is ugly and hard to read, or you write “click here,” which tells the reader nothing about where “here” goes.
A Markdown link solves both problems: [the actual source](https://example.com) turns visible, readable text into a clickable path, while keeping the raw address out of the sentence. The sentence stays smooth, and the reader still knows exactly what they’re clicking toward before they click it.
Divider: Marking a Scene Break
This is the mark writers know least about, and it might be the most useful one for anyone writing narrative, personal essays, or anything with more than one section of tone or time. Three dashes on their own line create a horizontal divider.
That line above is a divider. It tells a reader, without a single word, that something has shifted — a jump in time, a change of scene, a pause between two loosely connected thoughts. I use it constantly in personal essays where I don’t want to write a clunky transition sentence like “Now, moving on to a different point.” The divider does that work silently.
From Writer’s Intent to the Mark That Does It
Here’s the same six marks laid out as a straight lookup, so you can find the mark by what you’re trying to do rather than by its name.
| What you’re trying to do | What you’d call it while drafting | The mark that does it |
|---|---|---|
| Start a new section | “This is a new part of the piece” | # heading |
| Stress one word or phrase | “This needs a pull-out thought” | *italic* or **bold** |
| Break an idea into pieces | “This wants to be a list, not a sentence” | - or 1. |
| Set apart someone else’s words | “This is a source I’m quoting” | > block quote |
| Point to something else | “I want to reference this without breaking flow” | [text](url) |
| Shift scene, tone, or time | “This is a scene break” | --- |
The Marks That Actively Harm a Draft
Markdown supports a lot more than six marks, and some of the extras cause real damage to a draft the moment you reach for them. These aren’t neutral extra features. They pull you out of writing mode and into layout mode, which is a different kind of thinking entirely.
Tables Turn a Writer Into a Spreadsheet Builder
The moment you start typing pipe characters and dashes to build a table by hand, you’ve stopped drafting and started formatting. Getting the columns to line up, deciding on column widths, and keeping the syntax valid takes real attention — attention that just left the actual content of your piece.
Tables have a place. This article uses one. But a table belongs in the editing or formatting stage, added once the ideas are settled, not while you’re still working out what you want to say. Reaching for a table mid-draft is usually a sign that a simple list or a short comparison sentence would have done the job with far less effort.
Inline HTML Breaks the Whole Point of Plain Text
Markdown was built so writers could format text without touching code. Dropping raw HTML tags into a Markdown file undoes that entirely. Once you write <div> or <span> in the middle of a draft, you’re not writing prose anymore — you’re writing markup, and your attention has shifted from sentences to tags.
I’ve watched writers get stuck fiddling with an HTML tag for ten minutes over something that a plain sentence would have solved in five seconds. If you find yourself typing an angle bracket, that’s the moment to stop and ask what you were actually trying to say.
Footnote Sprawl Pulls You Away From the Argument
Footnotes have a real use in academic or heavily sourced writing. But footnote syntax in Markdown, with its numbered reference markers and separate definition blocks at the bottom of the file, invites over-use. Once the syntax is available, it’s tempting to footnote every aside, every qualifier, every “well, technically” thought that crosses your mind.
A draft weighed down with footnotes stops reading like a piece of writing and starts reading like a legal document. Most asides that would have become a footnote can either be cut entirely or folded into the sentence itself with a comma. Save footnotes for genuine citations, not for every stray thought.
The Same Passage, Two Ways
The difference between the six-mark approach and the everything-approach is easier to see than to explain. Here is one short passage from a draft I wrote about morning routines, first cluttered with extra syntax, then cleaned down to only the six marks.
Cluttered version:
## Morning <span style="color:gray">Routine</span> Notes
| Time | Task |
|---|---|
| 6:00 | Wake up |
| 6:15 | Coffee |
I wake up around 6<sup>[1]</sup> and the first thing I do is make coffee<sup>[2]</sup>. <div>Some people skip this step</div> but I never do.
[1]: Approximate, varies by season
[2]: Usually a pour-over, sometimes instant
Six-mark version:
## Morning Routine
I wake up around 6 and the first thing I do is *make coffee*. Some people skip that step. I never do.
The second version says exactly the same thing. It took less time to write, it’s easier to read, and nothing about the meaning was lost by dropping the table, the HTML tags, and the footnotes. The clutter in the first version wasn’t adding information — it was adding formatting decisions that had nothing to do with the actual sentence.
How to Build the Habit With Just Six Marks
Learning six marks isn’t really about memorizing symbols. It’s about building a habit of reaching for the right one without stopping to think. Here’s how that habit tends to form, based on how it played out in my own writing over time:
- Start by using only headings and lists for the first week. Those two alone cover most organizational needs in a typical draft.
- Add emphasis once headings and lists feel automatic. Watch for words you’d naturally stress out loud, and mark only those.
- Bring in the block quote the first time you cite or reference someone else’s exact words.
- Use the link syntax the first time you catch yourself pasting a raw web address into a sentence.
- Save the divider for pieces with more than one section or scene, and resist using it just to break up a wall of text — it should mark an actual shift, not just visual fatigue.
Within a few weeks, this stops being something you think about at all. The marks become as automatic as a comma or a period, and your attention stays where it belongs: on the sentence you’re actually writing.
Where the Six Marks Fall Short
No system covers every case, and it’s worth being honest about the gaps. If you’re writing something with genuinely tabular data — pricing comparisons, spec sheets, schedules — a table earns its place, and you should add it once the draft is otherwise done. If you’re writing academic work with formal citations, real footnotes make sense, used sparingly. And if you’re publishing to a platform that needs specific embed code, some inline HTML becomes unavoidable.
The point isn’t that these marks are forbidden. It’s that they belong to formatting, not drafting. Add them at the end, once your thinking is finished, rather than reaching for them while you’re still figuring out what you want to say.
Common Questions Writers Ask About Markdown
Do I need to learn every Markdown symbol to use it well? No. The six marks covered here — heading, emphasis, list, quote, link, and divider — handle nearly everything a typical draft needs. The rest of Markdown’s syntax exists mostly for code, data, and web publishing tasks that most writers rarely touch.
Will using only six marks limit what I can publish? Not for most writing. Essays, articles, newsletters, and notes rarely need anything beyond these six. If a specific piece genuinely needs a table or a citation format, you can add that one extra mark for that one piece without changing your everyday habits.
Is Markdown different across apps like Notion, Obsidian, or a blogging platform? The core six marks behave the same almost everywhere, since they come from the original Markdown specification. Extra features, like tables or footnotes, vary more between tools, which is another reason to lean on the six marks that stay consistent.
What’s the fastest way to actually learn these six marks? Use them in real drafts instead of a practice file. A symbol learned while solving an actual writing problem sticks far better than one memorized from a reference sheet.
Bringing It Together
Markdown looks bigger than it is because most guides to it are written from the software’s point of view instead of the writer’s. Strip that away and what’s left is a small, steady set of tools: a heading to mark structure, emphasis to mark stress, a list to break ideas apart, a quote to hold someone else’s words apart from yours, a link to point elsewhere without breaking your sentence, and a divider to mark a shift in scene or tone.
Everything past those six exists to solve problems that belong to a different kind of work. Learn the six, use them until they’re automatic, and leave the rest for the rare piece that actually needs it.
What does your own drafting setup look like right now, and is there a mark from this list you’ve been avoiding without meaning to? I’d like to hear what’s working for you in the comments.
