OakWiki
Use cases

Real teams, real wikis.

Four shapes our customers use most. Each comes with a starter template and a recipe for keeping the wiki current after the first week.

For engineering teams

The engineering wiki.

RFCs that get reviewed, runbooks that on-call actually uses, postmortems that turn into changes. Plus the architecture pages new engineers read on day one.

  • RFC template with checklist + reviewer assignments
  • Service-architecture pages with embedded service maps
  • On-call runbooks linked from your alerting tool
  • Blameless postmortem template with timeline + actions
  • Backlinks show which other docs reference this RFC
“We retired our Confluence space and Notion docs in the same week. OakWiki became the single source of truth our team will actually trust.”
Engineering
▾Architecture
❖Service map
❖Data model
▾RFCs
❖042 — Auth redesigndraft
❖041 — DB migrationapproved
❖040 — Cachingshipped
▾Runbooks
❖API outage
❖DB failover
▾Postmortems
❖2026-05-12 deploy halt
Team handbook
❖How we work
▾Communication
❖When to use Slack
❖When to write a doc
❖Meetings: agenda + outcome
▾Time off
❖Paid leave
❖Sick leave
❖Parental leave
▾Hiring
❖How we interview
❖Rubric
For company-wide handbooks

The handbook your team actually reads.

The opposite of the 90-page PDF that sits in a Google Drive folder. A handbook lives in pages, organised as a tree, owned by named people, kept current because editing it is fast.

  • One page per topic, no sprawling 30-section monsters
  • Each page has a clear owner shown at the top
  • “Last updated” auto-shows on every page
  • Stale-content alerts after configurable intervals
  • New-hire dashboard linking to onboarding pages by role
“Our handbook went from nobody reads it to a page that every new hire ships their first PR from.”
For customer-facing teams

The internal knowledge base.

For support teams answering tickets, sales teams answering RFPs, customer success teams onboarding accounts. The knowledge stays internal but stays current.

  • Per-feature pages with FAQ + known issues
  • Embed your help-desk macros and update them once
  • Public-share individual pages externally (Pro plan)
  • Search ranks by edit recency, not just keyword match
  • Page mentions notify the owner when something stale gets cited
“Our support team’s first-response time dropped by 40% after we moved the macro library to OakWiki.”
Support knowledge
▾Billing
❖Refund flow
❖Tax inquiries
❖Subscription changes
▾Features
❖Sharing & permissions
❖SSO troubleshooting
❖Import from Notion
▾Known issues
❖iOS Safari quirks
❖Slow searches on huge wikis
Q3 Planning
❖Q3 Roadmapyesterday
❖Customer-call summariestoday
❖Decision log
Meetings
▾Weekly sync
❖2026-05-19
❖2026-05-26
❖2026-06-02
▾1:1s
❖with Aino
❖with Mikko
For meetings & decisions

Meetings that land somewhere.

Agendas in the doc. Outcomes in the doc. The doc stays in the tree under the right project page. Meetings become artefacts.

  • Weekly recurring meeting template with carry-forward
  • 1:1 template with rolling agenda for both sides
  • Decision-log entry that links to the meeting it came from
  • Action items show on the assignee’s dashboard
  • Backlinks reveal which decisions reference this meeting
“We stopped having meetings twice. The wiki is the source of truth for what was decided.”

Ready to plant one?

Start with a template that matches what you’re trying to do. Everything is editable; nothing is locked.

Browse templates Start free