Edit on GitHub

Markdown Basics

If you’ve written Markdown before, you already know this. Here’s a quick reference.

Headings

# Page Title
## Section
### Subsection
#### Sub-subsection

Dorcs builds the table of contents on the right side of the page from your headings. You can see it right now on this page.

Text formatting

**bold text**
*italic text*
~~strikethrough~~
`inline code`

Lists

- First item
- Second item
  - Nested item

1. Step one
2. Step two
3. Step three

- [x] Completed task
- [ ] Incomplete task
[Another page](/usage/other-page)
[External site](https://example.com)

Internal .md links are automatically converted to clean URLs.

Images

![Description](/usage/images/screenshot.png)

Code blocks

Wrap code in triple backticks. Add the language name for syntax highlighting:

```python
def hello():
    print("Hello, world!")
```
def hello():
    print("Hello, world!")

Tip

Every code block gets a copy button in the top-right corner. Hover over the block above to see it.

Tables

| Name    | Role     |
| ------- | -------- |
| Alice   | Engineer |
| Bob     | Designer |
Name Role
Alice Engineer
Bob Designer

Blockquotes

> This is a blockquote. Great for citing sources or adding aside text.

This is a blockquote. Great for citing sources or adding aside text.

Horizontal rules

---

Footnotes

Dorcs supports footnotes for references and asides.[^1]

[^1]: Like this one — it appears at the bottom of the page.

Dorcs supports footnotes for references and asides.1

What’s next

Standard Markdown is just the start. Dorcs adds callouts for highlighted messages and extensions for tabs, badges, diagrams, and more.


  1. Like this one — it appears at the bottom of the page. ↩︎

Last updated: May 7, 2026