- 01Inspect the source
- 02Check the renderer
- 03Verify the destination
Each step answers a different question. Verify the final document in its actual destination.
Choose the structure for your readers
CommonMark specifies core Markdown parsing. GFM extends it with tables, task-list items, strikethrough and additional autolink behavior. Math, Mermaid, alerts and footnotes depend on further application support.
A small example to try
# Compatibility check
A paragraph with **emphasis**.
- [ ] Task marker
| Feature | Check |
| --- | --- |
| Table | Destination renderer |Paste this example into the editor and compare the source with its preview. Change one element at a time so you can identify which syntax controls the result.
Check compatibility before sharing
Test a representative sample through edit, preview, save, reopen and export. Include nested lists, code fences, relative images and every extension your team uses. Task-list appearance does not guarantee interactive checkboxes. Keep essential meaning in ordinary prose and preserve source files when changing tools.
A practical review checklist
- Check headings and labels explain the content without extra context.
- Test the example in the destination where people will read it.
- Verify links and relative asset paths after moving the file.
- Inspect exported documents separately from the live preview.
- Keep the editable Markdown original alongside distributed copies.
Primary source and further reading
Read the specification or project documentation. Explore the complete Markdown guide and Compatibility Lab.
Want to inspect a small example? Try it in a Markdown preview, then verify your publishing destination.