Status: Draft. This page is a work in progress, started following the June 2026 meeting.
This is the Editorial Board’s list of significant documentation projects we are actively leading or shepherding. It reflects our proactive stance: rather than only reacting to requests, we identify important work and find people to carry it out.
How this list works
- Every project has a committed lead. This is not a wish list. A project is added only when someone has agreed to lead it. If a project loses its lead, it moves to Parking lot until a new lead steps up.
- Each project names its challenges, not just the goal. Describing the hard parts up front helps contributors know what they are taking on.
- We keep the list short and prioritized rather than long and aspirational, so we can give each project real oversight.
Want to help with a project, or propose a new one? Open an issue on this repo or reach out in the Python Docs Discord.
Project template
Once a project is approved by the Editorial Board, copy this block to add a new project.
### <Project name>
- **Lead:** <name — required; no lead, no listing>
- **Status:** Proposed | Active | Blocked | Done
- **Summary:** One or two sentences on what this project delivers.
- **Why it matters:** Who benefits and why this is worth doing now.
- **Challenges / risks:** The hard parts — technical blockers, dependencies,
unknowns, things that could derail it.
- **How to help:** Concrete ways a contributor can get involved.
- **Links:** Relevant issues, PRs, discussions, or docs.
Active projects
None listed yet. Add projects here using the template above.
Parking lot
Ideas worth doing that do not yet have a committed lead. These are not active projects until someone steps up to lead them.
Empty for now.