Headings and hierarchy
Use one document title, then move through heading levels in order. Leave automatic numbering to the workspace when you enable it.
# Project brief · ## Decision summaryMarkdown field guide
A practical Markdown formatting guide
Write headings, tables, code, images, formulas, Mermaid diagrams, and metadata that convert cleanly into Word, PDF, and standalone HTML.
Structure first
Markdown structure for Word DOCX, PDF, and HTML
Use ordinary, explicit structure first. Templates then add the visual rules for the selected Word DOCX, PDF, and HTML.
Tables with a clear shape
Use pipe tables for ordinary data. Choose a grid table when cells need multiple paragraphs or supported spans.
| Owner | Status | · | --- | --- |Code that stays readable
Use fenced code blocks and add a language label. Technical templates can also preserve filenames and line-number settings.
```js · const ready = true; · ```Images and diagrams
Keep local image paths relative and package them with the Markdown. Mermaid diagrams are rendered in the browser before the job is submitted.
Math and references
Use supported TeX delimiters for formulas, and stable identifiers when figures, tables, or equations need cross-references.
Inline: $E = mc^2$Metadata before content
YAML front matter can supply title, subtitle, author, date, abstract, and keywords for the document cover and settings.
--- · title: Project brief · ---Before you convert
Check these items before changing the source.
Keep the source reviewable and make the output decision explicit before you click convert.
- 01Confirm the first heading is the document title.
- 02Check local assets, table width, and long formulas.
- 03Choose from Word DOCX, PDF, and HTML according to the handoff.
- 04Open the downloaded file in the target application.
Next step