Need a volunteer to help prepare for Codex updates

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.

WordPress 3.9 is arriving next week, which means that we need to get the codex updated. It helps to have a master list of pages in the codex that need to be updated, like this one here. We’re looking for a volunteer (or volunteers) to compile this list.This involves:

1. Listing all of the new features, functions, etc in a P2P2 P2 or O2 is the term people use to refer to the Make WordPress blog. It can be found at https://make.wordpress.org/. post. The 3.9 Codex page has many of them.
2. Finding all of the pages in the Codex that need to be updated to reflect the changes in WordPress and listing them. (You can create a checklist by putting a o at the start of a link in P2.)

This helps a lot with keeping track of what’s done and what needs to be done.

Anyone interested?

#codex

Want to get involved?

Weekly meetings

Share this: