New Polish Translation Progress

[jakubdrozdek]

New Site Translation Progress

Maintainer List

• @jakubdrozdek
• @dawidsabat

Retired maintainers

• @TeoTN
• @cvqprs
• @marcinostrouch
• @iamarek
• @arekmaz
• @g12i
• @bartlomiejzuber

Preview

https://pl.react.dev/

Original issue

This issue was based on: reactjs/react.dev#4135

How to translate

If you want to help with translation, please leave a comment in this issue and write the name of the page you would like to translate. One of the repo maintainers will add your GitHub nickname next to the page to "make a reservation".

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

• Quick Start (@jakubdrozdek) Translate Quick start page #335

  • Tutorial: Tic Tac Toe
  • Thinking in React (@jakubdrozdek) Translate Thinking in React page #333

• Installation

  • Start a New React Project (@dawidsabat) Translate Start a new react project page #444
  • Add React to an Existing Project (@tomaszwysocki) Translate Add React to an Existing Project page #454
  • Editor Setup (@jakubdrozdek) Translate Editor setup page #291
  • React Developer Tools (@jakubdrozdek) Translate React Developer Tools page #292

• Describing the UI (@jakubdrozdek) Translate Describing the UI page #340

  • Your First Component (@jakubdrozdek) Translate Your first component #294
  • Importing and Exporting Components (@jakubdrozdek) Translate Importing and exporting components page #295
  • Writing Markup with JSX (@jakubdrozdek) Translate Writing markup with JSX page #298
  • JavaScript in JSX with Curly Braces (@jakubdrozdek) Translate JavaScript in JSX with curly braces #300
  • Passing Props to a Component (@jakubdrozdek) Translate Passing props to a component page #301
  • Conditional Rendering (@lukbar48) Translated Conditional Rendering article #302
  • Rendering Lists (@dawidsabat) Translate Rendering Lists page #460
  • Keeping Components Pure (@dawidsabat) Translate Keeping components pure #464

• Adding Interactivity (@dawidsabat) Translate Learn / Adding interactivity #478

  • Responding to Events
  • State: A Component's Memory
  • Render and Commit (@dawidsabat) Translate Render and commit #465
  • State as a Snapshot
  • Queueing a Series of State Updates
  • Updating Objects in State
  • Updating Arrays in State

• Managing State

  • Reacting to Input with State
  • Choosing the State Structure
  • Sharing State Between Components
  • Preserving and Resetting State (@dawidsabat)
  • Extracting State Logic into a Reducer
  • Passing Data Deeply with Context
  • Scaling Up with Reducer and Context

• Escape Hatches

  • Referencing Values with Refs
  • Manipulating the DOM with Refs
  • Synchronizing with Effects
  • You Might Not Need an Effect
  • Lifecycle of Reactive Effects
  • Separating Events from Effects
  • Removing Effect Dependencies
  • Reusing Logic with Custom Hooks

API Reference

• react: Hooks

  • useCallback (@dawidsabat) Translation of useCallback reference #423
  • useContext
  • useDebugValue
  • useDeferredValue
  • useEffect (@dawidsabat) useEffect reference #431
  • useId
  • useImperativeHandle
  • useInsertionEffect
  • useLayoutEffect
  • useMemo
  • useReducer
  • useRef
  • useState (@jakubdrozdek) Translate useState hook API #341
  • useSyncExternalStore
  • useTransition

• react: Components

  • <Fragment> (<>)
  • <Profiler>
  • <StrictMode>
  • <Suspense>

• react: APIs

  • createContext
  • forwardRef
  • lazy
  • memo
  • startTransition

• react-dom: Components

  • Common (e.g. <div>)
  • <input>
  • <option>
  • <progress>
  • <select>
  • <textarea>

• react-dom: APIs

  • createPortal
  • flushSync
  • findDOMNode
  • hydrate
  • render
  • unmountComponentAtNode

• react-dom/client: Client APIs

  • createRoot
  • hydrateRoot

• react-dom/server: Server APIs

  • renderToNodeStream
  • renderToPipeableStream
  • renderToReadableStream
  • renderToStaticMarkup
  • renderToStaticNodeStream
  • renderToString

Navigation and UI

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.

• Homepage (currently in HomeContent.js)
• Sidebars (currently in src/sidebar*.json)
• Top-level navigation (currently in TopNav.tsx)

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

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

