...
All relevant material to be available in Crowdin as necessary. If the feature is very big, please prioritize sub-features, pages or components as necessary
...
Added / modified steps | Owner / driver | Supported by | |
1 | Review & finalize content for new feature | DL | PL, FSL |
2 | Finalize scope and timelines | PL | TL, DL, FSL |
3 | Make content available on Crowdin – screenshot, guidance documents, etc | FSA | FSL |
4 | Ensure all “translation” tagged tickets from Jira have been listed and shared with FS team | QA | FSL |
5 | Share timelines with translators (except German, Malayalam) | FSL | FSA |
56 | Periodical check-ins with translators (except German, Malayalam) | FSA | FSL |
67 | Share timelines with translators (German, Malayalam) | Research coordinator | FSA, FSL |
78 | Periodical check-ins with translators (except German, Malayalam) | Research coordinator | FSA, FSL |
89 | Language testing for content – coordinate with translators | FSA, FSL | QA, research coordinator |
...
This will have a need for versioning per language and it means that all features may not be available in all languages at a point of time. A later release can be planned with a next feature release.
Alternative option 2: Release the language with the feature available in English. Even if some of the phrases or words in the feature are translated, we release it in English. “Translation in progress” label can be shown against an incomplete feature without blocking the release.
Alternative option 3 (least preferable): Push release back to allow time for translations to reach 100%
Please add more suggestions if you have.