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

[ko] Translate /docs/figma-and-theme-integration/devup-figma-plugin into Korean

Open Beginner friendly
  • Is something wrong?
#868 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
Domain
documentation, internationalization

Research direction

Read the English source at apps/landing/src/app/(detail)/docs/figma-and-theme-integration/devup-figma-plugin/page.mdx and compare it with the Korean overview at apps/landing/src/app/ko/docs/overview/page.mdx. Follow the translation guide and add the translated page at apps/landing/src/app/ko/docs/figma-and-theme-integration/devup-figma-plugin/page.mdx, updating its metadata and canonical URL. Done when the complete page is naturally translated, its MDX structure and links are preserved, and the Korean URL renders correctly after prerequisite #881 merges.

Written by the indexing model from the issue text.

Description

documentation good first issue help wanted
Goal

Provide the Korean version of /docs/figma-and-theme-integration/devup-figma-plugin at /ko/docs/figma-and-theme-integration/devup-figma-plugin. This issue covers only this page.

English source
Files to add or update
  • apps/landing/src/app/(detail)/docs/figma-and-theme-integration/devup-figma-plugin/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/figma-and-theme-integration/devup-figma-plugin and language alternatives for the English and Korean URLs. Register /docs/figma-and-theme-integration/devup-figma-plugin 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

  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.