skills.rest
Nivl
NivlCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

i18n-translation

Configure next-intl locale routing and translate messages and blog content in Next.js apps.

1|Updated Sep 8, 2010
Search Tags:#localization#i18n#translations#next-intl#locale-management#blog-translation
One-click install
npx skills add https://github.com/Nivl/melvin.la --skill i18n-translation-nivl
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: i18n-translation
Source: https://github.com/Nivl/melvin.la/tree/main/.agents/skills/i18n-translation
Command: npx skills add https://github.com/Nivl/melvin.la --skill i18n-translation-nivl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Developers need to reach global audiences by localizing a Next.js app, keeping UI strings, routing, and content synchronized across languages. This skill provides a structured workflow to add languages, translate messages, and translate blog content while preserving placeholders and formatting.

Core Features & Use Cases

  • Locale management: define supported locales and add new ones in a single consistent workflow.
  • Translation orchestration: manage translations in messages/[locale].json and translate blog content under bundled_static/content/blog for each locale.
  • Blog content translation: update MDX frontmatter and body with translations while preserving structure and links.
  • Use case: when a user requests a new language, update locale definitions, generate locale-specific message files, translate UI text and blog content, and update the language switcher indicators.

Quick Start

Add a new locale by updating the locale definitions, duplicating en.json into the new locale, translating all strings and blog MDX, and adjusting routing and fonts as needed.

Frequently Asked Questions about i18n-translation

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

FAQPage Schema
How do I add a new language to my Next.js app?▼

Adding a new language involves updating locale definitions, duplicating your base messages file, translating UI strings and blog MDX content, and updating the language switcher. This structured workflow ensures routing and content stay synchronized across all locales.

How do I translate Next.js blog content without breaking MDX frontmatter?▼

Translating Next.js blog content safely requires updating the MDX body text while preserving the original frontmatter structure, formatting, and links. This ensures localized blog posts maintain consistent metadata and rendering behavior across different languages.

What is the best way to manage next-intl locale routing and message files?▼

Managing next-intl locales effectively requires maintaining structured messages/[locale].json files and enforcing consistent locale definitions. This approach operationalizes UI translations and routing configuration across your Next.js application for global audiences.

Does next-intl support translating both UI strings and bundled blog content?▼

Yes, next-intl supports translating both UI strings and bundled blog content. You can manage UI text in messages files and translate blog MDX content under bundled_static/content/blog while preserving placeholders and formatting across all locales.

How do I update the language switcher when adding a new locale?▼

Updating the language switcher requires adjusting its indicators to reflect the newly added locale definitions. This step is necessary during the translation workflow to ensure users can navigate between all available languages seamlessly.

Related Skills

Explore More Software Engineering Skills→
yutnayutna
2

nextjs-i18n

Implement Next.js internationalization with next-intl and centralized locale messages.

Community
Intermediate
fusenginefusengine
22

nextjs-i18n

Implement locale-based routing and type-safe messages in Next.js 16 applications.

Community
Intermediate
David-MeloDavid-Melo

blog_writer_agent

Generate SEO-optimized MDX blog posts with frontmatter from briefs.

Community
Intermediate
SufficientDaikonSufficientDaikon
8

i18n-strategy

Design internationalization systems with namespace-driven translations and type-safe keys.

Community
Advanced