Appearance
Block types
Every block type declares what it becomes in Markdown and at which fidelity tier. That declaration is part of defining the type — adding one without deciding its Markdown story is a compile error rather than an oversight to catch in review.
| Block | Insert with | Markdown | Tier |
|---|---|---|---|
| Paragraph | /text, or just type | plain text | T1 |
| Heading 1–6 | /h1, # … ###### , Mod+Alt+1..3 | # … ###### | T1 |
| Bulleted list item | /ul, - | - | T1 |
| Numbered list item | /ol, 1. | 1. | T1 |
| Quote | /quote, > | > | T1 |
| Code block | /code, ```lang | fenced code, with anything after the language — a title="…", {3-5} — kept as written | T1 |
| Maths | /math, ```math | a ```math fence — a code block, drawn beneath | T1 |
| Diagram | /diagram, ```mermaid | a ```mermaid fence — a code block, drawn beneath | T1 |
| Divider | /hr, --- | --- | T1 |
| Image | /image, or drop or paste a file |  | T1 |
| To-do item | /todo, [ ] | - [ ] (GFM), a task's fields as Dataview's [due:: …] at the end of the line | T2 |
| Task list | /tasks | a ```tasks fence — a code block holding the query, drawn beneath | T1 |
| Table | /table | GFM table | T2 |
| Callout | /callout | > [!NOTE] + sidecar | T3 |
| Block reference | ((, or paste a copied reference | rich page: a quote of the referenced text + sidecar; Markdown page: ![[page#^name]] | T3 |
| Database view | /database | a GFM table + a .base.yaml | T3 |
Lists nest; indentation is Tab, and structure is preserved through export and back.
Inline marks
strong, em, strike, code, and links. That is the whole set, and it is deliberately poor: structure may be rich, inline content may not, because inline content is where Markdown round-tripping actually breaks.
code excludes strong, em and strike — CommonMark cannot express a bolded code span adjacent to a word, and silently corrupting a document on export is not a trade worth making. A link around code is allowed: [`store.ts`](…) is ordinary CommonMark.
A link's address may be web, mail, phone or a Notesflow link.
A short reference such as PROJ-123 is not a mark at all: it is drawn as a link from the workspace's settings, and the text stays exactly as typed. A mention of a person is a link too, written as the words that were typed.
Properties any block can carry
Regardless of type:
date— the day this item is placed on in the timeline.timeline—pinnedorhidden.
A block carrying either is T3 for that export, whatever its row above says: its text is untouched, and one HTML-comment sidecar follows it.
- A name (
anchor) — written as^nameat the end of the block's line, Obsidian's form. - A region (
regionon its first block,regionEndon its last) — written as<!-- region: name -->…<!-- /region -->around the blocks it covers.
Names and regions are what block references point at. They are unique on their page, and a table's rows and cells cannot carry them. A copied or duplicated block does not take its original's name.
Things GFM cannot do, and therefore neither can this
- A table cell holds inline text and nothing else, because a GFM cell does.
- No colspan, no rowspan, no cell selection.
Those are not on a roadmap. They are the shape of a promise that a table exported from here opens correctly everywhere else.