Welcome to the official home of the WordPress documentation team.
This team is responsible for coordinating all documentation initiatives around WordPress, including the Codex (moving to HelpHub and DevHub), handbooks, parts of developer.wordpress.orgWordPress.orgThe 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/, admin help, inline docs, and other general wordsmithing across the WordPress project.
Want to get involved?
There are many ways in which you can help the Docs team. Every small contribution counts and helps! You can report an issue or typo you found in the docs, or even help us write new documentation for parts that are still missing. These are some helpful links to find out more about what we do and how to collaborate:
Block Editor Handbook: An overview of documentation contributions of 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 / GutenbergGutenbergThe Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/
Documentation Issue Tracker on GitHub: Submit any DevHub/HelpHub/”Doc Team Handbook” Docs-related issue on GitHubGitHubGitHub is a website that offers online implementation of git repositories that can 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.
Use can to convey permission, to refer to an optional action, or to refer to a possible outcome.
Examples
Tip:Recommended: You can also use the slash command to insert a 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..
Tip:Recommended: The process can take up to 15 minutes.
Avoid using in the context of features or functionalities of software or hardware. Instead, rewrite the sentence without using the term.
Examples
Warning:Not recommended:GutenbergGutenbergThe Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ has the capability of 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. editing.
Tip:Recommended: You can edit blocks with GutenbergGutenbergThe Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/.
Don’t use. Instead, use mobile or mobile phone, or if you’re talking about more than phones, then use mobile device. It’s OK to just use phone by itself when the context is clear.
In general, emphasize on the task to be accomplished, rather than how the user should interact with the UI element. If you have to use a descriptor, use checkbox.
When the environment is presumably a desktop with a mouse, use click to describe the act of selecting most targets such as buttons, links, list items, and radio buttons or initiating an action by briefly pressing and releasing the mouse.
In general, don’t hyphenate words beginning with co- such as coordinate, cooperate, and coexist, unless co- is followed by a proper noun or it is absolutely necessary to avoid confusion.
Two words. It’s OK to use combo box in developer documentation and for a technical audience to describe a box in which the user can enter or select a value.
Avoid using in user documentation and for a general audience. Instead, refer to it as a box.
In general, emphasize on the task to be accomplished, rather than how the user should interact with the UI element. If you have to use a descriptor, use command.
It’s OK to use item or option in the context of commands.
Avoid using whenever possible. Instead, spell out the entire word in a non-code context such as configuration or configuring. It’s OK to use config when referring to, for example, a data structure or a file with that name.
In general, emphasize on the task to be accomplished, rather than how the user should interact with the UI element.
In user documentation, don’t use control when you need to describe the UI element used to set a value on a continuous range of possible values, such as screen brightness or volume. Instead, use slider.
In general, don’t hyphenate words beginning with cyber- such as cybersecurity, cyberspace, and cyberattack, unless cyber- is followed by a proper noun or it is absolutely necessary to avoid confusion.
