Markdown vs HTML
Markdown and HTML end up producing the same page, but from opposite ends: Markdown is plain text with minimal marks (# for a heading, * for a list) built to write fast; HTML is the browser's real language, with full control but far more verbose. In practice you write in Markdown and convert to HTML.
| Aspect | Markdown | HTML |
|---|---|---|
| Writing speed | High | Low |
| Output control | Limited | Full |
| Readable unrendered | Yes | No |
| Browser understands it | No (converted) | Yes |
When to use Markdown
Use Markdown to write: READMEs, notes, blogs, documentation. It is readable even unrendered and does not distract you with tags.
When to use HTML
Use HTML when you need fine control: attributes, classes, semantic structure, forms, or embedding something Markdown does not cover. It is what the browser ultimately serves.
In short: Write in Markdown for speed and convert to HTML to publish. When Markdown falls short, you can always mix HTML inside it.