Skip to content

Templates

Every built-in template with the file it starts, from a task to a data processing agreement.

DocumentationTemplates

45 templates ship with notdocs. A repository adds or replaces them with files in docs/_templates/. For which to write at each stage of a product, see the templates guide.

page

page: A blank page.
page
---
type: page
title: Untitled
---

# Untitled
journey: A user journey map: stages, actions, thoughts and pain points.
journey
---
type: page
title: Untitled
---

# Untitled

| Stage | What they do | What they think | Pain points | Opportunity |
| ----- | ------------ | --------------- | ----------- | ----------- |
| Discover |          |                 |             |             |
| Try      |          |                 |             |             |
| Adopt    |          |                 |             |             |
standards: Engineering standards and the definition of done.
standards
---
type: page
title: Untitled
---

# Untitled

## Definition of done

- [ ] Tests pass
- [ ] Reviewed
- [ ] Documented
- [ ] Deployed behind a flag

## Code

Style, review and branching rules.

## Quality

Coverage, performance and accessibility bars.
oncall: The on-call and incident response process with escalation paths.
oncall
---
type: page
title: Untitled
---

# Untitled

## Rotation

Who is on call, for how long, and how handover works.

## Severity levels

| Level | Means | Response |
| ----- | ----- | -------- |
| sev1  |       |          |

## Escalation

Who is paged next and when.

## During an incident

1. Acknowledge
2. Communicate
3. Mitigate
4. Open a postmortem
user-guide: A customer-facing user guide or onboarding page.
user-guide
---
type: page
title: Untitled
---

# Untitled

## Getting started

The first thing to do.

## How to

- 

## Troubleshooting

Common problems and their fixes.
metrics: A metrics definition: north star, activation, retention and churn.
metrics
---
type: page
title: Untitled
---

# Untitled

| Metric | Definition | Source | Target |
| ------ | ---------- | ------ | ------ |
| North star |        |        |        |
| Activation |        |        |        |
| Retention  |        |        |        |
| Churn      |        |        |        |
feedback: A customer feedback log and voice-of-customer synthesis.
feedback
---
type: page
title: Untitled
---

# Untitled

## Themes

- **Theme.** What customers keep saying.

## Log

| Date | Source | Customer | Feedback | Theme |
| ---- | ------ | -------- | -------- | ----- |
|      |        |          |          |       |

task

task: A unit of work on the board.
task
---
type: task
title: Untitled
status: todo
---

# Untitled

## Goal

## Done when

- [ ] Acceptance criterion

decision

decision: An architecture or product decision record.
decision
---
type: decision
title: Untitled
date: 2026-10-21
status: proposed
---

# Untitled

## Context

## Decision

## Consequences
adr: An architecture decision record with the options that were weighed.
adr
---
type: decision
title: Untitled
date: 2026-10-21
status: proposed
---

# Untitled

## Context

The forces at play.

## Options considered

1. Option
2. Option

## Decision

What was chosen and why.

## Consequences

What becomes easier and what becomes harder.
deprecation: A deprecation or sunset decision for a feature being retired.
deprecation
---
type: decision
title: Untitled
date: 2026-10-21
status: proposed
---

# Untitled

## Context

What is being retired and why.

## Who is affected

Customers, integrations, internal users.

## Timeline

- Announce
- Stop new usage
- Remove

## Migration

What people move to and the help they get.

spec

spec: A feature or system specification.
spec
---
type: spec
title: Untitled
status: draft
---

# Untitled

## Problem

## Proposal

## Open questions
prd: A product requirements document: users, stories, scope and success metrics.
prd
---
type: spec
title: Untitled
status: draft
---

# Untitled

## Problem

What is hard today, for whom, and the evidence.

## Users

Who this is for.

## User stories

- As a …, I want … so that …

## Scope

What ships.

## Out of scope

What does not, and why.

## Success metrics

How we know it worked.

## Open questions

- 
rfc: A technical design document: architecture, data model, APIs and trade-offs.
rfc
---
type: spec
title: Untitled
status: draft
---

# Untitled

## Context

Why this is being built now.

## Goals and non-goals

- Goal
- Non-goal

## Design

Architecture, data model and APIs.

## Alternatives

What else was considered and the trade-offs.

## Rollout

How it ships and how it is rolled back.

## Open questions

- 
pricing: A pricing and packaging document: tiers, limits, and the reasoning.
pricing
---
type: spec
title: Untitled
status: draft
---

# Untitled

## Packaging

| Tier | Price | Includes | Limits |
| ---- | ----- | -------- | ------ |
| Free |       |          |        |

