Templates¶
Reusable page shapes for the wiki's repeating content types. Don't write a new SKU/vendor/campaign/decision page from scratch — copy the template. Every page of a given type looks the same, so the team always knows where to find a given field.
Available templates¶
- SKU — for every product. Hero shot, flats, dimensions, materials, construction, variants, cost, manufacturer, status. Used by everything under
products/skus/. - Vendor — for every manufacturer or supplier. Contact, scope, lead times, MOQs, payment terms. Used by everything under
vendors/manufacturers/. - Campaign Brief — for every marketing campaign. Objective, audience, dates, channels, creative, success metric. Used by everything under
marketing/campaigns/. - Decision Record — for every major decision. The question, options, the call, the reasoning. Used by everything under
strategy/decisions/.
How to use one¶
- Copy the template file to its destination folder with a kebab-case filename (e.g.
airplane-blanket.md,olmetex.md,holiday-2026.md). - Fill in every field. If a field doesn't apply, write "n/a" — don't delete it.
- Add the new page to
mkdocs.yml. - Commit. The "Last updated by … at …" line at the bottom of the page is set automatically from git.
Audience & the partner surface¶
This repo builds two sites from one codebase:
mkdocs.yml→ team.iverywhere.com (internal) — readsdocs/. The team sees everything.mkdocs.partners.yml→ partners.iverywhere.com (external) — reads onlydocs-partners/. Vendors, retail buyers, and creators see a curated, redacted subset.
The guarantee against leaks is physical: a page only reaches partners if it lives in docs-partners/; pages in docs/ are never compiled into the partner build.
Every page in docs-partners/ must carry an audience: value in its front matter so intent is explicit and machine-checkable (internal pages under docs/ may omit it — internal is the default):
```yaml¶
title: Care & Materials audience: partner-creator # partner-brand | partner-manufacturing | partner-wholesale | partner-creator | public
```
When a doc needs both an internal and a shareable version (SKU specs, pricing), keep them as two files — the full version in docs/, the redacted version in docs-partners/ — never one file with conditional includes (too easy to leak). Strip COGS/margin, banking, other vendors' identities, Drive file IDs, and open-issue notes from anything in docs-partners/.
Improving a template¶
If a template is missing a field that turns out to matter, add it to the template and backfill the field on every existing page that uses it.