Markdown in board tasks
Board actions use Obsidian’s Markdown renderer so links and inline formatting remain meaningful outside the source note.
Why it matters
Section titled “Why it matters”Task descriptions often carry essential context through links and restrained inline formatting. Rendering those descriptions as plain text exposes Markdown syntax and makes linked decisions harder to reach. Using Obsidian’s renderer keeps board actions consistent with the source note and the rest of the vault.
What to expect
Section titled “What to expect”- Internal links render as Obsidian links instead of raw wiki-link syntax.
- Emphasis and inline code retain their native Markdown presentation.
- Link resolution uses the task’s source note as its Markdown context.
- The rendered action continues to expose its normal task controls.
What it looks like
Section titled “What it looks like”Markdown-formatted architecture task
Section titled “Markdown-formatted architecture task”
