Guide: preview Markdown with live rendering
READMEs, PR comments, and API docs use Markdown with tables, task lists, and fenced code. Syntax issues (`_` vs `*`, code indentation) surface only after GitHub publish.
Preview renders in-browser — drafts are not stored server-side. Paste changelog or ADR drafts before committing.
Use for tool docs, technical posts, or release notes. Pair with the word counter for platform limits.
Step by step
- Write or paste Markdown — Headings, links, GitHub-flavored tables, and fenced code blocks with language tags.
- Review the preview pane — Check heading hierarchy, relative links, and external images loading.
- Fix problematic syntax — Nested lists need consistent indent; code fences need a blank line before them.
- Copy final HTML or Markdown — Export to CMS, README, or issues — verify in the repo after push.