Why I Write in Markdown for Most of My Work

Writing feels better when the tool disappears.

Quick Summary

• I write in Markdown because it is just plain text with light structure, which keeps writing readable and portable.
• Using the same syntax across tools protects focus and makes it easier to move work around.
• WordPress and many modern apps understand Markdown patterns, so the habit scales well.
• Rich editors offer more features, but Markdown is the one that reliably gets out of the way.

AI-generated summary based on the text of the article and checked by the author. Read more about how BUT. Honestly uses AI.

Most writing apps promise help. They offer menus, templates, formatting bars, and collaboration modes. They look powerful. In practice, they often slow down the only thing that matters, which is getting words out of your head and onto the page.

Markdown never tried to be helpful in that way. It does almost nothing, and that is why I write in Markdown for most of my work.

I started with it for boring reasons. I needed a clean way to write documentation and internal posts that would survive copy-paste, different tools, and years of edits. Markdown solved that. Over time it did something else. It changed how I think about writing work itself.

What Markdown Actually Is

Markdown is just plain text with small hints.

You type normal sentences. When you want a heading, you start the line with #. When you want emphasis, you wrap a word in *asterisks*. Lists are just lines that start with - or *.

You are not dragging sliders or choosing fonts. You are describing intent—what makes Markdown work.

• This line is a heading.
• This word should stand out.
• This group of lines is a list.

The text stays readable in its raw form. If you never convert it, you can still understand it. When you do render it, it becomes clean HTML, or a nicely formatted page, or a help article in your docs.

That gap between plain text and finished output is the point. Markdown does not ask you to commit to a final shape. It only asks you to be clear about structure.

Writing Without Friction

Good writing feels like a straight line between thought and hand.

Every time you leave the keyboard, that line bends. You move the mouse to find the bold button. You hunt inside a menu for “Heading 2”. You switch to a different app because the current one does not handle code blocks well.

Each small interruption is harmless on its own. Together they add a background drag. You feel it most on hard pieces. The part of your brain that should be holding onto an idea is busy managing the interface.

Markdown reduces that drag—a plain tool that holds the boring stuff in place.

Everything happens from the keyboard.

• Need a heading? Type ## and keep going.
• Need a list? Start a line with - and write the first item.
• Need a link? Write (url) and move on.

No modal windows. No “format painter”. No mode switches. The tool is not trying to be clever. It is just following along.

For me, this matters in the kind of writing I do most days. Documentation. Internal posts. Support replies. Essay drafts. The content is different, but the structure is the same, and Markdown stays stable under all of it.

One Syntax, Many Places

The real strength of Markdown is not any single editor. It is the fact that the same tiny language shows up almost everywhere.

In daily work I see it in:

• WordPress posts and pages
• P2 threads
• GitHub READMEs
• Documentation portals
• Slack messages
• AI prompt templates
• Google Docs (as of 2022)

I can move between these tools without changing how I write. A heading is a heading. A list is a list. The same characters mean the same thing in each place.

That consistency does two useful things.

First, it protects my attention. I do not have to relearn a new toolbar every time I switch context. My hands do the same thing, and my brain can stay on the problem.

Second, it makes my writing portable. A support reply drafted in a plain text file on my laptop can be pasted into WordPress, Slack, or a doc without breaking. The structure survives the trip.

Markdown Inside WordPress

When I first started, WordPress did not understand Markdown on its own. I used Jetpack’s Markdown module, which converted the syntax into HTML on save. It worked, but it added an extra layer to think about.

Then the block editor arrived and changed the picture.

WordPress learned just enough Markdown to be helpful. If you start a line with #, it becomes a heading block. If you type - and space, you are now in a list. The editor watches for the patterns and quietly turns your habit of writing in Markdown inside WordPress into structured content.

This feels like the right balance. WordPress adapts to how I already write instead of asking me to click my way into whatever block I want. The habit I use in plain text files carries directly into the editor.

