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.
From @tacitonic For the Style Guide: Priority: Completing the last remaining section. Challenge: Parser inconsistencies. Big Win: Style Guide was published. For the Style Guide, @tacitonic completed 20/28 articles in the last section.
From @themikedPluginPluginA plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party Handbook Priority: 1. Applying an external linking policy to pages as appropriate 2. Picking a single page and applying a style guide to it Challenge: not losing my mind in syntactic pedagogy Big Win: the above
@tacitonic inquired about whether the external linking policy finalised, because external linking articles in the style guide are on hold for that.
To which themiked replied – Partial implementation has been done.
From @justinahinon: For the restructuring of the blockBlockBlock is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. editor handbook: Priority (for next quarter): Continue iterating on the current documentation Challenge: The fact that the doc is synced 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/ and parsed sometimes leads to challenges (redirections, syncing errors, live updates, etc..) Big Win: The initial restructuring plan was completed.
@justinahinon shared tasks French WordPress documentation team is working on, that can be useful for EN docs team –
the French WordPress documentation team has been working on something really interesting in relation to the user documentation of the editor blocks.
Instead of rewriting the description and functioning of the common options for each block, the French Doc team created pages for those parts which are then reused in the block articles.
For example, block options like advanced settings, typography, colors and parts of the block toolbar are shared by all blocks. Having their docs separate makes it easier to maintain them, and not have to make changes to a dozen or so articles when there is a change in the editor.
@audrasjb made a screenshot with annotations to show how it works.
