Happy Contributors, High Standards pick two! Balancing quality and community
summary
Core docs process for Astro is community-driven and concrete: live edits on the public site, every PR needs an LGTM from a team-docs member, and reviewers ask two questions — is it correct and is it helpful — with an intentional acceptance floor summed up as not worse than what we had before. Community work is triaged via Discord, labels like should this be documented guide expectations, 160 volunteers get pinged for quick checks, and merged PRs trigger badges and shout-outs so contributors learn and return.
AI-written summary · about
chapters (11)
- 0:00Balancing quality and community
- 2:14Public docs leadership challenges
- 5:26Responsive docs by community needs
- 7:57Lower standards for quality?
- 10:04PR feedback to community growth
- 13:37Handling challenging PRs
- 18:57PRs as contribution opportunities
- 24:21Contribution expectations clarified
- 27:52Community-driven docs process
- 28:35Closing remarks
- 28:56Q&A
related talks
39mCommunity and Contributors Panel
35mHelping Your Community Contribute to Developer Documentation
23mKeep cool and maintain an open source project
39mOpen Docs, Open Collaboration: Building Better Documentation with Community PRs
44mBuilding On-Ramps for Non-Code Contributors in Open Source
14mBeyond the First PR: Why Contributors Stay in Open Source Communities
33mIncluding People
21mBecome Part of the Project