What is the difference between core and plugin translations?

Core translations are for the main Payload framework (ui, payload, next), while plugin translations are namespaced under the specific plugin name to prevent conflicts.

Does this skill work for any project?

No, this skill is specifically designed for the Payload CMS repository and follows its internal directory structure and naming conventions for core and plugin packages.

What is required to run the translation generation?

You must have an OPENAI_KEY environment variable set, as the underlying scripts use OpenAI to translate English strings into other supported languages.

Can this skill help me set up a new plugin for localization?

Yes, if a plugin lacks a translations folder, the skill can scaffold the required folder structure, types, and generation scripts automatically.

Payload Translation Generator

Name: Payload Translation Generator
Author: payloadcms

bypayloadcms

•

39,933

•

Content Management

Automates the generation and scaffolding of internationalization strings for Payload CMS core packages and plugins.

This skill streamlines the localization workflow within the Payload CMS ecosystem by managing both core and plugin-specific translations. It provides a structured process for adding English source keys, configuring client-side availability, and executing automated translation scripts powered by OpenAI. Beyond simple string management, the skill can scaffold the entire translation infrastructure for new plugins, including directory structures, type definitions, and the necessary scripts to maintain a consistent i18n implementation across the codebase.

Key Features

01Tailored workflows for both Core Payload and individual Plugin translations

0239,933 GitHub stars

03Script-based automation for synchronizing English keys across all supported languages

04Automated multi-language string generation via OpenAI integration

05Automated scaffolding for new plugin i18n directory structures

06Client key management for browser-side translation exposure

Use Cases

01Synchronizing multi-language support across a plugin ecosystem when adding new English keys

02Adding localized labels for a new feature in the Payload core admin panel

03Initializing a comprehensive translation system for a newly developed Payload plugin

Key Features

01Tailored workflows for both Core Payload and individual Plugin translations

0239,933 GitHub stars

03Script-based automation for synchronizing English keys across all supported languages

04Automated multi-language string generation via OpenAI integration

05Automated scaffolding for new plugin i18n directory structures

06Client key management for browser-side translation exposure

Use Cases

01Synchronizing multi-language support across a plugin ecosystem when adding new English keys

02Adding localized labels for a new feature in the Payload core admin panel

03Initializing a comprehensive translation system for a newly developed Payload plugin