Text Localizer

Appearance

Team Collaboration ​

Learn how to effectively use Text Localizer in a team environment and establish good collaboration practices.

Team Setup ​

Project Standards ​

  • Use consistent frame naming across the team
  • Follow agreed-upon text layer naming conventions
  • Share the "Localized" collection structure
  • Document common UI element variables

Shared Practices ​

  • Always start with variable generation on first page/screen
  • Reuse existing variables from "Localized" collection
  • Document any new variables created
  • Maintain consistent text layer naming

Variable Management ​

Using Shared Variables ​

  • Check "Localized" collection before creating new variables
  • Reuse existing variables for common elements
  • Keep variable names consistent with team standards
  • Understand automatic numbering for duplicate layer names

TIP

Before creating new variables, check if similar text content already exists in the "Localized" collection.

Communication Flow ​

Within Design Team ​

  • Share updates to common variables
  • Communicate new variable additions
  • Document variable usage patterns
  • Regular sync-ups on localization progress

Cross-team Collaboration ​

  • Share CSV exports with stakeholders when needed
  • Keep content team informed of text structure
  • Document text layer organization
  • Maintain clear communication about variable usage

Best Practices ​

File Organization ​

  • Keep master file with original variables
  • Use clear file naming for different language versions
  • Maintain organized frame structure
  • Document file dependencies

Version Control ​

  • Track major changes to variables
  • Document variable updates
  • Keep team informed of significant changes
  • Maintain changelog if needed

Training New Team Members ​

  • Share documentation on plugin usage
  • Explain variable naming conventions
  • Guide through first-page-first strategy
  • Review common pitfalls and solutions

Common Challenges ​

Managing Multiple Languages ​

  • Keep consistent variable structure
  • Document language-specific requirements
  • Maintain clear version control
  • Use clear naming for language variations

Scaling Projects ​

  • Plan variable structure for growth
  • Document scalable naming conventions
  • Maintain organized component structure
  • Regular cleanup of unused variables

WARNING

Remember that duplicate layer names (often found in components) will be automatically numbered (e.g., Label, Label 2, Label 3). Make sure team members understand this behavior.

Next Steps ​