reactjs / reactjs/id.react.dev

New Indonesian Translation Progress

未关闭
#330 127 条评论 6 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

good first issue help wanted
主要语言
JavaScript
星标
327
派生
265
平均合并
6 小时
30 天内合并 PR
17

描述

For New Translators

To translate a page:

  1. Check that no one else has claimed your page in the linked issues below.
  2. Comment on the linked issue that you would like to translate said page. Please take only one page at a time.
  3. Clone this repo, translate your page, and submit a pull request!

Before contributing, read the glossary and translation guidelines to understand how to translate various technical and React-specific terms.

Please be prompt with your translations! If you find that you can't commit anymore, let the maintainers know so they can assign the page to someone else.

For Maintainers

Make sure to link to the exact page being translated on the first comment of the issue. Ex:

Page: https://id.react.dev/learn

When PRs are created, make sure that it's linked to the correct issue! This will make sure the issue is closed automatically when the PR is merged.

This ensures your translation's progress is tracked correctly at https://translations.react.dev/.

Main Content

To do before releasing as an "official" translation. Please translate these pages first.

Note that each section has an index page, which needs to be translated too.

Learn React (High Priority)
  • #372

    • #373
    • #374
  • #375

    • #376
    • #377
    • #395
    • #658
    • #396
  • #464

    • #465
    • #417
    • #419
    • #425
    • #428
    • #431
    • #466
    • #435
    • #659
  • #452

    • #445
    • #446
    • #447
    • #448
    • #449
    • #450
    • #451
  • #378

    • #379
    • #380
    • #381
    • #382
    • #383
    • #384
    • #385
  • #386

    • #387
    • #388
    • #389
    • #390
    • #391
    • #392
    • #393
    • #394
API Reference (High Priority)
  • #397

    • #398
    • #463
    • #399
    • #400
    • #401
    • #402
    • #403
    • #404
    • #405
    • #406
    • #407
    • #408
    • #409
    • #410
    • #411
  • #412

    • #413
    • #414
    • #415
    • #416
  • #468

    • #469
    • #470
    • #471
    • #418
    • #420
  • #421

    • #422
    • #423
    • #424
    • #426
    • #427
    • #433
  • #434

    • #436
    • #438
    • #439
    • #440
    • #441
    • #443
  • #453

    • #454
    • #455
  • #456

    • #457
    • #458
    • #459
    • #460
    • #461
    • #462
Navigation and UI (Medium Priority)

We suggest to leave most of the UI translation until the end. We plan to do some invasive changes to the website folder layout and components, so postponing this until your translation is almost complete would make it easier to merge the changes from our side later. It might make sense to translate the homepage above the fold early, but leave the rest for later. As individual pages get translated, you can change the page titles in the corresponding sidebar files. Finally, when you're translating the navigation, make sure to test both desktop and mobile layouts.

  • #579
  • #583
  • #584
When You're Ready...

After everything above is translated, add your language to deployedLanguages in Seo.tsx of the original reactjs/react.dev repository.

Secondary Content (Medium Priority)

These API pages should ideally be translated too, but they're less urgent and can be done after the others:

  • #545
    • #546
    • #547
    • #548
    • #549
    • #550
    • #551
    • #552
    • #553

Optional Content (Low Priority)

These aren't the main translation targets, but if you'd like to do them, feel free to expand the list to include their subpages:

  • Community

Maintainers

This translation is maintained by:

  • @arfianadam
  • @gedeagas
  • @regalius
  • @rizafahmi
  • @resir014
  • @grikomsn
  • @zainfathoni
  • @r17x
  • @mhaidarhanif
  • @mazipan

If you want to become a maintainer, ask them to add you. If the original maintainers are no longer responsive, raise an issue in the main translations repository.

贡献指南

打开贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

调研方向

先从未翻译页面的关联 issue 开始,然后阅读 TRANSLATION.md 和术语表,再检查该页面的源代码。按照页面 issue 中的翻译和 pull request 说明执行;应翻译相关页面,并在此跟踪其进度。翻译完成后,维护者可以按照说明更新 Seo.tsx 中的 deployedLanguages。

由索引模型根据 Issue 内容生成。

评估

技术栈
javascript, react
领域
documentation, internationalization, localization
Issue 类型
文档
难度
5/5
预计耗时
一周以上
活跃度
停滞
描述清晰度
需要澄清
新手友好度
25/100

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。