WordPress.org

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:

Onboarding to Documentation Team: An overview of what we do and how to collaborate
Documentation Issue Tracker on GitHub: Submit any Documentation Team-related issues on GitHubGitHub GitHub 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.

The documentation team holds weekly office hours and monthly Contributor Days on each Tuesday of the month in the #docs SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel. It’s also where you can contact the team at any time outside meetings.

Attendance

@atachibana, @kafleg, @yui, @Sanyog, @LeRoy, @tcarney, @leogermani, @bph, @ibdz, @felipeloureirosantos, @felipeelia, @estelaris

Topics

WordcampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. feedback

First topic was a feedback from WordCamps. We had WCUS, WordCap Tokyo and many others

In WCUS, @zzap introduced:

Please everyone welcome our new GutenbergGutenberg The 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/ docs reps: @bph for end user docs and @pbrocks for developer’s docs.

@bph was in WCUS and informs that Jamie Wedholm also joined the team table and started a Google doc comparing current blockBlock Block 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. doc with current coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. version of a block.

She is working Gutenberg end user documentation, organizing at https://trello.com/b/JnTCzOsL/gutenberg-end-user-docs

Helphub Localization

@estelaris asked about the language icon on the new HelpHub pages design

my question is regarding the use if the language options. I need to know how it works and if it is necessary to include it on HelpHub

It was pointed out that the discussions around it has been done in this issue on githubGitHub GitHub 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/: https://github.com/WordPress/HelpHub/issues/201.

@felipeelia highlighted

It is worthy noting that HelpHub translations are not linked yet (and probably won’t be in the near future). So, while it will be a very important element in the future, we wouldn’t have a way to implement it right now

The discussion went on how and where to present the language selector. There has been quite a consensus that it should be in the sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme. and the language must be written in the the languages’ format (not in english), with an autocomplete tool so users can find their own language.

We also discussed the possibility of auto-detecting the browser language and then suggest, with a more intrusive message right at the top of the page, that this page is also available in the browser’s language. (similar of what is done in other places in wp.org)

@esteralis will work on a first suggestion, while de dev team have to figure out when this can be implemented.

Docs Team badges

One more comment from @felipeelia:

During our first America’s Polyglots Meeting, @fierevere asked about Docs Team contribution badges being given to HelpHub collaborators
Also @yui had details.

@atachibana answers:

This is definitely important to involving many people into I18N HelpHub. Badge policy is not still fixed in Docs team, and this is another topic that @Kenshino (Jon) should decide.
He will lead the next week meeting and let him pick up this topic.

Common APIs Handbook

@leogermani says Internationalization Docs are live on the Common APIs Handbook: https://developer.wordpress.org/apis/handbook/internationalization/ and asks for feedback.

Once it’s ok, we can edit plugins and themes handbooks and remove the repeated content from there.

Transcript

You can take a look at the meeting transcript via this link: https://wordpress.slack.com/archives/C02RP4WU5/p1573484411030000