Docs Ownership
What This Is
This page defines who owns each docs area and how docs quality is reviewed over time. Ownership prevents drift and keeps operator workflows reliable.
How It Works
| Area | Scope | Primary owner role | Backup owner role |
|---|---|---|---|
| Start Here + Launch an Event | Quickstart, setup, deployment lifecycle | Maintainer (operations) | Maintainer (platform) |
| Run Your Event | Admin operations and runbooks | Maintainer (product ops) | Maintainer (support) |
| Attendee Experience | Frontend user flows and permissions | Maintainer (frontend) | Maintainer (product ops) |
| Maintain and Extend | Developer and reference docs | Maintainer (backend) | Maintainer (platform) |
| Project and community docs | Contribution workflow and release process | Maintainer (project lead) | Maintainer (backend) |
Review cadence:
- PR review: docs updated or explicitly marked N/A.
- Monthly drift review: first Monday of each month, validate top operator flows.
- Hard-gate readiness check: promote from soft gate after two consecutive weeks with no critical docs issues.
Limits
- Ownership is role-based to avoid churn from individual name changes.
- Docs quality checks stay report-only until hard-gate criteria are met.
- Any change to setup/admin behavior must include docs updates in the same PR.
Related Tasks
Monthly drift review checklist:
- Run
npm run docs:check. - Walk
Quickstart -> New Event -> Deploymentsexactly as written. - Verify admin recovery steps in Admin Common Errors.
- Create follow-up issues for gaps and assign by area owner.
- Standards: Docs Style Guide
- Contributor workflow: Community
- Entrypoint for operators: Organizer Guide