Make translated content publishable on Learn WordPress: language connection and review

Description

Discussed in the Office Hours on August 22, 2026 #3640. Translated lessons do not reach learners today for two reasons: they cannot be found through the language switcher, and finished translations sit unpublished for want of a review. The two belong together, because they block the same path.

Work steps, language connection

• Document the conflict between the language detection plugin and Polylang in a reproducible way, with a short recording as evidence
• Describe and assess the connector that has been found, including the maintenance effort it implies
• Clarify with the Polylang team whether the functionality can be adopted into the plugin
• Evaluate the alternatives: our own connector as a plugin, or a change to the language detection plugin
• Reach a decision and record it in the handbook

Work steps, review

• Write down the four-eyes principle for translations and link it from the handbook
• Name at least one reviewer per language, starting with Urdu and Bengali
• Reach out to the local communities and the Polyglots teams
• Check which style guides are insufficient and document the gaps
• Record how machine-generated translations are handled

Context

Polylang has been under test for about two months. A connector between the two systems exists, but it lives in code. In parallel, a fully translated course in Urdu is waiting for a reviewer; the Urdu style guide contains roughly 27 entries. Without a solution on both sides, completed work stays invisible, which directly affects the motivation of the people doing the translations.