reactjs / reactjs/bn.react.dev

Bengali Translation Progress

Aperta
#1 81 commenti 10 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Lingua principale
JavaScript
Stelle
113
Fork
66
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Descrizione

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.

Guida per i contributori

Apri la guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Direzione di ricerca

Scegli una pagina non ancora spuntata dalla checklist e conferma prima nei commenti che non sia stata presa in carico. Leggi il glossario e la guida di stile, quindi segui la pagina sorgente corrispondente; il lavoro di navigazione si trova in HomeContent.js, src/sidebar*.json e TopNav.tsx. Il lavoro è completato quando una traduzione in Bengali viene inviata in una pull request e la voce della checklist viene aggiornata.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Valutazione

Stack tecnologico
javascript, react, typescript
Ambito
content, documentation, localization
Tipo di issue
Documentazione
Difficoltà
5/5
Tempo stimato
Più di una settimana
Stato di attività
Tranquilla
Chiarezza
Da chiarire
Idoneità per principianti
32/100

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.