docs: rewrite Contributing Translations for the AI pipeline (drop GlotPress)#220
docs: rewrite Contributing Translations for the AI pipeline (drop GlotPress)#220kilbot wants to merge 1 commit into
Conversation
The Contributing Translations page still documented translate.wordpress.org (GlotPress) for plugin strings and "edit en.json in wcpos/monorepo" for the app — both retired. WCPOS has moved entirely to an AI-driven pipeline. - Drop GlotPress / PTE / WordPress polyglots Slack guidance; add a short note explaining the move (slow, dated, no machine translation allowed). - Collapse the old "four places" model into the two repos that now exist: wcpos/translations (apps + plugin, JS + PHP) and wcpos/docs (these docs). - Document the real pipeline: auto-extracted source, AI translation into every locale, daily completeness check, human-review PR before release. - Give accurate contributor paths: translations/js/<locale>/<project>/ <namespace>.json and translations/php/<locale>/*.po (+ the four JS projects). - Fix the locale list (add nl/Dutch; 10 -> 11 docs locales) and clarify the underscore (apps) vs hyphen (docs) locale-code conventions. - Refresh translator tips to mirror the AI rule set; trim help links. The 11 translated copies under i18n/ are regenerated by the docs translation pipeline and are intentionally left untouched here. Validated with `docusaurus build --locale en` (exit 0; onBrokenLinks=throw did not trip).
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository: wcpos/coderabbit/.coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThis PR updates the translations documentation to describe the current AI-assisted translation workflow, redirects contributors to the correct repositories ( ChangesTranslation Documentation Update
Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
What
Rewrites the Contributing Translations support page (
versioned_docs/version-1.x/support/translations.mdx) to match how WCPOS is actually translated today.The page was flagged as containing bad information: it still told contributors to translate plugin strings on translate.wordpress.org (GlotPress) and to edit
en.jsoninwcpos/monorepofor the app. Both flows are retired. WCPOS has moved entirely to an AI-driven pipeline, and contributions now go to just two repos.Why it was wrong
wcpos/monorepo,wcpos/woocommerce-pos+-pro,wcpos/docs) no longer reflects reality. App + plugin source strings are now extracted into the centralwcpos/translationsrepo and translated by AI.nlhas since been added → 11 docs locales).What the page says now
wcpos/translations(apps + plugin, JS + PHP) andwcpos/docs(these docs).translations/js/<locale>/<project>/<namespace>.jsonandtranslations/php/<locale>/*.po(with the four JS projects:monorepo,electron,woocommerce-pos,woocommerce-pos-pro), plus asource/"don't edit" warning.nl) and a clear underscore (apps) vs hyphen (docs) note.Sourced from the internal translation-pipeline runbook and the
wcpos/translationsrepo structure.Translations of this page
The 11 translated copies under
i18n/<locale>/.../support/translations.mdxare intentionally left untouched — the docs translation pipeline regenerates them from this English source.Validation
docusaurus build --locale en→ exit 0,[SUCCESS] Generated static files.onBrokenLinks: 'throw'did not trip, so the internal link and in-page anchors all resolve.Icon "grid"/"sparkles", avscode-languageserver-typeswebpack note) are pre-existing and originate on other pages.Summary by CodeRabbit