New Polish Translation Progress

[jakubdrozdek]

New Site Translation Progress

Maintainer List

• @jakubdrozdek
• @dawidowski

Retired maintainers

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

Preview

https://pl.react.dev/

Original issue

This issue was based on: https://github.com/reactjs/reactjs.org/issues/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

• [x] Quick Start (@jakubdrozdek) https://github.com/reactjs/pl.react.dev/pull/335

  • [ ] Tutorial: Tic Tac Toe
  • [x] Thinking in React (@jakubdrozdek) #333

• [ ] Installation

  • [x] Start a New React Project (@dawidowski) #444
  • [ ] Add React to an Existing Project
  • [x] Editor Setup (@jakubdrozdek) https://github.com/reactjs/pl.react.dev/pull/291
  • [x] React Developer Tools (@jakubdrozdek) https://github.com/reactjs/pl.react.dev/pull/292

• [x] Describing the UI (@jakubdrozdek) #340

  • [x] Your First Component (@jakubdrozdek) #294
  • [x] Importing and Exporting Components (@jakubdrozdek) #295
  • [x] Writing Markup with JSX (@jakubdrozdek) #298
  • [x] JavaScript in JSX with Curly Braces (@jakubdrozdek) #300
  • [x] Passing Props to a Component (@jakubdrozdek) #301
  • [x] Conditional Rendering (@lukbar48) #302
  • [x] Rendering Lists (@dawidowski) #460
  • [ ] Keeping Components Pure (@dawidowski)

• [ ] Adding Interactivity

  • [ ] Responding to Events
  • [ ] State: A Component's Memory
  • [ ] Render and Commit
  • [ ] State as a Snapshot
  • [ ] Queueing a Series of State Updates
  • [ ] Updating Objects in State
  • [ ] Updating Arrays in State

• [x] Managing State

  • [ ] Reacting to Input with State
  • [ ] Choosing the State Structure
  • [ ] Sharing State Between Components
  • [ ] Preserving and Resetting State
  • [ ] 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

• [x] react: Hooks

  • [x] useCallback (@dawidowski) #423
  • [ ] useContext
  • [ ] useDebugValue
  • [ ] useDeferredValue
  • [x] useEffect (@dawidowski) #431
  • [ ] useId
  • [ ] useImperativeHandle
  • [ ] useInsertionEffect
  • [ ] useLayoutEffect
  • [ ] useMemo
  • [ ] useReducer
  • [ ] useRef
  • [x] useState (@jakubdrozdek) https://github.com/reactjs/pl.react.dev/pull/341
  • [ ] useSyncExternalStore
  • [ ] useTransition

• [x] react: Components

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

• [x] 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"

[dawidowski]

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

[dawidowski]

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

[dawidowski]

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

[dawidowski]

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

[tomaszwysocki]

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

[dawidowski]

@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

[dawidowski]

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