Export GitHub Flavored Markdown without flattening the structure

GitHub Flavored Markdown is useful because it carries more than plain paragraphs. Task lists, fenced code blocks, tables, and short release notes often need to stay intact when the document leaves the repo.

The easiest workflow is to start from the raw markdown instead of printing a rendered web page. That keeps the PDF closer to the source and gives you more control over spacing, headings, and long sections.

What to check first

1. Remove badges or repo-only links that will not help the final reader.
2. Shorten very wide table headers before export.
3. Keep task lists and fenced code blocks close to the notes that explain them.

Where this works best

This workflow is useful for release checklists, onboarding docs, internal setup notes, and client-facing project summaries that start life in GitHub but need to circulate as a portable PDF.