reactjs / reactjs/sr.react.dev
Serbian Translation Progress
まだ誰も着手していません。
- 主要言語
- JavaScript
- スター
- 7
- フォーク
- 3
- 平均マージ
- 10時間 8分
- マージ済み PR(30日)
- 4
説明
For New Translators
To translate a page:
- Check that no one else has claimed your page in the checklist and comments below.
- Comment below with the name of the page you would like to translate. Please take only one page at a time.
- 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 that you can't commit anymore, 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:
- [ ] Some Page (@exampleusername) #12345
When PRs are merged, make sure to mark that page as completed like this:
- [x] Some Page (@exampleusername) #12345
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
-
#2 (@lxmarinkovic)
- #70 (@lxmarinkovic)
- #77 (@rammba)
-
#5 #7 (@cvijandj)
- Start a New React Project #7 (@cvijandj)
- Add React to an Existing Project #11 (@cvijandj)
- Editor Setup #10 (@cvijandj)
- React Developer Tools #10 (@cvijandj)
-
Describing the UI #10 (@cvijandj)
- #81 (@rammba)
- #83 (@rammba)
- #86 (@rammba)
- JavaScript in JSX with Curly Braces #19 (@cvijandj)
- #90 (@rammba)
- #96 (@rammba)
- #105 (@rammba)
- #107 (@rammba)
-
#103 (@lxmarinkovic)
- #109 (@rammba)
- #112 (@rammba)
- #119 (@rammba)
- #124 (@rammba)
- #134 (@rammba)
- #140 (@rammba)
- #143 (@rammba)
-
#146 (@rammba)
- #150 (@rammba)
- #152 (@rammba)
- #154 (@rammba)
- #157 (@rammba)
- #161 (@rammba)
- #169 (@rammba)
- Scaling Up with Reducer and Context
-
#181 (@rammba)
- 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
-
#179 (@rammba)
- #184 (@rammba)
- #186 (@rammba)
- #188 (@rammba)
- #190 (@rammba)
-
useEffect - #193 (@rammba)
-
useImperativeHandle -
useInsertionEffect -
useLayoutEffect -
useMemo -
useReducer -
useRef -
useState -
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>
- Common (e.g.
-
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 finishedTranslations in finishedTranslations.ts 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
Maintainer List
This translation is maintained by:
- @lxmarinkovic
- @vaske
- @cvijandj
- @rammba
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.
コントリビューションガイド
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
調査の方向性
この issue のチェックリストを使って未チェックのページを見つけ、まずそのページがチェックリストやコメントで担当者として申告されていないことを確認します。利用できる場合は用語集とスタイルガイドを読み、1 ページを翻訳して pull request を送信します。ページに貢献者と PR を記載して完了済みとマークすると、完了が記録されます。
索引モデルが issue の本文から書いたものです。
評価
- 技術スタック
- javascript, react
- 領域
- documentation
- issue の種類
- ドキュメント
- 難易度
- 5/5
- 見積もり時間
- 1週間以上
- 活発さ
- 停滞
- 明瞭さ
- 説明が足りない
- 初心者へのやさしさ
- 20/100