- DevHub – We are working on the developer.wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ test site at developer.rarst.net. There’s a github repo and currently the main contributors are @krogsgard and @rarst, but we’d love to have other contributions.
- Docs Issue Tracker – Otto’s hard at work on the Issue Tracker and making progress. More to come soon. . .
- Inline Docs – @DrewAPicture and @kimparsell are still making steady progress.
- Docs Sprint – The Docs Sprint is going back to meeting once a month. Next meetup is Feb 1. Join us in-person in Seattle, or virtually via IRC in #wordpress-sfd.
- AH-O2 – The Admin Help (AH-O2) project now has an AH-O2 plugin in the repo for testing. @jazzsequence needs content for Admin Help and is looking for contributors.
- Docs Project Landing Pages – We’ve decided to have landing pages for each docs-related project that provide an overview of the project and tell contributors all they need to know to get involved. Target date for completion is Feb 28th. There is a Projects section where others can add their landing pages like the Inline Docs landing page that @DrewAPicture posted. @siobhan would like a volunteer to oversee this project.
- Handbook Scope – @siobhan brought up a concern that some of the content in the Handbooks getting out of scope. Currently, there aren’t formal scope documents for each Handbook, so we plan to create these and add/link to them from each docs project’s landing page.
- Administrative Chat – @siobhan proposed an administrative chat to review where the docs team is, discuss how we get new contributors, and float ideas for future projects. @siobhan will suggest a date or two shortly.