HelpHub Localisation Plan

Hi! This is Jon from docs team. This post outlines our plan for localising HelpHub for Rosetta sites. HelpHub is currently live on English wordpress.org site and can be accessed from https://wordpress.org/support/ (e.g. https://wordpress.org/support/category/getting-started/ ).

We’d like Polyglots team’s input to make this translation as smoothly as possible.

Background

At  WordCamp Europe (Summit) we discussed the localisation of WordPress systems such as DevHub and HelpHub.

We recognised that GlotPress was not great for long-form translation and we evaluated the possibility of actually re-engineering GlotPress (or at least translate.wordpress.org) to work for it. But this is a huge undertaking and it may involve formalisation of the whole of WordPress.org’s translation.

So it was indicated it might be best for HelpHub to look at translation out of GlotPress.

Therefore HelpHub was designed as a stand-alone plugin that could be activated at numerous places such as Rosetta sites.

Plan Phases (Proposal)

Phase 1

Goals

  • Test HelpHub localisation on one locale’s Rosetta site.
  • Migrate existing English content, but update notification/diff will not be available yet.

Candidate Locales

  • Japanese, since they maintain their own Codex site with a large number of docs
  • French (France), since they want to set up a fr_FR Documentation team (~10 volunteers for the moment)

Process

  1. Activate HelpHub plugin on Rosetta [Meta]
    1. Need Meta help as Rosetta sites are likely on a different network
  2. Migrate English content over (without activating HelpHub’s home interface) [Locale Team]
    1. Explore automated process (but unlikely due to WordPress.org infra)
    2. At this phase, this may need to be a manual process
    3. If manual process, adapt and refine tracking system of migration designed by Docs Team
  3. Translation by locale team based on English contents [Locale Team]
  4. Possibly re-take related screenshots in locale language [Locale Team]
    1. Create a list of needed screenshots so other locale’s volunteers can contribute as needed
  5. Development work to link English and localised content [Meta]
  6. Define a syndication plan to track updates of the English version and trigger notifications to localisation team [Meta] [Docs]
  7. Activate HelpHub’s home interface on the Rosetta (just this test locale) on /support [Meta]
  8. Adjust the documentation links on the Rosetta site from Codex to HelpHub [Locale Team]
  9. “Push” forums link back to /support/forums [Meta]
  10. Redirect locale’s version of Codex or support materials to locale HelpHub (e.g. https://www.mediawiki.org/wiki/Help:Redirects) [Locale Team]
  11. Establish communication channel between English HelpHub and locale teams [Docs] [Locale Team]
  12. Write a blog post on the locale news page to announce the move of user support resources [Locale Team]
  13. Do a retrospective and identify pain points [Docs] [Locale Team]
  14. Refine Phase 1 Plan for other locales based on first candidate [Docs]

Phase 2

Goal

Roll out the localisation to more Rosetta sites.

Process

  1. Enable HelpHub plugin on active Rosetta site (individual sign up) [Meta]
    1. What happens to teams without active volunteers? Maybe we’ll show English docs on their site
    2. Explore the possibility of showing machine-translated content
  2. Allow main WordPress.org to reveal that there are other locales’ HelpHubs/Support [Meta]
  3. (To be determined)

+make.wordpress.org/docs

#documentation, #helphub, #rosetta

PTE request for “WP User Manager”

Dear polyglots,

I am working on translations for “WP User Manager” and it’s extensions:

  • https://wordpress.org/plugins/wp-user-manager/
  • https://wordpress.org/plugins/wpum-personal-data/
  • https://wordpress.org/plugins/wpum-delete-account/
  • https://wordpress.org/plugins/wpum-recaptcha/
  • https://wordpress.org/plugins/wpum-username-length/

Please add me as PTE to languages below:

In the past I translated my own plugin “Randomize” (https://wordpress.org/plugins/randomize/). I am also a member on german WordPress Slack, if there are any questions related to my request.

Thank you,
Sebastian

#editor-requests

Hello Polyglots, I have suggested…

Hello Polyglots, I have suggested strings for WordPress Core in Bhojpuri and would like to become a PTE, can you please add me:

Name: 5.1.x – Development
URL: https://translate.wordpress.org/locale/bho/default/wp/dev

If you have any questions, just comment here. Thank you!

#editor-requests
Ping: @pratikkry

PTE Request for Woo-One-Product-Per-Category

Hello Polyglots, I am the plugin author for the plugin

Woo-One-Product-Per-Category – https://wordpress.org/plugins/woo-one-product-per-category

I’d like to become PTE and approve cz_cs translations for my plugin. Please add me as a translation editor:

Thank you

Greetings

#editor-requests

PTE Request

Hi, Polyglots. We’re the authors of Rife Free theme: https://wordpress.org/themes/rife-free/ and Apollo13 Framework Extension plugin: https://wordpress.org/plugins/apollo13-framework-extensions/

Please add @atachibana as translation editor for these two projects.

Thank you!
With kind regards
Daniel

#editor-requests

Hi Polyglots,

@rogierlankhorst and I are author/contributors of Complianz GDPR Cookie Consent. We like to add @badrien as a PTE for the French Translation. Strings are added and waiting to be approved. He’s active in the French Slack currently.

Thank you. Regards Aert

#editor-requests

PTE Request for WP-HR Manager, TreePress, BookPress

Hello Polyglots, I am the plugin author for the following:

WP-HR Manager https://wordpress.org/plugins/wp-hr-manager/
TreePress https://wordpress.org/plugins/treepress/
Book-Press https://wordpress.org/plugins/book-press/

I have a new translation editor that we’d like to be able to approve translation for our plugins. Please add the following WordPress.org users as a translation editor for their respective locales:

The translator has submitted examples of their work for the plugin named above.

Thanks
=====
NB I also have the following requests outstanding:

All translators have submitted examples of their work for at least one of the plugins named above.

Thanks in advance for your assistance.

Paul

#editor-requests

PTE Request for TreePress

Hello Polyglots, I am the plugin author for the following:

TreePress https://wordpress.org/plugins/treepress/

I have a new translation editor that we’d like to be able to approve translation for our plugins. Please add the following WordPress.org users as a translation editor for their respective locales:

The translator has submitted examples of their work for the plugin named above.

Thanks in advance for your assistance.

Paul

#editor-requests

We have another translation editor…

We have another translation editor here at Yoast that we’d like to be able to approve German translations for our plugins:

— https://wordpress.org/plugins/wordpress-seo/ Yoast SEO
— https://wordpress.org/plugins/acf-content-analysis-for-yoast-seo/ ACF Content Analysis for Yoast SEO
— https://wordpress.org/plugins/yoast-seo-search-index-purge/ Yoast SEO: Search Index Purge
— https://wordpress.org/plugins/yoast-comment-hacks/ Yoast Comment Hacks
— https://wordpress.org/plugins/glue-for-yoast-seo-amp/ Glue for Yoast SEO & AMP
— https://wordpress.org/plugins/clicky/ Clicky by Yoast

Please add the following WordPress.org users as translation editor for German:

If you have any questions, just comment here. Thank you!
#editor-requests

PTE Request for Duplicate Post By Enrico Battocchi

Hello Polyglots, I have suggested strings for this Duplicate Post and would like to become a PTE, can you please add me:

Plugin Name: Duplicate Post
URL: https://wordpress.org/plugins/duplicate-post/

If you have any questions, just comment here. Thank you!

#editor-requests

WordPress Translation Day 4 Meeting Notes (March 19, 2019)

Attendance: @nao, @zetaraffix, @xkon, @ugyen, @ronakganatra, @bhargavmehta, @tobifjellner, @pedromendonca, @fitehal, @kartiks16, @jordicuevas, @rohit

This was the seventh weekly meeting for WordPress Translation Day 4 (Saturday, May 11, 2019). Here’s the meeting archive link.

The site is live!

Team Updates

New team members: @kartiks16 and @tokyobiyori on Outreach Team and @vrajshah705 on Communication Team (as a social media wrangler)

Design

Outreach

  • With help from @vedanshu of Community Team, gathered meetup chapter and country data
    • At GWTD3, 23 Chapters from GWTD2 did not host a meetup. 71 could be 90+
    • Out of 99 Countries, Only 42 Have Participated in Translation Day
    • Currently, there are 715 Meetup Chapters across 99 Countries. Many new chapters were initiated this year. Let’s Welcome them to Polyglots
  • The team worked on dividing up the chapters to reach out. They can use more help if anyone wants to volunteer
  • Outreach status sheet is being prepared
  • @nao and others finished up blog post draft

Website/Admin

  • @xkon + team launched https://wptranslationday.org on Sunday
  • @audrasjb is handling the event map
  • @nemanja will be handling the blog section
  • Block editor is set to default
  • There still are some more design tweaks to be done; please don’t publish posts/pages without checking first
  • The team won’t be using Trello for internal task tracking

Livestreming

Notes on Trello Task Management

  • @webcommsat updated the labels to mark status
  • @nao shared tasks that need volunteers or help with scoping (currently in the area of blog post & documentation writing only)
  • Teams are encouraged to create task cards that need volunteer(s), and set the label to green

Reminders for Organizing Team

  • Please file all docs/assets for the event under our Google Drive folder.
  • If you need to access the event’s Trello board & website dashboard, please message @nao or @webcommsat (Slack ID: @abhanonstopnewsuk) on Slack
  • Always refer to the event date as “May 11” not 11/5 or 5/11 to avoid confusion.
  • The official event title is “WordPress Translation Day 4” (“Global” is removed) and social media hashtag is #WPTranslationDay (no trailing “4”)

Awesome team work, everyone! See you next week: Tuesday, March 26, 2019, 1:00 PM GMT in #polyglots-events

#gwtd, #gwtd4

Agenda: Weekly Polyglots Chat – March 20, 2019

Here’s the agenda for the chats this week. If you have anything you’d like to add, please leave a comment.

  • Weekly locale stats
  • Translation Day
  • HelpHub i18n meeting Doodle: https://doodle.com/poll/ak5rpyrivywz5a9x
  • Open floor

Chat time:

Wednesday, March 20, 2019, 6:00 AM GMT in #polyglots

See you there!

#weekly-meeting-agenda, #weekly-meetings

Hello Polyglots, I am the…

I’m a native Spanish speaker and I’d like to be able to approve my translations for these plugins of mine:

  • https://wordpress.org/plugins/wp-whatsapp-chat/ WhatsApp Chat
  • https://wordpress.org/plugins/quadmenu/ QuadMenu

Please add me as translation editor:

#editor-requests

PTE Request for picu

Hello Polyglots, I am the plugin author of picu. Please add the following WordPress.org user as translation editor:

Thank you!

#editor-requests

Hello Polyglots,

We have a translation editor here at Yoast that we’d like to be able to approve German translations for our plugins:

— https://wordpress.org/plugins/wordpress-seo/ Yoast SEO
— https://wordpress.org/plugins/acf-content-analysis-for-yoast-seo/ ACF Content Analysis for Yoast SEO
— https://wordpress.org/plugins/yoast-seo-search-index-purge/ Yoast SEO: Search Index Purge
— https://wordpress.org/plugins/yoast-comment-hacks/ Yoast Comment Hacks
— https://wordpress.org/plugins/glue-for-yoast-seo-amp/ Glue for Yoast SEO & AMP
— https://wordpress.org/plugins/clicky/ Clicky by Yoast

Please add the following WordPress.org users as translation editor for German:

If you have any questions, just comment here. Thank you!
#editor-requests

PTE Request for Email Subscribers & Newsletters

Hello Polyglots, I am the plugin author for Email Subscribers & Newsletters. Please add the following WordPress.org user as translation editor for German

— de_de @docolli

If you have any questions, just comment here. Thank you!
#editor-requests