Internationalisation readiness audit of one user flow
This is a team plan, best installed into a shared workspace so everyone with a role in it can see and own their tasks. Before a single string goes to a translator, the code has to be able to hold another language: strings outside the source code, no sentences glued together from fragments, dates and numbers formatted by locale, and layouts that survive longer words.
First tasks
- Pick one user flow that touches the most screens and emails
- Screenshot every screen, email and error message in that flow
- Tag each hard-coded string, concatenation and fixed date or number format
- Ask an engineer to size each issue as small, medium or large