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:
Documentation Issue Tracker on GitHub: Submit any Documentation Team-related issues on GitHubGitHubGitHub 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.
We faced some issues at the systems level – there was no direct way to import the media that we have.
So now we’re gonna have to manually feed the media to the CDN and we might end up with HelpHub going up with no ability to upload media.
We’re gonna look at fixing the upload media portion with the Systems & MetaMetaMeta 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. teams after.
This will likely take more time, I don’t have a clear estimate now. @clorith@netweb are working hard on it
There is also a content freeze in effect now to make sure we don’t need to do content migrationMigrationMoving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. twice when the migration is particularly difficult right now.
Phase 2 Starts
Current Focus
As a fair bit of the improvements require data from Phase 1 (e.g. how people use the site and getting appropriate feedback), we’ve decided to work on functionality that promotes the involvement from the wider audience.
Reminder for what we planned for Phase 2
Feedback Mechanism
A new issue was created to differentiate from the Article Voting functionality and a healthy discussion has started – https://github.com/Kenshino/HelpHub/issues/240
WP Versions
We voted to revisit requirements for this with the CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. Team. The issue can certainly be written better – e.g. putting Codex screenshots to show what we’re replacing and how we intent for content to be restructured
A new Epic was created to track this – https://github.com/Kenshino/HelpHub/issues/249
GitHubGitHubGitHub 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/ issues
It was suggested that we have proper issues created (if not already) for each of the suggested parts of Phase 2. That is being worked on @pskli
Development Meta
Gulp/Grunt is currently broken on HelpHub repo. @pskli and @netweb are working to fix it.
AOB
Doc Team Meetings
We voted to alternate HelpHub meetings with Documentation Team meetings. This is especially helpful as HelpHub requires other Doc Team work such as Codex redirection for HelpHub to get the visitors it’s intended for.
