These are patterns, not templates to copy word for word: every file below is written for a made-up site on a reserved example domain. Replace the names, URLs and notes with your own, and keep the structure.
1. A small business site
Few pages, one section. The notes say what a reader finds on each page, including the facts people ask for most (prices, hours, cut-off times).
# Example Bakery > A neighbourhood bakery in Springfield with online pre-orders. ## Pages - [Menu](https://example.com/menu): Breads, pastries and cakes with prices - [Pre-order](https://example.com/order): Order by 6 pm for pickup the next morning - [Visit us](https://example.com/visit): Address, opening hours and parking ## Optional - [Privacy](https://example.com/privacy)
2. A documentation site
Docs and API in separate sections, a details line that says which version the docs cover, and the changelog under Optional because a reader can skip it.
# Example CLI > A command-line tool that syncs folders to object storage. Version 2 commands are documented here; version 1 is no longer supported. ## Docs - [Install](https://docs.example.org/install): Packages for macOS, Linux and Windows - [Configuration](https://docs.example.org/config): The config file, every key with defaults - [Commands](https://docs.example.org/commands): sync, watch and verify, with flags ## API - [Library usage](https://docs.example.org/library): Calling the sync engine from your own code ## Optional - [Changelog](https://docs.example.org/changelog): Release notes since 2.0 - [Contributing](https://docs.example.org/contributing)
3. A software product with a blog
Product pages first, help next, then only the blog posts that answer real questions. Legal pages go under Optional at the end.
# Example Invoices > Invoicing for freelancers: quotes, invoices and automatic payment reminders. ## Product - [Features](https://example.net/features): Quotes, recurring invoices, reminders and exports - [Pricing](https://example.net/pricing): Plans, limits and what each includes - [Integrations](https://example.net/integrations): Bank feeds and accounting exports ## Help - [Getting started](https://example.net/help/start): Create an account and send a first invoice - [Reminders](https://example.net/help/reminders): How and when reminders are sent ## Blog - [Writing payment terms](https://example.net/blog/payment-terms): Wording for due dates and late fees ## Optional - [Terms](https://example.net/terms) - [Privacy](https://example.net/privacy)
4. Fixing a broken file
Before: two H1 headings, a bullet without a link, a relative URL, a note without the colon, an H3 and a lower-case "optional".
# Example Agency # Services - Web design - [SEO audits](/seo) - monthly reports ### Contact - [Contact](https://example.com/contact) ## optional - [Jobs](https://example.com/jobs)
After: one H1, a summary, links with absolute URLs and colon notes, and a section named exactly "Optional" at the end.
# Example Agency > A two-person studio that designs and builds websites for local businesses. ## Services - [Web design](https://example.com/web-design): Small business sites from brief to launch - [Site audits](https://example.com/audits): A monthly report on speed and broken links - [Contact](https://example.com/contact): Ask for a quote ## Optional - [Jobs](https://example.com/jobs)
Patterns that hold up
- Write notes for a reader who has not seen the site. "Plans, limits and what each includes" beats "Pricing page".
- Keep it short. List the pages that answer real questions; leave out tag pages, archives and duplicates.
- One topic per section. Section names are labels, not sentences.
- Use the final URL. Link the address that answers 200, not one that redirects.
- Put what can be skipped under Optional, and keep it last.
The generator follows these patterns for your first 25 pages, and the checker tells you which rule a line breaks.