WordPress Help
Official documentation, learning resources, and contributor guides collected from WordPress.org.
-
Plugin/Theme Authors Guide
Interested in getting your project translated? This page will show you, as the theme or plugin author, some tips for working with translators in the Polyglot community. If you are looking for a technical localization guide, please see the meta and plugin handbooks. If you are looking to request PTE status, please see Project Translation…
-
Handbook
The Marketing team focuses on making WordPress marketable in all sorts of contexts, from the WordPress.org side all the way to core and the wider community. The Marketing team promotes WordPress to current and future users and contributors. We create and amplify campaigns to support the growth of the WordPress project. When does the Global Marketing Team meet? The…
-
Block Editor
The WordPress Block Editor (codename “Gutenberg”) is the new editor for WordPress, with the goal of creating a better new post and page editing experience that makes it easy for anyone to create rich post layouts. The Block Editor documentation is published at https://developer.wordpress.org/block-editor/ Refer to the latest Block Editor Documentation on how to contribute to…
-
Accessibility tickets, tasks, and reports
WordPress uses several systems for tracking issues. Issues in WordPress itself are tracked in core ticket tracking. Issues with the network of sites at WordPress.org are tracked in the meta ticket tracker or in various independent repositories in the WordPress Github organization. Issues in the development of the block and site editors are tracked in…
-
Get involved
Members of the Make WordPress Accessibility Team are volunteers working on improvements to accessibility in WordPress for people with disabilities. Not everybody contributing to WordPress is technically minded; in fact, everyone connected with accessibility can contribute to the Accessibility Team. We particularly want to hear from people who are regular users of assistive technology (AT),…
-
Accessibility standards and best practices
What are the best practices for an accessible WordPress website, theme or plugin? The documentation about accessibility itself is now published on the WP Accessibility Knowledge Base. There you can find information about: How to start with accessibility The accessibility-ready program Accessibility standards and best practice Accessibility testing WordPress and Accessibility This documentation is additional…
-
How to do a review (Draft)
This page is opinionated. It should not be used in place of the requirements page. What we expect of themes submitted to WordPress.org The theme must: be GPL compatible. be secure. be free of PHP or JS notices. not be in conflict with plugins e.g. prefixing. be translation ready. use WordPress functions, hooks, filters,…
-
Resources
The following resources are design-oriented talks from WordCamps. If you have a video or other resource you’d like to suggest, please let us know in #design. User Research and Testing Visual and Interface Design Accessibility Design and Inclusion Open Source and Design Non-WordPress Events and Conferences See this ongoing list of non-WordPress events and conferences…
-
Using User Notes
User Notes are how we keep records on particular users when necessary. These notes generally include reasons why a particular user was blocked or flagged, or specific things to watch out for when interacting with the particular user. There are two rules for User Notes: Make your note as detailed as possible, but don’t write…
-
Skeleton for the locale-based PTE Onboarding process
This is a skeleton for local sites. Locale manager can use and adjust it for their locale team guidelines. Please replace [YOUR LOCALE] with your locale. Example: How the German community handles PTE requests. How the [YOUR LOCALE] community handles PTE requests Following the path of some other locales, here are the guidelines for all…