Telugu Translation Progress

Aperta
#1 6 commenti 2 reazioni 1 assegnatario Vedi su GitHub

@srikanth-kandi ci sta già lavorando.

Dal 25/3/2024.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

good first issue help wanted

For New Translators

To translate a page:

  1. Check that no one else has claimed your page in the checklist and comments below.
    • 🟢 - It has not been assigned to anyone yet
    • 🔴 - It was assigned to somebody
    • 🎉 - It was translated and completed
  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 to understand how to translate various technical and React-specific terms.

Want to contribute, but still confused? check this YouTube video by @g-savitha.

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 #6 🟢

    • Tutorial Tic-Tac-Toe (@srikanth-kandi) #89 🎉
    • Thinking in React (@srikanth-kandi) #103 🎉
  • Installation (@poojitha-kandi) #142 🎉

    • Start a New React Project (@srikanth-kandi) #82 🎉
    • Add React to an Existing Project (@srikanth-kandi) #80 🎉
    • Editor Setup (@srikanth-kandi) #85 🎉
    • Using TypeScript (@shajahanshaik915 & @srikanth-kandi) #116 🎉
    • React Developer Tools (@srikanth-kandi) #86 🎉
  • Describing the UI #95 🟢

    • Your First Component (@Shiva-Sai-ssb) #134 🎉
    • Importing and Exporting Components (@Shiva-Sai-ssb) #136 🎉
    • Writing Markup with JSX (@Shiva-Sai-ssb) #138 🎉
    • JavaScript in JSX with Curly Braces (@Shiva-Sai-ssb) #139 🎉
    • Passing Props to a Component (@TenEplaysOfficial) #141 🎉
    • Conditional Rendering #40 🟢
    • Rendering Lists #41 🟢
    • Keeping Components Pure #42 🟢
    • Understanding Your UI as a Tree #100 🟢
  • Adding Interactivity (@sandeepvinnu & @srikanth-kandi) #105 🎉

    • Responding to Events #43 🟢
    • State: A Component's Memory #44 🟢
    • Render and Commit #45 🟢
    • State as a Snapshot #46 🟢
    • Queueing a Series of State Updates #47 🟢
    • Updating Objects in State #48 🟢
    • Updating Arrays in State #49 🟢
  • Managing State #97 🟢

    • Reacting to Input with State #50 🟢
    • Choosing the State Structure #51 🟢
    • Sharing State Between Components #52 🟢
    • Preserving and Resetting State #53 🟢
    • Extracting State Logic into a Reducer #54 🟢
    • Passing Data Deeply with Context #55 🟢
    • Scaling Up with Reducer and Context #56 🟢
  • Escape Hatches #98 🟢

    • Referencing Values with Refs #57 🟢
    • Manipulating the DOM with Refs #58 🟢
    • Synchronizing with Effects #59 🟢
    • You Might Not Need an Effect #60 🟢
    • Lifecycle of Reactive Effects #61 🟢
    • Separating Events from Effects #62 🟢
    • Removing Effect Dependencies #63 🟢
    • Reusing Logic with Custom Hooks #64 🟢
API Reference
  • react: Hooks

    • useCallback
    • useContext
    • useDebugValue
    • useDeferredValue
    • useEffect
    • useId
    • 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>
  • 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

Maintainer List

This translation is maintained by:

  • @srikanth-kandi

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.

Lingua principale
JavaScript
Stelle
14
Fork
15
Merge medio
1g 2h
PR unite (30g)
9

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.

Altre issue di reactjs/te.react.dev

Tutte le issue di reactjs/te.react.dev

Issue simili

Altre issue su JavaScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.