internationalizing websites

Engineering Community

Skill notes

When to use this Skill

Adding new language versions to existing website Setting up i18n (internationalization) for new website Configuring SEO for multiple languages User mentions: "add language", "translation", "localization", "hreflang", "multi-language"

Supported Languages

Common target markets: 🇺🇸 English (en) - Global market 🇯🇵 Japanese (ja) - Asian market 🇨🇳 Chinese (zh) - Chinese market Extended support available for:

Internationalization Workflow

Copy this checklist and track your progress:

Step 1: Prepare base language files

Ensure English (en.json) files exist as templates: Required directories: i18n/messages/en.json - Main translations i18n/pages/landing/en.json - Landing page translations Verify structure:

Step 2: Add new language files

Run the language addition script: What this script does: Copies en.json to all target language files Updates i18n/locale.ts with new locales Updates i18n/request.ts with language mappings

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Engineering
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@tomevault-io · no license declared
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
macOS · Linux · Windows
Runtime requirements
Node.js
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
External requests
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 1: Prepare base language files

Ensure English (`en.json`) files exist as templates: Required directories: `i18n/messages/en.json` - Main translations `i18n/pages/landing/en.json` - Landing page translations Verify structure:

02
Step 2: Add new language files

Run the language addition script: What this script does: Copies `en.json` to all target language files Updates `i18n/locale.ts` with new locales Updates `i18n/request.ts` with language mappings

03
Step 3: Verify configuration updates

Check `i18n/locale.ts`: Check `i18n/request.ts`: Language code mappings configured `zh-CN` → `zh`, `zh-HK` → `zh-hk` mappings present Check `public/sitemap.xml`:

04
Step 4: Add translations

Option A: Using AI translation (faster but needs review): Configure translations in the script's `translations` object. Option B: Manual translation (recommended for quality): Edit each language file with proper translations: Translation best practices:

05
Step 5: Configure SEO elements

hreflang tags - Automatic via sitemap, but verify: See reference/hreflang-guide.md for complete guide. Localized meta tags - Translate in each language file: URL structure - Verify correct format: English: `https://example.com/` or `https://example.com/en/`

06
Step 6: Validate and test

Build the project: CRITICAL: Fix any errors before proceeding. Manual testing: Language switcher: Visit each language version

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.