reactjs / reactjs/bn.react.dev

Bengali Translation Progress

未關閉
#1 81 則留言 10 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

主要語言
JavaScript
星號
113
分支
66
PR 合併指標
30 天內沒有已合併 PR

描述

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 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
  • Quick Start ( @anwarhossain1 ) #10

    • Tutorial: Tic Tac Toe (@indranildeveloper, @nafistiham) #15
    • Thinking in React (@nafistiham) #8 #16
  • Installation (@nafistiham) #61

    • Start a New React Project ( @moshfiqrony ) #3
    • Add React to an Existing Project ( @sowrovsarkar63 ) #40 (@nafistiham) #114
    • Editor Setup ( @shakib609 ) #4
    • React Developer Tools ( @nomandhoni-cs ) #11
  • Describing the UI (@nafistiham) #62

    • Your First Component ( @ahnafyy )
    • Importing and Exporting Components ( @KhanShaheb34 ) #9
    • Writing Markup with JSX ( @AhmdShuvo ) #48
    • JavaScript in JSX with Curly Braces ( @nazmulweb ) #24
    • Passing Props to a Component (@azmainadel) #31
    • Conditional Rendering ( @RazuAhmad )
    • Rendering Lists (@nisabzahid)
    • Keeping Components Pure ( @shakib609 ) #18
  • Adding Interactivity (@nazir021)

    • Responding to Events (@mhasan320)
    • State: A Component's Memory (@moinul192000) #38 (@nafistiham) #106
    • Render and Commit ( @MahdiMurshed ) #12
    • State as a Snapshot ( @MahdiMurshed ) #14 (@nafistiham) #116
    • Queueing a Series of State Updates (@deveasin) #41
    • Updating Objects in State (@deveasin )
    • Updating Arrays in State (@Arifulhaque-02128)
  • Managing State ( @ahmmedabir9 )

    • Reacting to Input with State (@shm-dsgn) #46
    • Choosing the State Structure (@AhmdShuvo)
    • Sharing State Between Components (@Sukhendu2002)
    • Preserving and Resetting State (@S907) #73
    • Extracting State Logic into a Reducer (@habibium) #100
    • Passing Data Deeply with Context (@habibium) #92
    • Scaling Up with Reducer and Context (@Shahriar-Rumel) #93
  • Escape Hatches (@nafistiham) #21

    • Referencing Values with Refs (@nafistiham) #25
    • Manipulating the DOM with Refs (@nafistiham) #34
    • Synchronizing with Effects (@AFM-Taha) (@habibium) #160
    • You Might Not Need an Effect (@nasirmasud)
    • Lifecycle of Reactive Effects ( @shomriddho )
    • Separating Events from Effects ( @perashanid )
    • Removing Effect Dependencies ( @perashanid )
    • Reusing Logic with Custom Hooks ( @perashanid )
API Reference
  • react: Hooks ( @SusmoySenGupta ) #39

    • useCallback (@JaznanOfficial )
    • useContext (@asif-jalil) #35 #37
    • useDebugValue ( @syum-akhlaque )
    • useDeferredValue
    • useEffect ( @lifeparticle ) #44
    • useId (@aleena314)
    • useImperativeHandle (@nafistiham) #72
    • useInsertionEffect (@nafistiham) #77
    • useLayoutEffect (@mustaquenadim)
    • useMemo (@foridpathan )
    • useReducer (@Arifur-Rahaman)
    • useRef (@MostofaNobiTanveer)
    • useState (@thecodermehedi)
    • useSyncExternalStore (@habibium) #204
    • useTransition (@mustaquenadim) #139
  • react: Components (@nafistiham) #58

    • <Fragment> (<>) (@nafistiham) #57
    • <Profiler> (@nafistiham) #59
    • <StrictMode> (@nafistiham)
    • <Suspense> (@nz-m) #33
  • react: APIs (@nafistiham) #60

    • createContext (@nafistiham) #97
    • forwardRef (@nafistiham) #105
    • lazy (@nafistiham) #80
    • memo (@nafistiham) #117
    • startTransition (@nafistiham) #79
  • react-dom: Components (@nafistiham) #68

    • Common (e.g. <div>)
    • <input>
    • <option> (@nafistiham) #67
    • <progress> (@mahbub-mahi)
    • <select>
    • <textarea>
  • react-dom: APIs (@nafistiham) #69

    • createPortal (@nafistiham) #119
    • flushSync (@nafistiham) #78
    • findDOMNode
    • hydrate (@nafistiham) #83
    • render (@nafistiham) #81
    • unmountComponentAtNode (@nafistiham) #70
  • react-dom/client: Client APIs (@nafistiham) #49

    • createRoot (@nafistiham) #50
    • hydrateRoot (@nafistiham) #53
  • react-dom/server: Server APIs (@nafistiham) #63

    • renderToNodeStream (@nafistiham) #64
    • renderToPipeableStream (@habibium) #195
    • renderToReadableStream
    • renderToStaticMarkup (@nafistiham) #65
    • renderToStaticNodeStream (@nafistiham) #66
    • renderToString (@habibium) #153
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

Maintainer List

This translation is maintained by:

  • @moshfiqrony
  • @ahmmedabir9
  • @nazir021
  • @nomandhoni-cs
  • @shakib609
  • @ahnafyy
  • @nafistiham
  • @nutboltu
  • @habibium

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.

貢獻指南

開啟貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

研究方向

從檢查清單中選擇一個尚未勾選的頁面,並先在留言中確認該頁面尚未被認領。閱讀術語表和樣式指南,然後依照對應的來源頁面進行操作;導覽相關工作位於 HomeContent.js、src/sidebar*.json 和 TopNav.tsx 中。當 Bengali 翻譯透過 pull request 提交並更新檢查清單項目後,即視為完成。

由索引模型根據 Issue 內容生成。

評估

技術堆疊
javascript, react, typescript
領域
content, documentation, localization
Issue 類型
文件
難度
5/5
預估耗時
一週以上
活躍度
冷清
描述清晰度
需要釐清
新手友好度
32/100

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。