Hey there Docs team I’ve been working on…

Welcome to the official home of the WordPress Documentation Team.

This team is responsible for coordinating all documentation initiatives around WordPress, including the handbooks and other general wordsmithing across the WordPress project.

Want to get involved?

Start here to find out more about what we do and how to contribute:

Onboarding to Documentation Team: An overview of what we do and how to collaborate
Documentation Issue Tracker on GitHub: Submit any Documentation Team-related issues on GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/

Weekly meetings

Join our discussions of documentation issues here on the blog and on Slack.

The documentation team holds weekly office hours and monthly Contributor Days on each Tuesday of the month in the #docs SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel. It’s also where you can contact the team at any time outside meetings.

Hey there Docs team. I’ve been working on a turnkey local development environment for Meta sites, and added 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/ to it last night.

I think this will be much more convenient for anyone wanting to help out, since they can just install a few programs and then the entire environment will be provisioned for them automatically, rather than having to manually complete the list of setup tasks.

#devhub

Eric Amundson 10:52 pm on June 24, 2014

That’s terrific, Ian. Thanks!
trishasalas 8:11 pm on June 25, 2014

Ian, thanks for doing this. I’ve been wanting to help with themes/dev. Where can I start? 🙂
- Ian Dunn 9:18 pm on June 25, 2014
  
  Hi Trisha, when you said “themes/dev”, did you mean general theme development for any site in the network? If so, all 3 of the sites that WME currently supports could probably use help there. The MetaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. has lots of tickets that need contributors 🙂
trishasalas 1:23 am on June 26, 2014

Ian,

I was thinking of the docs team but I’m open to anything. The list you provided looks like a great place to start. What does the WME acronym stand for?
- Ian Dunn 3:27 pm on June 26, 2014
  
  Oh, sorry, it’s WordPress Meta Environment, the name of the Vagrant configuration that builds the environment with devhub and other sites automatically.
  
  For the devhub specifically, someone more in involved in the Docs team would know better than me, but it looks like #252 and #493 might be good places to start, or you can always create a new ticket if you see a problem/opportunity that isn’t already tracked in an existing ticket.
trishasalas 12:52 am on June 27, 2014

Cool, no problem. I figured it out once I looked at your original post 🙂 I use VVV daily already so I’m familiar with it and have this setup (mostly). I’ll take a look at the tickets you mentioned. Thanks!

Want to get involved?

Weekly meetings

Share this: