[wp-meta] [Making WordPress.org] #8035: Bug Report and Improvement Suggestions for Learn WordPress Localization Strings and Link Behavior

[Making WordPress.org]

#8035: Bug Report and Improvement Suggestions for Learn WordPress Localization
Strings and Link Behavior
-------------------------------------------+--------------------
 Reporter:  kimjiwoon                      |      Owner:  (none)
     Type:  enhancement                    |     Status:  new
 Priority:  normal                         |  Milestone:
Component:  International Sites (Rosetta)  |   Keywords:
-------------------------------------------+--------------------
 ### Title: Bug Report and Improvement Suggestions for Learn WordPress
 Localization Strings and Link Behavior

 #### Summary

 While reviewing the Korean localization status of `learn.wordpress.org`
 and `wordpress.org`, several issues were identified: inconsistent
 translation strings, link behaviors that appear to be bugs, and
 opportunities for significant user experience improvements.

 ### 1. Bug: Incorrect Polyglots Team Link in Rosetta Site Footer

 There is a bug in the global footer of Rosetta sites where the language
 name link does not direct users to the correct language team page.

 - **Observed Behavior:**
     - On the Korean Rosetta site (`ko.wordpress.org`), clicking the
 language name '한국어' in the footer leads to the general Polyglots team
 listing page (`https://make.wordpress.org/polyglots/teams/`) instead of
 the specific Korean team page.
 - **Expected Behavior:**
     - The link should direct users to the Korean translation team’s
 dedicated page
 (`https://make.wordpress.org/polyglots/teams/?locale=ko_KR`).
 - **Steps to Reproduce:**
     1. Visit `https://ko.wordpress.org`.
     2. Scroll to the bottom footer.
     3. In the language list next to the WordPress logo, click the '한국어'
 link.
     4. Check the resulting URL.
 - **Impact:**
     - This increases the difficulty for Korean users who wish to
 contribute to translations, as it makes finding their language team less
 intuitive.

 ### 2. Improvement Proposal: Multilingual UI Support on the Main
 `wordpress.org` Site

 It is proposed that the main `wordpress.org` site adopt the same localized
 UI (header/footer) functionality via the `?locale` parameter as already
 available on `learn.wordpress.org`.

 - **Background:**
     - Currently, Rosetta site footers (such as `ja.wordpress.org` or
 `ko.wordpress.org`) link to `learn.wordpress.org` with the appropriate
 `?locale` parameter, offering a localized UI.
     - This shows that `learn.wordpress.org` is capable of providing a
 multilingual UI via the `locale` parameter.
     - However, the main `wordpress.org` site does not offer this dynamic
 UI translation unless users visit a Rosetta site.
 - **Proposal:**
     - Enable the main `wordpress.org` site to recognize the `?locale`
 parameter and dynamically display core UI elements (global header/footer)
 in the selected language.
     - This would allow users to browse global information on
 `wordpress.org` in their preferred language interface, independent of the
 community-driven Rosetta sites.
 - **Expected Benefits:**
     - Improved accessibility for users worldwide.
     - Enhanced user experience by allowing separation of UI language and
 content language (which is mainly English).

 ### 3. Reference: Inconsistency in "Learn WordPress" String Management

 The key brand term "Learn WordPress" is distributed across multiple
 translation projects, making consistency difficult to maintain.

 - **Relevant String Locations:**
     1. **Learn WordPress Site Heading**
         - **Project:** Meta / Learn WordPress
         - **Source:** `wp-content/themes/pub/wporg-learn-2024/patterns
 /front-page-header.php:27`
         - **Link:**
 [translate.wordpress.org](https://translate.wordpress.org/projects/meta
 /learn-
 wordpress/ko/default/?filters%5Bstatus%5D=either&filters%5Boriginal_id%5D=11104852&filters%5Btranslation_id%5D=87771795)
     2. **WordPress.org Global Navigation**
         - **Project:** Meta / WordPress.org
         - **Source:** `mu-plugins/blocks/global-header-
 footer/blocks.php:497`
         - **Link:**
 [translate.wordpress.org](https://translate.wordpress.org/projects/meta
 /wordpress-
 org/ko/default/?filters%5Bstatus%5D=either&filters%5Boriginal_id%5D=14468969&filters%5Btranslation_id%5D=133382970)
     3. **Self-Hosted WordPress Admin Bar**
         - **Project:** WordPress / 6.8.x - Development
         - **Source:** `wp-includes/admin-bar.php:207`
         - **Link:**
 [translate.wordpress.org](https://translate.wordpress.org/projects/wp/dev/ko/default/?filters%5Bstatus%5D=either&filters%5Boriginal_id%5D=16513173&filters%5Btranslation_id%5D=133383507)
 - **Issue:**
     - The same term ("Learn WordPress") is managed separately across
 different projects, which can lead to inconsistent translations and harm
 the unified brand experience. Centralized management of key terminology
 strings should be considered.

 ---

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/8035>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org