Maintain both languages together
Treat English and Korean as equal published versions, not a primary page with an incomplete fallback.
Content ownership
Player guides live under client/docs/content/en and client/docs/content/ko with identical route names. Change both when a policy or behavior changes. Keep English in-game labels alongside Korean explanations when it helps readers recognize a control.
editorial-pages.json maps authored routes to their source references. Internal specifications own policy; code and release verification establish implementation. Do not promote draft JSON examples into a live catalog or a future mode into a released guide.
Generated references
error-catalog.json contains reviewed English and Korean code meanings. Run node client/docs/scripts/generate-error-pages.mjs after editing it. Code values are not translated. Keep the current code inventory and reproducible checks; historical archives are not part of the published guides.
Verification
pnpm --filter docs check
pnpm --filter docs buildThe checks cover language parity, source paths, local links, registered error coverage, generated page drift and legacy redirects. The build verifies MDX compilation and search indexing. Also inspect desktop and narrow layouts, keyboard focus, language switching on a nested page, and search in both languages.
Editorial style
Lead with what the player can do and why it is interesting. Give concrete steps and expected results. Explain constraints beside the action they affect. Keep technical storage details in developer pages. Label expanding experiences without turning every introduction into a disclaimer.