Documentation that engineers actually trust looks like it was written by engineers. The Technical Manual sets monospace headings over a clean sans body with a teal accent on A4 — code blocks with real syntax presence, tables built for parameters, and a hierarchy deep enough for reference material.
Your manual is already Markdown — in the docs folder, next to the code it describes. Send it as-is: fenced code blocks keep their formatting, nested headings become a navigable structure, and page breaks respect code fences instead of slicing through them. Re-render on every release so the PDF never lags the docs.
# Northwind SDK — Operations Manual
## Installation
```bash
npm install @northwind/sdk
export NORTHWIND_API_KEY=nw_live_...
```
## Configuration
| Option | Type | Default | Description |
| ----------- | ------ | ------- | ------------------------- |
| `region` | string | `us-1` | API region |
| `timeout` | number | `30000` | Request timeout (ms) |
| `retries` | number | `3` | Automatic retry attempts |
## Basic usage
```ts
import { Northwind } from "@northwind/sdk";
const client = new Northwind({ region: "eu-1" });
const job = await client.jobs.create({ type: "sync" });
```
## Error handling
All SDK errors extend `NorthwindError` and carry a stable
`code`. Retry on `RATE_LIMITED` and `UNAVAILABLE`; treat
everything else as terminal.
> Never retry `INVALID_REQUEST` — fix the payload instead.
Paste your Markdown in the editor, pick Technical Manual, and download the PDF — no code involved.
curl https://inkrun.dev/api/v1/render \
-H "Authorization: Bearer sk_..." \
-H "Accept: application/pdf" \
-d '{"template": "technical-manual", "markdown": "# ..."}' \
--output technical-manual.pdfAdd the Inkrun MCP connector once, then ask your agent:
“Compile the docs/ folder into a single manual and render it with the technical-manual template.”
Yes — code renders in a true monospace block with the template's styling, and the theme avoids breaking a fence across pages where possible.
Concatenate them in your build step (or let your agent do it) and send one document — heading levels keep the chapters organized.
Code blocks are styled for readability with the template's monospace stack and boxed background; language-aware color highlighting is on the roadmap.
Roboto Mono headings and grid tables for endpoint docs.
Operational runbook in a calm teal with monospace headings.
Montserrat headings over Open Sans in a fresh teal.