Docs Chat Roundup – Jan 23, 2014

1. DevHub

Things are getting back in gear and progress is being made on 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. We are working on the test site at

There’s a github repo and currently the bulk of the work is being done by @krogsgard and @rarst, but we’d love to have other contributions.

There’s also a Skype channel for this effort. If you’d like to be added, contact @siobhan.

2. Docs Issue Tracker

Otto’s hard at work on the Documentation Issue Tracker and making progress. More to come . . .

3. Inline Docs

@DrewAPicture and @kimparsell are still making steady progress.

4. Docs Sprint

The Docs Sprint is going back to meeting once a month.

The next meetupMeetup All local/regional gatherings that are officially a part of the WordPress world but are not WordCamps are organized through A meetup is typically a chance for local WordPress users to get together and share new ideas and seek help from one another. Searching for ‘WordPress’ on will help you find options in your area. is Feb 1. Join us in-person in Seattle, or virtually via IRC in #wordpress-sfd.

5. AH-O2P2 P2 or O2 is the term people use to refer to the Make WordPress blog. It can be found at

The Admin Help (AH-O2) project now has an AH-O2 plugin in the repo for testing and it’s looking more polished.

@jazzsequence needs help with content for Admin Help and is looking for contributions. There’s now a doc detailing how to add new documentation to the Help overviews too.

If you can help, please join the AH-O2 project:

6. Docs Project Landing Pages

We’ve decided to have helpful landing pages for each docs-related project, each providing an overview of the project and telling contributors all they need to know to get involved.

There is a Projects section where others can add their docs project landing pages.

@DrewAPicture posted the landing page for Inline Docs, which is a great example.

We’re targeting Feb 28th to have these all landing pages complete. @siobhan would like a volunteer to oversee this project and make sure these all get created and posted.

7. Handbook Scope

@siobhan brought up a concern that some of the content in the Handbooks getting out of scope and there was discussion about what’s in, and out, of scope.

Currently, there aren’t formal scope documents for each Handbook, so we should create these and consider adding, or linking to, them from each project’s landing page.

8. Administrative Chat

@siobhan followed up on her proposal for holding an administrative chat to review where the docs team is, discuss how we get new contributors, and float ideas for future projects.

We’re thinking this might best work on a Saturday to avoid work conflicts. @siobhan will suggest a date or two shortly.