I Write All My Blog Posts in Markdown Now. Here's Why.
I used to write blog posts directly in WordPress. You know how it goes — the block editor loads slowly, you fight with the toolbar to format a simple heading, and then the auto-save kicks in at the worst moment and your cursor jumps somewhere random. After losing a draft for the third time (okay, I admit the first two were my fault), I decided to try something different.
Now I write everything in markdown. Every blog post, every article, every documentation page. I haven't touched a visual editor in over two years. Here's why I'm not going back.
No Distractions, Just Writing
When you write in markdown, there's no formatting toolbar staring at you. No button to bold, no dropdown for headings, no color picker you'll never use. It's just you and the text. I open MDtoTEXT, switch to dark mode, and all I see is my words on the left and the rendered preview on the right. That's it.
There's actually research that shows visual formatting tools distract writers from the actual writing process. I believe it. When I used WordPress, I'd spend way too much time tweaking font sizes and alignment instead of finishing the damn article.
Portability Is a Huge Deal
Here's the thing nobody tells you about WordPress, Medium, Ghost, or any platform with a proprietary editor: if you ever want to leave, your content is trapped. Good luck exporting 50 blog posts from WordPress without losing formatting. I've done it. It's a nightmare.
Markdown is just text. Plain text files with a .md extension. They'll work in 50 years. You can open them in Notepad, VS Code, your phone, whatever. No special software needed. When I switched my blog from WordPress to a static site generator, the migration was as simple as copying files. Every heading, every link, every code snippet — it all just worked.
Version Control for Writers
If you write markdown files and store them in a Git repository, you get version control for free. I can see every change I made to a blog post, revert to an earlier draft, or see when I added a specific paragraph. This is incredibly useful when you're editing and realize the first draft was actually better in some places.
Writers already do this with Google Docs' version history, but Git gives you way more control. And since my markdown files are on GitHub, I can work on a post from any computer, pull the latest changes, push updates, and never worry about syncing conflicts.
Markdown Makes You a Better Writer
This sounds pretentious, I know, but hear me out. When you can't rely on visual formatting to make your writing look good, you have to actually write well. Instead of using a bigger font to make a point, you use better words. Instead of color-coding sections, you structure your arguments logically.
There's also something about seeing your writing in its raw form. Markdown strips away the illusion of a finished document and shows you the draft for what it is. It forces you to focus on structure — headings, lists, blockquotes — which mirrors good writing structure.
Publishing Is Faster
My publishing workflow now is: write in MDtoTEXT, export to HTML, copy into my CMS, hit publish. It takes maybe two minutes. With WordPress editors, I'd spend ten minutes just making sure the formatting didn't break during pasting.
Some platforms like Ghost and Dev.to actually support markdown natively. You can paste the raw markdown directly and it renders correctly. Hugo and Jekyll (static site generators) use markdown as their source format. More and more platforms are moving to markdown because it's simpler and more reliable than rich text.
What About Non-Technical Writers?
I hear this question a lot. "But markdown is for developers, right?" Not really. The syntax is dead simple. You learn it in five minutes. My wife is not a technical person at all — she works in marketing — and she learned markdown in an afternoon. Now she writes all her internal documentation in it.
The key is having a good editor with live preview. When you can see the formatted result next to your text, it doesn't feel like coding at all. MDtoTEXT shows you both the source and the rendered view side by side, which makes the learning curve basically flat.
Tools I Use for Blogging in Markdown
- MDtoTEXT — my go-to for drafting. Fast, dark mode, auto-saves drafts in localStorage so I never lose work.
- Obsidian — for managing my personal knowledge base and linking ideas between posts.
- VS Code — when I need to do heavy editing across multiple files or batch operations.
- Git + GitHub — for version control and backup.
The Only Downside
Images can be annoying. You have to host them somewhere and link them with the markdown image syntax. I use a simple image hosting service and paste the URLs. It's one extra step compared to drag-and-drop in WordPress, but honestly, the tradeoff is worth it for everything else you gain.
If you're still writing blog posts in a visual editor, I'd say just try markdown for your next article. Use a tool with live preview so it doesn't feel intimidating. My bet is you'll be surprised how much faster and cleaner your writing process becomes.
Try it free at MDtoTEXT — no signup, no commitment, just a text box and a preview pane.