pimcore-studio-ui-i18n

Standardize i18n workflows for Pimcore Studio UI with flat translation keys.

13|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/pimcore/skills --skill pimcore-studio-ui-i18n
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pimcore-studio-ui-i18n
Source: https://github.com/pimcore/skills/tree/main/skills/pimcore-studio-ui-i18n
Command: npx skills add https://github.com/pimcore/skills --skill pimcore-studio-ui-i18n

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standardizes internationalization in Pimcore Studio UI by providing a clear i18n workflow, preventing hardcoded text and ensuring consistent translation usage across components and bundles.

Core Features & Use Cases

  • useTranslation hook for accessing translations in UI components
  • Translation key structure and flat dot notation conventions
  • Translation file locations, formats, and English-first workflow
  • Interpolation and pluralization support with real-world examples
  • Practical patterns for forms, navigation, and error messaging

Quick Start

Install the translation hook in your components and start replacing hardcoded strings with t('translation.key') calls to render localized text.

Frequently Asked Questions about pimcore-studio-ui-i18n

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I replace hardcoded strings with React translations in Pimcore Studio UI?

To replace hardcoded strings with React translations in Pimcore Studio UI, install the useTranslation hook in your components and call t('translation.key') to render localized text dynamically.

What is the correct translation key structure for Pimcore Studio UI components?

The correct translation key structure for Pimcore Studio UI components uses flat dot notation conventions. This standardized format ensures consistent translation usage across UI components, forms, navigation, and error messages.

Does Pimcore Studio UI i18n support interpolation and pluralization for error messages?

Pimcore Studio UI i18n supports both interpolation and pluralization for error messages. These patterns are applied across bundles to handle dynamic text rendering and variable counts in localized outputs.

How do I manage translation file locations and English base keys in a React localization workflow?

Managing translation file locations and English base keys in a React localization workflow requires following an English-first workflow. Standardized file locations and formats ensure translation consistency across all bundles.

Why do I need a standardized i18n workflow for React UI components?

You need a standardized i18n workflow for React UI components to prevent hardcoded text and resolve localization gaps. Establishing clear translation structure ensures consistent usage across the entire application.