PRIVATE CONTENT
Client:
Home Depot
Duration:
6 months
UX Research
UX Research
UX Research
IA
IA
IA
Buisness Architecture
Buisness Architecture
Buisness Architecture
Langauges Added
Langauges Added
Langauges Added
Langauges Added
Variables
Variables
Variables
Variables
Faster Updates
Faster Updates
Faster Updates
Faster Updates
Details
Details
Details
Details
Problem Statement:
Home Depot's Custom Order Configurator admin space, which handles the options and choices for custom-ordered products, faced a critical need to integrate multi-language functionality, specifically adding Canadian French. This integration had to be accomplished within a mixed environment of legacy and new design elements, while ensuring compliance with ADA (Americans with Disabilities Act) and AODA (Accessibility for Ontarians with Disabilities Act) standards. The primary challenge was to implement this functionality without causing significant downtime or disrupting the existing workflow.
Goal:
To integrate multi-language support, including Canadian French, into Home Depot's Custom Order Configurator admin space while ensuring compliance with ADA and AODA standards. The goal was to implement this functionality incrementally to minimize downtime and maintain operational continuity, ultimately enhancing the user experience for both internal administrators and external customers.
Target Audience:
Administrators and staff who manage custom orders through the configurator
Initital Interviews
Admin User
Compliance Officer
Type:
Admin User
Context:
Discussing the challenges of managing orders without multi-language support.
Role:
Admin managing custom orders in the configuratorr
Initital Interviews
Admin User
Compliance Officer
Type:
Admin User
Context:
Discussing the challenges of managing orders without multi-language support.
Role:
Admin managing custom orders in the configuratorr
Initital Interviews
Admin User
Compliance Officer
Type:
Admin User
Context:
Discussing the challenges of managing orders without multi-language support.
Role:
Admin managing custom orders in the configuratorr
Initital Interviews
Admin User
Compliance Officer
Type:
Admin User
Context:
Discussing the challenges of managing orders without multi-language support.
Role:
Admin managing custom orders in the configuratorr
Key Takeaways
Key Takeaways
Key Takeaways
Key Takeaways
Interview Requirments
The interviews highlighted the critical need for integrating Canadian French into the Custom Order Configurator admin space, driven by both operational efficiency and compliance with ADA and AODA standards. Admin users struggled with the lack of built-in language support, which complicated order management and increased the risk of errors.
Focus on importance of meeting accessibility standards
Importance of a strategic, user-centered approach to integrating multilingual support, ensuring both compliance and minimal disruption.
Compliance officers and the need for a phased implementation to avoid downtime.
User Flows
Internal User / Admin
The user-flow was designed with the complicated process of the data input department. They would need to add a language to the site in question and then will be able to edit the additional languages added.
User Flows
Internal User / Admin
The user-flow was designed with the complicated process of the data input department. They would need to add a language to the site in question and then will be able to edit the additional languages added.
User Flows
Internal User / Admin
The user-flow was designed with the complicated process of the data input department. They would need to add a language to the site in question and then will be able to edit the additional languages added.
User Flows
Internal User / Admin
The user-flow was designed with the complicated process of the data input department. They would need to add a language to the site in question and then will be able to edit the additional languages added.
Language Management UI – Custom Order Configurator (Admin Tool) Wireframe
This screen is part of the Custom Order Configurator Admin Interface built for Blinds.ca and used across platforms like Home Depot Canada. The tool enables internal teams to manage multilingual product configurations and streamline product publishing workflows.
🎯 Purpose
The goal of this interface is to allow administrators to:
Add and manage localized language variants for complex, configurable products
Control how product details appear in different markets (e.g., English US, French Canadian)
Make updates to product configurations without disrupting the live product data
💡 Key Features
Language selector dropdown for adding or modifying content in alternate languages
Editable product fields for name, dimensions, and other configurable options
Mode toggles like Live, Clone Product, Create Draft, and Preview to support staging and testing workflows
Save & Apply functionality scoped per language for granular control
This screen ensures a clean separation between language-specific edits and core product data, supporting a scalable workflow across different regional sites.
🛠️ Design Considerations
Designed to be ADA- and AODA-compliant for internal and vendor use
Built to support multi-vendor data entry while preserving consistent naming conventions and configurations
Integrated with backend systems via SKUs and production logic fields (e.g., OMS ID, production time)
🗣️ Feedback
✅ “Now we can make French updates without risking the English copy — huge time saver.”
✅ “Being able to create a draft without pushing to live is super helpful.”
🛠️ “Let’s explore grouping product data fields by type (e.g., visual, dimensions, metadata).”
Language Management UI – Custom Order Configurator (Admin Tool) Wireframe
This screen is part of the Custom Order Configurator Admin Interface built for Blinds.ca and used across platforms like Home Depot Canada. The tool enables internal teams to manage multilingual product configurations and streamline product publishing workflows.
🎯 Purpose
The goal of this interface is to allow administrators to:
Add and manage localized language variants for complex, configurable products
Control how product details appear in different markets (e.g., English US, French Canadian)
Make updates to product configurations without disrupting the live product data
💡 Key Features
Language selector dropdown for adding or modifying content in alternate languages
Editable product fields for name, dimensions, and other configurable options
Mode toggles like Live, Clone Product, Create Draft, and Preview to support staging and testing workflows
Save & Apply functionality scoped per language for granular control
This screen ensures a clean separation between language-specific edits and core product data, supporting a scalable workflow across different regional sites.
🛠️ Design Considerations
Designed to be ADA- and AODA-compliant for internal and vendor use
Built to support multi-vendor data entry while preserving consistent naming conventions and configurations
Integrated with backend systems via SKUs and production logic fields (e.g., OMS ID, production time)
🗣️ Feedback
✅ “Now we can make French updates without risking the English copy — huge time saver.”
✅ “Being able to create a draft without pushing to live is super helpful.”
🛠️ “Let’s explore grouping product data fields by type (e.g., visual, dimensions, metadata).”
Language Management UI – Custom Order Configurator (Admin Tool) Wireframe
This screen is part of the Custom Order Configurator Admin Interface built for Blinds.ca and used across platforms like Home Depot Canada. The tool enables internal teams to manage multilingual product configurations and streamline product publishing workflows.
🎯 Purpose
The goal of this interface is to allow administrators to:
Add and manage localized language variants for complex, configurable products
Control how product details appear in different markets (e.g., English US, French Canadian)
Make updates to product configurations without disrupting the live product data
💡 Key Features
Language selector dropdown for adding or modifying content in alternate languages
Editable product fields for name, dimensions, and other configurable options
Mode toggles like Live, Clone Product, Create Draft, and Preview to support staging and testing workflows
Save & Apply functionality scoped per language for granular control
This screen ensures a clean separation between language-specific edits and core product data, supporting a scalable workflow across different regional sites.
🛠️ Design Considerations
Designed to be ADA- and AODA-compliant for internal and vendor use
Built to support multi-vendor data entry while preserving consistent naming conventions and configurations
Integrated with backend systems via SKUs and production logic fields (e.g., OMS ID, production time)
🗣️ Feedback
✅ “Now we can make French updates without risking the English copy — huge time saver.”
✅ “Being able to create a draft without pushing to live is super helpful.”
🛠️ “Let’s explore grouping product data fields by type (e.g., visual, dimensions, metadata).”
Language Management UI – Custom Order Configurator (Admin Tool) Wireframe
This screen is part of the Custom Order Configurator Admin Interface built for Blinds.ca and used across platforms like Home Depot Canada. The tool enables internal teams to manage multilingual product configurations and streamline product publishing workflows.
🎯 Purpose
The goal of this interface is to allow administrators to:
Add and manage localized language variants for complex, configurable products
Control how product details appear in different markets (e.g., English US, French Canadian)
Make updates to product configurations without disrupting the live product data
💡 Key Features
Language selector dropdown for adding or modifying content in alternate languages
Editable product fields for name, dimensions, and other configurable options
Mode toggles like Live, Clone Product, Create Draft, and Preview to support staging and testing workflows
Save & Apply functionality scoped per language for granular control
This screen ensures a clean separation between language-specific edits and core product data, supporting a scalable workflow across different regional sites.
🛠️ Design Considerations
Designed to be ADA- and AODA-compliant for internal and vendor use
Built to support multi-vendor data entry while preserving consistent naming conventions and configurations
Integrated with backend systems via SKUs and production logic fields (e.g., OMS ID, production time)
🗣️ Feedback
✅ “Now we can make French updates without risking the English copy — huge time saver.”
✅ “Being able to create a draft without pushing to live is super helpful.”
🛠️ “Let’s explore grouping product data fields by type (e.g., visual, dimensions, metadata).”
Site Language Settings – Multi-Site Admin Panel
This modal is part of the Site Configuration Settings used to manage individual brand portals under a unified e-commerce umbrella (e.g., Home Depot, Blinds.ca, Blinds.com, etc.). It enables administrators to define the active languages per site, ensuring multilingual support for customers across North America.
🎯 Purpose
To support regional and international expansion by giving each site the ability to:
Assign one or more supported languages
Ensure consistent translation workflows across all content
Reduce translation errors by initializing new languages as clones of English content
💡 Design Features
Editable site name field
Checkbox list of available languages with language code identifiers (e.g., EN_US, FR_CA, SP_MX)
Clear default indicator (EN_US is marked as default)
Confirmation behavior: Once a language is enabled, it cannot be removed to preserve translation consistency across systems
This was a UX recommendation I made to improve global readiness while reducing the risk of broken content from partial language removal or mismatched translations.
🛠️ Strategic Benefits
Simplifies onboarding for vendors translating content
Reduces time-to-launch for non-English sites by starting with a mirrored English copy
Centralizes language visibility across all brands in one interface
🗣️ Feedback
✅ “Really smart to prevent deletion — it avoids so many downstream issues with broken content.”
✅ “The language codes help our dev team connect this to the right CMS flags.”
🛠️ “Eventually we’d love to define default currency or units per language too.”
Site Language Settings – Multi-Site Admin Panel
This modal is part of the Site Configuration Settings used to manage individual brand portals under a unified e-commerce umbrella (e.g., Home Depot, Blinds.ca, Blinds.com, etc.). It enables administrators to define the active languages per site, ensuring multilingual support for customers across North America.
🎯 Purpose
To support regional and international expansion by giving each site the ability to:
Assign one or more supported languages
Ensure consistent translation workflows across all content
Reduce translation errors by initializing new languages as clones of English content
💡 Design Features
Editable site name field
Checkbox list of available languages with language code identifiers (e.g., EN_US, FR_CA, SP_MX)
Clear default indicator (EN_US is marked as default)
Confirmation behavior: Once a language is enabled, it cannot be removed to preserve translation consistency across systems
This was a UX recommendation I made to improve global readiness while reducing the risk of broken content from partial language removal or mismatched translations.
🛠️ Strategic Benefits
Simplifies onboarding for vendors translating content
Reduces time-to-launch for non-English sites by starting with a mirrored English copy
Centralizes language visibility across all brands in one interface
🗣️ Feedback
✅ “Really smart to prevent deletion — it avoids so many downstream issues with broken content.”
✅ “The language codes help our dev team connect this to the right CMS flags.”
🛠️ “Eventually we’d love to define default currency or units per language too.”
Site Language Settings – Multi-Site Admin Panel
This modal is part of the Site Configuration Settings used to manage individual brand portals under a unified e-commerce umbrella (e.g., Home Depot, Blinds.ca, Blinds.com, etc.). It enables administrators to define the active languages per site, ensuring multilingual support for customers across North America.
🎯 Purpose
To support regional and international expansion by giving each site the ability to:
Assign one or more supported languages
Ensure consistent translation workflows across all content
Reduce translation errors by initializing new languages as clones of English content
💡 Design Features
Editable site name field
Checkbox list of available languages with language code identifiers (e.g., EN_US, FR_CA, SP_MX)
Clear default indicator (EN_US is marked as default)
Confirmation behavior: Once a language is enabled, it cannot be removed to preserve translation consistency across systems
This was a UX recommendation I made to improve global readiness while reducing the risk of broken content from partial language removal or mismatched translations.
🛠️ Strategic Benefits
Simplifies onboarding for vendors translating content
Reduces time-to-launch for non-English sites by starting with a mirrored English copy
Centralizes language visibility across all brands in one interface
🗣️ Feedback
✅ “Really smart to prevent deletion — it avoids so many downstream issues with broken content.”
✅ “The language codes help our dev team connect this to the right CMS flags.”
🛠️ “Eventually we’d love to define default currency or units per language too.”
Site Language Settings – Multi-Site Admin Panel
This modal is part of the Site Configuration Settings used to manage individual brand portals under a unified e-commerce umbrella (e.g., Home Depot, Blinds.ca, Blinds.com, etc.). It enables administrators to define the active languages per site, ensuring multilingual support for customers across North America.
🎯 Purpose
To support regional and international expansion by giving each site the ability to:
Assign one or more supported languages
Ensure consistent translation workflows across all content
Reduce translation errors by initializing new languages as clones of English content
💡 Design Features
Editable site name field
Checkbox list of available languages with language code identifiers (e.g., EN_US, FR_CA, SP_MX)
Clear default indicator (EN_US is marked as default)
Confirmation behavior: Once a language is enabled, it cannot be removed to preserve translation consistency across systems
This was a UX recommendation I made to improve global readiness while reducing the risk of broken content from partial language removal or mismatched translations.
🛠️ Strategic Benefits
Simplifies onboarding for vendors translating content
Reduces time-to-launch for non-English sites by starting with a mirrored English copy
Centralizes language visibility across all brands in one interface
🗣️ Feedback
✅ “Really smart to prevent deletion — it avoids so many downstream issues with broken content.”
✅ “The language codes help our dev team connect this to the right CMS flags.”
🛠️ “Eventually we’d love to define default currency or units per language too.”
Legacy Admin Enhancement – Language Field Integration
This page is part of the Custom Order Configurator admin space for Blinds.ca, also used by retail partners like The Home Depot. The interface allows internal users to configure core product attributes — including availability, SKUs, pricing, and now, language-specific settings.
🎯 Project Goal
Introduce a way for admins to add and manage language codes (e.g., EN_US, FR_CA) so translated versions of product data could be safely handled across regional sites — without breaking existing workflows or systems tied to legacy infrastructure.
⚠️ Design Constraints
Due to the age and complexity of the admin panel, there was:
No existing design system or documentation for this space
Inconsistent UI patterns across pages and no component library
Limited dev flexibility due to tight coupling with production logic
💡 My Approach
To address these challenges while keeping momentum:
I used annotated screenshots and detailed UX notes to communicate layout tweaks and field placements
Recommended subtle UI additions that blended with existing styles to avoid breaking the UI
Partnered closely with developers to explain logic and behavior, since formal prototypes were not feasible in every case
This specific update shows the new language selector dropdown and code field, which ties directly into how products are configured and published to multilingual sites.
🗣️ Feedback
✅ “Great job working around the limitations — this fits in well with the existing UI.”
✅ “Now we can start prepping French and Spanish content without creating a separate product.”
🛠️ “Would be helpful to eventually define content per tab per language too.”
Legacy Admin Enhancement – Language Field Integration
This page is part of the Custom Order Configurator admin space for Blinds.ca, also used by retail partners like The Home Depot. The interface allows internal users to configure core product attributes — including availability, SKUs, pricing, and now, language-specific settings.
🎯 Project Goal
Introduce a way for admins to add and manage language codes (e.g., EN_US, FR_CA) so translated versions of product data could be safely handled across regional sites — without breaking existing workflows or systems tied to legacy infrastructure.
⚠️ Design Constraints
Due to the age and complexity of the admin panel, there was:
No existing design system or documentation for this space
Inconsistent UI patterns across pages and no component library
Limited dev flexibility due to tight coupling with production logic
💡 My Approach
To address these challenges while keeping momentum:
I used annotated screenshots and detailed UX notes to communicate layout tweaks and field placements
Recommended subtle UI additions that blended with existing styles to avoid breaking the UI
Partnered closely with developers to explain logic and behavior, since formal prototypes were not feasible in every case
This specific update shows the new language selector dropdown and code field, which ties directly into how products are configured and published to multilingual sites.
🗣️ Feedback
✅ “Great job working around the limitations — this fits in well with the existing UI.”
✅ “Now we can start prepping French and Spanish content without creating a separate product.”
🛠️ “Would be helpful to eventually define content per tab per language too.”
Legacy Admin Enhancement – Language Field Integration
This page is part of the Custom Order Configurator admin space for Blinds.ca, also used by retail partners like The Home Depot. The interface allows internal users to configure core product attributes — including availability, SKUs, pricing, and now, language-specific settings.
🎯 Project Goal
Introduce a way for admins to add and manage language codes (e.g., EN_US, FR_CA) so translated versions of product data could be safely handled across regional sites — without breaking existing workflows or systems tied to legacy infrastructure.
⚠️ Design Constraints
Due to the age and complexity of the admin panel, there was:
No existing design system or documentation for this space
Inconsistent UI patterns across pages and no component library
Limited dev flexibility due to tight coupling with production logic
💡 My Approach
To address these challenges while keeping momentum:
I used annotated screenshots and detailed UX notes to communicate layout tweaks and field placements
Recommended subtle UI additions that blended with existing styles to avoid breaking the UI
Partnered closely with developers to explain logic and behavior, since formal prototypes were not feasible in every case
This specific update shows the new language selector dropdown and code field, which ties directly into how products are configured and published to multilingual sites.
🗣️ Feedback
✅ “Great job working around the limitations — this fits in well with the existing UI.”
✅ “Now we can start prepping French and Spanish content without creating a separate product.”
🛠️ “Would be helpful to eventually define content per tab per language too.”
Legacy Admin Enhancement – Language Field Integration
This page is part of the Custom Order Configurator admin space for Blinds.ca, also used by retail partners like The Home Depot. The interface allows internal users to configure core product attributes — including availability, SKUs, pricing, and now, language-specific settings.
🎯 Project Goal
Introduce a way for admins to add and manage language codes (e.g., EN_US, FR_CA) so translated versions of product data could be safely handled across regional sites — without breaking existing workflows or systems tied to legacy infrastructure.
⚠️ Design Constraints
Due to the age and complexity of the admin panel, there was:
No existing design system or documentation for this space
Inconsistent UI patterns across pages and no component library
Limited dev flexibility due to tight coupling with production logic
💡 My Approach
To address these challenges while keeping momentum:
I used annotated screenshots and detailed UX notes to communicate layout tweaks and field placements
Recommended subtle UI additions that blended with existing styles to avoid breaking the UI
Partnered closely with developers to explain logic and behavior, since formal prototypes were not feasible in every case
This specific update shows the new language selector dropdown and code field, which ties directly into how products are configured and published to multilingual sites.
🗣️ Feedback
✅ “Great job working around the limitations — this fits in well with the existing UI.”
✅ “Now we can start prepping French and Spanish content without creating a separate product.”
🛠️ “Would be helpful to eventually define content per tab per language too.”
Promo Management – Multilingual Field Validation and Information Architecture (IA) Audit
This screen is part of the legacy promo creation tool used across multiple brand portals. The primary challenge was integrating multilingual support into a system that was not originally designed for it, while preserving existing backend logic and workflows.
🎯 Goal
Ensure all promo content (such as discount text, eligibility, and display info) could be:
Translated per language
Properly routed through the backend
Displayed conditionally on the correct product page(s) and localized sites
⚙️ My Role
Introduced the yellow alert banner at the top: a lightweight but critical addition to warn users that all language fields must be completed to ensure visibility across French/Spanish/English markets.
Collaborated with engineering to identify and map every touchpoint where language data needed to flow—especially for frontend preview, site-level validation, and site publishing.
Worked on the IA to ensure the correct data structures were in place and that translations would fall back to English safely where missing (without breaking site logic).
💡 Design & Technical Constraints
The promo tool was built years ago, with no modern component structure or validation logic for multiple locales.
I had to use inline UI enhancements and clear system feedback while maintaining the visual language of the legacy UI.
All updates were delivered via annotated screenshots, process flows, and dev collaboration—no full UI redesign was feasible due to system complexity and time.
🗣️ Feedback
✅ “That warning really helped prevent missing translations.”
✅ “We’re finally seeing promos render correctly across all languages.”
🛠️ “Let’s eventually build a system that allows promo entry per language tab instead of inline.”
Promo Management – Multilingual Field Validation and Information Architecture (IA) Audit
This screen is part of the legacy promo creation tool used across multiple brand portals. The primary challenge was integrating multilingual support into a system that was not originally designed for it, while preserving existing backend logic and workflows.
🎯 Goal
Ensure all promo content (such as discount text, eligibility, and display info) could be:
Translated per language
Properly routed through the backend
Displayed conditionally on the correct product page(s) and localized sites
⚙️ My Role
Introduced the yellow alert banner at the top: a lightweight but critical addition to warn users that all language fields must be completed to ensure visibility across French/Spanish/English markets.
Collaborated with engineering to identify and map every touchpoint where language data needed to flow—especially for frontend preview, site-level validation, and site publishing.
Worked on the IA to ensure the correct data structures were in place and that translations would fall back to English safely where missing (without breaking site logic).
💡 Design & Technical Constraints
The promo tool was built years ago, with no modern component structure or validation logic for multiple locales.
I had to use inline UI enhancements and clear system feedback while maintaining the visual language of the legacy UI.
All updates were delivered via annotated screenshots, process flows, and dev collaboration—no full UI redesign was feasible due to system complexity and time.
🗣️ Feedback
✅ “That warning really helped prevent missing translations.”
✅ “We’re finally seeing promos render correctly across all languages.”
🛠️ “Let’s eventually build a system that allows promo entry per language tab instead of inline.”
Promo Management – Multilingual Field Validation and Information Architecture (IA) Audit
This screen is part of the legacy promo creation tool used across multiple brand portals. The primary challenge was integrating multilingual support into a system that was not originally designed for it, while preserving existing backend logic and workflows.
🎯 Goal
Ensure all promo content (such as discount text, eligibility, and display info) could be:
Translated per language
Properly routed through the backend
Displayed conditionally on the correct product page(s) and localized sites
⚙️ My Role
Introduced the yellow alert banner at the top: a lightweight but critical addition to warn users that all language fields must be completed to ensure visibility across French/Spanish/English markets.
Collaborated with engineering to identify and map every touchpoint where language data needed to flow—especially for frontend preview, site-level validation, and site publishing.
Worked on the IA to ensure the correct data structures were in place and that translations would fall back to English safely where missing (without breaking site logic).
💡 Design & Technical Constraints
The promo tool was built years ago, with no modern component structure or validation logic for multiple locales.
I had to use inline UI enhancements and clear system feedback while maintaining the visual language of the legacy UI.
All updates were delivered via annotated screenshots, process flows, and dev collaboration—no full UI redesign was feasible due to system complexity and time.
🗣️ Feedback
✅ “That warning really helped prevent missing translations.”
✅ “We’re finally seeing promos render correctly across all languages.”
🛠️ “Let’s eventually build a system that allows promo entry per language tab instead of inline.”
Promo Management – Multilingual Field Validation and Information Architecture (IA) Audit
This screen is part of the legacy promo creation tool used across multiple brand portals. The primary challenge was integrating multilingual support into a system that was not originally designed for it, while preserving existing backend logic and workflows.
🎯 Goal
Ensure all promo content (such as discount text, eligibility, and display info) could be:
Translated per language
Properly routed through the backend
Displayed conditionally on the correct product page(s) and localized sites
⚙️ My Role
Introduced the yellow alert banner at the top: a lightweight but critical addition to warn users that all language fields must be completed to ensure visibility across French/Spanish/English markets.
Collaborated with engineering to identify and map every touchpoint where language data needed to flow—especially for frontend preview, site-level validation, and site publishing.
Worked on the IA to ensure the correct data structures were in place and that translations would fall back to English safely where missing (without breaking site logic).
💡 Design & Technical Constraints
The promo tool was built years ago, with no modern component structure or validation logic for multiple locales.
I had to use inline UI enhancements and clear system feedback while maintaining the visual language of the legacy UI.
All updates were delivered via annotated screenshots, process flows, and dev collaboration—no full UI redesign was feasible due to system complexity and time.
🗣️ Feedback
✅ “That warning really helped prevent missing translations.”
✅ “We’re finally seeing promos render correctly across all languages.”
🛠️ “Let’s eventually build a system that allows promo entry per language tab instead of inline.”
Options & Choices Translation System – Reusable Data Structure for Multilingual Consistency
This interface is part of the Options & Choices management screen within the custom order configurator for Blinds.ca and affiliated brands. The screen supports bulk creation, editing, and translation of selectable product values like fabrics, colors, sizes, and finishes.
🎯 Objective
Create a centralized source of truth for product options that:
Supports reusability across multiple questions or product configurations
Enables language translations at the option level, so they don’t need to be translated repeatedly when reused
Maintains data consistency across the system while reducing translator workload
⚙️ How It Works
Options like “White_2005” or “Toffee_2298” can be linked to multiple questions or product templates (e.g., Question 1: “Choose a color” and Question 2: “Select your trim finish”).
Once an option is translated into French or Spanish, the system reuses that translation automatically wherever the option appears again.
This structure ensures both translation efficiency and visual/semantic consistency across the user experience.
💡 Design & UX Considerations
Language selector with code display (e.g., EN_US) to view and manage translations
Bulk actions like “Import Options,” “Create Option,” “Reorder/Upload,” and “Create Dependent Option” to support admin workflows at scale
Inline controls for editing status, default setting, visibility, and translations for each value
🛠️ My Contributions
Designed the IA strategy to decouple options from individual questions
Proposed the translation logic: store translations once per option and call them wherever needed
Worked with dev and translation stakeholders to ensure technical feasibility and system-wide integration
🗣️ Feedback
✅ “Massive time saver for our translation vendors — they only have to do it once.”
✅ “This reduces human error from inconsistent naming across templates.”
🛠️ “Eventually we’d love a translation status tag next to each option to know what’s missing.”
Options & Choices Translation System – Reusable Data Structure for Multilingual Consistency
This interface is part of the Options & Choices management screen within the custom order configurator for Blinds.ca and affiliated brands. The screen supports bulk creation, editing, and translation of selectable product values like fabrics, colors, sizes, and finishes.
🎯 Objective
Create a centralized source of truth for product options that:
Supports reusability across multiple questions or product configurations
Enables language translations at the option level, so they don’t need to be translated repeatedly when reused
Maintains data consistency across the system while reducing translator workload
⚙️ How It Works
Options like “White_2005” or “Toffee_2298” can be linked to multiple questions or product templates (e.g., Question 1: “Choose a color” and Question 2: “Select your trim finish”).
Once an option is translated into French or Spanish, the system reuses that translation automatically wherever the option appears again.
This structure ensures both translation efficiency and visual/semantic consistency across the user experience.
💡 Design & UX Considerations
Language selector with code display (e.g., EN_US) to view and manage translations
Bulk actions like “Import Options,” “Create Option,” “Reorder/Upload,” and “Create Dependent Option” to support admin workflows at scale
Inline controls for editing status, default setting, visibility, and translations for each value
🛠️ My Contributions
Designed the IA strategy to decouple options from individual questions
Proposed the translation logic: store translations once per option and call them wherever needed
Worked with dev and translation stakeholders to ensure technical feasibility and system-wide integration
🗣️ Feedback
✅ “Massive time saver for our translation vendors — they only have to do it once.”
✅ “This reduces human error from inconsistent naming across templates.”
🛠️ “Eventually we’d love a translation status tag next to each option to know what’s missing.”
Options & Choices Translation System – Reusable Data Structure for Multilingual Consistency
This interface is part of the Options & Choices management screen within the custom order configurator for Blinds.ca and affiliated brands. The screen supports bulk creation, editing, and translation of selectable product values like fabrics, colors, sizes, and finishes.
🎯 Objective
Create a centralized source of truth for product options that:
Supports reusability across multiple questions or product configurations
Enables language translations at the option level, so they don’t need to be translated repeatedly when reused
Maintains data consistency across the system while reducing translator workload
⚙️ How It Works
Options like “White_2005” or “Toffee_2298” can be linked to multiple questions or product templates (e.g., Question 1: “Choose a color” and Question 2: “Select your trim finish”).
Once an option is translated into French or Spanish, the system reuses that translation automatically wherever the option appears again.
This structure ensures both translation efficiency and visual/semantic consistency across the user experience.
💡 Design & UX Considerations
Language selector with code display (e.g., EN_US) to view and manage translations
Bulk actions like “Import Options,” “Create Option,” “Reorder/Upload,” and “Create Dependent Option” to support admin workflows at scale
Inline controls for editing status, default setting, visibility, and translations for each value
🛠️ My Contributions
Designed the IA strategy to decouple options from individual questions
Proposed the translation logic: store translations once per option and call them wherever needed
Worked with dev and translation stakeholders to ensure technical feasibility and system-wide integration
🗣️ Feedback
✅ “Massive time saver for our translation vendors — they only have to do it once.”
✅ “This reduces human error from inconsistent naming across templates.”
🛠️ “Eventually we’d love a translation status tag next to each option to know what’s missing.”
Options & Choices Translation System – Reusable Data Structure for Multilingual Consistency
This interface is part of the Options & Choices management screen within the custom order configurator for Blinds.ca and affiliated brands. The screen supports bulk creation, editing, and translation of selectable product values like fabrics, colors, sizes, and finishes.
🎯 Objective
Create a centralized source of truth for product options that:
Supports reusability across multiple questions or product configurations
Enables language translations at the option level, so they don’t need to be translated repeatedly when reused
Maintains data consistency across the system while reducing translator workload
⚙️ How It Works
Options like “White_2005” or “Toffee_2298” can be linked to multiple questions or product templates (e.g., Question 1: “Choose a color” and Question 2: “Select your trim finish”).
Once an option is translated into French or Spanish, the system reuses that translation automatically wherever the option appears again.
This structure ensures both translation efficiency and visual/semantic consistency across the user experience.
💡 Design & UX Considerations
Language selector with code display (e.g., EN_US) to view and manage translations
Bulk actions like “Import Options,” “Create Option,” “Reorder/Upload,” and “Create Dependent Option” to support admin workflows at scale
Inline controls for editing status, default setting, visibility, and translations for each value
🛠️ My Contributions
Designed the IA strategy to decouple options from individual questions
Proposed the translation logic: store translations once per option and call them wherever needed
Worked with dev and translation stakeholders to ensure technical feasibility and system-wide integration
🗣️ Feedback
✅ “Massive time saver for our translation vendors — they only have to do it once.”
✅ “This reduces human error from inconsistent naming across templates.”
🛠️ “Eventually we’d love a translation status tag next to each option to know what’s missing.”
Other Projects
Other Projects
Other Projects
Other Projects
© 2025. All rights Reserved.
© 2025. All rights Reserved.
© 2025. All rights Reserved.
© 2025. All rights Reserved.