## Reasoning

Why these tiers and these lines between them.

## Comparables

What the market charges.

## Open questions

- 
accessibility: Accessibility requirements against WCAG for a feature or product.
accessibility
---
type: spec
title: Untitled
status: draft
---

# Untitled

## Target

WCAG 2.2 level AA.

## Requirements

- [ ] Keyboard operable
- [ ] Focus visible
- [ ] Screen reader labels
- [ ] Colour contrast 4.5:1

## Testing

How conformance is checked and by whom.

## Known gaps

- 
threat-model: A security threat model and data-handling review.
threat-model
---
type: spec
title: Untitled
status: draft
---

# Untitled

## System

What is in scope and its trust boundaries.

## Data

What is stored, where, for how long, and who can read it.

## Threats

| Threat | Likelihood | Impact | Mitigation |
| ------ | ---------- | ------ | ---------- |
|        |            |        |            |

## Open risks

- 
infrastructure: An infrastructure and deployment plan: environments, CI/CD, infrastructure as code.
infrastructure
---
type: spec
title: Untitled
status: draft
---

# Untitled

## Environments

Development, staging, production and what differs.

## Pipeline

Build, test, deploy, and what gates each step.

## Infrastructure as code

Where it lives and how it is applied.

## Secrets and access

Who can deploy and how credentials are kept.

meeting

meeting: Meeting notes with attendees and action items.
meeting
---
type: meeting
title: Untitled
date: 2026-10-21
---

# Untitled

## Notes

## Action items

- [ ] Action item
quarterly-review: A quarterly product review or retrospective.
quarterly-review
---
type: meeting
title: Untitled
date: 2026-10-21
---

# Untitled

## Shipped

- 

## Metrics

What moved and what did not.

## What worked

- 

## What did not

- 

## Next quarter

- [ ] 

launch

launch: A launch checklist an agent or human can work through.
launch
---
type: launch
title: Untitled
status: planning
---

# Untitled

## Pre-launch

- [ ] Landing page live
- [ ] Pricing decided
- [ ] Analytics wired
- [ ] Waitlist emailed

## Launch day

- [ ] Post published
- [ ] Replies handled

## Retro

- [ ] Metrics recorded

letter

letter: A business letter with a letterhead and a signature block, exportable to PDF and DOCX.
letter
---
type: letter
title: Untitled
date: 2026-10-21
document-type: business-letter
---

:::letterhead
Your Company
Street 1
City, Country
:::

:::contact-info
Phone: +30 000 000 0000
Email: <hello@example.com>
:::

2026-10-21

Dear Recipient,

# Untitled

Body of the letter.

Sincerely,

:::signature-block
Name
Title
Your Company
:::

proposal

proposal: A proposal with scope, pricing table and timeline, exportable to PDF and DOCX.
proposal
---
type: proposal
title: Untitled
date: 2026-10-21
document-type: proposal
status: draft
version: "1.0"
---

:::letterhead
Your Company
Street 1
City, Country
:::

:::header
Untitled | Page {{page}}
:::

:::footer
Confidential
:::

# Untitled

## Summary

## Scope

## Pricing

| Item | Quantity | Rate | Total |
| ---- | -------- | ---- | ----- |
| Work | 1        | €0   | €0    |

## Timeline

## Next steps

:::signature-block
Name
Title
Your Company
:::

invoice

invoice: An invoice with line items and payment terms, exportable to PDF and DOCX.
invoice
---
type: invoice
title: Untitled
date: 2026-10-21
document-type: invoice
invoice-number: INV-0001
payment-terms: Net 30
---

:::header
Untitled | Invoice INV-0001
:::

:::letterhead
Your Company
Street 1
City, Country
:::

# Invoice

**Invoice number:** INV-0001  
**Date:** 2026-10-21  
**Due:** 

**Bill to:**  
Recipient

## Items

| Description | Quantity | Unit price | Amount |
| ----------- | -------- | ---------- | ------ |
| Work        | 1        | €0         | €0     |
|             |          | **Total**  | **€0** |

## Payment

Payment is due within 30 days.

:::footer
Questions? hello@example.com | Page {{page}}
:::

contract

contract: A contract with parties, terms and signature blocks, exportable to PDF and DOCX.
contract
---
type: contract
title: Untitled
date: 2026-10-21
document-type: contract
effective-date: 2026-10-21
parties:
  - Party A
  - Party B
---

:::letterhead
Your Company
Street 1
City, Country
:::

:::header
Untitled | Page {{page}}
:::

