Markdown Preflight

Research / Constructs / Obsidian syntax

Obsidian syntax in five publishing editors

One Markdown fixture, five real publishing editors, tested 2026-08-24. For obsidian syntax the observed result was untested in LinkedIn; a manual step in WordPress, Substack, Beehiiv, and X. Every row below is a rule with its own page and its own dated record.

Matches obsidian_wikilink, obsidian_embed, obsidian_callout, obsidian_blockref. Fixture markdown-portability-test-v1. Tested 2026-08-24. How these tests are run.

What happens, per destination

Every rule that touches obsidian syntax, worst outcome first. Generated from the rule set the product runs, so this table and the tool cannot disagree.
DestinationWhat happensResultSeverityRuleConfidenceLast tested
LinkedInMath, Mermaid, Obsidian syntax, raw HTML, and heading anchors are not live-verified on LinkedIn.UnknownEvidence gapLI-SPECIAL-01Unknown2026-08-24
WordPressObsidian syntax is flattened to ordinary text.Manual stepActionWP-OBS-01Verified2026-08-24
SubstackObsidian syntax is flattened to ordinary rich content.Manual stepActionSUB-OBS-01Verified2026-08-24
BeehiivObsidian syntax is flattened to ordinary text.Manual stepActionBEE-OBS-01Verified2026-08-24
XMath, Mermaid, Obsidian syntax, and raw HTML are resolved to readable text or a media task.Manual stepActionX-SPECIAL-01Verified2026-08-24

Manual steps this creates

Limits of what was tested

Prepare a draft

Related