Built and contributed by people who actually keep their wiki current. Open one with a click; everything is editable. Save back to your workspace as a reusable template.
For docs that engineers will actually read. RFCs, on-call runbooks, postmortems, architecture pages.
Brief one-paragraph summary of what we’re proposing and why.
What happened, who noticed, what we did to recover.
14:32 first alert
14:35 acknowledged
14:48 root cause identified
Marketing campaign launches Tue.
What this service does, what it depends on, what depends on it.
p99 latency < 200ms · 99.9% uptime
What we look for in code review, what we don’t.
1. Reply within 1 BD
2. Approve or block, no maybes
3. Suggest, don’t demand
For making decisions and remembering why you made them. Roadmaps, decision logs, customer interviews.
Auth redesign · Billing UI · SSO
API v2 · Admin v1
Marketplace
Context: what was the situation?
Decision: what did we decide?
Consequences: what does that mean?
Background: their role & org size.
Quotes: verbatim, transcribed.
Pricing pressure · integration gaps
For meetings that produce something. Agendas in the doc, outcomes in the doc, the doc stays in the wiki.
Bug bash Friday
What’s on your mind?
Feedback · context
Pair sessions, deploy cadence
CI flakiness, scope creep
For the things that should live somewhere stable. How we work, who’s who, what we’ve agreed on.
Async first, agenda + outcome required.
Slack for now, wiki for later.
How much leave you have, how to request it, how to cover handover.
Country-specific list
Our interview process, the rubric, what we score on.
Intro → Take-home → Pair → Cultural