Telugu Translation Progress
gaearon opened this issue · comments
For New Translators
To translate a page:
- 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
- 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 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 #7 🟢
- Start a New React Project (@srikanth-kandi) #82 🎉
- Add React to an Existing Project (@srikanth-kandi) #80 🎉
- Editor Setup (@srikanth-kandi) #85 🎉
- Using TypeScript #99 🟢
- React Developer Tools (@srikanth-kandi) #86 🎉
-
Adding Interactivity (@sandeepvinnu) #105 🔴
-
Managing State #97 🟢
-
Escape Hatches #98 🟢
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>
- 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 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:
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.
I would like to contribute to Your First Component page.
Hey @gaearon,
The existing maintainers @g-savitha, @gsteja2307 and @vamsikrishnareddybevara are inactive on this repository.
I also contacted all the existing maintainers via Email and other social platforms regarding adding me as a maintainer for this repository.
As stated in translations.react.dev repo about Adding a maintainer, these existing maintainers are inactive for the past couple of weeks.
As I'm a Native Telugu Speaker and have a good knowledge of React, If possible consider adding me as another maintainer to this repository.
Thank you :)
Hey @gaearon,
The existing maintainers @g-savitha, @gsteja2307 and @vamsikrishnareddybevara are inactive on this repository.
I also contacted all the existing maintainers via Email and other social platforms regarding adding me as a maintainer for this repository.As stated in translations.react.dev repo about Adding a maintainer, these existing maintainers are inactive for the past couple of weeks.
As I'm a Native Telugu Speaker and have a good knowledge of React, If possible consider adding me as another maintainer to this repository.
Thank you :)
Hi @srikanth-kandi , me and @g-savitha are no longer maintainers for this repo
Hi @srikanth-kandi , me and @g-savitha are no longer maintainers for this repo
Could you add me as a new maintainer, if possible?
Hi @srikanth-kandi, done!