[{"data":1,"prerenderedAt":76},["Reactive",2],{"blog-post-markdown-in-obsidian-complete-workflow-guide":3},{"slug":4,"title":5,"description":6,"excerpt":7,"date":8,"category":9,"author":10,"keywords":11,"readingMinutes":12,"html":13,"headings":14,"tools":46,"related":48},"markdown-in-obsidian-complete-workflow-guide","Markdown in Obsidian: The Complete Workflow Guide","A practical guide to using Markdown in Obsidian — covering wiki-links, callouts, YAML frontmatter, essential plugins, and real workflows for knowledge management.","Obsidian has grown from a niche note-taking app to one of the most popular tools among developers, writers, and researchers. It’s built entirely around plain Markdown files stored locally — and…","2026-05-01","Guide","Matthew Rathbone","obsidian markdown, obsidian workflow, obsidian wiki-links, obsidian callouts, obsidian plugins, obsidian zettelkasten, obsidian markdown guide, obsidian tutorial",7,"\u003Cp>Obsidian has grown from a niche note-taking app to one of the most popular tools among developers, writers, and researchers. It’s built entirely around plain Markdown files stored locally — and that combination of local-first storage with a rich linking system has attracted millions of users.\u003C/p>\n\u003Cp>But Obsidian’s Markdown isn’t quite standard Markdown. It layers on proprietary extensions that make it incredibly powerful for knowledge management, but those extensions can break compatibility when you share files elsewhere.\u003C/p>\n\u003Cp>This guide covers everything you need to use Markdown effectively in Obsidian: what’s standard, what’s Obsidian-specific, which plugins are worth using, and what workflows actually work in practice.\u003C/p>\n\u003Ch2 id=\"what-makes-obsidian-different\">What Makes Obsidian Different\u003C/h2>\n\u003Cp>Most Markdown editors convert \u003Ccode>.md\u003C/code> files to HTML for display. Obsidian does that too, but it adds:\u003C/p>\n\u003Cul>\n\u003Cli>\u003Cstrong>Bi-directional links\u003C/strong> between notes via wiki-links\u003C/li>\n\u003Cli>\u003Cstrong>Graph view\u003C/strong> — a visual map of how your notes connect\u003C/li>\n\u003Cli>\u003Cstrong>Local-first storage\u003C/strong> — your files are plain \u003Ccode>.md\u003C/code> files in a folder you control\u003C/li>\n\u003Cli>\u003Cstrong>Plugin ecosystem\u003C/strong> — hundreds of community plugins that extend core functionality\u003C/li>\n\u003Cli>\u003Cstrong>Live Preview mode\u003C/strong> — renders Markdown while you type, like a WYSIWYG editor\u003C/li>\n\u003C/ul>\n\u003Cp>This architecture matters for Markdown because some features you’ll use daily in Obsidian won’t render anywhere else.\u003C/p>\n\u003Ch2 id=\"standard-markdown-in-obsidian\">Standard Markdown in Obsidian\u003C/h2>\n\u003Cp>Obsidian supports most of CommonMark and the GFM (GitHub Flavored Markdown) extensions. The following all work as expected:\u003C/p>\n\u003Cpre>\u003Ccode class=\"hljs language-markdown\">\u003Cspan class=\"hljs-section\"># Heading 1\u003C/span>\n\u003Cspan class=\"hljs-section\">## Heading 2\u003C/span>\n\n\u003Cspan class=\"hljs-strong\">**Bold**\u003C/span>, \u003Cspan class=\"hljs-emphasis\">*italic*\u003C/span>, ~~strikethrough~~, \u003Cspan class=\"hljs-code\">`inline code`\u003C/span>\n\n\u003Cspan class=\"hljs-bullet\">-\u003C/span> Unordered lists\n\u003Cspan class=\"hljs-bullet\">1.\u003C/span> Numbered lists\n\n[\u003Cspan class=\"hljs-string\">Links\u003C/span>](\u003Cspan class=\"hljs-link\">https://example.com\u003C/span>)\n![\u003Cspan class=\"hljs-string\">Images\u003C/span>](\u003Cspan class=\"hljs-link\">image.png\u003C/span>)\n\n| Column A | Column B |\n|----------|----------|\n| Cell     | Cell     |\n\u003C/code>\u003C/pre>\u003Cp>Task lists work and render as interactive checkboxes in Reading mode:\u003C/p>\n\u003Cpre>\u003Ccode class=\"hljs language-markdown\">\u003Cspan class=\"hljs-bullet\">-\u003C/span> [x] Completed task\n\u003Cspan class=\"hljs-bullet\">-\u003C/span> [ ] Pending task\n\u003C/code>\u003C/pre>\u003Cp>Footnotes are fully supported:\u003C/p>\n\u003Cpre>\u003Ccode class=\"hljs language-markdown\">This claim needs a source.[^1]\n\n[\u003Cspan class=\"hljs-symbol\">^1\u003C/span>]: \u003Cspan class=\"hljs-link\">Here is the source.\u003C/span>\n\u003C/code>\u003C/pre>\u003Cp>Math works with \u003Ccode>$\u003C/code> for inline and \u003Ccode>$$\u003C/code> for block (no extension required in recent Obsidian versions):\u003C/p>\n\u003Cpre>\u003Ccode class=\"hljs language-markdown\">Inline: $E = mc^2$\n\nBlock:\n$$\n\\sum\u003Cspan class=\"hljs-emphasis\">_{i=1}^{n} x_\u003C/span>i = \\frac{n(n+1)}{2}\n$$\n\u003C/code>\u003C/pre>\u003Ch2 id=\"obsidian-specific-markdown-features\">Obsidian-Specific Markdown Features\u003C/h2>\n\u003Cp>These features work in Obsidian but will produce plain text or broken output in GitHub, VS Code, Notion, and most other renderers.\u003C/p>\n\u003Ch3 id=\"wiki-links\">Wiki-Links\u003C/h3>\n\u003Cp>The defining feature of Obsidian. Instead of standard Markdown links, you link between notes with double brackets:\u003C/p>\n\u003Cpre>\u003Ccode class=\"hljs language-markdown\">[[Note Title]]\n[[Folder/Note Title]]\n[[Note Title|Custom display text]]\n\u003C/code>\u003C/pre>\u003Cp>Clicking a wiki-link opens that note. If the note doesn’t exist, Obsidian creates it — making it trivial to build a connected web of ideas.\u003C/p>\n\u003Cp>\u003Cstrong>Portability warning\u003C/strong>: Wiki-links render as plain text in GitHub, VS Code, and Notion. If your notes ever need to live outside Obsidian, use standard Markdown links instead.\u003C/p>\n\u003Ch3 id=\"callouts\">Callouts\u003C/h3>\n\u003Cp>Obsidian supports callout blocks using a syntax based on GitHub’s alert syntax:\u003C/p>\n\u003Cpre>\u003Ccode class=\"hljs language-markdown\">\u003Cspan class=\"hljs-quote\">> [!NOTE]\u003C/span>\n\u003Cspan class=\"hljs-quote\">> This is a note.\u003C/span>\n\n\u003Cspan class=\"hljs-quote\">> [!TIP]\u003C/span>\n\u003Cspan class=\"hljs-quote\">> A helpful tip.\u003C/span>\n\n\u003Cspan class=\"hljs-quote\">> [!WARNING]\u003C/span>\n\u003Cspan class=\"hljs-quote\">> Be careful here.\u003C/span>\n\n\u003Cspan class=\"hljs-quote\">> [!DANGER]\u003C/span>\n\u003Cspan class=\"hljs-quote\">> This action is destructive.\u003C/span>\n\u003C/code>\u003C/pre>\u003Cp>You can add a custom title:\u003C/p>\n\u003Cpre>\u003Ccode class=\"hljs language-markdown\">\u003Cspan class=\"hljs-quote\">> [!WARNING] Check your config first\u003C/span>\n\u003Cspan class=\"hljs-quote\">> This replaces the default "Warning" heading.\u003C/span>\n\u003C/code>\u003C/pre>\u003Cp>And make them collapsible with \u003Ccode>+\u003C/code> (open by default) or \u003Ccode>-\u003C/code> (closed by default):\u003C/p>\n\u003Cpre>\u003Ccode class=\"hljs language-markdown\">\u003Cspan class=\"hljs-quote\">> [!NOTE]+ This is open by default\u003C/span>\n\u003Cspan class=\"hljs-quote\">> Content here.\u003C/span>\n\n\u003Cspan class=\"hljs-quote\">> [!NOTE]- This is closed by default\u003C/span>\n\u003Cspan class=\"hljs-quote\">> Content here.\u003C/span>\n\u003C/code>\u003C/pre>\u003Cp>Full list of supported types: \u003Ccode>NOTE\u003C/code>, \u003Ccode>TIP\u003C/code>, \u003Ccode>INFO\u003C/code>, \u003Ccode>SUCCESS\u003C/code>, \u003Ccode>QUESTION\u003C/code>, \u003Ccode>WARNING\u003C/code>, \u003Ccode>FAILURE\u003C/code>, \u003Ccode>DANGER\u003C/code>, \u003Ccode>BUG\u003C/code>, \u003Ccode>EXAMPLE\u003C/code>, \u003Ccode>QUOTE\u003C/code>, \u003Ccode>ABSTRACT\u003C/code>.\u003C/p>\n\u003Cp>GitHub supports only a small subset (\u003Ccode>NOTE\u003C/code>, \u003Ccode>TIP\u003C/code>, \u003Ccode>IMPORTANT\u003C/code>, \u003Ccode>WARNING\u003C/code>, \u003Ccode>CAUTION\u003C/code>). Most other tools render these as plain blockquotes.\u003C/p>\n\u003Ch3 id=\"embedded-notes\">Embedded Notes\u003C/h3>\n\u003Cp>You can embed another note’s content inline:\u003C/p>\n\u003Cpre>\u003Ccode class=\"hljs language-markdown\">![[Note Title]]\n![[Note Title#Section Heading]]\n![[Note Title#^block-id]]\n\u003C/code>\u003C/pre>\u003Cp>This is powerful for building modular knowledge bases — a hub note can pull in content from many individual notes. Entirely Obsidian-specific.\u003C/p>\n\u003Ch3 id=\"tags\">Tags\u003C/h3>\n\u003Cp>Tags work both inline and in YAML frontmatter:\u003C/p>\n\u003Cpre>\u003Ccode class=\"hljs language-markdown\">---\n\u003Cspan class=\"hljs-section\">tags: [productivity, markdown, writing]\n---\u003C/span>\n\nThis note is also tagged #inline and #writing.\n\u003C/code>\u003C/pre>\u003Cp>In recent Obsidian versions, nested tags work: \u003Ccode>#tools/markdown\u003C/code>.\u003C/p>\n\u003Ch3 id=\"block-references\">Block References\u003C/h3>\n\u003Cp>You can create a linkable ID for any paragraph:\u003C/p>\n\u003Cpre>\u003Ccode class=\"hljs language-markdown\">This is the paragraph I want to reference. ^my-block-id\n\u003C/code>\u003C/pre>\u003Cp>Then reference it from another note:\u003C/p>\n\u003Cpre>\u003Ccode class=\"hljs language-markdown\">[[Note Title#^my-block-id]]\n\u003C/code>\u003C/pre>\u003Ch2 id=\"yaml-frontmatter\">YAML Frontmatter\u003C/h2>\n\u003Cp>Obsidian uses YAML frontmatter heavily. Core properties:\u003C/p>\n\u003Cpre>\u003Ccode class=\"hljs language-yaml\">\u003Cspan class=\"hljs-meta\">---\u003C/span>\n\u003Cspan class=\"hljs-attr\">title:\u003C/span> \u003Cspan class=\"hljs-string\">My\u003C/span> \u003Cspan class=\"hljs-string\">Note\u003C/span>\n\u003Cspan class=\"hljs-attr\">date:\u003C/span> \u003Cspan class=\"hljs-number\">2026-05-01\u003C/span>\n\u003Cspan class=\"hljs-attr\">tags:\u003C/span> [\u003Cspan class=\"hljs-string\">markdown\u003C/span>, \u003Cspan class=\"hljs-string\">obsidian\u003C/span>]\n\u003Cspan class=\"hljs-attr\">aliases:\u003C/span> [\u003Cspan class=\"hljs-string\">alternative\u003C/span> \u003Cspan class=\"hljs-string\">name\u003C/span>, \u003Cspan class=\"hljs-string\">other\u003C/span> \u003Cspan class=\"hljs-string\">alias\u003C/span>]\n\u003Cspan class=\"hljs-meta\">---\u003C/span>\n\u003C/code>\u003C/pre>\u003Cp>\u003Ccode>aliases\u003C/code> is Obsidian-specific: it lets you link to a note by any of its aliases. If a note is titled “JavaScript” with \u003Ccode>aliases: [JS]\u003C/code>, you can link to it as \u003Ccode>[[JS]]\u003C/code>.\u003C/p>\n\u003Cp>From Obsidian 1.4+, frontmatter is displayed in a \u003Cstrong>Properties panel\u003C/strong> rather than raw YAML. You can define custom property types (text, number, date, list, checkbox) in Settings → Properties.\u003C/p>\n\u003Cp>For a deeper dive, see our \u003Ca href=\"/blog/markdown-metadata-yaml-frontmatter-complete-guide\">YAML frontmatter in Markdown guide\u003C/a>.\u003C/p>\n\u003Ch2 id=\"essential-plugins\">Essential Plugins\u003C/h2>\n\u003Cp>Obsidian’s plugin ecosystem is where it really shines.\u003C/p>\n\u003Ch3 id=\"core-plugins-worth-enabling\">Core Plugins Worth Enabling\u003C/h3>\n\u003Cul>\n\u003Cli>\u003Cstrong>Templates\u003C/strong> — insert predefined note templates with a hotkey\u003C/li>\n\u003Cli>\u003Cstrong>Daily Notes\u003C/strong> — one note per day for journaling and task tracking\u003C/li>\n\u003Cli>\u003Cstrong>Backlinks\u003C/strong> — sidebar showing all notes that link to the current one\u003C/li>\n\u003Cli>\u003Cstrong>Outline\u003C/strong> — jump between headings without scrolling\u003C/li>\n\u003Cli>\u003Cstrong>Tag Pane\u003C/strong> — browse all tags across your vault\u003C/li>\n\u003C/ul>\n\u003Ch3 id=\"community-plugins-worth-installing\">Community Plugins Worth Installing\u003C/h3>\n\u003Cp>\u003Cstrong>Dataview\u003C/strong> — query your vault like a database with SQL-like syntax:\u003C/p>\n\u003Cpre>\u003Ccode class=\"hljs language-markdown\">\u003Cspan class=\"hljs-code\">```dataview\nTABLE date, tags FROM "Projects" WHERE status = "active" SORT date DESC\n```\u003C/span>\n\u003C/code>\u003C/pre>\u003Cp>This turns your notes into a queryable database. One of the most powerful plugins in the ecosystem.\u003C/p>\n\u003Cp>\u003Cstrong>Templater\u003C/strong> — more powerful templates than the core plugin. Supports dynamic content like current date, prompts, and JavaScript snippets.\u003C/p>\n\u003Cp>\u003Cstrong>Calendar\u003C/strong> — sidebar calendar showing which days have Daily Notes.\u003C/p>\n\u003Cp>\u003Cstrong>Excalidraw\u003C/strong> — embed hand-drawn diagrams directly in notes.\u003C/p>\n\u003Cp>\u003Cstrong>Kanban\u003C/strong> — turn any note into a Trello-style board using Markdown lists.\u003C/p>\n\u003Cp>\u003Cstrong>Advanced Tables\u003C/strong> — tab-based table editing with auto-formatting (similar to our \u003Ca href=\"/tools/markdown-table-formatter\">Markdown Table Formatter\u003C/a> tool, but live in the editor).\u003C/p>\n\u003Cp>\u003Cstrong>Linter\u003C/strong> — auto-formats Markdown on save: consistent heading styles, frontmatter order, whitespace, etc.\u003C/p>\n\u003Ch2 id=\"workflows-that-work-well-in-obsidian\">Workflows That Work Well in Obsidian\u003C/h2>\n\u003Ch3 id=\"daily-notes\">Daily Notes\u003C/h3>\n\u003Cp>Enable the Daily Notes core plugin and set a template. A simple template:\u003C/p>\n\u003Cpre>\u003Ccode class=\"hljs language-markdown\">---\ndate: {{date}}\n\u003Cspan class=\"hljs-section\">tags: [daily]\n---\u003C/span>\n\n\u003Cspan class=\"hljs-section\">## Today's Focus\u003C/span>\n\u003Cspan class=\"hljs-bullet\">-\u003C/span> \n\n\u003Cspan class=\"hljs-section\">## Notes\u003C/span>\n\u003Cspan class=\"hljs-bullet\">-\u003C/span> \n\n\u003Cspan class=\"hljs-section\">## Done\u003C/span>\n\u003Cspan class=\"hljs-bullet\">-\u003C/span> \n\u003C/code>\u003C/pre>\u003Cp>Link daily notes to project notes using wiki-links: \u003Ccode>Working on [[Project Alpha]] today.\u003C/code>\u003C/p>\n\u003Ch3 id=\"zettelkasten-atomic-notes\">Zettelkasten (Atomic Notes)\u003C/h3>\n\u003Cp>The Zettelkasten method works naturally in Obsidian:\u003C/p>\n\u003Col>\n\u003Cli>Each note covers exactly one idea — kept short and self-contained\u003C/li>\n\u003Cli>Notes link to related notes via wiki-links\u003C/li>\n\u003Cli>An index note collects links to related atomic notes\u003C/li>\n\u003Cli>The graph view reveals emergent connections you didn’t plan\u003C/li>\n\u003C/ol>\n\u003Ch3 id=\"para-method\">PARA Method\u003C/h3>\n\u003Cp>\u003Cstrong>P\u003C/strong>rojects, \u003Cstrong>A\u003C/strong>reas, \u003Cstrong>R\u003C/strong>esources, \u003Cstrong>A\u003C/strong>rchives — a folder structure for keeping things organized:\u003C/p>\n\u003Cpre>\u003Ccode>📁 Projects/     # Active projects with a deadline\n📁 Areas/        # Ongoing responsibilities (health, finance, work)\n📁 Resources/    # Reference material organized by topic\n📁 Archive/      # Completed or inactive items\n\u003C/code>\u003C/pre>\u003Cp>Use wiki-links freely within Projects and Areas. Resources serve as reference notes linked from anywhere.\u003C/p>\n\u003Ch3 id=\"mocs-maps-of-content\">MOCs (Maps of Content)\u003C/h3>\n\u003Cp>A Map of Content is an index note linking to many related notes — a navigation layer on top of your atomic notes:\u003C/p>\n\u003Cpre>\u003Ccode class=\"hljs language-markdown\">\u003Cspan class=\"hljs-section\"># Markdown MOC\u003C/span>\n\n\u003Cspan class=\"hljs-section\">## Core Syntax\u003C/span>\n\u003Cspan class=\"hljs-bullet\">-\u003C/span> [[Headings in Markdown]]\n\u003Cspan class=\"hljs-bullet\">-\u003C/span> [[Markdown Lists]]\n\u003Cspan class=\"hljs-bullet\">-\u003C/span> [[Markdown Tables]]\n\n\u003Cspan class=\"hljs-section\">## Advanced\u003C/span>\n\u003Cspan class=\"hljs-bullet\">-\u003C/span> [[Markdown Callouts]]\n\u003Cspan class=\"hljs-bullet\">-\u003C/span> [[Markdown Frontmatter]]\n\u003Cspan class=\"hljs-bullet\">-\u003C/span> [[Markdown Math]]\n\u003C/code>\u003C/pre>\u003Ch2 id=\"portability-what-to-avoid-when-sharing-files\">Portability: What to Avoid When Sharing Files\u003C/h2>\n\u003Cp>If your Obsidian vault stays private, use every feature freely. If you need to share notes on GitHub, in a team wiki, or in Confluence, avoid:\u003C/p>\n\u003Cdiv class=\"table-responsive\">\u003Ctable class=\"table\">\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Feature\u003C/th>\n\u003Cth>Portable alternative\u003C/th>\n\u003C/tr>\n\u003C/thead>\n\u003Ctbody>\u003Ctr>\n\u003Ctd>\u003Ccode>[[wiki-links]]\u003C/code>\u003C/td>\n\u003Ctd>Standard \u003Ccode>[text](path.md)\u003C/code> links\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>![[embedded notes]]\u003C/code>\u003C/td>\n\u003Ctd>Copy content manually\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>[!CUSTOM]\u003C/code> callout types\u003C/td>\n\u003Ctd>Stick to \u003Ccode>NOTE\u003C/code>, \u003Ccode>TIP\u003C/code>, \u003Ccode>WARNING\u003C/code> (GitHub-compatible)\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>#^block-id\u003C/code> references\u003C/td>\n\u003Ctd>Use heading references \u003Ccode>#section-name\u003C/code>\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Dataview queries\u003C/td>\n\u003Ctd>Export to a static table\u003C/td>\n\u003C/tr>\n\u003C/tbody>\u003C/table>\u003C/div>\n\u003Cp>For a full breakdown of what works across platforms, see \u003Ca href=\"/blog/markdown-platform-compatibility-guide\">Markdown across platforms: what works where\u003C/a>.\u003C/p>\n\u003Ch2 id=\"syncing-obsidian-across-devices\">Syncing Obsidian Across Devices\u003C/h2>\n\u003Cp>\u003Cstrong>Obsidian Sync\u003C/strong> (paid, ~$10/month) is the easiest option: end-to-end encrypted, version history included, works on iOS and Android.\u003C/p>\n\u003Cp>\u003Cstrong>Free alternatives:\u003C/strong>\u003C/p>\n\u003Cul>\n\u003Cli>\u003Cstrong>iCloud\u003C/strong> — works well on macOS/iOS; Windows support is inconsistent\u003C/li>\n\u003Cli>\u003Cstrong>Dropbox / Google Drive\u003C/strong> — store your vault folder inside a synced directory\u003C/li>\n\u003Cli>\u003Cstrong>Git\u003C/strong> — version control your vault with a private repo; use the Git community plugin for in-app commits\u003C/li>\n\u003C/ul>\n\u003Cp>If syncing via Git, add these to \u003Ccode>.gitignore\u003C/code> to avoid conflicts:\u003C/p>\n\u003Cpre>\u003Ccode>.obsidian/workspace.json\n.obsidian/workspace-mobile.json\n\u003C/code>\u003C/pre>\u003Cp>Keep \u003Ccode>.obsidian/plugins/*/manifest.json\u003C/code> committed so plugin configs sync across devices.\u003C/p>\n\u003Ch2 id=\"obsidian-vs-other-markdown-editors\">Obsidian vs Other Markdown Editors\u003C/h2>\n\u003Cdiv class=\"table-responsive\">\u003Ctable class=\"table\">\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Feature\u003C/th>\n\u003Cth>Obsidian\u003C/th>\n\u003Cth>VS Code\u003C/th>\n\u003Cth>Typora\u003C/th>\n\u003Cth>iA Writer\u003C/th>\n\u003C/tr>\n\u003C/thead>\n\u003Ctbody>\u003Ctr>\n\u003Ctd>Local file storage\u003C/td>\n\u003Ctd>✅\u003C/td>\n\u003Ctd>✅\u003C/td>\n\u003Ctd>✅\u003C/td>\n\u003Ctd>✅\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Wiki-links\u003C/td>\n\u003Ctd>✅\u003C/td>\n\u003Ctd>❌\u003C/td>\n\u003Ctd>❌\u003C/td>\n\u003Ctd>❌\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Graph view\u003C/td>\n\u003Ctd>✅\u003C/td>\n\u003Ctd>❌\u003C/td>\n\u003Ctd>❌\u003C/td>\n\u003Ctd>❌\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Plugin ecosystem\u003C/td>\n\u003Ctd>✅ extensive\u003C/td>\n\u003Ctd>✅ extensive\u003C/td>\n\u003Ctd>limited\u003C/td>\n\u003Ctd>❌\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>WYSIWYG / Live Preview\u003C/td>\n\u003Ctd>✅\u003C/td>\n\u003Ctd>❌\u003C/td>\n\u003Ctd>✅\u003C/td>\n\u003Ctd>✅\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Free\u003C/td>\n\u003Ctd>✅ core app\u003C/td>\n\u003Ctd>✅\u003C/td>\n\u003Ctd>Paid\u003C/td>\n\u003Ctd>Paid\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Mobile app\u003C/td>\n\u003Ctd>✅\u003C/td>\n\u003Ctd>❌\u003C/td>\n\u003Ctd>❌\u003C/td>\n\u003Ctd>✅\u003C/td>\n\u003C/tr>\n\u003C/tbody>\u003C/table>\u003C/div>\n\u003Ch2 id=\"summary\">Summary\u003C/h2>\n\u003Cp>Obsidian is the most capable local Markdown editor for knowledge management, but it has a vocabulary of proprietary extensions you need to understand. The short version:\u003C/p>\n\u003Cul>\n\u003Cli>Use \u003Cstrong>wiki-links\u003C/strong> and \u003Cstrong>callouts\u003C/strong> freely if notes stay in Obsidian\u003C/li>\n\u003Cli>Use \u003Cstrong>standard Markdown links\u003C/strong> if you need files to work elsewhere\u003C/li>\n\u003Cli>\u003Cstrong>Dataview\u003C/strong> + \u003Cstrong>Templater\u003C/strong> unlock the most workflow power\u003C/li>\n\u003Cli>\u003Cstrong>YAML frontmatter\u003C/strong> is the bridge between your notes and Dataview queries\u003C/li>\n\u003Cli>Sync via Obsidian Sync for simplicity, or Git for version history\u003C/li>\n\u003C/ul>\n\u003Ch3 id=\"related-guides\">Related guides\u003C/h3>\n\u003Cul>\n\u003Cli>\u003Ca href=\"/blog/markdown-admonitions-callouts-complete-guide\">Markdown callouts and admonitions guide\u003C/a>\u003C/li>\n\u003Cli>\u003Ca href=\"/blog/markdown-metadata-yaml-frontmatter-complete-guide\">YAML frontmatter in Markdown\u003C/a>\u003C/li>\n\u003Cli>\u003Ca href=\"/blog/footnotes-in-markdown\">Markdown footnotes guide\u003C/a>\u003C/li>\n\u003Cli>\u003Ca href=\"/blog/how-to-create-table-of-contents-in-markdown\">How to create a table of contents in Markdown\u003C/a>\u003C/li>\n\u003Cli>\u003Ca href=\"/blog/markdown-platform-compatibility-guide\">Markdown across platforms: what works where\u003C/a>\u003C/li>\n\u003C/ul>\n",[15,19,22,25,28,31,34,37,40,43],{"id":16,"text":17,"level":18},"what-makes-obsidian-different","What Makes Obsidian Different",2,{"id":20,"text":21,"level":18},"standard-markdown-in-obsidian","Standard Markdown in Obsidian",{"id":23,"text":24,"level":18},"obsidian-specific-markdown-features","Obsidian-Specific Markdown Features",{"id":26,"text":27,"level":18},"yaml-frontmatter","YAML Frontmatter",{"id":29,"text":30,"level":18},"essential-plugins","Essential Plugins",{"id":32,"text":33,"level":18},"workflows-that-work-well-in-obsidian","Workflows That Work Well in Obsidian",{"id":35,"text":36,"level":18},"portability-what-to-avoid-when-sharing-files","Portability: What to Avoid When Sharing Files",{"id":38,"text":39,"level":18},"syncing-obsidian-across-devices","Syncing Obsidian Across Devices",{"id":41,"text":42,"level":18},"obsidian-vs-other-markdown-editors","Obsidian vs Other Markdown Editors",{"id":44,"text":45,"level":18},"summary","Summary",[47],"markdown-table-formatter",[49,58,66],{"slug":50,"title":51,"description":52,"excerpt":53,"date":54,"category":55,"author":56,"keywords":57,"readingMinutes":12},"markdown-for-github-complete-workflow-guide","Markdown for GitHub: The Complete Workflow Guide","A practical reference for writing Markdown on GitHub across READMEs, Issues, PRs, Wikis, and more — including which GFM features work where.","Writing Markdown on GitHub feels simple — until you discover that task lists are interactive in Issues but static in READMEs, or that > [!NOTE] renders a beautiful callout in a README but produces…","2026-05-08","platform-guides","Matt Rathbone","github markdown, github flavored markdown, github readme markdown, gfm, github wiki markdown, github pull request markdown",{"slug":59,"title":60,"description":61,"excerpt":62,"date":63,"category":64,"author":56,"keywords":65,"readingMinutes":12},"markdown-for-technical-writers-docs-as-code","Markdown for Technical Writers: The Docs-as-Code Workflow Guide","How to set up a docs-as-code workflow with Markdown, Git, and a static site generator — practical guidance for technical writers moving away from wiki-based tools.","\"Docs-as-code\" is the practice of treating documentation the same way software teams treat code: write in plain text (usually Markdown), version-control in Git, review through pull requests, and…","2026-05-15","workflows","docs as code, markdown technical writing, documentation workflow, markdownlint, vale prose linter, mkdocs markdown, docusaurus technical writing, docs as code workflow",{"slug":67,"title":68,"description":69,"excerpt":70,"date":71,"category":72,"author":73,"keywords":74,"readingMinutes":75},"obsidian-plugins-for-developers","Obsidian Plugins for Developers: The Essential Setup (2026)","The best Obsidian plugins for software developers — from code-aware note-taking and project tracking to Git sync and API access. Opinionated recommendations with real configuration examples.","Obsidian's plugin ecosystem has over 1,500 community plugins. Most of them are noise. After spending two years using Obsidian as a developer's second brain — for architecture notes, runbooks,…","2026-06-26","tools","Matthew","obsidian plugins developers, obsidian for software engineers, obsidian development workflow, best obsidian plugins 2026, obsidian dataview, obsidian git, obsidian code blocks",8,1792184946716]