[ko] Translate /docs/devup/typography into Korean
Maintainers usually reply within 11 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- markdown, react
- Domain
- internationalization
Research direction
Read the translation guide and compare the English source at apps/landing/src/app/(detail)/docs/devup/typography/page.mdx with the Korean overview at apps/landing/src/app/ko/docs/overview/page.mdx. After prerequisite #881 merges, add the translated page at apps/landing/src/app/ko/docs/devup/typography/page.mdx, updating its metadata and preserving MDX structure. Done means the complete page is translated and the specified URL, layout, links, and build checks pass.
Written by the indexing model from the issue text.
Description
Goal
Provide the Korean version of /docs/devup/typography at /ko/docs/devup/typography. This issue covers only this page.
English source
Files to add or update
- apps/landing/src/app/(detail)/docs/devup/typography/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/devup/typography and language alternatives for the English and Korean URLs. Register /docs/devup/typography 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.
- Dominant language
- Rust
- Stars
- 359
- Forks
- 31
- Avg merge
- 8d 20h
- Merged PRs (30d)
- 92
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from dev-five-git/devup-ui
-
documentation good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
dev-five-git/devup-ui#879 ·
Maintainers usually reply within 11 days
-
documentation good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
dev-five-git/devup-ui#876 ·
Maintainers usually reply within 11 days
-
documentation good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
dev-five-git/devup-ui#871 ·
Maintainers usually reply within 11 days
-
documentation good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
dev-five-git/devup-ui#869 ·
Maintainers usually reply within 11 days
-
documentation good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
dev-five-git/devup-ui#868 ·
Maintainers usually reply within 11 days
All issues in dev-five-git/devup-ui
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
area:ci kind:bug priority:p3 ready
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
srikanth235/centraid#1155 ·
Maintainers usually reply within 1 day
-
dotfiles: failed batch untrack removes earlier tracking declarationsPossibly taken @jdx claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 2 days