Why people use it
- No lock-in: a Markdown file is just text, so it’s easy to move, version, or back up.
- Focus: you write first, format later—without a complicated toolbar.
- Works everywhere: most editors, apps, and websites support it (or can convert it).
- Plays well with Git: small changes are easy to track.
The basics (examples)
Headings
# Title ## Section ### Subsection
Use
# for larger headings.Bold, italic, and strikethrough
This is **bold** This is *italic* This is ~~strikethrough~~
Asterisks are the most common.
Links
[Pipdown](https://example.com)
Text in brackets, URL in parentheses.
Lists
- Item one - Item two - Sub-item 1. First 2. Second
Indent with two spaces for nested items.
Blockquotes
> This is a quote. > It can span multiple lines.
Useful for callouts and citations.
Inline code and code blocks
Use `inline code` in a sentence.
```js
function hello() {
console.log("Hi!");
}
```
Triple backticks create a code block (optionally with a language).
Images

Same as a link, but with
! in front.Checkboxes (task lists)
- [ ] Write draft - [x] Edit - [ ] Publish
Support depends on the app (many do).
Small tips that make Markdown nicer
- Keep it readable: if it looks good as plain text, it will usually render well too.
- Use headings: they make long notes scannable and easy to navigate.
- Prefer simple formatting: bold, lists, and links cover most real-world writing.
- Export when needed: Markdown can convert to PDF, HTML, Word, and more.
Compatibility note
Markdown has a few “flavors” (slightly different features). The basics above work almost everywhere. If something doesn’t render in another app, it’s usually a feature like tables, checkboxes, or special extensions.