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 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/.
Join our discussions of documentation issues here on the blog and on Slack.
Note:Highlight: Use tables to present lengthy and complex pieces of data that are related, in a well-structured format.
Tables are useful to present lengthy and complex pieces of data that are related, in a well-structured format that is easy to read and scan for readers. Generally a table consists of two or more rows and two or more columns in addition to the header row.
To create multiple paragraphs, use the <p> element rather than using the <br> element. For more information on which uses of <br> are correct and which ones aren’t, see the HTML specification for <br>.
Lets you link directly to a specific block on a page. This property adds a field to define an id for the block and a button to copy the direct link.
When the style picker is shown, a dropdown is displayed so the user can select a default style for this block type. If you prefer not to show the dropdown, set this property to false.
In most cases, introduce a table with an introductory sentence that initiates the table that follows. If the heading of the content explains what the table is about, and no additional context is required, then don’t include an introductory statement. You can introduce a table with an imperative statement.
The introductory sentence can end with a colon or a period. Use a period if the introductory content is extended, and a colon if the introductory statement is shorter and immediately precedes the table. The text preceding the colon must distinctly stand alone as a complete sentence. That is, don’t introduce a table with a partial statement.
Use sentence case capitalization for the table title and each column heading. For text inside table cells, use sentence case capitalization; with exceptions. For example, some values, keywords, or strings are written in lowercase.
For text inside table cells, use periods or other end punctuation only if the sentences contain complete sentences or a combination of phrases and sentences.
If your document or article contains only one table, the table doesn’t need a caption. However, ensure that the table succeeds an introductory statement.
But if your document or article contains more than one table in close proximity to each other, include a caption for each table. Write the caption in the form: “Table number. Description“. Use sentence case capitalization and don’t insert a period at the end.
While referring to a table, refer to it by its number. For example, Enter the values as shown in table 3. Don’t capitalize table unless it starts a sentence.
Tip:Recommended: Table 3. 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.APIAPIAn API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. reference
For HTML tables, insert a caption using the <caption> element as the first child of the <table> element.
<caption><b>Table 3.</b> Block API reference</caption>
Use column headings in the first row of your table, also known as the header row.
Distinguish the header row from the rest of the text in the table. For example, highlight the text in the header row such as making it bolder, larger, and changing the background color.
Ensure that the header row is always visible in long tables, so that the column headings are visible while scrolling. Don’t use collapsible or unbound header rows; instead use fixed header rows. It is acceptable to occasionally repeat the header row in downloadable documents.
Use sentence case capitalization for column headings.
Don’t end column headings with punctuation such as a period, colon, semicolon, or an ellipsis.
Write concise headings and omit articles (a, an, the).
Don’t write partial column headings such that the sentence or phrase in the column heading continues from the cell text. Discontinuous content proves to be difficult for accessibility and for localization. Instead, write complete column headings.
Use table headings for the first column and the first row only. Use the th element.