Page: https://id.react.dev/learn/passing-data-deeply-with-context

Assignee: @ridhlab

Page: https://id.react.dev/learn/managing-state

Assignee: @kalmndo

Page: https://id.react.dev/learn/thinking-in-react

Assignee: @resir014

Page: https://id.react.dev/reference/react/useDebugValue

Assignee: @arganaphang

Page: https://id.react.dev/reference/react/Profiler

Assignee: @rimuhamu

Page: https://id.react.dev/reference/react/useTransition

Assignee: @dickygiancini

Assignee: @padunk

Page: https://id.react.dev/learn/scaling-up-with-reducer-and-context

Assignee: @R1dwanMaulana

Page: https://id.react.dev/reference/react/useMemo

Assignee: @annisann

Page: https://id.react.dev/learn/referencing-values-with-refs

Assignee: @irsyaadbp

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

Assignee: @KevinPalowa

Page: https://id.react.dev/learn/reacting-to-input-with-state

Assignee: @JfrAziz

Page: https://id.react.dev/reference/react/Suspense

Assignee: @maulanasdqn @chez14

UPDATE: 👉 Please Check out the Glossary and TRANSLATION.md file

Hi @reactjs/reactjs-org-indonesian-translation ,

Before more contributors joined, I think we need to:

1. Start building our style guide
2. Agreed upon common diction/terms that we'll choose

Perhaps, we need a TRANSLATION.md like our Japanese counterpart.

Page: https://app.grammarly.com/ddocs/2031021306

Assignee: @adamcanray

Page: https://id.react.dev/learn/extracting-state-logic-into-a-reducer

Assignee: @thaddeuscleo

Page: https://id.react.dev/learn/synchronizing-with-effects

broken link
isreacttranslatedyet.com

Page: https://id.react.dev/learn/reusing-logic-with-custom-hooks

Assignee: @rvndaputra

Page: https://id.react.dev/reference/react/useLayoutEffect

Assignee: @milhamm

Assignee: @igihcksn

Page: https://id.react.dev/learn/manipulating-the-dom-with-refs

Assignee: @andriawan

Page: https://id.react.dev/learn/choosing-the-state-structure

Assignee: @dzakiafif

Page: https://id.react.dev/reference/react/useRef

Assignee: @xevorte

Page: https://id.react.dev/reference/react/useEffect

Assignee: @R1dwanMaulana

Page: https://id.react.dev/learn/you-might-not-need-an-effect

Assignee: @averrows

Page: https://id.react.dev/reference/react/useCallback

Assignee: @intanirnanda5796

Page URL: https://id.react.dev/reference/react/useImperativeHandle

Assignee: @sozonome

Page: https://id.react.dev/learn/sharing-state-between-components

Assignee: @yaffalhakim1

Page: https://id.react.dev/reference/react/Fragment

Assignee: @AudiWu

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

Assignee: @mhaidarhanif

PR: #500

Progress

• Creating and nesting components
• Writing markup with JSX
• Adding styles
• Displaying data
• Conditional rendering
• Rendering lists
• Responding to events
• Updating the screen
• Using Hooks
• Sharing data between components
• Next Steps

Page: https://id.react.dev/learn/preserving-and-resetting-state

Assignee: @hendraaagil

Assignee: @syauqy

Page: https://id.react.dev/reference/react/useReducer

Assignee: @rivldy

Maintainer List

• @arfianadam
• @gedeagas
• @regalius
• @rizafahmi
• @resir014
• @grikomsn

For New Translators

To translate a page:

1. Check that no one else has claimed your page in the checklist and comments below.
2. Comment below with the name of the page you would like to translate. Take only one page at a time.
3. Clone this repo, make your translations, and submit a pull request!

