Nudj is built for multi-language out of the box. Every piece of content — challenges, rewards, achievements, posts, games, leaderboards, variables — supports translations.Documentation Index
Fetch the complete documentation index at: https://docs.nudj.cx/llms.txt
Use this file to discover all available pages before exploring further.
The translation editor
Community Settings -> Languages. The editor shows:- Every translation key in the community.
- The English source string.
- Per-locale translations.
- Multi-line support (#589) for long copy blocks.
- Root-level JSON edits (#2012) for advanced use cases.
Language switcher
The admin has an in-app language switcher (#746, #1053) — flip between locales to see how members in that language experience content. Posts studio has a dedicated sidebar language switcher (#2226) for in-flow translation during content creation.Content-language cookie + API x-language header
Nudj sets a content-language cookie (#1916) that controls the x-language header on every API request. This makes the backend language-aware without URL prefixes. Adjust the cookie from the content-language setting on the translations screen (#1043).
Multi-language variables
Question action variables (#1171) support translation — the prompt, options, and stored data can all be localised.Language key reference
A language key reference (#579) lists every key used in the community with its location. Helpful when you’re translating and want to see where a string appears.Adding a new language
Import defaults
New-language translations (#1163) ship with sensible platform defaults — so members see a usable app even before you translate every key.
Translate custom content
Per-challenge, per-reward, per-achievement translation. Language switch bugs across the admin were fixed in #845, #868, #2137, #2247.
Games support
Games ship with French and German defaults (#2011) built-in. Other languages use the standard translation flow.Troubleshooting
Switching language breaks the form
Switching language breaks the form
Older bug, fixed across #845, #868, #2137, #2247. Hard-refresh. If it persists, clear the Turbopack cache.
Members see English in a non-English community
Members see English in a non-English community
Check the content-language cookie (#1916, #1043). It should match the community default.

