Hacktoberfest 2026:維護者為十月標記出來的 issue,仍然開放、適合新手。 瀏覽 Hacktoberfest issue

[ko] Translate /docs/limitations into Korean

未關閉 適合新手
#871 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 11 天內回覆

還沒有人認領這個 Issue。

評估

難度
2/5
預估耗時
1-3 小時
新手友好度
72/100
Issue 類型
文件
描述清晰度
描述清楚
活躍度
活躍
技術堆疊
markdown, react

研究方向

閱讀 apps/landing/src/app/(detail)/docs/limitations/page.mdx 中的英文原文和 apps/landing/src/app/ko/docs/overview/page.mdx 中的韓文範例,以及翻譯指南。新增 apps/landing/src/app/ko/docs/limitations/page.mdx,內容包含完整的韓文翻譯,以及更新後的標題、描述和 canonical。請先等待前置 issue #881 合併。完成標準是翻譯後的頁面能夠建置並顯示於 /ko/docs/limitations,同時英文副本保持不變。

由索引模型根據 Issue 內容生成。

描述

documentation good first issue help wanted
Goal

Provide the Korean version of /docs/limitations at /ko/docs/limitations. This issue covers only this page.

English source
Files to add or update
  • apps/landing/src/app/(detail)/docs/limitations/page.ko.mdx
  • apps/landing/src/i18n/pages.ts
Work

Copy the English page.mdx to page.ko.mdx in the same directory and translate it. Preserve imports and JSX structure. Update the metadata title/description, canonical to /ko/docs/limitations and language alternatives for the English and Korean URLs. Register /docs/limitations in apps/landing/src/i18n/pages.ts with a lazy import of the translated page. Follow the existing /docs/overview entry. Reuse the English layout directly; no Korean directory or layout wrapper is needed. Use the existing docs layout in the map entry.

Getting started

This is intended for a first-time contributor. Comment to claim this page before starting, and send one focused PR. Questions are welcome.

Prerequisite: #881. Wait for that infrastructure to merge before submitting the translation. Context: #584.

Read the translation guide and use the Korean overview at apps/landing/src/app/(detail)/docs/overview/page.ko.mdx as an example. English stays at the original URL; untranslated /ko URLs automatically redirect to their English page.

Acceptance checklist
  • Translate the complete assigned scope into natural Korean, including headings, prose, table descriptions and metadata.
  • Keep API/package names, code behavior, numeric data, external links and benchmark caveats unchanged. Explanatory code comments may be translated.
  • Preserve MDX imports and JSX structure. Fix relative imports when moving files; prefer @/ imports.
  • Keep internal links root-relative (for example /docs/installation); locale-aware navigation adds /ko automatically.
  • Verify both English and Korean URLs, mobile and desktop, links, tables and code blocks.
  • From the repository root run bun install and bun run build; from apps/landing run bun dev and bun run build. Run node script.js to refresh search data; translated pages are connected explicitly in src/i18n/pages.ts. Run the type, lint and i18n checks listed in the translation guide.
  • Register the translated page in src/i18n/pages.ts and verify that its /ko URL renders the translation instead of redirecting.
  • Keep the English copy unchanged. Do not translate other pages in this PR.
主要語言
Rust
星號
359
分支
31
平均合併
8 天 20 小時
30 天內合併 PR
92

環境準備

這個專案沒有提供開發容器、Dockerfile 或貢獻指南,環境需要你自己搭建:先看它的 README,通用步驟見我們的新手貢獻指南。

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

dev-five-git/devup-ui 的其他 Issue

查看 dev-five-git/devup-ui 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。