Every documentation surface now serves in Korean: prefix any page with /ko and docs, drops, updates, and use-case articles read in Korean, with navigation and cross-links staying in the language you chose.
How it works.
The same content model drives both languages — Korean is a first-class rendering of each page, not a separate site. Search engines see both through hreflang alternates, and pages without a translation fall back to English rather than breaking.