Skip to content

docs(ko): add Korean translation for getting-started pages - #993

Open
amondnet wants to merge 1 commit into
alibaba:mainfrom
amondnet:docs/ko-getting-started
Open

docs(ko): add Korean translation for getting-started pages#993
amondnet wants to merge 1 commit into
alibaba:mainfrom
amondnet:docs/ko-getting-started

Conversation

@amondnet

@amondnet amondnet commented Aug 18, 2026

Copy link
Copy Markdown
Contributor

Description

Korean translations for the three getting-started docs pages — quickstart, installation, configuration (654 lines of English source) — following the incremental batch pattern of the Russian docs (#696/#698/#701), as follow-up to the ko UI locale (#857).

  • docsMap's ko entry graduates from {} to a partial LocalizedDocs; the 13 untranslated pages keep falling back to English per-page.
  • Terminology reuses what ko.ts already ships (프로바이더, 내장, 대화형, 워크스페이스 모드), so docs and UI never disagree.
  • Code blocks, flags, config keys, URLs, and the provider table values are verbatim; only prose and bash comments are translated.
  • DOCS_LOCALES in check-translation-sync.js intentionally still excludes ko — sync warnings would be unactionable until the full set exists. It flips in the final batch.

Remaining pages will follow in two batches: the four integration guides, then the rest + the DOCS_LOCALES flip.

Korean quickstart page rendered with Korean sidebar and TOC

Type of Change

  • Bug fix (non-breaking change that fixes an issue)
  • New feature (non-breaking change that adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Refactoring (no functional changes)
  • Documentation update
  • CI / Build / Tooling

How Has This Been Tested?

  • make test passes locally
  • Manual testing (describe below)

typecheck / lint / test (32/32) / build / size (94.7 kB / 150 kB) and go run scripts/verify-english-only.go all pass. Rendering verified with headless Chrome under --accept-lang=ko-KR: the three pages serve Korean content with a Korean TOC, untranslated pages still fall back to English.

Checklist

  • My code follows the project's coding style (go fmt, go vet)
  • I have performed a self-review of my code
  • I have added tests that prove my fix is effective or my feature works
  • New and existing unit tests pass locally with my changes
  • I have updated the documentation accordingly (if applicable)
  • I have signed the CLA

Related Issues

Follow-up to #471 / #857.

@github-actions

github-actions Bot commented Aug 18, 2026

Copy link
Copy Markdown
Contributor

🔍 OpenCodeReview found 1 issue(s) in this PR.

  • ✅ Successfully posted inline: 1 comment(s)

Comment thread pages/src/content/docs/index.ts
Translates quickstart, installation, and configuration — the three pages
a new Korean-speaking user hits first — following the incremental locale
pattern the Russian docs used (alibaba#696). docsMap's ko entry graduates from
{} to a partial LocalizedDocs; the remaining pages keep falling back to
English per-page.

DOCS_LOCALES in check-translation-sync.js intentionally still excludes
ko: warnings on en-docs changes would be unactionable until the full set
is translated. It flips in the final batch.

Terminology matches the ko UI locale (alibaba#857): 프로바이더, 내장, 대화형,
워크스페이스 모드, and the staged/unstaged/untracked renderings all reuse
the strings ko.ts already ships.
@amondnet
amondnet force-pushed the docs/ko-getting-started branch from 5c78b84 to 2acc230 Compare August 18, 2026 11:02
@amondnet
amondnet marked this pull request as ready for review August 18, 2026 14:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant