skills.rest
iwritec0de
iwritec0deCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

wordpress-i18n

Generate POT/PO/MO/JSON translation files for WordPress plugins and themes.

1|Updated Apr 19, 2026
Search Tags:#i18n#translations#l10n#gettext#wordpress#text-domain#pot-file
One-click install
npx skills add https://github.com/iwritec0de/wp-dev --skill wordpress-i18n
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wordpress-i18n
Source: https://github.com/iwritec0de/wp-dev/tree/main/skills/wordpress-i18n
Command: npx skills add https://github.com/iwritec0de/wp-dev --skill wordpress-i18n

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps developers internationalize and localize WordPress plugins and themes, enabling translations, proper text domains, and scalable localization workflows.

Core Features & Use Cases

  • Set up and load text domains in PHP and JavaScript.
  • Generate POT/PO/MO and JSON translation files for multilingual support.
  • Add translator comments to provide translators with context and placeholders.
  • Follow i18n best practices (no string concatenation, proper placeholders, and locale-aware formatting) across plugins and themes.
  • Support standard WordPress localization workflows, including WordPress.org compatibility and language packs.

Quick Start

Initialize i18n for a plugin or theme by defining a text domain, loading translations, and generating POT/PO/MO/JSON files.

Frequently Asked Questions about wordpress-i18n

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

FAQPage Schema
How do I make a WordPress plugin translatable with proper text domains?▼

To make a WordPress plugin translatable, define a distinct text domain, load it in PHP and JavaScript, and use non-concatenated strings with proper placeholders. This ensures translation files can be generated and loaded correctly.

How do I generate POT, PO, and MO translation files for WordPress themes?▼

Generating POT, PO, and MO translation files for WordPress themes involves extracting translatable strings into a POT file, translating them into PO files, and compiling them into MO files for runtime use.

What is the best way to add translator comments in WordPress internationalization workflows?▼

Adding translator comments in WordPress i18n workflows requires placing descriptive notes above gettext function calls to provide context and clarify placeholder usage for translators.

Can I use WordPress i18n workflows for both PHP and JavaScript translation pipelines?▼

Yes, WordPress i18n workflows support both PHP and JavaScript translation pipelines, including loading text domains and generating JSON translation files for multilingual support across plugins and themes.

Why does string concatenation break WordPress localization and how do I avoid it?▼

String concatenation breaks WordPress localization because it fragments translatable strings and disrupts word order in other languages. Avoid it by using complete sentences and proper gettext placeholders like %s.

Does WordPress.org compatibility require distinct text domains for plugin language packs?▼

Yes, WordPress.org compatibility and language pack generation require distinct text domains for each plugin to ensure translations are correctly scoped and loaded during runtime.

Related Skills

Explore More Software Engineering Skills→
gaupoitgaupoit
4

wordpress-development

Automates Docker-based WordPress setup, hardening, and verification workflows using WP-CLI and PHP 8.0+.

Community
Advanced
jnealey88jnealey88
12

i18n-update

Scan WordPress plugin source files and update POT, PO, and MO language files.

Community
Intermediate
jpoindexterjpoindexter
1

internationalization-and-localization

Guide web and app UI internationalization with CLDR locale data.

Community
Advanced
danilomartinellidanilomartinelli
1

i18n-localization

Detect hardcoded strings and manage translation files for software applications.

Community
Intermediate