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:
Docs & Polyglots teamPolyglots TeamPolyglots Team is a group of multilingual translators who work on translating plugins, themes, documentation, and front-facing marketing copy. https://make.wordpress.org/polyglots/teams/. are ready to turn on the HelpHub feature on Rosetta sites as requested. Locale teams can request the feature activation on metaMetaMeta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress.tracTracTrac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. (examples). For more background, refer to HelpHub & Handbook i18n Updates (July 2019) and linked posts.
HelpHub MigrationMigrationMoving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. Guide for Rosetta Sites#HelpHub Migration Guide for Rosetta Sites
Grant access to other contributors at the bottom of this page: https://LOCALE.wordpress.org/support/users/USERNAME (note: the dropdown will keep showing “no role for this site” until #meta-4762 is fixed)
Set up a call for help on your Rosetta site blog or your /team P2. Use the instruction described in the next section to clarify the steps for contributors (some examples can be found on the status spreadsheet, column H).
Join documentation and/or translation channel on your local Slack.
Request HelpHub Editor role. Make sure to provide your 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/ username.
Go to your locale’s Migration Worksheet.
Pick an article, enter your name, and update the status.
Go to https://LOCALE.wordpress.org/support/wp-admin/edit.php?post_type=helphub_article and start editing.
Once some pages are published, a HelpHub Administrator can use the CustomizerCustomizerTool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings.WidgetWidgetA WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. to show HelpHub article on /support/ landing page.
Select “Widgets” in the customizer.
Select the “Front page blocks” widget area.
Search for a “(HelpHub) Link 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. widget” and add it.
