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 to refer to a collection of images, graphics, pictures, charts, or other media items that the user can view or interact with. Use the verb select for items in a gallery.
Use to mean usually, typically, in most cases, or normally. When generally is used, there might be exceptions or specific instances which might differ from usual practices. Use proper judgement to choose a contextually relevant term.
As a noun, use graphic or graphics to refer to one or more computer-generated images such as pictures and charts used for illustration or visual representation.
Example
Tip:Recommended: Select the graphic you want to display.
As an adjective, use graphic to refer to the field of visual art. Use graphics to refer to software or hardware used to generate computer-generated images such as pictures and charts.
Examples
Tip:Recommended: The website implements intuitive graphic design.
Tip:Recommended: This website uses the latest graphics software.
Generally, use graphical as an adjective to refer to visual art.
Example
Tip:Recommended: You can include a graphical representation, such as a picture or chart, on your website.
In general, emphasize on the task to be accomplished, rather than how the user should interact with the UI element.
Don’t use grayed or grayed out to describe UI elements that are in an unusable state; instead, use not available or unusable. If you have to use a descriptor, use dimmed or appears dimmed.
