[OLD] Legacy Hindi Translation Progress

[tesseralis]

Translation details of beta site is available here #168
We are not translating these pages anymore.

Maintainer List

• @saranshkataria
• @arshadkazmi42

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 find that you can't commit any more, 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:

• Home Page (@saranshkataria) Home page translation #3 translated home page to hindi #6

When PRs are merged, make sure to mark that page as completed!

Core Pages

To do before releasing as an "official" translation. Please translate these pages first.

• Home Page (@saranshkataria ) Home page translation #3 translated home page to hindi #6
• Tutorial (@arshadkazmi42 ) hindi translation #8

Basics

• Hello World (@gurjotsingh4398 ) Hello World Page Translation #13
• Introducing JSX (@arshadkazmi42 ) adds introduction-jsx para of introducing-jsx page #12
• Rendering Elements (@AbhishekCode && @saranshkataria ) Translated rendering element page #21 updating rendering elements from #21 #41
• Components and Props (@helios1101 ) Translating Components and Props page  #24
• State and Lifecycle Translating page Style and Lifecycle. #26
• Handling Events (@yashguptaz ) [Translation] Handling Events #27
• Conditional Rendering (@kambleaa007) Condition rendering fixed updated final #43
• Lists and Keys (@anchal7299 ) Translated Lists-and-Keys page #25
• Forms (@aashirwadgupta ) Translating forms.md #22 + (New PR)
• Lifting State Up (@SambhavSacheti ) Translated - Lifting State Up #30
• Composition vs Inheritance (@apoorvtomar2222) Translate entire Composition vs Inheritance page #28
• Thinking in React (@mayank-gangwal )

API Reference

• React (@Hrshk15 )
• React.Component 30-40% translation of React -> Component page is done #76
• ReactDOM (@charBap ) Translating API Reference -> ReactDOM #31
• ReactDOMServer (@neeraj-here)
• DOM Elements (@rao123dk )
• SyntheticEvent (@ps0305 ) translation: SyntheticEvent #66
• Test Utilities (@paramaggarwal ) API Reference > Test Utilities #45
• Shallow Renderer (@vermasachin && @arshadkazmi42 ) Translated shallow renderer #44
• Test Renderer (@tanishqchamola )
• JS Environment Requirements (@AlokTakshak) added hindi translation for js environment requirement #47
• Glossary (@AlokTakshak) Translated API REFERENCE > Glossary #51

Navigation

These are the navigation links that appears in the sidebar. Possibly wait until
the corresponding sections are translated to do these.

• tutorial/nav.yml
• docs/nav.yml

Next Steps

These are the next most important translations, ordered by importance:

Installation

• Getting Started (@yashguptaz ) [Translation] - Getting Started #17
• Add React to a Website (@NorinMp143 ) Add React to a Website #65
• Create a New React App (@vishalsodani ) Translated create new react app page #52
• CDN Links (@AninditaBasu ) Added translation for cdn-links.md #53

Hooks

Everyone is hooked on hooks! People are really excited for these and it would be great for them to be translated.

• Introducing Hooks (@shob0 )
• Hooks at a Glance (@gautam-pahuja ) [Translation] Hooks at a Glance #58
• Using the State Hook (@AlokTakshak )
• Using the Effect Hook (@anoopsingh1996 )
• Rules of Hooks (@chandrakantnaik789 )
• Building Your Own Hooks (@visshaljagtap ) [Translation] Building Your Own Hooks #68
• Hooks API Reference
• Hooks FAQ (@ps0305 )

Warnings

