reactjs / hi.react.dev Goto Github PK

Starter code from CodeSandbox not loading in Production (Current) release

Link: https://hireactjsorg.fbopensource.vercel.app/tutorial/tutorial.html#inspecting-the-starter-code

So hey,
I am Akshit and I am from India
I want to help you guys by translating the website to a Hindi website
so I wanted to ask how is it done and what all has to be done because I am not able to understand the process given in the README.md file, so can anyone explain me what all do we have to do exactly

रिएक्ट => React

we are not translating React word

Originally posted by @arshadkazmi42 in #169 (comment)

The current translation for "todo" in the example description seems little off from real definition. Tried to add the right work phonetically.

Current -> टोडो
Correct -> टूडू

Shall I work on it and improve it?

Let's integrate Circle CI similar to Japanese translation repository

https://github.com/reactjs/ja.reactjs.org/tree/master/.circleci

Adding a list of commonly used translations

Content that does not need to be translated:

.

https://github.com/reactjs/hi.reactjs.org/blob/master/content/docs/rendering-elements.md

Here Text is used as it is but it should be written as टेक्स्ट according to hindi glossary as decide in #2

The homepage of the reactjs project in the Hindi Language has a translation that is not proper.
On, https://hi.reactjs.org/ ,

It says React Native का उपयोग करके पावर मोबाइल ऐप भी बना सकते हैं। which is a wrong translation of the same text on the english version that says and power mobile apps using React Native. It can be simply translated to React Native का उपयोग करके मोबाइल एप्प्स भी बना सकते हैं।. Will be happy to send a PR for this if you all also feel that this issue warrants attention.

we need a global accepted open source tool which can convert English word to Hindi,
itself convertes filters words which need to be get converted or not,
it could save alot of time,
knowledge sharing between all contributors,
new beginners get attracted too,
it will make development fast and easy,
Not just for react conversion it could help to all different upcoming libraries, in future

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) #3 #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 ) #3 #6
• Tutorial (@arshadkazmi42 ) #8

Basics

• Hello World (@gurjotsingh4398 ) #13
• Introducing JSX (@arshadkazmi42 ) #12
• Rendering Elements (@AbhishekCode && @saranshkataria ) #21 #41
• Components and Props (@helios1101 ) #24
• State and Lifecycle #26
• Handling Events (@yashguptaz ) #27
• Conditional Rendering (@kambleaa007) #43
• Lists and Keys (@anchal7299 ) #25
• Forms (@aashirwadgupta ) #22 + (New PR)
• Lifting State Up (@SambhavSacheti ) #30
• Composition vs Inheritance (@apoorvtomar2222) #28
• Thinking in React (@mayank-gangwal )

API Reference

• React (@Hrshk15 )
• React.Component #76
• ReactDOM (@charBap ) #31
• ReactDOMServer (@neeraj-here)
• DOM Elements (@rao123dk )
• SyntheticEvent (@ps0305 ) #66
• Test Utilities (@paramaggarwal ) #45
• Shallow Renderer (@vermasachin && @arshadkazmi42 ) #44
• Test Renderer (@tanishqchamola )
• JS Environment Requirements (@AlokTakshak) #47
• Glossary (@AlokTakshak) #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 ) #17
• Add React to a Website (@NorinMp143 ) #65
• Create a New React App (@vishalsodani ) #52
• CDN Links (@AninditaBasu ) #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 ) #58
• Using the State Hook (@AlokTakshak )
• Using the Effect Hook (@anoopsingh1996 )
• Rules of Hooks (@chandrakantnaik789 )
• Building Your Own Hooks (@visshaljagtap ) #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 ) #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 ) #50
• Passing Functions to Components (@nnhhiilliisstt )
• Component State (@bhatvikrant )
• Styling and CSS (@PriyankaCodes99)
• File Structure (@anchal7299 ) #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

Please note that the internal Search bar and the headings in the right-hand sidebar are shifting a bit:
I am not sure if this is intentional. If it is please ignore. 🙂

Issue

• Merge Conflict Head trail needs to be removed from Documentation route
• Link: https://hireactjsorg.fbopensource.vercel.app/tutorial/tutorial.html#inspecting-the-starter-code
  

For reviewing we follow this process.

• Add the list of all the section names (in english) in the pull request description, which reviewer will mark check as and when the review of each section is getting completed (For reference check this PR #17 )
• You should not resolve review feedback, you can add a comment or an 👍 emoji to every review comment once it's resolved and pushed.
• A reviewer will review the changes and resolve the conversations

Review Phases

• Currently we have two phases of review
  • First review is done by Arshad (@arshadkazmi42 )
  • Second review is done by Saransh (@saranshkataria )

ReactJs - Hindi Documentation - New Site

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

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

  • Tutorial: Tic Tac Toe (@saurabhsri108 )
  • Thinking in React (@USKhokhar )

• Installation (@khizarq313 )

  • Start a New React Project (@Johnn837 )
  • Add React to an Existing Project
  • Editor Setup (@Subramanyarao11 )
  • React Developer Tools (@Anishpras ) #174

• Describing the UI

  • Your First Component (@Akshit1025 ) #204
  • Importing and Exporting Components (@ujvaljoshi )
  • Writing Markup with JSX (@Anku5hk ) #198
  • JavaScript in JSX with Curly Braces (@lucifertrj ) #175
  • Passing Props to a Component (@sanskar-mk2 ) #199
  • Conditional Rendering (@sanchit36 ) #176 #177
  • Rendering Lists (@lucifertrj )
  • Keeping Components Pure (@rajpatel17-bot )

• Adding Interactivity

  • Responding to Events (@karanthek2002 )
  • State: A Component's Memory (@MayurSMahajan ) #209
  • Render and Commit (@Rohan-Makwana ) #179
  • State as a Snapshot (@PriyankaBelhekar77 )
  • Queueing a Series of State Updates (@anaskhan28 )
  • Updating Objects in State (@Akshat2Jain ) #211
  • Updating Arrays in State (@DeepshikaS )

• Managing State

  • Reacting to Input with State (@Kalyan-velu )
  • Choosing the State Structure (@BrijenMakwana ) #221
  • Sharing State Between Components (@BryanRonad ) #212
  • Preserving and Resetting State
  • Extracting State Logic into a Reducer (@GyanPrakashRaj )
  • Passing Data Deeply with Context
  • Scaling Up with Reducer and Context

• Escape Hatches

  • Referencing Values with Refs (@khizarq313 ) #229
  • Manipulating the DOM with Refs
  • Synchronizing with Effects
  • You Might Not Need an Effect
  • Lifecycle of Reactive Effects
  • Separating Events from Effects
  • Removing Effect Dependencies
  • Reusing Logic with Custom Hooks

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

When ever i am trying to start the project using yarn dev it throws the attached error

OS- Ubuntu 18.04
node- 10.16.3
yarn- 1.19.1