A new hire's first document sets the tone for the whole job. The Onboarding Guide is set in an approachable all-sans with a warm amber accent on A4 — generous spacing, checklist-friendly lists, and callouts that make week-one instructions feel like a welcome, not a compliance exercise.
Keep the guide where you already write it — a Markdown file in the repo or wiki. Headings become a scannable structure, task lists become checklists, and links stay clickable in the PDF. Update the source, re-render, and everyone's copy is current; no stale Google Doc with six conflicting versions.
# Welcome to Northwind — Engineering Onboarding **Your first two weeks**, one page at a time. ## Before day one - [ ] Laptop shipped and MDM-enrolled - [ ] Accounts provisioned: GitHub, Slack, Linear, AWS (read-only) - [ ] Buddy assigned — yours is listed in the welcome email ## Week 1 — get running 1. Clone the monorepo and run `make bootstrap` 2. Ship a docs fix on day two (yes, really) 3. Pair with your buddy on one on-call ticket > The goal of week one is a merged PR, not a finished feature. ## Week 2 — get context - Architecture walkthrough (recorded, link in #eng-onboarding) - Shadow one customer call - Pick your first starter project with your manager ## Who to ask | Topic | Person | Channel | | -------------- | ------- | -------------- | | Dev environment| Priya | #eng-help | | Product context| Marcus | #product | | Anything else | Buddy | DM |
Paste your Markdown in the editor, pick Onboarding Guide, and download the PDF — no code involved.
curl https://inkrun.dev/api/v1/render \
-H "Authorization: Bearer sk_..." \
-H "Accept: application/pdf" \
-d '{"template": "onboarding-guide", "markdown": "# ..."}' \
--output onboarding-guide.pdfAdd the Inkrun MCP connector once, then ask your agent:
“Turn our new-engineer onboarding notes into a PDF with the onboarding-guide template.”
Yes — task-list syntax renders as printable checkboxes, so the guide doubles as a first-week checklist.
Duplicate the template per team if you want different accents, or keep one template and swap the Markdown per role — the design stays identical.
Keep the source in your repo or wiki and re-render on change — one API call in CI regenerates the PDF whenever the Markdown is edited.
Monospace headings for API references and developer docs.
Operational runbook in a calm teal with monospace headings.
Neutral slate for crisp, skimmable notes.