reactjs / reactjs/id.react.dev

New Indonesian Translation Progress

Aperta
#330 127 commenti 6 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

good first issue help wanted
Lingua principale
JavaScript
Stelle
327
Fork
265
Merge medio
6h
PR unite (30g)
17

Descrizione

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.

Guida per i contributori

Apri la guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Direzione di ricerca

Inizia dalla issue collegata relativa a una pagina non tradotta, poi leggi TRANSLATION.md e il glossario prima di controllare il sorgente di quella pagina. Segui le istruzioni per la traduzione e la pull request della issue della pagina; la pagina interessata deve essere tradotta e i suoi progressi devono essere tracciati qui. Quando la traduzione sarà completata, i maintainer potranno aggiornare deployedLanguages in Seo.tsx come descritto.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Valutazione

Stack tecnologico
javascript, react
Ambito
documentation, internationalization, localization
Tipo di issue
Documentazione
Difficoltà
5/5
Tempo stimato
Più di una settimana
Stato di attività
Ferma
Chiarezza
Da chiarire
Idoneità per principianti
25/100

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.