Shopify i18n Basics

A documentação do plugin está em preparação.

4|1|Updated Nov 23, 2025
One-click install
npx skills add https://github.com/sarojpunde/shopify-dev-toolkit-claude-plugins --skill shopify-i18n-basics
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Shopify i18n Basics
Source: https://github.com/sarojpunde/shopify-dev-toolkit-claude-plugins/tree/main/shopify-theme-development/skills/shopify-i18n-basics
Command: npx skills add https://github.com/sarojpunde/shopify-dev-toolkit-claude-plugins --skill shopify-i18n-basics

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill introduces internationalization (i18n) fundamentals for Shopify themes, outlining locale file structure, translation keys, and Liquid usage to support multiple languages.

Core Features & Use Cases

  • Locale File Structure: Organization of locales/en/fr/de files and their schema translations.
  • Translation Usage: How to reference translations in Liquid and handle variables, HTML, and pluralization.
  • Practical Examples: Typical keys for navigation, product, cart, and forms.

Quick Start

Scaffold locale files for English and French, then render translations in templates using the t filter.

Frequently Asked Questions about Shopify i18n Basics

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

FAQPage Schema
How do I set up localization for a Shopify theme with multiple languages?

Localization for Shopify themes requires organizing JSON translation files in a locales/ directory with language-specific files (en.default.json, fr.json, de.json) and corresponding schema files for Theme Editor. Structure keys consistently across all language files, nest related translations together, and use the Liquid t filter to render translated content in templates.

What's the difference between content translations and schema translations in Shopify?

Content translations live in language JSON files (en.default.json, fr.json) and handle customer-facing UI text rendered via the t filter. Schema translations use separate schema JSON files (en.default.schema.json, fr.schema.json) and define labels, descriptions, and options visible in the Theme Editor for merchants configuring the theme.

How do I use the Liquid t filter to display translated text in Shopify templates?

The t filter retrieves translation strings from locale files and renders them in Liquid templates. Reference translation keys with dot notation (t 'namespace.key'), pass variables for interpolation, and use t filter modifiers for HTML-safe output. The filter automatically selects the correct language file based on the current locale.

Can I use variables and dynamic text within Shopify translations?

Yes, Shopify translations support variable interpolation and dynamic content through the t filter with parameter passing. Store template strings in JSON with placeholder syntax, then pass variable values to the t filter in Liquid, allowing the same translation key to render different content based on runtime data like product names or customer names.

What are the key naming conventions I should follow for translation files?

Use consistent, hierarchical key naming across all language files to maintain structure and prevent mismatches. Organize keys by feature or section (e.g., 'navigation.home', 'cart.empty', 'forms.email'), use lowercase with dots for nesting, and ensure every key exists in all language files to avoid missing translations or errors.

Does Shopify handle translation pluralization and conditional text?

Shopify's t filter supports pluralization through JSON structure and variable logic in Liquid. Define plural forms in translation files, pass count variables to the t filter, and use Liquid conditionals to render appropriate translation keys based on quantity, ensuring grammatically correct output across languages with different plural rules.