Page Template
This is the standard structure every wiki page follows. Copy this when creating new pages.
Every page in the wiki uses this exact structure. When running a document digestion pass, extract content into these sections. If a section doesn't apply, mark it “N/A” rather than removing it.
Page Title
[Page Title]
[Short subtitle or one-liner describing what this page covers]
Purpose
[Why does this exist? What problem does it solve? 2-3 sentences explaining the “why” behind this process, script, system, or tool. Someone reading this should immediately understand why they should care.]
When To Use It
- [Specific trigger or situation that calls for this]
- [Another scenario where this applies]
- [Frequency — daily, weekly, per-client, as-needed, etc.]
Step-by-Step SOP
[Step title]
[What to do, how to do it, what the output should be]
[Step title]
[What to do, how to do it, what the output should be]
[Step title]
[What to do, how to do it, what the output should be]
[Step title]
[What to do, how to do it, what the output should be]
[Step title]
[What to do, how to do it, what the output should be]
Tools Used
Roles Responsible
Common Mistakes
- [Thing people get wrong #1]
- [Thing people get wrong #2]
- [Thing people get wrong #3]
Related Pages
Source Links
- [Original doc, Google Drive link, Notion page, etc.]
- [Video recording, Loom, training session]
- [Slack thread, email, or conversation source]
Document Digestion Process
When processing a document, script, SOP, or set of notes into a wiki page:
- Identify which pillar it belongs to (SOPs, Sales Scripts, HR/Onboarding, Marketing Systems, or Product/Dev)
- Extract into template sections — map the raw content into Purpose, When To Use, SOP steps, Tools, Roles, Mistakes, Related Pages, and Sources
- Add cross-links — connect to related pages in the same or other pillars
- Flag gaps — if a section can't be filled from the source doc, mark it as “[Needs input]” for human review