# LocalFlux Markdown-to-PDF Field Guide

![LocalFlux loop logo](file:///C:/tmp/LocalFluxMarkdownToPdfBlog/localflux-logo.png)

This self-authored document tests a practical **Markdown-to-PDF** workflow on
Windows. It contains only publication-safe LocalFlux material and a local logo.

> A useful PDF test checks the pages, not just the filename.

## What this fixture covers

- headings and paragraphs;
- **bold**, *italic*, and `inline code`;
- ordered and unordered lists;
- a block quote and horizontal rule;
- a local image referenced with a `file:///` URI;
- a table and a fenced code block;
- a fragment link that does not require the network; and
- enough prose to exercise natural page breaks.

## Conversion checklist

1. Keep the Markdown source and logo in a neutral working folder.
2. Add the `.md` file to LocalFlux.
3. Confirm that the route reads **MD -> PDF**.
4. Convert the file and keep the source unchanged.
5. Open every PDF page and inspect the result.

See [Verification notes](#verification-notes) later in this document.

---

## Formatting sample

Markdown is useful because the source stays readable without a special editor.
The exported PDF is a delivery copy: it is convenient for review, printing, or
sharing with someone who should see a fixed document rather than Markdown syntax.

| Element | Expected PDF result |
| --- | --- |
| Heading | Clear visual hierarchy |
| Local logo | Visible without a web request |
| Code fence | Monospaced, readable block |
| Table | Bordered rows and columns |
| Long prose | Natural pagination without overlap |

```powershell
# This is displayed text, not a command run by the conversion.
$source = "localflux-markdown-guide.md"
$output = "localflux-markdown-guide_converted.pdf"
```

### Notes for authors

Use a representative source before converting a large folder. A short note may
fit on one page while a report with wide tables or long code lines can reveal
wrapping and pagination problems. Fonts available to the bundled rendering path
also influence line breaks, glyph coverage, and the amount of text on each page.

Markdown itself does not define physical paper size, print margins, headers,
footers, or forced page breaks. Those are publishing-layout concerns. A direct
conversion is most dependable when the document can accept the converter's
normal page flow rather than requiring exact placement.

## Verification notes

After conversion, inspect each page at a readable zoom. Confirm that the title,
logo, lists, quote, table, and code block are present. Look for clipped columns,
unexpected blank pages, broken glyphs, awkward page breaks, and lines of code
that extend beyond the printable area.

The words café, résumé, naïve, and 日本語 exercise common Unicode text. Their
appearance should be checked visually because successful text extraction alone
does not prove that every glyph rendered correctly.

### Source preservation

LocalFlux writes a new PDF beside the Markdown source. The `.md` file remains the
editable original, and the PDF becomes a separate output. Retaining both makes it
easy to revise the source and produce a new delivery copy later.

### Local-reference boundary

This fixture uses a local logo. It intentionally contains no `http://` or
`https://` links or images. LocalFlux rejects remote web references in Markdown
instead of fetching them during conversion. Raw HTML is also outside this route's
supported input contract.

## Closing summary

A reliable Markdown-to-PDF workflow is simple: keep dependencies local, convert
to a new file, then inspect every page. The conversion is complete only when the
PDF is readable and the original Markdown remains available for the next edit.