Collaborative translation infrastructure?

[OriolAbril]

It might be helpful to integrate with some service for collaborative translations like crowdin or transifex, or to avoid that and recommend translating locally and submitting PRs with the translations (like #13 did). I don't have much experience with this, so any feedback is extremely welcome.

It would also be useful to add some CI/pre-commit checks. For example, to ensure if a file is renamed, the corresponding .po files with its translations are renamed too. Or to run gettext and sphinx-intl if new files are added.

[kamila-NF]

Currently, we don't have that type of skills in NF, so collaboration with external organizations would be great.

[sanchalitorpe-source]

I suggest we adopt a GitHub-first translation workflow as the default recommendation:

• Translations live in the repo (.po / .mo)
• Contributors translate locally and submit PRs
• CI enforces consistency (file renames, missing msgids, etc.)
• No mandatory dependency on external platforms initially

This keeps the barrier low, avoids new infra/admin overhead, and fits NF’s current capacity.

We can explicitly note that projects with higher translation volume may later integrate Weblate/Transifex, but that should not be a prerequisite for getting started.