That same pattern exists outside WordPress too. Many modern tools speak a kind of Markdown dialect now. You can feel the influence of the original idea even when the exact syntax changes.

The Markdown Tools I Actually Use

I have tried many editors over the years. It is easy to get lost in this part, because writing tools are often more fun to explore than writing itself.

Ulysses on macOS is the one long-form editor that stuck. It treats each piece as a sheet, handles large libraries well, and exports clean files. For a while, almost everything I wrote started there.

Today, my writing is more spread out:

• WordPress for public posts.
• P2 for internal discussions.
• Plain text files in a synced folder for notes and drafts.

Markdown is the thread that connects all of them. It is the same pattern in each place. Headings, lists, emphasis, and links. The exact app becomes less important, which is a comfortable place to be.

If Ulysses vanished, or WordPress changed, or I needed to switch laptops, my writing would still live in simple text files that any editor can open.

Why I Still Write in Markdown

By now, there are many other options.

Some editors give you AI assistants, goal trackers, and complex outlining tools. Some let you design the final layout as you write. Others try to be full publishing platforms on their own.

I test these sometimes. They are impressive. They also tend to pull my attention outward. I end up thinking about features, templates, and workflows instead of the thing I sat down to write.

Markdown remains the only system that consistently stays out of the way.

• It does not assume anything about the final form.
• It adds structure when I ask and stays quiet otherwise.
• It works the same across almost every tool I use.

There is also a simple, practical reason: longevity.

Ten years from now, any text editor will still open a .md or .txt file. Plain text writing means no vendor lock-in, no proprietary format to migrate away from, and no sudden “version 2” that breaks older drafts.

My words are just text. If I want to move them into a new system, I can. If I want to keep them as they are, that works too.

How To Start Using Markdown This Week

If you want to try Markdown, you do not need a whole new system. You can treat this week as a small test.

Here is a simple way to do that.

1. Pick one place where you already write. Maybe it is WordPress, P2, a docs tool, or a folder of notes. Do not change the tool. Just decide that for the next seven days, anything you write there will use Markdown.
2. Learn five patterns and ignore the rest. You can do a lot of real work with only these:
   • # for a main heading
   • ## for a subheading
   • - for a list item
   • *emphasis* for italics
   • [link text](https://example.com) for links
3. Draft in plain text. Open a basic editor on your computer and write there first. No formatting bar. No distractions. When you are done, paste it into your tool and let it handle the rendering.
4. Use one real piece of work as a test. Do not practice on a fake example. Write a real support reply, a real internal post, or a real blog draft in Markdown. Notice when your hands reach for the mouse and ask if there is a Markdown shortcut instead.
5. Decide after one week, not one hour. The first day feels strange because your habits are different. By the third or fourth day, it usually feels normal. At the end of the week, you can decide if the tradeoffs are worth it for you.

The goal is not to become a Markdown expert. The goal is to see how it feels when the tool asks less of you while you write.

Clarity By Subtraction

Most of the time, productivity advice is about adding more.

More tools. More views. More ways to optimize. Markdown takes the opposite path. It removes options until only a few useful patterns remain.

That constraint is where the clarity comes from.

When headings are just #, you stop worrying about typography. When emphasis is simply *this*, you stop tinkering with styles. When lists are only lines that start with -, you stop thinking about spacing.

You are left with questions that matter more.

• What am I trying to say.
• Who is this for.
• Is this the clearest version of the idea I can write today.

Markdown is not magic. It will not fix a bad argument or fill an empty page. What it does is reduce the number of things you have to manage while you are doing the harder part.

That is why I still write in it.

It keeps my hands on the keyboard. It keeps my drafts portable. It aligns the tools I use with the kind of work I care about, which is slow, honest writing about where humans and technology keep bumping into each other. When the tool itself writes, though, honesty becomes a different question—less about which tools to choose, more about what authorship means in a collaboration with language.

In the end, that is enough.