reactjs / pl.react.dev

React documentation website in Polish

react.dev

This repo contains the source code and documentation powering react.dev.

Getting started

Prerequisites

1. Git
2. Node: any 12.x version starting with v12.0.0 or greater
3. Yarn: See Yarn website for installation instructions
4. A fork of the repo (for any contributions)
5. A clone of the react.dev repo on your local machine

Installation

1. cd react.dev to go into the project root
2. yarn to install the website's npm dependencies

Running locally

1. yarn dev to start the development server (powered by Next.js)
2. open http://localhost:3000 to open the site in your favorite browser

Contributing

Guidelines

The documentation is divided into several sections with a different tone and purpose. If you plan to write more than a few sentences, you might find it helpful to get familiar with the contributing guidelines for the appropriate sections.

Create a branch

1. git checkout main from any folder in your local react.dev repository
2. git pull origin main to ensure you have the latest main code
3. git checkout -b the-name-of-my-branch (replacing the-name-of-my-branch with a suitable name) to create a branch

Make the change

1. Follow the "Running locally" instructions
2. Save the files and check in the browser
3. Changes to React components in src will hot-reload
4. Changes to markdown files in content will hot-reload
5. If working with plugins, you may need to remove the .cache directory and restart the server

Test the change

1. If possible, test any visual changes in all latest versions of common browsers, on both desktop and mobile.
2. Run yarn check-all. (This will run Prettier, ESLint and validate types.)

Push it

1. git add -A && git commit -m "My message" (replacing My message with a commit message, such as Fix header logo on Android) to stage and commit your changes
2. git push my-fork-name the-name-of-my-branch
3. Go to the react.dev repo and you should see recently pushed branches.
4. Follow GitHub's instructions.
5. If possible, include screenshots of visual changes. A preview build is triggered after your changes are pushed to GitHub.

Translation

If you are interested in translating react.dev, please see the current translation efforts here.

License

Content submitted to react.dev is CC-BY-4.0 licensed, as found in the LICENSE-DOCS.md file.

pl.react.dev's Issues

Word repetition in docs

https://pl.reactjs.org/docs/components-and-props.html

Hello!
There is double "mogą" word in "Komponenty przy zwracaniu wyniku mogą mogą odwoływać się do innych komponentów." sentance on polish version of docs.
Link above c:

Bug Error in Polish page

Hello, I see an error in the link.

Page: https://pl.reactjs.org/docs/add-react-to-a-website.html#step-3-create-a-react-component

szablon startowy and szablonu startowego

https://gist.github/.... => https://gist.github.com/....

Rendering Elements page - lack of translation for Try it on CodePen

Steps:
Open Rendering Elements page - polish version

Actual result:
We don't have translation for Try it on CodePen

Expected result:
Try it on CodePen => Przetestuj kod na CodePen

PL Consultations [in Polish]

EDIT: Przenosimy dyskusje na Slacka ❗️ Wyślijcie sobie zaproszenie pod tym linkiem.

Cześć,

Proponuję używać tego wątku do konsultowania tłumaczeń. Chciałbym zacząć od zaproponowania odmiany nazwy "React", bo widziałem wiele różnych preferencji:

Przypadek	Odmiana - l.poj.	l.mn.
M	React	Reacty (?)
D	Reacta	Reactów
C	Reactowi	Reactom
B	Reacta	Reacty
N	Reactem	Reactami
Msc	Reakcie	Reactach
W	React	Reacty

Kierowałem się opinią dr-a Malinowskiego (zawiera poprawkę nie Reaccie a Reakcie), która wygląda imho całkiem sensownie.

[OLD] Legacy Polish Translation Progress

Slack

https://react-translations.slack.com - join to see the glossary and chat with other team members!
Channels:
#pl - general discussion
#pl-glossary - the glossary (use the search feature to find words)

Maintainer List

• @jakubdrozdek

Retired maintainers

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

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. 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 style guide (once they exist) to understand how to translate various technical and React-specific terms.

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!
Note: We require two maintainers to approve a PR for it to be merged.

Note: Since most of the PRs are created from forks, we can't add our own commits to them. Let's make a rule that if a PR's author doesn't respond within 7 days, we take the translated page over. Another person can create their own PR with the translated content, apply any suggestions added to the old PR, and submit. To be fair, let's not remove entirely the original author from the list below - just add the new translator after comma.
If the author leaves a message that they won't be available for a few days - that's fine, we'll wait.

Core Pages

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

• Home Page (@jakubdrozdek) #27
• Tutorial (@jakubdrozdek) #12

Basics

• Hello World (@cvqprs @TeoTN) #38
• Introducing JSX (@cvqprs @TeoTN) #39
• Rendering Elements (@arekmaz) #42
• Components and Props (@arekmaz) #45
• State and Lifecycle (@jakubdrozdek) #8
• Handling Events (@jakubdrozdek) #5
• Conditional Rendering (@marcinostrouch) #59
• Lists and Keys (@bartlomiejzuber) #58
• Forms (@marcinostrouch ) #57
• Lifting State Up (@iamarek) #11
• Composition vs Inheritance (@jakubdrozdek) #10
• Thinking in React (@marcinostrouch) #15

API Reference