# Untitled

This agreement is made between Party A and Party B.

## 1. Scope

## 2. Term

## 3. Fees

## 4. Confidentiality

## 5. Governing law

::page-break

:::signature-block
Name
Title
Your Company
:::

:::signature-block
Name
Title
Your Company
:::

memo

memo: An internal memo with a header, exportable to PDF and DOCX.
memo
---
type: memo
title: Untitled
date: 2026-10-21
document-type: memo
---

:::header
Memo | 2026-10-21
:::

# Untitled

**To:**  
**From:**  
**Date:** 2026-10-21  
**Subject:** Untitled

## Summary

## Details

## Action

report

report: A report with an executive summary and findings, exportable to PDF and DOCX.
report
---
type: report
title: Untitled
date: 2026-10-21
document-type: report
status: draft
version: "1.0"
---

:::letterhead
Your Company
Street 1
City, Country
:::

:::header
Untitled | Page {{page}}
:::

:::footer
© 2026
:::

# Untitled

## Executive summary

## Findings

## Recommendations

## Appendix
competitive: A market and competitive analysis, exportable to PDF and DOCX.
competitive
---
type: report
title: Untitled
date: 2026-10-21
document-type: report
status: draft
version: "1.0"
---

:::letterhead
Your Company
Street 1
City, Country
:::

:::header
Untitled | Page {{page}}
:::

# Untitled

## Market

Size, segments and where it is going.

## Competitors

| Competitor | Positioning | Pricing | Strengths | Gaps |
| ---------- | ----------- | ------- | --------- | ---- |
| Name       |             |         |           |      |

## Where we win

The differences that matter to buyers.

## Risks

What could change the picture.
research: UX research findings: method, participants, findings and recommendations.
research
---
type: report
title: Untitled
date: 2026-10-21
document-type: report
status: draft
version: "1.0"
---

:::letterhead
Your Company
Street 1
City, Country
:::

:::header
Untitled | Page {{page}}
:::

# Untitled

## Method

Interviews, usability tests, surveys; how many and when.

## Participants

Who took part.

## Findings

1. Finding, with the evidence.

## Recommendations

- 

brief

problem: A problem statement or opportunity brief: the pain, who has it, the evidence.
problem
---
type: brief
title: Untitled
status: draft
---

# Untitled

## Problem

What pain exists.

## Who has it

The people or segment.

## Evidence

Interviews, data, support tickets.

## Opportunity

What solving it is worth.

## Next step

What we do to learn more.
brief: A marketing brief: positioning, messaging and target segments.
brief
---
type: brief
title: Untitled
status: draft
---

# Untitled

## Objective

What this needs to achieve.

## Audience

The segments and what they care about.

## Positioning

One sentence.

## Messages

1. Message, with proof.

## Channels

- 

playbook

battlecard: A sales battlecard: positioning, objections, and how to answer them.
battlecard
---
type: playbook
title: Untitled
audience: sales
---

# Untitled

## Positioning

One sentence on why us.

## Against

| Competitor | They say | We say |
| ---------- | -------- | ------ |
|            |          |        |

## Objections

- **Objection.** Answer.

## Proof

Customers, numbers, quotes.
playbook: A support playbook: common questions and the answers to give.
playbook
---
type: playbook
title: Untitled
audience: support
---

# Untitled

## When to use this

The situation it covers.

## Questions and answers

### Question

Answer.

## Escalate when

- 

runbook

disaster-recovery: A disaster recovery and backup plan with recovery objectives.
disaster-recovery
---
type: runbook
title: Untitled
---

# Untitled

## Objectives

Recovery time and recovery point targets.

## Backups

What is backed up, where, how often, and how restores are tested.

## Recovery

1. Step

## Contacts

Who to reach and how.
runbook: How to operate a service: restart, diagnose and fix the common failures.
runbook
---
type: runbook
title: Untitled
---

# Untitled

## Service

What it does and where it runs.

## Dashboards and logs

- 

## Restart

1. Step

## Common failures

### Symptom

Cause and fix.

postmortem

postmortem: An incident report: timeline, impact, root cause and follow-ups.
postmortem
---
type: postmortem
title: Untitled
date: 2026-10-21
status: draft
---

# Untitled

## Summary

What happened, in two sentences.

## Impact

Who was affected, for how long.

## Timeline

- HH:MM Detected
- HH:MM Mitigated
- HH:MM Resolved

## Root cause

Why it happened.

## Follow-ups

- [ ] Action, owner, due

release

