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.
Avoid using whenever possible. Instead, replace master with a contextually relevant term such as primary, main, original, parent, initiator, driver, controller, manager, mixer, aggregator, publisher, leader, or active. Use primary/secondary, primary/subordinate, principal/agent or other relevant terms instead of master/slave.
Avoid using in standard documentation; reserve may for official policy or legal considerations. To convey possibility, use might instead. To convey permission, use can instead.
Use medium as a singular subject and media as a plural subject. Accordingly, use the correct verb form; the medium is and the media are.
However, when discussing audio, video, and images, you can use media as a singular subject to describe a collection of content such as a set of images.
In general, don’t hyphenate words beginning with mega- such as megabit, megabyte, megahertz, and megapixel, unless mega- is followed by a proper noun or it is absolutely necessary to avoid confusion.
In most cases, refer to a specific kind of memory, such as random-access memory (RAM), read-only memory (ROM), virtual memory, or portable storage devices.
In the noun forms that refer to memory measurements, use of in a prepositional phrase before the unit, such as 512 MB of RAM.
Don’t use memory to refer to storage capacity; instead, use a term such as storage space.
Don’t use as a verb. Instead, use send, receive, or a contextually relevant term.
OK to use as a noun. If required, you can also provide adjective to present further context, such as text message, email message, audio message or video message.
In general, don’t hyphenate words beginning with meta- such as metadata, and metafeed, unless meta- is followed by a proper noun or it is absolutely necessary to avoid confusion.
In the context developer documentation or for a technical audience, where method refers to a member of a class, avoid also using method as a synonym for manner or approach.
In general, don’t hyphenate words beginning with micro- such as microprocessor, microservices, and microcomputer unless micro- is followed by a proper noun or it is absolutely necessary to avoid confusion.
Use to move databases, media, users, applications or code, from one server, environment or platform to another. Don’t use as a synonym for upgrade or port.
Avoid referring to the mouse whenever possible. Instead, emphasize on the task to be accomplished, and the interaction verb with the mouse such as select, click, or press.
In general, don’t hyphenate words beginning with multi- such as multimedia, multilevel, multisite, and multiuser, unless multi- is followed by a proper noun or it is absolutely necessary to avoid confusion.
