Syntax Basics
Markdown formats text using plain characters instead of HTML tags, so a document stays readable even before it's rendered. Headings start with one to six # characters; emphasis wraps text in asterisks or underscores; links and images use square brackets followed by parentheses.
| You type | You get |
|---|---|
## Heading | A level-2 heading |
**bold** | bold text |
*italic* | italic text |
`code` | Inline code |
[2all.in](https://2all.in) | A clickable link |
> a quote | A blockquote |
--- | A horizontal rule |
Lists, Code Blocks & Tables
Start a line with -, *, or + followed by a space for a bullet list, or 1. for a numbered list. Wrap multi-line code in a fenced block using three backticks on their own line before and after the code; a single backtick pair wraps a short inline code snippet instead.
Simple tables use pipes to separate columns, with a second row of dashes to mark the header separator:
|----------|----------|
| Row 1A | Row 1B |
-, *, or + plus a space become a bulleted list.1., 2., and so on become a numbered list.| - render as a table.How Live Rendering Works
As you type, the editor waits for a brief pause (about 100 milliseconds) before re-parsing your Markdown, so the preview stays smooth even on long documents instead of re-rendering on every single keystroke. The parser reads your text line by line: it first looks for block-level structure - headings, fenced code, blockquotes, lists, tables, horizontal rules - and treats everything else as ordinary paragraph text.
Once a piece of text is identified as a heading, list item, table cell, or paragraph, a second pass handles inline formatting within it - turning **bold**, *italic*, `code`, and [links](url) into their HTML equivalents. The two passes are kept separate deliberately: block structure depends on where a line starts (like a leading # or >), while inline formatting can appear anywhere within a line's text.
Why HTML Escaping Matters
The preview pane is rendered by inserting generated HTML into the page, which means special characters like <, >, and & in your source text need careful handling. If you paste a raw <script> tag or other HTML directly into the editor, this tool escapes those characters into their safe text equivalents before any Markdown formatting is applied - so the tag shows up as plain, visible text in the preview instead of being interpreted as real markup or executed as code.
This matters whenever you're previewing Markdown from an untrusted source - a comment, a pull request description, a file you didn't write yourself - since a previewer that doesn't escape raw HTML could let a maliciously crafted document run script in your browser the moment you paste it in.
Frequently Asked Questions
Block structure like headings, lists, and blockquotes depends on how a line starts, so it has to be identified first, line by line. Inline formatting such as bold, italic, and links can appear anywhere within a line's text, so it's applied in a second pass over each block's content. Keeping the two passes separate avoids a heading marker or list bullet being misread as part of a bold or link pattern.
No. The parser only cares about pipe-delimited cells and a dash separator row under the header - it doesn't look at column width or spacing. Lining up the pipes with extra spaces makes the raw Markdown easier for a human to read, but it has no effect on the rendered table.
Escaping converts characters like < and > into their text equivalents instead of deleting them, so you can still see exactly what you pasted - as inert, visible text - rather than having content silently disappear. Stripping tags can also leave the content between them behind in a confusing, half-formatted state; escaping keeps the whole snippet intact and readable.
Inline code uses a single pair of backticks around a short snippet and stays part of the surrounding paragraph's text flow. A fenced code block uses three backticks on their own line before and after the code, produces a separate preformatted block, and preserves whitespace and line breaks exactly - better suited to multi-line snippets.
Standard Markdown treats a single line break as a soft break within the same paragraph. Leave a fully blank line between lines to start a new paragraph, or end a line with two trailing spaces to force a line break within the same paragraph.