Markdown fundamentals
A Short History of Markdown
By KenRich ยท Last updated: July 31, 2026
Markdown began in 2004 as a readable plain-text format for web writing. John Gruber wrote the first converter in Perl, Aaron Swartz helped shape the syntax, and later CommonMark tried to reduce the ambiguity that accumulated across implementations.
Timeline
2004: John Gruber introduces Markdown as a text-to-HTML tool for readable plain-text writing.
December 17, 2004: Markdown 1.0.1 is published as the early public release.
Later: Aaron Swartz's feedback helps shape the syntax, and CommonMark appears to reduce ambiguity across implementations.
2004 and the first release
Markdown was introduced in 2004 by John Gruber as a text-to-HTML tool for web writers. The first public release, Markdown 1.0.1, was published on December 17, 2004.
Its core idea was simple: keep the source readable as plain text, then convert that source into HTML when needed. A heading still looks like a heading, a list still looks like a list, and a link is still understandable before it is rendered.
# Release Notes
## Fixed
- Faster preview rendering
- Clearer history restore state
[Download the preview](https://velowrite.app/download)NoteThe source is readable in any text editor, while the preview becomes a structured page.
Aaron Swartz and early feedback
Aaron Swartz gave Markdown a lot of the feedback and testing that helped the syntax settle into something practical. Gruber credits Aaron directly in the original Markdown page acknowledgements.
That early feedback is part of why Markdown stayed practical. It grew around the way people were already writing plain text.
Why Markdown spread
Markdown spread because it did not ask people to change their whole setup. It worked in simple text editors, email drafts, issue trackers, code comments, Git repositories, documentation generators, and static-site tools.
That portability matters. A Markdown file can live in a folder, move through Git, become a blog post, or sit inside a project repository without needing a proprietary database.
Why variants and CommonMark appeared
Markdown was intentionally small, so many platforms and tools extended it for their own needs. Over time, syntax drift made the same document render differently across implementations.
CommonMark was later created to give Markdown a stronger, testable specification. In practice, that meant trying to reduce ambiguity that had built up around the original syntax and its buggy first implementation.
What stayed useful after all these years
The most durable Markdown idea is simple: the source still makes sense without the editor. That keeps Markdown practical for notes, specs, drafts, and long-lived documentation.
Another durable idea is separation of writing from presentation. You can draft in a clean plain-text structure, then export to HTML, print to PDF, publish to a site, or apply a style later.
What this history means for modern editors
A good Markdown editor should not make the file feel trapped. It should make writing faster while preserving plain text ownership. Preview, history recovery, export, and navigation should support the file instead of replacing it.
VeloWrite follows that direction: quick browser editing for a first draft, a lightweight desktop app for files you keep, and a roadmap that puts everyday editing before AI, export, and publishing.