Before contributing, read the glossary and translation guidelines to understand how to translate various technical and React-specific terms. (If you're still not sure about something, please don't hesitate to ask them here, we won't bite 😄)

Previously, some translations were done in Crowdin. You can use that a starting point for your translations. Do not contribute to Crowdin directly.

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

For maintainers

When someone volunteers, edit this issue with the username of the volunteer, and with the PR. Ex:

• Home Page (@tesseralis) #1

When PRs are merged, make sure to mark that page as completed!

Work Status

Core Pages

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

• Home Page (@regalius) #4
• Tutorial (@martinock) #10

Basics

• Hello World (@vferdiansyah) #132
• Introducing JSX (@gedeagas) #13
• Rendering Elements (@alchristleo) #23
• Components and Props (@andreepratama27) #19
• State and Lifecycle (@amiruddinid) #61
• Handling Events (@TitusEfferian) #17
• Conditional Rendering (@andriawan) #92
• Lists and Keys (@aisy) #14
• Forms (@fajrizulfikar) #118
• Lifting State Up (@mendoanjoe) #6
• Composition vs Inheritance (@regalius) #7
• Thinking in React (@resir014) #8

API Reference

• React (@mnindrazaka)
• React.Component (@lunmay) #156
• ReactDOM (@anggras) #11
• ReactDOMServer (@RiftSplitter)
• DOM Elements (@kafinsalim) #120
• SyntheticEvent (@devinryanriota) #31
• Test Utilities (@Lukereonal) #16
• Shallow Renderer (@riandy-dimas) #18
• Test Renderer (@rianonehub) #21
• JS Environment Requirements (@antonybudianto) #15
• Glossary (@hilalarsa) #36

Navigation

These are the navigation links that appears in the sidebar. Possibly wait until
the corresponding sections are translated to do these.

• tutorial/nav.yml (@IzzanNurdin) #137
• docs/nav.yml (@kuuhaku86) #186

Next Steps

These are the next most important translations, ordered by importance:

Installation

• Getting Started (@hryer) #60
• Add React to a Website (@regalius) #56
• Create a New React App (@fanyspenda) #25
• CDN Links (@vferdiansyah)

Hooks

Everyone is hooked on hooks! People are really excited for these and it would be great for them to be translated.

• Introducing Hooks (@handywijaya) #59
• Hooks at a Glance (@grikomsn) #88
• Using the State Hook (@igarramaddhan) #28
• Using the Effect Hook (@RiskyFeryansyahP) #38
• Rules of Hooks (@anggras) #53
• Building Your Own Hooks (@rizkyalviandra) #63
• Hooks API Reference (@bangunbagustapa) #127
• Hooks FAQ (@dummyeuy) #123

Concurrent Mode

• Introducing Concurrent Mode (@xtrixia) #169
• Suspense for Data Fetching (@suliskh) #182
• 🏃 Concurrent UI Patterns (@ahmad-reza619, @resir014) #181, #191
• 🏃 Adopting Concurrent Mode (@padulkemid)
• Concurrent Mode API Reference (@spondbob) #180

Testing

• Testing Overview (@agusID) #116
• Testing Recipes (@winndo) #129
• Testing Environments (@winndo) #144

Warnings

These are the pages that you get when you click the links in the console (e.g. https://reactjs.org/warnings/dont-call-proptypes.html). People tend to search these, so please don't translate the error message itself.

• dont-call-proptypes (@jonasqq) #57
• invalid-aria-prop (@anwari666) #114
• invalid-hook-call-warning (@andriawan) #107
• legacy-factories (@andriawan) #108
• refs-must-have-owner (@anwari666) #113
• special-props (@andriawan) #105
• unknown-prop (@ismailnagib) #104

Advanced Guides

• Accessibility (@ekafyi) #58
• Code-Splitting (@masbagal) #52
• Context (@tegarjgap) #131
• Error Boundaries (@lunmay) #157
• Forwarding Refs (@agallio) #205
• Fragments (@iwgx) #109
• Higher-Order Components (@andriawan) #158
• Integrating with Other Libraries (@mramadhanr) #119
• JSX In Depth (@dummyeuy) #125
• Optimizing Performance (@resir014) #136
• Portals (@lunmay) #48
• 🏃 Profiler API (@rasisbuldan)
• React Without ES6 (@lunmay) #49
• React Without JSX (@brilyandk) #55
• Reconciliation (@gattigaga) #115
• Refs and the DOM (@lunmay) #47
• Render Props (@imiro) #62
• Static Type Checking (@lunmay) #51
• Strict Mode (@lunmay) #155
• Typechecking With PropTypes (@rizafahmi) #40
• Uncontrolled Components (@lunmay) #50
• Web Components (@farazaulia) #45

FAQ

• APIs and AJAX (@dizzy322) #35
• Babel, JSX, and Build Steps (@DMM31) #33
• Passing Functions to Components (@goFrendiAsgard) #82
• Component State (@xtrixia) #185
• Styling and CSS (@AyuPermatasari) #64
• File Structure (@bangunbagustapa) #143
• Versioning Policy (@asharimh97) #111
• Virtual DOM and Internals (@zweimach) #130

Contributing

Priority: Low

• How to Contribute (@paramithatm) #122
• Codebase Overview (@paramithatm) #128
• Implementation Notes (@tegarjgap) #124
• 🏃 Design Principles (@kafinsalim)

Components

Components in src/components that have some text in them.

• CodeEditor (@IzzanNurdin) #133
• CodeExample (@IzzanNurdin) #133
• ErrorDecoder (@IzzanNurdin) #133
• LayoutFooter (@IzzanNurdin) #133
• LayoutHeader (@IzzanNurdin) #133
• MarkdownPage (@IzzanNurdin) #133

Additional Translations

These are not the primary translation targets.

• Blog
• 🏃 Community (@resir014)

Page: https://id.react.dev/reference/react/useId

Assignee: @AndriP8

Maintainer List

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

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.

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
• Blog
• Warnings

Page: https://id.react.dev/reference/react/components

Page: https://id.react.dev/reference/react/useState

Assignee: @vashafaris