These are the pages that you get when you click the links in the console (e.g. https://reactjs.org/warnings/dont-call-proptypes.html). People tend to search these, so please don't translate the error message itself.

• dont-call-proptypes (@ShivamPorwal02 )
• invalid-aria-prop
• invalid-hook-call-warning
• legacy-factories
• refs-must-have-owner
• special-props
• unknown-prop

Advanced Guides

• Accessibility
• Code-Splitting
• Context
• Error Boundaries
• Forwarding Refs
• Fragments
• Higher-Order Components
• Integrating with Other Libraries
• JSX In Depth (@vishalnagda1 )
• Optimizing Performance
• Portals (@Mayankverr ) portals page #73
• React Without ES6 (@kumari1224 )
• React Without JSX (@vishalnagda1)
• Reconciliation
• Refs and the DOM
• Render Props
• Static Type Checking
• Strict Mode
• Typechecking With PropTypes
• Uncontrolled Components
• Web Components

FAQ

• APIs and AJAX (@helios1101 )
• Babel, JSX, and Build Steps (@shobhitsingh29 ) added translations for Babel, JSX, and Build Steps #50
• Passing Functions to Components (@nnhhiilliisstt )
• Component State (@bhatvikrant )
• Styling and CSS (@PriyankaCodes99)
• File Structure (@anchal7299 ) Updated faq-structure #54
• Versioning Policy
• Virtual DOM and Internals (@bhatvikrant)

Contributing

Priority: Low

• How to Contribute
• Codebase Overview
• Implementation Notes
• Design Principles

Components

Components in src/components that have some text in them.

• CodeEditor
• CodeExample
• ErrorDecoder
• LayoutFooter
• LayoutHeader
• MarkdownPage

Additional Translations

These are not the primary translation targets.

• Blog
• Community

[arshadkazmi42]

@saranshkataria I am starting with Tutrial page

[apoorvtomar2222]

@tesseralis @arshadkazmi42 @saranshkataria

How can we differentiate that what all pages among the list have already been done ?

[arshadkazmi42]

@apoorvtomar2222 If any page is completed, it will has a check mark like below

• Done
  And if its in progress it will have the username of contributor who is working on it like below
• Page (@arshadkazmi42 )

[arshadkazmi42]

if you would like to work on any of the page translation you can comment here with the page name and we will assign that page to you.

[saranshkataria]

@arshadkazmi42 I am picking up the home page. @apoorvtomar2222 feel free to pick anything else apart from the homepage or tutorial. I think it would be great if we go sequentially though.

[gurjotsingh4398]

I would like to work on Hello World page.

[arshadkazmi42]

Go ahead

[arshadkazmi42]

@saranshkataria Home Page is still not completely translated. I have unmarked it as done.
You can try running it locally. These are the subtitles which are not translated.

• A Simple Component
• A Stateful Component
• An Application
• A Component Using External Plugins

We will mark it as done, when all these are also translated.

[saranshkataria]

@arshadkazmi42, I had mentioned in the PR that it is not complete. I wanted to put something in to kick things off. I know about the remaining sections. I had never marked it as done initially because of that. Working on those sections. Thanks though.

[arshadkazmi42]

Ok cool. I thought you missed it.
I think those are part of Home page right? Or do we have separate entries for those in the list?

We will add tick mark to every item once its {{done done}}

[saranshkataria]

They are in the home page. Also, should we split these into multiple issues instead of just one?

[arshadkazmi42]

I think this is fine. To keep track for all the Pages.

Also, I am trying to get more contributors to help us with the translations

[saranshkataria]

@arshadkazmi42 the home page is done now! Waiting for you to complete the tutorial page to have the basics done.

[arshadkazmi42]

@saranshkataria Awesome.
I am 70% done with the tutorial page. Will send a PR in a day or two

[hozefaj]

I can take a crack at the Warning section.

[arshadkazmi42]

Cool. go ahead. Which warning page you will be working on? Can you pick one, so I can assign your name next to page name

[hozefaj]

I can start with dont-call-proptypes. Do you have a timeline by which the pages need to get done?

[arshadkazmi42]

Cool. I will add your username to that page.
We don't have any fixed timelines, but if you get stuck at anything you can let us know.

[hozefaj]

Just curious if there is any long term automation plan to keep the docs in sync with the English version? Or the updates are expected to happen manually every time?

[tesseralis]

@hozefaj a bot will create PRs around once a day when it detects changes to master branch, as so:

#11

[PriyankaCodes99]

Can I translate the Styling and CSS page?

[saranshkataria]

@PriyankaCodes99 go for it! Adding your name next to it

[PriyankaCodes99]

@PriyankaCodes99 go for it! Adding your name next to it

Thanks! The work is in progress.

[AbhishekCode]

Hey, Can I translate Rendering Elements page?

[arshadkazmi42]

@AbhishekCode go ahead. I will assign your name next to the page

[AbhishekCode]

@arshadkazmi42 Thanks 👍

[Hrshk15]

@arshadkazmi42 Can I translate the react section under API REFERENCE.
And if yes , thn can u kindly tell me the procedure.

[arshadkazmi42]

@Hrshk15 Assigned API Reference > React page to you.

This is the page you need to translate
https://github.com/reactjs/hi.reactjs.org/blob/master/content/docs/reference-react.md

Translate the complete file in Hindi. Refer #2 for common translations.
Do not translate code blocks.
Once complete file is translated, send a PR for review.
There will be two phases of review. Once your PR gets approved from both the reviewers, your change will be merged.

For creating branch locally follow this
https://github.com/reactjs/hi.reactjs.org#create-a-branch

[Hrshk15]

I have tried running it locally, following the steps mentioned.
But it gives this error-

ERROR #85923 GRAPHQL

There was an error in your GraphQL query:

Cannot query field "allExampleCode" on type "Query".

Kindly suggest me what should I do.

[arshadkazmi42]

Follow the below steps

1. Clone repository
2. Run npm install in the root directory hi.reactjs.org
3. Run npm start

if you are seeing some error after this, share screenshot and error logs.

[neeraj-here]

Hi @arshadkazmi42
I am interested in translating the ReactDOMServer under API Reference. Can I do that? If yes, please guide me with the procedure.

[saranshkataria]

@neeraj-here assigned 👍

[neeraj-here]

@neeraj-here assigned 👍

After

Follow the below steps

1. Clone repository
2. Run npm install in the root directory hi.reactjs.org
3. Run npm start

if you are seeing some error after this, share screenshot and error logs.
@arshadkazmi42 @saranshkataria
I faced the same problem as by @Hrshk15 . Tried the above mentioned way but still getting a error. Here are the logs:

**HP@LAPTOP-BNE4L5IB MINGW64 ~
$ cd e:
HP@LAPTOP-BNE4L5IB MINGW64 /e
$ dir
!qhlogs.doc CodeBlocks GIMP\ 2 My\ photos System\ Volume\ Information
$RECYCLE.BIN coursera-sub Interactivity\ with\ JS New\ folder website
bootstrap DS It's\ me.rtf New\ folder\ (2) Whatsapp\ docs
cfrbackup-SSNIWRZC DS.c movies reactjs.org

HP@LAPTOP-BNE4L5IB MINGW64 /e
$ cd reactjs.org
HP@LAPTOP-BNE4L5IB MINGW64 /e/reactjs.org
$ cd hi.reactjs.org
HP@LAPTOP-BNE4L5IB MINGW64 /e/reactjs.org/hi.reactjs.org (master)
$ npm start

[email protected] start E:\reactjs.org\hi.reactjs.org
yarn dev

yarn run v1.22.5
$ gatsby develop -H 0.0.0.0
E:\reactjs.org\hi.reactjs.org\node_modules\gatsby-recipes\node_modules\graphql\jsutils\instanceOf.js:28
throw new Error("Cannot use ".concat(className, " "").concat(value, "" from another module or realm.\n\nEnsure that there is only one instance of "graphql" in the node_modules\ndirectory. If different versions of "graphql" are the dependencies of other\nrelied on modules, use "resolutions" to ensure only one version is installed.\n\nhttps://yarnpkg.com/en/docs/selective-version-resolutions\n\nDuplicate "graphql" modules cannot be used at the same time since different\nversions may have different capabilities and behavior. The data from one\nversion used in the function from another could produce confusing and\nspurious results."));
^

Error: Cannot use GraphQLInputObjectType "FileInput" from another module or realm.

Ensure that there is only one instance of "graphql" in the node_modules
directory. If different versions of "graphql" are the dependencies of other
relied on modules, use "resolutions" to ensure only one version is installed.

https://yarnpkg.com/en/docs/selective-version-resolutions

Duplicate "graphql" modules cannot be used at the same time since different
versions may have different capabilities and behavior. The data from one
version used in the function from another could produce confusing and
spurious results.
at instanceOf (E:\reactjs.org\hi.reactjs.org\node_modules\gatsby-recipes\node_modules\graphql\jsutils\instanceOf.js:28:13)
at isInputObjectType (E:\reactjs.org\hi.reactjs.org\node_modules\gatsby-recipes\node_modules\graphql\type\definition.js:168:34)
at typeMapReducer (E:\reactjs.org\hi.reactjs.org\node_modules\gatsby-recipes\node_modules\graphql\type\schema.js:290:41)
at Array.reduce ()
at typeMapReducer (E:\reactjs.org\hi.reactjs.org\node_modules\gatsby-recipes\node_modules\graphql\type\schema.js:285:34)
at Array.reduce ()
at new GraphQLSchema (E:\reactjs.org\hi.reactjs.org\node_modules\gatsby-recipes\node_modules\graphql\type\schema.js:145:28)
at Object. (E:\reactjs.org\hi.reactjs.org\node_modules\gatsby-recipes\dist\graphql-server\server.js:223:16)
at Module._compile (internal/modules/cjs/loader.js:1133:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1153:10)

success open and validate gatsby-configs - 0.188s
success load plugins - 4.133s
success onPreInit - 0.190s
success initialize cache - 0.045s
success copy gatsby files - 0.234s
warn gatsby-plugin-feed was initialized in gatsby-config.js without a title in a feed.
This means that the plugin will use the default feed title, which may not match your use case.
This behavior will be removed in the next major release of gatsby-plugin-feed.
For more info, check out: https://gatsby.dev/adding-rss-feed
success onPreBootstrap - 0.049s
success createSchemaCustomization - 0.407s
success Checking for changed pages - 0.006s
success source and transform nodes - 8.971s

ERROR

Missing onError handler for invocation 'building-schema', error was 'TypeError: (0 , _graphql.isScalarType) is not a function'. Stacktrace was 'TypeError: (0 , _graphql.isScalarType) is not a function
at TypeMapper.get (E:\reactjs.org\hi.reactjs.org\node_modules\graphql-compose\lib\TypeMapper.js:88:76)
at TypeMapper.typeFromAST (E:\reactjs.org\hi.reactjs.org\node_modules\graphql-compose\lib\TypeMapper.js:608:17)
at TypeMapper.typeFromAST (E:\reactjs.org\hi.reactjs.org\node_modules\graphql-compose\lib\TypeMapper.js:603:24)
at TypeMapper.getWrapped (E:\reactjs.org\hi.reactjs.org\node_modules\graphql-compose\lib\TypeMapper.js:105:17)
at TypeMapper.convertOutputFieldConfig (E:\reactjs.org\hi.reactjs.org\node_modules\graphql-compose\lib\TypeMapper.js:272:114)
at resolveOutputConfigAsThunk (E:\reactjs.org\hi.reactjs.org\node_modules\graphql-compose\lib\utils\configAsThunk.js:19:41)
at ObjectTypeComposer.getFieldConfig (E:\reactjs.org\hi.reactjs.org\node_modules\graphql-compose\lib\ObjectTypeComposer.js:300:58)
at E:\reactjs.org\hi.reactjs.org\node_modules\graphql-compose\lib\utils\toInputObjectType.js:44:19
at Array.forEach ()
at toInputObjectType (E:\reactjs.org\hi.reactjs.org\node_modules\graphql-compose\lib\utils\toInputObjectType.js:38:14)
at ObjectTypeComposer.getInputTypeComposer (E:\reactjs.org\hi.reactjs.org\node_modules\graphql-compose\lib\ObjectTypeComposer.js:600:84)
at E:\reactjs.org\hi.reactjs.org\node_modules\gatsby\src\schema\types\node-interface.js:22:8
at SchemaComposer.getOrCreateOTC (E:\reactjs.org\hi.reactjs.org\node_modules\graphql-compose\lib\SchemaComposer.js:382:54)
at getOrCreateNodeInterface (E:\reactjs.org\hi.reactjs.org\node_modules\gatsby\src\schema\types\node-interface.js:10:37)
at getNodeInterface (E:\reactjs.org\hi.reactjs.org\node_modules\gatsby\src\schema\types\node-interface.js:81:3)
at createSchemaComposer (E:\reactjs.org\hi.reactjs.org\node_modules\gatsby\src\schema\schema-composer.js:15:3)
at build (E:\reactjs.org\hi.reactjs.org\node_modules\gatsby\src\schema\index.js:104:26)
at buildSchema (E:\reactjs.org\hi.reactjs.org\node_modules\gatsby\src\services\build-schema.ts:19:3)'

⠴ building schema**

It seems to be indefinite as nothing happens after this.
Please guide me the solution or any alternative.

[bhatvikrant]

@neeraj-here do you have access to GitHub codespaces beta?

If not then check this blog, and open the project in code sandbox instead. Maybe this might help.

[tanishqchamola]

@saranshkataria @arshadkazmi42
Hi, can I help with translating Test Renderer page?

[ShivamPorwal02]

Hi, Can I take dont-call-proptypes page for translation ?

[arshadkazmi42]

@neeraj-here assigned 👍

After

Follow the below steps

1. Clone repository
2. Run npm install in the root directory hi.reactjs.org
3. Run npm start

if you are seeing some error after this, share screenshot and error logs.
@arshadkazmi42 @saranshkataria
I faced the same problem as by @Hrshk15 . Tried the above mentioned way but still getting a error. Here are the logs:

**HP@LAPTOP-BNE4L5IB MINGW64 ~
$ cd e:
HP@LAPTOP-BNE4L5IB MINGW64 /e
$ dir
!qhlogs.doc CodeBlocks GIMP\ 2 My\ photos System\ Volume\ Information
$RECYCLE.BIN coursera-sub Interactivity\ with\ JS New\ folder website
bootstrap DS It's\ me.rtf New\ folder\ (2) Whatsapp\ docs
cfrbackup-SSNIWRZC DS.c movies reactjs.org

HP@LAPTOP-BNE4L5IB MINGW64 /e
$ cd reactjs.org
HP@LAPTOP-BNE4L5IB MINGW64 /e/reactjs.org
$ cd hi.reactjs.org
HP@LAPTOP-BNE4L5IB MINGW64 /e/reactjs.org/hi.reactjs.org (master)
$ npm start

[email protected] start E:\reactjs.org\hi.reactjs.org
yarn dev

yarn run v1.22.5
$ gatsby develop -H 0.0.0.0
E:\reactjs.org\hi.reactjs.org\node_modules\gatsby-recipes\node_modules\graphql\jsutils\instanceOf.js:28
throw new Error("Cannot use ".concat(className, " "").concat(value, "" from another module or realm.\n\nEnsure that there is only one instance of "graphql" in the node_modules\ndirectory. If different versions of "graphql" are the dependencies of other\nrelied on modules, use "resolutions" to ensure only one version is installed.\n\nhttps://yarnpkg.com/en/docs/selective-version-resolutions\n\nDuplicate "graphql" modules cannot be used at the same time since different\nversions may have different capabilities and behavior. The data from one\nversion used in the function from another could produce confusing and\nspurious results."));
^

Error: Cannot use GraphQLInputObjectType "FileInput" from another module or realm.

Ensure that there is only one instance of "graphql" in the node_modules
directory. If different versions of "graphql" are the dependencies of other
relied on modules, use "resolutions" to ensure only one version is installed.

https://yarnpkg.com/en/docs/selective-version-resolutions

Duplicate "graphql" modules cannot be used at the same time since different
versions may have different capabilities and behavior. The data from one
version used in the function from another could produce confusing and
spurious results.
at instanceOf (E:\reactjs.org\hi.reactjs.org\node_modules\gatsby-recipes\node_modules\graphql\jsutils\instanceOf.js:28:13)
at isInputObjectType (E:\reactjs.org\hi.reactjs.org\node_modules\gatsby-recipes\node_modules\graphql\type\definition.js:168:34)
at typeMapReducer (E:\reactjs.org\hi.reactjs.org\node_modules\gatsby-recipes\node_modules\graphql\type\schema.js:290:41)
at Array.reduce ()
at typeMapReducer (E:\reactjs.org\hi.reactjs.org\node_modules\gatsby-recipes\node_modules\graphql\type\schema.js:285:34)
at Array.reduce ()
at new GraphQLSchema (E:\reactjs.org\hi.reactjs.org\node_modules\gatsby-recipes\node_modules\graphql\type\schema.js:145:28)
at Object. (E:\reactjs.org\hi.reactjs.org\node_modules\gatsby-recipes\dist\graphql-server\server.js:223:16)
at Module._compile (internal/modules/cjs/loader.js:1133:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1153:10)

success open and validate gatsby-configs - 0.188s
success load plugins - 4.133s
success onPreInit - 0.190s
success initialize cache - 0.045s
success copy gatsby files - 0.234s
warn gatsby-plugin-feed was initialized in gatsby-config.js without a title in a feed.
This means that the plugin will use the default feed title, which may not match your use case.
This behavior will be removed in the next major release of gatsby-plugin-feed.
For more info, check out: https://gatsby.dev/adding-rss-feed
success onPreBootstrap - 0.049s
success createSchemaCustomization - 0.407s
success Checking for changed pages - 0.006s
success source and transform nodes - 8.971s

ERROR

Missing onError handler for invocation 'building-schema', error was 'TypeError: (0 , _graphql.isScalarType) is not a function'. Stacktrace was 'TypeError: (0 , _graphql.isScalarType) is not a function
at TypeMapper.get (E:\reactjs.org\hi.reactjs.org\node_modules\graphql-compose\lib\TypeMapper.js:88:76)
at TypeMapper.typeFromAST (E:\reactjs.org\hi.reactjs.org\node_modules\graphql-compose\lib\TypeMapper.js:608:17)
at TypeMapper.typeFromAST (E:\reactjs.org\hi.reactjs.org\node_modules\graphql-compose\lib\TypeMapper.js:603:24)
at TypeMapper.getWrapped (E:\reactjs.org\hi.reactjs.org\node_modules\graphql-compose\lib\TypeMapper.js:105:17)
at TypeMapper.convertOutputFieldConfig (E:\reactjs.org\hi.reactjs.org\node_modules\graphql-compose\lib\TypeMapper.js:272:114)
at resolveOutputConfigAsThunk (E:\reactjs.org\hi.reactjs.org\node_modules\graphql-compose\lib\utils\configAsThunk.js:19:41)
at ObjectTypeComposer.getFieldConfig (E:\reactjs.org\hi.reactjs.org\node_modules\graphql-compose\lib\ObjectTypeComposer.js:300:58)
at E:\reactjs.org\hi.reactjs.org\node_modules\graphql-compose\lib\utils\toInputObjectType.js:44:19
at Array.forEach ()
at toInputObjectType (E:\reactjs.org\hi.reactjs.org\node_modules\graphql-compose\lib\utils\toInputObjectType.js:38:14)
at ObjectTypeComposer.getInputTypeComposer (E:\reactjs.org\hi.reactjs.org\node_modules\graphql-compose\lib\ObjectTypeComposer.js:600:84)
at E:\reactjs.org\hi.reactjs.org\node_modules\gatsby\src\schema\types\node-interface.js:22:8
at SchemaComposer.getOrCreateOTC (E:\reactjs.org\hi.reactjs.org\node_modules\graphql-compose\lib\SchemaComposer.js:382:54)
at getOrCreateNodeInterface (E:\reactjs.org\hi.reactjs.org\node_modules\gatsby\src\schema\types\node-interface.js:10:37)
at getNodeInterface (E:\reactjs.org\hi.reactjs.org\node_modules\gatsby\src\schema\types\node-interface.js:81:3)
at createSchemaComposer (E:\reactjs.org\hi.reactjs.org\node_modules\gatsby\src\schema\schema-composer.js:15:3)
at build (E:\reactjs.org\hi.reactjs.org\node_modules\gatsby\src\schema\index.js:104:26)
at buildSchema (E:\reactjs.org\hi.reactjs.org\node_modules\gatsby\src\services\build-schema.ts:19:3)'

⠴ building schema**

It seems to be indefinite as nothing happens after this.
Please guide me the solution or any alternative.

try delete node-modules folder and package-lock.json or yarn.lock then try running yarn and then yarn dev

[arshadkazmi42]

@saranshkataria @arshadkazmi42
Hi, can I help with translating Test Renderer page?

sure @tanishqchamola . page assigned

[arshadkazmi42]

Hi, Can I take dont-call-proptypes page for translation ?

@ShivamPorwal02 page assigned

[vivek80801]

Can I also help in translation of reactjs?

[vieee]

Hi, can I help with translating the Hooks API reference page within the Hooks section..?

[piyush9311]

I would like to work upon the issue #26 and translate "State and Lifecycle".

[Himnashu]

Hi @arshadkazmi42, can I help with translating the Reconciliation page?

[vishalnagda1]

@tesseralis I would like to translate React Without JSX page in Advanced Guides.
Please assign it to me.

[arshadkazmi42]

@tesseralis I would like to translate React Without JSX page in Advanced Guides.

Please assign it to me.

@vishalnagda1 Go ahead

[vishalnagda1]

@arshadkazmi42 Completed the last task. Please review the PR #163
Next I would like to take JSX In Depth page in Advanced Guides for translation.

[vishalnagda1]

@arshadkazmi42 Should I proceed with JSX In Depth page in Advanced Guides for translation, or should I wait for previous PR to get merge before starting with new one?

[arshadkazmi42]

@vishalnagda1 sure go ahead

[gaearon]

Thanks to everyone who contributed to this iteration!
Here is the issue for the new website translation: #168.