• Legacy React APIs
  • Children
  • cloneElement
  • Component
  • createElement
  • createFactory
  • createRef
  • isValidElement
  • PureComponent

Optional Content

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

[lukbar48]

I will take Conditional rendering

[cyntler]

@lukbar48 do you do something with Rendering Lists?

[cyntler]

@jakubdrozdek I can take Keeping Components Pure. Could you assign it to me?
Ok, as @lukbar48 mentioned below, assign also Rendering Lists to me please.

[lukbar48]

@lukbar48 do you do something with Rendering Lists?

no, take it

[gaearon]

Hi folks,

Just a heads-up that we've done our best to bring main and legacy branches up-to-date with upstream. This brings you to the latest visual design and sets up all the redirects. We don't anticipate more changes necessary on legacy. For main, there's a few things you need to be aware of:

• Keep in mind translating UI is best done closer to the end. We plan to make non-trivial code changes to the repo over the next few months. So it's best to focus on the content rather than on UI components.
• The homepage is untranslated so ideally it would be good if you could do a pass at that. For now, unfortunately it requires messing with the code file.
• A few rewritten pages (from Installation) are currently untranslated.
• This was a massive PR to merge, so we might have regressed somewhere or missed some changes that needed to be translated. Ideally, it would be great if you could go over the already-translated pages at your own pace and verify nothing important got lost.

Thank you so much for your cooperation!

[jakubdrozdek]

Hey @gaearon , I'll take a look at this soon and try to update our translations for the new docs. Thanks for resolving all conflicts. I saw how big and complex they were. I'm glad you did this for us 😅

[gaearon]

Ah this wasn't me, that's all @rickhanlonii's doing :)

[gaearon]

I've updated this issue's TODO list to the current template.

[aadamw]

Hey, I could pick up the "Start a New React Project"

[dawidsabat]

Hi @jakubdrozdek, I would like to contribute a bit. I can start with useCallback.

[dawidsabat]

PR for useCallback is ready. I would like to start with useEffect now.

[dawidsabat]

I would like to translate "Start a New React Project" section.

[dawidsabat]

I would like to take "Rendering Lists" from "Describing the UI".

[tomaszwysocki]

I would like to translate "Add React to an Existing Project" page.

[dawidsabat]

@jakubdrozdek, I would like to. take now Keeping Components Pure .

Two PRs already wait for for next comments or approval ;)
#444 - Start a New React Project
#460 - Rendering Lists

[dawidsabat]

I would like to take Render and Commit page - need something light now ;)

[wizarddos]

Can I pick up Add react to an existing project page?

[tomaszwysocki]

@wizarddos I was doing that. It has been pushed already.

[wizarddos]

@tomaszwysocki Oh, all right

[dawidsabat]

I would like to Adding Interactivity now.

[dawidsabat]

PR for Adding Interactivity is ready under #478.
I would like to translate Preserving and Reseting State now.

Moreover, I see Add React to an Existing Project is already translated by @tomaszwysocki but not marked as done in the checklist. @jakubdrozdek, could you update it? ;)

[JohnyKam]

Hi. I would like to translate Tutorial: Tic Tac Toe page. I hope that I will handle it. :-)

[wizarddos]

Can I take Responding to Events or State: A Component's Memory ?

[dawidsabat]

@JohnyKam and @wizarddos, welcome aboard! Good to see we have more contributors! 😄

Basically, you can take whatever is not taken yet. Posting here what you want to translate is enough.
Take a look into PL Consultations and TRANSLATIONS.md to follow patterns and glossary. Feel free to propose new translations!

@JohnyKam, I would recommend to start with some shorter page. Tutorial: Tic Tac Toe is quite big page to start with.
But if you fill you will handle it, go for it 😃

By the way, @jakubdrozdek, I have recently changed my nickname from @dawidowski to @dawidsabat. Could I ask you to change it as well in the starting post above? I would love to do it myself but you are the author of this post

[JohnyKam]

True, Tutorial: Tic Tac Toe is quite big. Can I start with Sharing State Between Components? Then, if necessary, I will move on to Tutorial: Tic Tac Toe :-).

[dawidsabat]

@JohnyKam, go for it! 😀

[dawidsabat]

I would like to translate State as a Snapshot now.

@jakubdrozdek, @wizarddos - PR #490 for Preserving and Resetting State is ready for the review. I would love to hear your feedback 😉