• React ( @cvqprs @iamarek) #48
• React.Component (@arekmaz) #71
• ReactDOM (@patpienkowski) #35
• ReactDOMServer (@g12i) #81
• DOM Elements (@cvqprs @czechowiczmateusz) #62
• SyntheticEvent (@jakubdrozdek) #51
• Test Utilities (@jakubdrozdek) #21
• Shallow Renderer (@jakubdrozdek) #24
• Test Renderer (@jakubdrozdek) #25
• JS Environment Requirements (@cvqprs) #34
• Glossary (@jakubdrozdek) #76

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 (@jakubdrozdek) #56
• docs/nav.yml (@cvqprs) #77

Next Steps

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

Installation

• Getting Started (@iamarek) #6
• Add React to a Website (@cvqprs) #17
• Create a New React App (@marcinostrouch) #23
• CDN Links (@cvqprs) #18

Hooks

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

• Introducing Hooks (@g12i) #28
• Hooks at a Glance (@g12i) #33
• Using the State Hook (@g12i) #40
• Using the Effect Hook (@g12i) #50
• Rules of Hooks (@g12i) #54
• Building Your Own Hooks (@g12i) #60
• Hooks API Reference (@g12i) #65
• Hooks FAQ (@bartlomiejzuber, @jakubdrozdek) #191

Testing

• Testing Overview (@jakubdrozdek) #124
• Testing Recipes (@jakubdrozdek) #125
• Testing Environments (@jakubdrozdek) #126

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 (@m8ms) #157
• invalid-aria-prop (@jakubdrozdek) #88
• invalid-hook-call-warning (@jakubdrozdek) #96
• legacy-factories (@jakubdrozdek) #89
• refs-must-have-owner (@m8ms) #158
• special-props (@jakubdrozdek) #90
• unknown-prop (@jakubdrozdek) #97

Advanced Guides

• Accessibility (@danzawadzki) #61
• Code-Splitting (@JakeTvvv) #86
• Context (@jakubdrozdek) #129
• Error Boundaries (@PanFrontend) #128
• Forwarding Refs (@m8ms) #159
• Fragments (@jakubdrozdek) #102
• Higher-Order Components (@jakubdrozdek) #156
• Integrating with Other Libraries (@jakubdrozdek) #163
• JSX In Depth (@PanFrontend) #181
• Optimizing Performance (@jakubdrozdek) #210
• Portals (@polapolaczek) #215
• React Without ES6 (@jakubdrozdek) #194
• React Without JSX (@karpiuMG) #175
• Reconciliation (@marcin-wicha)
• Refs and the DOM
• Render Props (@bartlomiejzuber) #106
• Static Type Checking (@jakubdrozdek) #197
• Strict Mode (@bartlomiejzuber) #113
• Typechecking With PropTypes (@stepek) #185
• Uncontrolled Components (@karpiuMG) #173
• Web Components (@lffabled) #137

FAQ

• APIs and AJAX (@Iffabled) #140
• Babel, JSX, and Build Steps (@karpiuMG) #176
• Passing Functions to Components
• Component State (@jakubdrozdek) #195
• Styling and CSS (@Iffabled) #139
• File Structure (@karpiuMG) #177
• Versioning Policy
• Virtual DOM and Internals (@karpiuMG) #178

Contributing

Priority: Low

• How to Contribute
• Codebase Overview
• Implementation Notes
• Design Principles

Components

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

• CodeEditor (@jakubdrozdek) #55
• CodeExample (@jakubdrozdek) #55
• ErrorDecoder (@jakubdrozdek) #55
• LayoutFooter (@jakubdrozdek) #55
• LayoutHeader (@jakubdrozdek) #55
• MarkdownPage (@jakubdrozdek) #55

Additional Translations

These are not the primary translation targets.

• Blog

• Community

• addons-create-fragment (@mbiesiad) #212

• error-decoder (@mbiesiad) #213

• 404 (@mbiesiad) #214

Create a New React App page - formatting issue

The is an issue with of note section

Original:

Polish version:

Missing content in "Basic information"

Hey, in the React documentation in Polish I discovered that there are several sections missing from the "Podstawowe informacje" tab such as:
"Ucz się Reacta",
"Bądź na bieżąco",
"Dokumentacje wersji" and
"Czegoś brakuje?"

Polish Translation Final Steps

Congrats on almost finishing the core of the Polish translation! There are a couple more tasks we need to do before we mark the core pages as complete.

• Change the DocSearch API key . One of the maintainers needs to sign up for DocSearch
• Go over the pages of the site one last time to check for consistency

New Polish Translation Progress

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: 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) #335

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

• Installation

  • Start a New React Project (@dawidowski) #444
  • Add React to an Existing Project
  • Editor Setup (@jakubdrozdek) #291
  • React Developer Tools (@jakubdrozdek) #292

• Describing the UI (@jakubdrozdek) #340

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

• Adding Interactivity

  • Responding to Events
  • State: A Component's Memory
  • Render and Commit (@dawidowski) #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
  • 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 (@dawidowski) #423
  • useContext
  • useDebugValue
  • useDeferredValue
  • useEffect (@dawidowski) #431
  • useId
  • useImperativeHandle
  • useInsertionEffect
  • useLayoutEffect
  • useMemo
  • useReducer
  • useRef
  • useState (@jakubdrozdek) #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

Problem With your tooltip

I did not understand how did you implement the tooltip there?
if explain more about it i will be appreciate. thank you for your kindness.