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/.
Join our discussions of documentation issues here on the blog and on Slack.
In general, emphasize on the task to be accomplished, rather than how the user should interact with the UI element. Refer to a dialog box by its label. If you have to use a descriptor, use dialog or dialog box.
Use dialog, not dialogue. Use dialogue only for verbal interaction between people.
Use to describe a UI element such as a menu item, dropdown list option, or button that the user can’t interact with due to certain conditions.
In general, describe how the user should interact with the UI rather than describing the state of the UI. Use appears dimmed for describing its appearance. Also include how the user can enable it and interact with the element.
It’s OK to use disable as a verb in developer documentation and for a technical audience, to mean making a function or feature inactive. Use disabled for such functions and features. Avoid using in user documentation and for a general audience.
Don’t use disabled to refer to UI elements, functions, or features that are turned off or unavailable. Instead, use a more accurate term such as turned off, inactive, or unavailable.
Use to refer to magnetic storage media such as hard disks.
It’s OK to use disk to generically refer to other types of computer storage such as flash storage and solid-state drives. For example, terms like disk image and disk partition are used in the general sense without considering the type of storage.
Instead of disk, you can also use a more general term, such as computer or storage space.
For optical storage media such as CDs or DVDs, use disc.
Don’t use as an intransitive verb. Display is a transitive verb; therefore it requires an object.
Warning:Not recommended: The dropdown menu displays.
Tip:Recommended: The dropdown menu is displayed.
Tip:Recommended: The dropdown menu appears.
Use display as a general term as a noun, to refer to any visual output device such as a monitor or a built-in display on most devices. Don’t use display when you mean desktop or screen. Use screen to distinguish the usable portion of the display from its edges.
Use in this document while referencing in a particular document. Avoid using in this article or in this topic.
Warning:Not recommended: This article lists all the available WP-CLIWP-CLIWP-CLI is the Command Line Interface for WordPress, used to do administrative and development tasks in a programmatic way. The project page is http://wp-cli.org/https://make.wordpress.org/cli/ commands.
Warning:Not recommended: This topic lists all the available WP-CLIWP-CLIWP-CLI is the Command Line Interface for WordPress, used to do administrative and development tasks in a programmatic way. The project page is http://wp-cli.org/https://make.wordpress.org/cli/ commands.
Tip:Recommended: This document lists all the available WP-CLIWP-CLIWP-CLI is the Command Line Interface for WordPress, used to do administrative and development tasks in a programmatic way. The project page is http://wp-cli.org/https://make.wordpress.org/cli/ commands.
Use file for general uses such as file management or file structure.