Markdown Syntax Reference

MDflow supports GitHub Flavored Markdown (GFM). If it renders on GitHub, it almost certainly renders here.

The editor's built-in help panel covers the same ground interactively.

Headings

# Heading 1
## Heading 2
### Heading 3

Emphasis

*italic* or _italic_
**bold** or __bold__
***bold italic***
~~strikethrough~~
`inline code`

Links

[Link text](https://mdflow.cz)
<https://mdflow.cz>

To link to another document in your workspace, type @ and pick from the list — see 03 Linking Documents Together.

Lists

- Bulleted item
- Another item
  - Nested item

1. Numbered item
2. Another item

Task lists

- [ ] Not done yet
- [x] Finished

Task lists are more than formatting in MDflow. Every checkbox across your documents is aggregated into the Tasks view, where you can filter, tick and edit them — and you can attach a due date and an owner. See 06 Tasks.

Blockquotes

> A quoted passage.
>
> > And a nested one.

Code blocks

Fence with triple backticks, optionally naming the language:

```python
def hello():
    print("Hello")
```

Tables

| Column A | Column B |
| --- | --- |
| Value | Value |
| Value | Value |

Alignment is controlled with colons:

| Left | Center | Right |
| :--- | :----: | ----: |
| a | b | c |

Dividers

---

Images

![Alt text](https://example.com/image.png)

You rarely need to type this by hand — drag an image into the editor or paste it from the clipboard and MDflow inserts the syntax for you. Externally hosted images referenced by URL also render. See 04 Images.

A note on portability

Everything above is standard GFM. That is deliberate: your documents are plain text with no MDflow-specific syntax, so a document written here renders correctly in Obsidian, VS Code, on GitHub, or anywhere else markdown is understood.

The one MDflow-flavoured convention is the optional due date and owner on a task line — - [ ] (20260706)(jan@example.com) Send the invoice. Even that degrades gracefully: in any other markdown tool it is simply a task with some text in front of it.