The complete practical guide to Markdown

Markdown is the quiet default for writing on the web — README files, notes, chat messages, documentation, and a growing number of publishing tools all accept it. It is small enough to learn in an evening and powerful enough to format a whole book. This guide covers the features you will actually use, with real examples, and calls out the edge cases that quietly break your documents.

The core: headings, emphasis, and lists

These four things make up the majority of any Markdown document.

• Headings. One to six hash marks, from <h1> to <h6>. Use at most two levels in a document — a heading hierarchy with five levels is usually a sign the document needs restructuring, not more hashes.
  • # Level 1
  • ## Level 2
  • ### Level 3
• Emphasis. *italic* or _italic_ for one word; **bold** or __bold__ for stress. Nest them (**a *b* c**) but keep it to one level of nesting.
• Lists. - or * for unordered, 1. for ordered. Indent a list item by two spaces to nest it.
• Links. [label](https://example.com) for a link, ![alt](image.png) for an image. The label is what readers see; the alt text is what screen readers announce.

The features people underuse

A few blocks do more than most writers realize they can.

• Blockquotes. Start a line with > . Chain several > lines for a multi-paragraph quote. Good for citing sources or calling out a definition.

• Code. Inline code with backticks (`code`), fenced blocks with triple backticks and a language tag for syntax highlighting. Always add the language — it is what makes highlighting work.

• Tables.

  Column A	Column B
  cell 1	cell 2

  Tables are the one Markdown feature that is verbose and fiddly; a long table is often better as a list.

• Horizontal rules. Three dashes (---) on their own line. Use them sparingly — a heading is almost always a better section break.

The edge cases that break

These are the places documents silently go wrong.

1. Intra-word underscores. snake_case renders the middle as italic in most parsers. If you write a lot of code identifiers, prefer hyphens or backticks.
2. Unescaped characters. A literal *, _, or backtick in prose needs escaping with a backslash, or it will be treated as markup.
3. Blank lines around blocks. Headings, lists, and fenced code blocks generally need a blank line before and after them, or they merge into the surrounding paragraph.
4. One idea per list item. A list item that contains a full paragraph should be split; a list is for parallel short items, not for paragraphs wearing a dash.

How to keep documents clean

• Use headings to outline first, then fill in the body.
• One paragraph per idea; break it when the topic shifts.
• Prefer a link with a descriptive label over a raw URL.
• Read the rendered output, not the source — Markdown is a format you read as HTML, and the two do not always line up.

Why it matters for a local converter

A clean Markdown document is the most portable form a text file can take. It opens in any editor, renders in any browser, and converts to PDF, HTML, or Word without loss. That is why converting to Markdown is often the right move when you need a document to travel — and it is exactly what the DailyWise converter is built to produce, entirely on your device, with nothing uploaded.