Everyday Markdown syntax in one practical reference, with rendered examples and the common extensions clearly labeled. No scavenger hunt required.
# Clear notes
**Important**
- [ ] Next step
This first table is the short version. Everything marked Extension is widely supported but not part of core CommonMark.
| What you want | Write this | Result or note |
|---|---|---|
| Heading | # Heading 1 | Use one to six # characters. |
| Bold | **important** | important |
| Italic | *emphasis* | emphasis |
| Bold and italic | ***both*** | both |
| Link | [Ariv](https://ariv.one) | Ariv |
| Image |  | Alt text describes the image. |
| Blockquote | > Quoted text | Prefix each quoted paragraph with >. |
| Bullet list | - First item | * and + also work. |
| Numbered list | 1. First item | Numbers may be normalized by the renderer. |
| Task list Extension | - [ ] Open | Part of GitHub Flavored Markdown. |
| Inline code | `npm test` | npm test |
| Code block | ```js | Add a language after the opening fence when supported. |
| Horizontal rule | --- | Put it on a line by itself. |
| Hard line break | First line\ | A trailing backslash or two spaces creates a hard break. |
| Strikethrough Extension | ~~removed~~ | |
| Table Extension | | Name | State | | Part of GitHub Flavored Markdown. |
| Center text HTML | <p align="center">Centered text</p> | No portable Markdown syntax. Requires an HTML-aware renderer. |
| Literal formatting character | \*not italic\* | Use a backslash to escape punctuation. |
| Comment HTML | <!-- hidden note --> | Renderer and sanitization support varies. |
The examples below use the smallest syntax that communicates the structure. Select the code manually or use the copy button.
# Project brief
## Why this matters
Write the **important point** clearly.
Add *emphasis* only where it helps.
Use ***both*** sparingly.Write the important point clearly.
Add emphasis only where it helps.
Use both sparingly.
[Visit Ariv](https://ariv.one)
Use meaningful link text. Image alt text should explain the image's purpose, not repeat “image of.”
> Clarity comes from removing
> what the reader does not need.
---Clarity comes from removing
what the reader does not need.
- Capture the idea
- Add enough context
- Link the source
- Name the next step
1. Draft
2. Review
3. Publish- [x] Gather the evidence
- [ ] Write the first draft
- [ ] Review on mobileTask lists are a GFM extension. Many apps support them, but plain CommonMark renderers are not required to.
| Item | Owner | Status |
| :--- | :---: | ---: |
| Guide | Maya | Ready |
| Demo | Lee | Draft || Item | Owner | Status |
|---|---|---|
| Guide | Maya | Ready |
| Demo | Lee | Draft |
Colons in the delimiter row request left, center or right alignment. Some renderers ignore alignment while still rendering the table.
Run `npm test` before shipping.
```js
const ready = true;
console.log(ready);
```Run npm test before shipping.
const ready = true;
console.log(ready);The language name after the opening fence is an info string. Syntax highlighting depends on the renderer.
This is one paragraph.
This is a new paragraph.
This line ends with a backslash.\
This stays in the same paragraph.This is one paragraph.
This is a new paragraph.
This line ends with a backslash.
This stays in the same paragraph.
A blank line is usually the clearest choice. Use a hard break only when the line break itself carries meaning.
\*literal asterisks\*
\# not a heading
\[not a link\]
Use `` `code with a backtick` ``.*literal asterisks*
# not a heading
[not a link]
`code with a backtick`
<p align="center">
Centered text
</p>
<p align="center">
<img src="logo.png" alt="Project logo">
</p>Centered text
Markdown itself has no centering syntax. This raw HTML works only when the reader accepts and preserves it. Some apps sanitize or ignore the HTML or the align attribute.
Visible paragraph.
<!-- This note is hidden in many renderers. -->
Another visible paragraph.Visible paragraph.
Another visible paragraph.
Markdown has no dedicated comment syntax. HTML comments are common, but HTML filtering and export behavior vary.
This example combines portable structure with clearly marked GFM task syntax. It remains readable even in an editor that does not render every extension.
# Launch checklist
**Goal:** Publish a useful guide without losing accuracy.
## Before publishing
- [x] Check the primary sources
- [x] Test every example
- [ ] Review the mobile layout
- [ ] Confirm the canonical URL
## Notes
> The page should be useful before it asks for anything.
Read the [CommonMark specification](https://spec.commonmark.org/)
and the [GFM specification](https://github.github.com/gfm/).
```sh
npm test
```
---
Updated: 2026-08-11Goal: Publish a useful guide without losing accuracy.
The page should be useful before it asks for anything.
Read the CommonMark specification and the GFM specification.
npm testCore CommonMark syntax is the safest foundation when a file needs to move between apps. Extensions can still be useful. The important part is knowing when you are using one.
[[Note]]Some apps generate a table of contents from headings. A manual version uses ordinary links, but the heading anchor must match the renderer that will display the file. GitHub, static-site tools and note apps can generate those anchors differently.
## Contents
- [Getting started](#getting-started)
- [Next steps](#next-steps)<!-- hidden note -->. Sanitizing renderers may remove or display raw HTML differently, so treat comments as renderer-dependent.<p align="center">Centered text</p> may work. Treat it as renderer-dependent because an app may sanitize, ignore or display the HTML differently.Open a folder of Markdown files in Ariv and add capture, search, tasks, Kanban, backlinks and optional AI without converting the notes into a proprietary format.