Configuration for ERG content and translations
I designed a scalable CMS configuration that enabled admin. teams to manage ERG (Employee resource group) content and translations without engineering support. The solution reduced support tickets and improved the accuracy and consistency of localized ERG pages across Phenom’s enterprise clients.
Phenom’s global clients needed a way to manage ERG content in multiple languages without relying on developers. This project was part of a strategic effort to modernize Phenom's CMS and support scalable, multilingual employee experiences.
Problem Refinement
Analyzing System Gaps
After exploring the existing CMS admin section, I found a designated area for creating resource groups, but no way to see which locale each group belonged to or to associate additional locales to it. Translation management simply didn’t exist in the product. I chose to place the new configuration flow in a familiar area under “D&I Management” in the Diversity & Inclusion section, so admins could discover the feature where they already managed their ERG programs.
UX Scoping
Once understanding the gaps in the existing system, I partnered with PMs and developers to define the core capabilities admins would need in order to manage ERG content independently. These requirements formed the foundation of the new configuration model and guided the structure of the redesign and included:
Creating a resource group that is associated to a specific locale
Connecting multiple locales to the same resource group
Creating content for global site locale and mapping to content in other locales
Adding translations to a piece of content and linking that to its corresponding locale
UX Logic
Structured Creation Flow
To create a more structured flow, I made locale selection a required first step when creating a resource group. This ensures admins understand the group’s language context before entering any details. Parts of the interface remains disabled until a locale is chosen, guiding users through a clear, intentional setup process.
Simple Locale Management
A multi-select dropdown provided the simplest way to connect multiple locales to a resource group without adding complexity. The locales shown come from the tenant’s existing locale settings, ensuring admins can select from valid options.
Global to Local Content Mapping
To support multi locale publishing, the system needed a clear way to create primary content in the main locale and map it to its localized versions. By establishing a defined source to variant structure, admins could understand how updates flowed between locales and could manage content relationships more predictably.
Adding and Managing Translations
Adding translations requires both a source locale and a target locale to exist within the resource group. This ensures admins always know which version they’re translating from and where the translation will be applied.
Style Guide
The CMS UI was built using the design system I initiated and led. Leveraging existing components allowed me to move and deliver quickly in efforts to prevent escalation.
Final Design
Adding locales to resource group creation flow
Default Locale
Admins must select a default locale before entering any details. This anchors the group to its primary language and activates the remaining steps in the creation flow.
Progressive Disclosure
Once a locale is selected, adding group details and publishing become available. This reduces ambiguity and guides admins through a clear, structured process.
Global & Local Relationships
When the admin designates a group as global, an additional dropdown appears prompting them to select at least one local group to connect to it. This triggers the “Global” and “Translations” tabs, revealing only the options relevant to the chosen structure.
Translation creation and management
Enabling Translation Mode
The “+ Add New Translation” button is active only after the global group is created and all required fields are filled. This ensures admins set the correct structure before adding translated versions.
Selecting a Target Locale
Clicking “+ Add New Translation” opens a side module where admins choose which locale they want to translate. Only locales associated with the resource group appear in the list of options.
Creating a Translation
After selecting a target locale, clicking “Continue” opens the translation page. The target locale fields are editable so admins can enter localized content.
Managing saved translations
Any translation that is saved, or saved and published, appears under the 'Translations' tab, giving admins a clear snapshot of all localized versions in progress or completed.
