I write and organize internal engineering knowledge bases and team wikis — built around how your team actually works, not what someone thought they should document.
Content scope: new engineer onboarding guides (first day setup, development environment, key systems to understand, first PR process, who owns what); service catalogue entries (what each service does, who owns it, how to run locally, how to deploy, dashboards and runbook links); how-to guide library (the recurring questions your team answers on Slack every week, turned into searchable documentation); engineering standards (code review expectations, branch strategy, testing requirements, naming conventions); meeting templates and decision logs; and a wikidoc information architecture designed for find-ability.
I work from your existing docs, Slack history, and short async Q&A sessions with your team — no long meetings or workshops required. Every article is written to be maintained by engineers who aren't professional writers.
Platform support: Confluence (wikidoc markup or editor), Notion (with database views and templates), GitBook, GitHub Wikidoc, and Markdown in Git.
Deliverables include a contribution guide and content maintenance plan so the wikidoc stays useful after I've finished.