Obsidian Flavored Markdown

Standard Markdown plus Obsidian’s vault extensions — the format this garden’s notes are written in (as opposed to the GitHub Flavored Markdown used in repo _specs/-style docs). OFM builds on the CommonMark/GFM base and adds the vault-native layer:

The extensions

• Wikilinks [[Note Name]] — link by note name, no path or extension needed; Obsidian tracks renames. Variants: [[Note|display text]], [[Note#heading]], [[Note#^block-id]] (block references via ^id suffixes). The feature that makes the vault a graph rather than a folder tree.
• Embeds ![[Note]] — inline any note, section (![[Note#heading]]), or file (![[image.png|300]] width, ![[doc.pdf#page=3]]). Transclusion rather than linking.
• Tags #tag, #nested/tag — inline searchable labels (letters/numbers/underscores/hyphens/slashes; digit-first forbidden). Frontmatter tags: is the structured equivalent.
• Callouts > [!type] — blockquote-based admonitions: > [!note], > [!warning] Custom title, > [!faq]- (foldable, - collapsed by default). Same syntax family GitHub adopted for its alerts.
• Properties — YAML frontmatter (title, tags, aliases, cssclasses + arbitrary keys); the garden’s status/type/publish convention lives here.
• Minor: %%comments%% (hidden in reading view), ==highlights==, $math$/$$, Mermaid fenced blocks with class Node internal-link; node linking.

Dialect boundaries

Everything above the base is vault-only: wikilinks render literally outside Obsidian (this site’s Quartz engine translates them at publish time — the garden’s portability bridge). Writing for the vault means OFM freely; writing for repos/portable docs means dropping to the GFM subset. See Markdown Flavors for the full ladder and portability rules.

Related: Markdown Flavors · Obsidian · CommonMark · GitHub Flavored Markdown