The PO-File Editor was built to replace a fragmented, technical workflow for managing translations. Previously, localization relied on manually editing .po files—creating friction between development teams, content owners, and translators.
As the product designer, I designed a structured, table-based editor that made translations transparent, editable, and context-aware. Special cases like plural forms, comments, and contextual labels were integrated into the UI without overwhelming users.
Designed a structured, table-based interface for managing multilingual PO files
Accounted for linguistic edge cases such as plural forms and contextual dependencies
Introduced tooltips, context labels, and helper elements to support accurate translation
Developed a role-based permission system for internal teams and external translators
Created interactive Figma prototypes including conditional UI logic
Refined the UX through internal feedback and developer collaboration
The main challenge was translating complex localization logic—such as plural forms, contextual dependencies, and role-based permissions—into a user interface that remained accessible and intuitive for both technical and non-technical users.
It required balancing clarity with precision, modeling abstract linguistic structures into tangible UI patterns, and embedding contextual help without adding cognitive overload.
The editor became the new standard for managing PO content—improving quality, reducing overhead, and enabling non-technical contributors to work more independently.
