Markdown, created in 2004 by John Gruber (with input from Aaron Swartz) had a modest goal. At the time writing for the web meant wrapping your words in HTML tags — <p> here, <strong> there — which was tedious and made the raw text hard to both read and write. Gruber's idea was to let people "write using an easy-to-read, easy-to-write plain text format" that could then be converted into valid HTML. Crucially, the plain text was supposed to stay readable as-is, never looking like it had been "marked up with tags or formatting instructions".
It worked. Two decades on Markdown has become a de-facto standard, a convention for writing on the web; asterisks for emphasis, # for headings, hyphens for lists. It has spread from blogs to README files, chat apps, static site generators, documentation systems, and a hundred note-taking tools. From a single beginning it grew uncontrolled, spawning different dialects along the way. A 2014 effort called CommonMark set out to tackle these deviations and create a 'standard' approach. More recently it's started to become a standard in communicating with AI agents. Markdown documents are now (as of 2026) seen as the lingua franca for text-based communication with AI.
But notice what this origin story tells you. Markdown was designed for one job — presentation. It describes how text should look once it becomes HTML. However, at MellowMill we believe this is not good enough for two reasons:
- Markdown totally misses the meaning of the text and the intent of the author.
- Markdown is a general syntax aimed at the lowest common denominator.
The Margin format, the plain-text language behind MellowMill Studio, was designed for a different job: capturing what text means. That sounds like a small distinction. In daily work, though, it changes everything.
The same note, two languages
Here is a small working example — a couple of tasks, a decision, and an open question. On the left is how you might write it in Markdown. On the right, the same thing in Margin.
## To Do - [ ] Draft the launch email - [x] Book the venue ## Decision **Q: Which date?** *A: April 30th — avoids the conference.* > **Important:** Send invites by Friday
> To Do - Draft the launch email | Book the venue ? Which date? A. April 30th — avoids the conference. ! Send invites by Friday
In Markdown, everything is just formatting: a list, some italics, a blockquote. It looks structured, but the software underneath has no idea what any of it means.
Margin treats the same lines as real objects — tasks, questions, answers, decisions — so the structure you intended becomes structure the software can use.
Markdown describes shapes; Margin describes things
In Markdown, - [ ] and - [x] are checkboxes — a visual convention bolted onto the list syntax. The asterisks around the answer mean "make this italic." The blockquote with bold text inside is just that: a quote that happens to start with the word Important. The document looks structured, but to the software underneath it is all paragraphs, emphasis, and lists. Nothing knows that "Send invites by Friday" is a commitment with a deadline.
Margin reads the same note as a set of real objects. A line beginning with - is a task; | marks it complete; / would mark it in progress. ? opens a question and A. binds the answer to it, so the two travel together. ! is a genuine decision or commitment — and because the line says "Friday," MellowMill Studio can recognise the date without you tagging it. The prefixes are not decoration. They are the meaning, written down. This becomes especially powerful when you then apply it to a specific domain - work, productivity and getting things done.
Why that matters when notes pile up
A single note looks similar either way. The difference shows when you have a knowledge-base full of them. Because Margin knows that a task is a task, MellowMill Studio can pull every unfinished item across your whole notebook into one view — without you maintaining a separate to-do app. It can surface open questions you never answered. It can list the decisions you made last month and the reasons you recorded beside them. It can gather every task you need to do, automatically grouped by topic. Markdown can't do any of this because it never knew what those lines meant — only how they should look.
The fair comparison
None of this makes Markdown bad. For general writing Markdown is good enough and the two formats optimise for different moments:
- Markdown is for general text where you only need to capture what formatting to apply.
- Margin is for the thinking you do along the way — tasks, decisions, questions, meeting notes — where structure and recall are the point - it's less about the appearance and more about the meaning.
There is also a quieter advantage. Margin is still just plain text in a file on your machine. There is no database and no cloud account standing between you and your information. If MellowMill Studio vanished tomorrow, your notes would open in any text editor — exactly like Markdown. You get the durability of plain text and a format that understands what you wrote.
Try it yourself
The quickest way to feel the difference is to take a note you already keep in Markdown and add it in MellowMill Studio. Download for free to experience the power of the Margin format, and then upgrade for extra funtionality.
Read the Margin format guide for every block type, or download MellowMill Studio and let the visual editor write the syntax for you.