Markdown Preflight

Research / Constructs / Code

Inline code and fenced code blocks in five publishing editors

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

Matches inline_code, code, code_long_line. Fixture markdown-portability-test-v1. Tested 2026-08-24. How these tests are run.

What happens, per destination

Every rule that touches code, worst outcome first. Generated from the rule set the product runs, so this table and the tool cannot disagree.
DestinationWhat happensResultSeverityRuleConfidenceLast tested
XCode loses its formatting and gets a Code: label.DegradedReviewX-CODE-01Verified2026-08-24
LinkedInCode loses its formatting and gets a Code: label.DegradedReviewLI-CODE-01Verified2026-08-24
WordPressCode is preserved, but a long unbroken line may overflow.KeptReviewWP-CODE-01Verified2026-08-24
WordPressInline formatting is preserved.KeptInfoWP-EMPH-01Verified2026-08-24
SubstackCode survives, but a long unbroken line needs a mobile check.KeptReviewSUB-CODE-01Verified2026-08-24
SubstackInline formatting survives rich paste.KeptInfoSUB-EMPH-01Verified2026-08-24
BeehiivCode is kept, but a long unbroken line may overflow in email.KeptReviewBEE-CODE-01Verified2026-08-24
BeehiivInline formatting is kept as Markdown.KeptInfoBEE-EMPH-01Verified2026-08-24

Manual steps this creates

Limits of what was tested

Prepare a draft

Related