Skip to content

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.

BlockInsert withMarkdownTier
Paragraph/text, or just typeplain textT1
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, ```langfenced code, with anything after the language — a title="…", {3-5} — kept as writtenT1
Maths/math, ```matha ```math fence — a code block, drawn beneathT1
Diagram/diagram, ```mermaida ```mermaid fence — a code block, drawn beneathT1
Divider/hr, ------T1
Image/image, or drop or paste a file![description](path)T1
To-do item/todo, [ ] - [ ] (GFM), a task's fields as Dataview's [due:: …] at the end of the lineT2
Task list/tasksa ```tasks fence — a code block holding the query, drawn beneathT1
Table/tableGFM tableT2
Callout/callout> [!NOTE] + sidecarT3
Block reference((, or paste a copied referencerich page: a quote of the referenced text + sidecar; Markdown page: ![[page#^name]]T3
Database view/databasea GFM table + a .base.yamlT3

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 — pinned or hidden.

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 ^name at the end of the block's line, Obsidian's form.
  • A region (region on its first block, regionEnd on 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.

Blocks and the op log are canonical. Markdown is a projection. Git is a target.