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.
Avoid using. Instead, use a more accurate term such as coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. or built-in whenever possible.
Avoid using to describe going from one place to other on the internet or other networks. Instead, use browse.
To describe going directly to a website or webpage, whether by entering a URLURLA specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org or selecting a link, use go to.
Avoid using navigate for interacting with UIUIUI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing. elements.
In most cases, avoid describing a product or feature as new as it is likely to become out of date. Instead, state the version of software in which the feature or product was introduced.
In general, don’t hyphenate words beginning with non- such as nonstandard, noncompliant, and nonrestrictive, unless non- is followed by a proper noun or it is absolutely necessary to avoid confusion.
Don’t use non- to negate an entire phrase.
Examples
Not recommended: non-numbered steps or instructions
Recommended: steps or instructions that are not numbered
Use nonprintable to refer to an area of a page that can’t be printed on. Use nonprinting to refer to characters and other data that can’t or won’t be printed.
Don’t use normal to as a synonym for usual, typical, common, or a similar term. Don’t use normally as a synonym for usually, typically, commonly, often, generally, or a similar term.
Use instead of notice to describe information displayed to a user such as errors, updates, or other communications. Don’t use pop-up, toast, or banner.
For more information about notice types in WordPress, see Notices.
OK to abbreviate as no. in UI, tables, or headings where space is limited. It’s acceptable to abbreviate number as no., but consider a global audience; as many languages don’t abbreviate number as no. which may cause confusion.
For more information about formatting numbers, see Numbers.
For more information about spelling out abbreviations, see Abbreviations.
