Documents, well made

Templates and examples

The Word reference carries the typography, styles, A4 layout, first-page header, subsequent-page title field, and page-number footer. It is an editable style reference, not a body-content template. It uses the Teamwright palette and the supplied static fonts.

Download the reference and sample Markdown into your own working folder. The sample also uses workflow.png; save it next to report.md. No repository or toolkit folder layout is needed.

Generate from Markdown with Pandoc

Install the tools

Install Pandoc 3.x for DOCX and PDF generation. Install the desktop fonts: Inter, Fraunces 72pt, and JetBrains Mono. Google Fonts CSS supplies web typography only; it does not install fonts on your computer.

For PDF, also install XeLaTeX, supplied by a TeX distribution: MiKTeX on Windows, MacTeX on macOS, or TeX Live on Linux. A minimal installation may need additional LaTeX packages requested by Pandoc. On Debian/Ubuntu, the usual packages are texlive-xetex, texlive-latex-extra, texlive-pictures, and texlive-fonts-recommended.

Check installation:

pandoc --version
xelatex --version

XeLaTeX is needed only for PDF. These workflows do not require LibreOffice, Python, Node.js, or a helper script.

Create an editable Word document

Save the downloaded Word template as reference.docx. Run in the folder containing it and report.md:

pandoc "report.md" --standalone --reference-doc="reference.docx" \
  --resource-path=. -o "report.docx"

Create a PDF directly from Markdown

pandoc "report.md" --standalone --pdf-engine=xelatex \
  -V mainfont="Inter" -V monofont="JetBrains Mono" \
  -V fontsize=11pt -V papersize=a4 -V geometry:margin=1in \
  --resource-path=. -o "report.pdf"

This generates PDF directly from Markdown; no DOCX conversion is involved. The Word reference styles only DOCX. The PDF command uses Pandoc’s default LaTeX layout with the specified fonts and page settings; it does not reproduce the Word template’s logo, heading styles, callouts, or footer. Matching the full design requires a separate LaTeX PDF template. The preview below shows the Office reference design.

Replace filenames with your own and quote paths containing spaces. Keep images next to the Markdown or adjust --resource-path. See Pandoc’s PDF documentation for other supported engines.

Give the document structure

---
title: Weekly customer brief
subtitle: Themes, sources, and open questions
author: Teamwright
date: 9 October 2026
abstract: A short summary of this document's purpose.
---

Use # for major sections and ##/### for their supporting structure. Write clear paragraphs, descriptive captions, and meaningful link text. Keep tables narrow enough to read at the chosen page width. Images resolve using the working folder and the resource path you supply.

::: {custom-style="Callout"}
**Decision needed.** State the decision and the relevant context.
:::

| Step | Owner | Result |
|:---|:---|:---|
| Prepare | Research agent | Draft |
| Review | Morgan | Feedback |

: Example responsibilities

![Description of the illustration.](workflow.png){width=6in}

A custom style must exist in the reference file to receive its intended appearance. The supplied reference includes Callout and the compact character style Label.

Customize the reference

Open reference.docx in Word and modify named styles: Title, Subtitle, Heading 1–6, Body Text, Compact, Caption, Source Code, Callout, and Table. Change the styles rather than directly formatting the sample paragraphs.

The reference uses A4 with 1-inch margins. To use Letter, change the reference’s page size and save it. Review tables and images after changing size. Public output is the default; for internal documents, create a separate copy of the reference with an appropriate footer instead of marking every document Confidential.

The subsequent-page header uses a Word TITLE field. Refresh fields in Word when necessary. Check page numbers and wrapping in the Office application used for final delivery.

Fonts and inspection

Install the desktop TTF files before opening editable files or generating PDFs. They include Inter, Fraunces 72pt, and JetBrains Mono; downloads and licenses are on the Assets page.

Read the generated PDF. Check heading placement, page breaks, table wrapping, image captions, footnotes, and the footer. The example PDF contains selectable text and embedded fonts. Accessibility conformance requires additional reading-order and assistive-technology evaluation; font embedding alone does not establish it.

Preview the example

Open PDF · Download DOCX · Read sample Markdown