book-translation

To translate MDX content into a new language, you copy an existing base locale directory like src/content/book/{locale}/ and adapt the prose while preserving the structural syntax. This ensures the localized interactive book content renders correctly in the target language.

Localizing UI strings and JSON metadata involves translating the key values in messages/{locale}.json. You adjust chapter titles and descriptions in the book metadata to match the target locale, ensuring the interface displays correctly for non-English readers.

To register a new locale, you add the target locale configuration to src/components/book/elements/locales/{locale}.ts and update the index.ts file. This integrates the translated MDX chapters and JSON strings into the active project structure.

Yes, you can use an existing language base like Turkish to start your MDX translation workflow. Copying the Turkish base provides a structured starting point, allowing you to translate the prose and JSON keys into the target language efficiently.

Translated MDX chapters break when structural syntax or import references are accidentally modified during prose translation. Quality assurance requires verifying that all imports and structural references remain intact while adapting the text for the target locale.

To localize The Interactive Book of Prompting, you need to translate the MDX chapter content and UI JSON strings, then register the locale in the configuration files. This workflow makes the educational content accessible to non-English learners.