obsidian-markdown

To generate Obsidian Markdown, draft your notes using [[wikilinks]] for internal references, > [!type] for callouts, and ![[embeds]] to inline-render vault content. This ensures proper knowledge-vault workflows and tag-driven organization.

Add YAML frontmatter properties to structure Obsidian notes by defining blocks with title, tags, aliases, and cssclasses. This enables tag-driven organization and styling for search and knowledge management within your vault.

Yes, you can inline-render notes, sections, images, and PDFs in Obsidian Markdown using the ![[...]] embed syntax. This allows rich note insertion and direct content referencing within your knowledge vault.

The best way to create internal links in Obsidian is using the [[Note]] syntax, which supports headings and ^block-id targets. This establishes precise internal references for drafting and editing connected notes.

Regular Markdown does not support Obsidian-specific syntax like [[wikilinks]], ![[embeds]], or > [!type] callouts. You need Obsidian Flavored Markdown to properly execute these knowledge-vault workflows and internal references.

You need Obsidian Flavored Markdown when drafting and editing notes that require wikilinks, page embedding, callouts, and YAML frontmatter properties. Standard Markdown cannot handle these specific tag-driven organization and internal reference features.