HelpHub and DevDocs redesign request

About four years ago, Polyglots teams began migrating user documentation from the Codex to HelpHub on RosettaRosetta The code name of the theme for the local WordPress sites (eg. bg.wordpress.org is a “Rosetta” site). All locale specific WordPress sites are referred to as “Rosetta sites.” The name was inspired from the ancient Rosetta Stone, which contained more or less the same text in three different languages. sites. Once HelpHub was launched for translations, localeLocale Locale = language version, often a combination of a language code and a region code, for instance es_MX denotes Spanish as it’s used in Mexico. A list of all locales supported by WordPress in https://make.wordpress.org/polyglots/teams/ teams actively translating support documentation tracked it via the HelpHub Migration sheet.

One of the challenges of translating HelpHub articles via Rosetta sites was, and is, communicating updates. This is why many teams also used a Google spreadsheet to track which documents existed, which were being translated, and which were completed.

Earlier this year, the Docs and MetaMeta Meta 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. teams launched a redesign of WordPress.org/Support.

With HelpHub’s redesign also comes a reclassification of user and developer documentation. The Docs team is interested in collaborating with Polyglots to better understand how teams currently handle HelpHub and DevHub translation, and sharing information on how to help test these changes in the future.

To start, the Docs team is working with three locale teams – Spanish (#es_ES), Japanese (#ja), and Serbian (#sr_RS). After this initial feedback, they’ll share more updates on the Docs team blog for how other locale teams can get involved.

Sharing some information on your team’s current progress, tools, and process will help the Docs team better understand how to approach testing for other localesLocale Locale = language version, often a combination of a language code and a region code, for instance es_MX denotes Spanish as it’s used in Mexico. A list of all locales supported by WordPress in https://make.wordpress.org/polyglots/teams/. With all that in mind, could the teams who are translating or have translated HelpHub share the following?

• Are you still actively translating HelpHub docs?
• If so, how do you coordinate translations?
• What tools do you use for translating? For example, translate in the site editorSite Editor Site Editors aka Rosetta site Editors are the users who have access to a specific Rosetta site associated with a locale. Site Editors can add General Translation Editors and appoint per project translation editors.Site Editors also have a complimentary role of a General Translation Editors even though they don't necessarily handle translations for the locale.Site Editors can create content on Rosetta sites - write blog posts, create showcase items and manage menu items. or use Google docs for feedback.
• What tools does your locale team use to track larger projects like this? For example, Google sheets or 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/ issues.

I’m adding tags for the teams that I know are translating or have translated HelpHub. If you know of any other teams that I may be missing, please let me know!

• #ja
• #fr_FR
• #es_MX
• #ru_RU
• #es_ES
• #pt_BR
• #es_VE
• #zh_CN
• #pt_AO
• #sr_RS
• #it_IT
• #nl_NL
• #ko_KR
• #es_AR
• #gl_ES
• #vi
• #bn_BD

Props to @estelaris for reviewing and sharing feedback on this post 🎉

+make.wordpress.org/docs/