Figure out best way to manage docs localization #2

New issue

Open

opened 2026-04-22 13:18:32 +00:00 by nathan · 1 comment

nathan commented

2026-04-22 13:18:32 +00:00

Owner

the "docs" on the site are just a big pile of markdown documents. do we just have translators work directly on the various locale path copies that are located in the project at:

www/i18n/es/docusaurus-plugin-content-docs/
www/i18n/ru/docusaurus-plugin-content-docs/

and so on...

or is there some other tool that can work for tracking changes from the base "en" docs and enable more friendly localization / translation like weblate does? weblate doesn't seem suited for mass documentation localization imho.

the "docs" on the site are just a big pile of markdown documents. do we just have translators work directly on the various locale path copies that are located in the project at: www/i18n/es/docusaurus-plugin-content-docs/ www/i18n/ru/docusaurus-plugin-content-docs/ and so on... or is there some other tool that can work for tracking changes from the base "en" docs and enable more friendly localization / translation like weblate does? weblate doesn't seem suited for mass documentation localization imho.

acute was assigned by irl

2026-04-24 11:15:51 +00:00

chris was assigned by irl

2026-04-24 11:15:54 +00:00

acute was unassigned by irl

2026-04-24 11:16:00 +00:00

nathan was assigned by irl

2026-04-30 12:21:55 +00:00

chris was unassigned by irl

2026-04-30 12:21:55 +00:00

irl commented

2026-04-30 12:22:31 +00:00

Owner

@nathan please review and see if you have any improvements to suggest, we can probably consolidate more of those JSON files with some custom tooling to integrate through po4a but not without development effort

irl added the

question

label

2026-04-30 12:22:43 +00:00