Print a Markdown release checklist and verify its states
Admin ·
A release checklist contains three kinds of evidence: a completed check, a quantity in a table and a literal code value. Loading the sample makes it possible to verify each of them before passing the PDF to the next reviewer.
Verify a checked item against its source
Load example with GitHub-style tables and task lists enabled. The first item, Verify order 0427, has a checked marker. Sign dispatch copy has an empty marker. Change its [ ] to [x]. Confirm that both markers are checked in the preview, then check the same two lines in the PDF.
Find the missing table delimiter
The sample table pairs bay B7 with 18 crates. Turn the GitHub-style option off. The pipes remain ordinary text rather than table boundaries. Turn it back on, then remove the delimiter row between the headings and data. The table disappears even with the option on. Restore the delimiter before exporting.
Check the literal code line and the saved page
The fenced text block contains BIN_07 = ready. Search the saved PDF for BIN_07 to check that the underscore survived. A screenshot would require a different check because its letters are pixels. For long lines inspect wrapping at your chosen paper size.
Review pagination in the print dialog. Choose Download edited source to keep a .md copy that a colleague can update. The PDF captures the current review state.
Common questions
Why do I see a label instead of a linked picture?
The Markdown preview prints the image alternative text. Use a descriptive label or use HTML to PDF with a self-contained PNG or JPEG.
What happens to raw HTML in Markdown?
The Markdown renderer shows raw HTML as literal text. Use Markdown syntax for headings and tables, or open HTML to PDF when you have an HTML document.