release: Release notes for one version.
release
---
type: release
title: Untitled
date: 2026-10-21
version: 0.1.0
---

# Untitled

## New

- 

## Changed

- 

## Fixed

- 

## Upgrading

What to do, if anything.

experiment

experiment: An experiment brief: hypothesis, variants, metric and result.
experiment
---
type: experiment
title: Untitled
status: proposed
---

# Untitled

## Hypothesis

If we …, then … because ….

## Variants

- Control
- Treatment

## Metric

What decides it and the size of change we can detect.

## Result

Filled in when it concludes.

persona

persona: A user persona: goals, frustrations and how they work today.
persona
---
type: persona
title: Untitled
---

# Untitled

## Who

Role, context, a sentence in their words.

## Goals

- 

## Frustrations

- 

## How they work today

Tools and workarounds.

slo

slo: A service level objective with its indicators and alerts.
slo
---
type: slo
title: Untitled
objective: 99.9%
service: service
window: 30d
---

# Untitled

## Indicators

| SLI | Measured as | Source |
| --- | ----------- | ------ |
| Availability |    |        |

## Objective

The target over the window, and the error budget it leaves.

## Alerts

- Condition, severity, who is paged

terms

terms: Terms of service, exportable to PDF and DOCX.
terms
---
type: terms
title: Untitled
date: 2026-10-21
document-type: terms-of-service
effective-date: 2026-10-21
version: "1.0"
---

:::letterhead
Your Company
Street 1
City, Country
:::

:::footer
Untitled | Page {{page}}
:::

# Untitled

Effective 2026-10-21.

## 1. The service



## 2. Accounts



## 3. Payment



## 4. Acceptable use



## 5. Termination



## 6. Liability



## 7. Changes to these terms



## 8. Contact


privacy

privacy: A privacy policy, exportable to PDF and DOCX.
privacy
---
type: privacy
title: Untitled
date: 2026-10-21
document-type: privacy-policy
effective-date: 2026-10-21
version: "1.0"
---

:::letterhead
Your Company
Street 1
City, Country
:::

:::footer
Untitled | Page {{page}}
:::

# Untitled

Effective 2026-10-21.

## 1. What we collect



## 2. Why we use it



## 3. Who we share it with



## 4. How long we keep it



## 5. Your rights



## 6. Contact


nda

nda: A non-disclosure agreement with signature blocks, exportable to PDF and DOCX.
nda
---
type: nda
title: Untitled
date: 2026-10-21
document-type: nda
effective-date: 2026-10-21
parties:
  - Party A
  - Party B
---

:::letterhead
Your Company
Street 1
City, Country
:::

:::header
Untitled | Page {{page}}
:::

# Untitled

This agreement is made between Party A and Party B.

## 1. Confidential information



## 2. Obligations



## 3. Exclusions



## 4. Term



## 5. Governing law



::page-break

:::signature-block
Name
Title
Your Company
:::

:::signature-block
Name
Title
Your Company
:::

dpa

dpa: A data processing agreement, exportable to PDF and DOCX.
dpa
---
type: dpa
title: Untitled
date: 2026-10-21
document-type: agreement
effective-date: 2026-10-21
parties:
  - Controller
  - Processor
version: "1.0"
---

:::letterhead
Your Company
Street 1
City, Country
:::

:::header
Untitled | Page {{page}}
:::

# Untitled

This agreement is made between the Controller and the Processor.

## 1. Definitions



## 2. Processing

Subject matter, duration, nature and purpose.

## 3. Obligations of the processor



## 4. Sub-processors



## 5. Security



## 6. Data subject rights



## 7. International transfers



## 8. Deletion and return



::page-break

:::signature-block
Name
Title
Your Company
:::

:::signature-block
Name
Title
Your Company
:::

sla

sla: A service level agreement with uptime commitments and credits, exportable to PDF and DOCX.
sla
---
type: sla
title: Untitled
date: 2026-10-21
document-type: service-agreement
effective-date: 2026-10-21
parties:
  - Provider
  - Customer
version: "1.0"
---

:::letterhead
Your Company
Street 1
City, Country
:::

:::header
Untitled | Page {{page}}
:::

# Untitled

This agreement is made between the Provider and the Customer.

## 1. Service commitment

Monthly uptime of 99.9%.

## 2. Definitions



## 3. Exclusions



## 4. Service credits

| Uptime | Credit |
| ------ | ------ |
| < 99.9% | 10%   |

## 5. Claims



## 6. Support



::page-break

:::signature-block
Name
Title
Your Company
:::

:::signature-block
Name
Title
Your Company
:::