Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[ko] Translate /team into Korean

Open Beginner friendly
  • Is something wrong?
#879 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 11 days

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
74/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
markdown, react, typescript
Domain
internationalization

Research direction

Read the translation guide and the Korean overview at apps/landing/src/app/ko/docs/overview/page.mdx, then compare it with apps/landing/src/app/(detail)/team/page.mdx. Add the Korean translation at apps/landing/src/app/ko/team/page.mdx, updating its metadata and using the Korean layout wrapper. Done when the full page is translated, its canonical is /ko/team, and the listed link, layout, and build checks pass.

Written by the indexing model from the issue text.

Description

documentation good first issue help wanted
Goal

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

English source
Files to add or update
  • apps/landing/src/app/ko/team/page.mdx
Work

Copy the English MDX to the target file and translate it. Update the metadata title/description and canonical to /ko/team. App Router picks up the translated page automatically; no registry edits are required. For the team page, reuse its English layout with a Korean layout wrapper.

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/ko/docs/overview/page.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; no translation registry is needed. Run the type, lint and i18n checks listed in the translation guide.
  • 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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dev-five-git/devup-ui

All issues in dev-five-git/devup-ui

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.