reactjs / he.react.dev Goto Github PK

Maintainer List

• @galnir
• @galtalmor
• @itayyehezkel

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 (@tesseralis) #1

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 (@gmadar) #4
• Tutorial (@galtalmor) #10

Basics

• Hello World (@bromy) #8
• Introducing JSX (@galtalmor) #42
• Rendering Elements (@dormd) #21
• Components and Props (@galtalmor) #20
• State and Lifecycle (@galtalmor) #25
• Handling Events (@galtalmor) #26
• Conditional Rendering (@galtalmor) #30
• Lists and Keys (@itayyehezkel) #36
• Forms (@galtalmor) #32
• Lifting State Up (@galtalmor) #34
• Composition vs Inheritance (@dormd) #40
• Thinking in React (@galnir) #14

API Reference

• React
• React.Component (@itzikya) #65
• ReactDOM (@galtalmor) #45
• ReactDOMServer (@galtalmor) #43
• DOM Elements (@galnir) #46
• SyntheticEvent (@galnir) #51
• Test Utilities (@galnir) #52
• Shallow Renderer (@itayyehezkel) #39
• Test Renderer (@galtalmor) #93
• JS Environment Requirements (@itayyehezkel) #37
• Glossary (@galtalmor) #49

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 (@galtalmor) #10
• docs/nav.yml (@galtalmor) #13

Next Steps

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

Installation

• Getting Started (@galtalmor) #15
• Add React to a Website (@galnir) #51
• Create a New React App (@galnir) #55
• CDN Links (@dormd) #31

Hooks

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

• Introducing Hooks (@itayyehezkel) #18 (@galnir) #265
• Hooks at a Glance (@galnir ) #94
• Using the State Hook (@galnir) #57
• Using the Effect Hook (@galnir) #73
• Rules of Hooks (@galnir) #84
• Building Your Own Hooks (@galnir) #101
• Hooks API Reference (@galnir) #113
• Hooks FAQ (@galnir)

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 (@galnir)
• invalid-aria-prop (@itayyehezkel) #112
• invalid-hook-call-warning
• legacy-factories
• refs-must-have-owner
• special-props (@itayyehezkel) #111
• unknown-prop

Advanced Guides

• Accessibility (@rgrnwd) #71
• Code-Splitting (@rgrnwd) #92
• Context (@rgrnwd) #77
• Error Boundaries (@rgrnwd) #74
• Forwarding Refs (@rgrnwd) #77
• Fragments (@itayyehezkel) #109
• Higher-Order Components (@rgrnwd) #95
• Integrating with Other Libraries
• JSX In Depth
• Optimizing Performance
• Portals
• React Without ES6
• React Without JSX (@tsehori)
• Reconciliation
• Refs and the DOM
• Render Props
• Static Type Checking
• Strict Mode
• Typechecking With PropTypes
• Uncontrolled Components (@itayyehezkel) #110
• Web Components

FAQ

• APIs and AJAX (@itayyehezkel) #62
• Babel, JSX, and Build Steps (@itayyehezkel) #63
• Passing Functions to Components (@orrsteinberg) #172
• Component State
• Styling and CSS (@itayyehezkel) #64
• File Structure (@galnir) #44
• Versioning Policy
• Virtual DOM and Internals

Contributing

Priority: Low

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

Components

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

• CodeEditor (@itayyehezkel) #27
• CodeExample (@itayyehezkel) #28
• ErrorDecoder (@galnir) #23
• LayoutFooter (@galtalmor) #13
• LayoutHeader (@galtalmor) #11
• MarkdownPage (@itayyehezkel) #19

Additional Translations

These are not the primary translation targets.

• Blog
• Community

Hello,

I have a background in technical writing and I am currently working as a developer and instructor in web technologies, including React.

I am eager to contribute to the Hebrew translation of the new React documentation. I have noticed that the repository is lagging behind by 13 PRs, some from as far back as 3 months ago, including important updates for RTL support which would be beneficial to have integrated before commencing with the translation work.

If you are seeking assistance with maintaining this project, I would be more than happy to offer my expertise in this area.

Thank you for your consideration and I am looking forward to potentially collaborating with you.

Hey guys,

I think we should stay synchronized by adding a style guide as @tesseralis mentioned in her issue. So I made a few translations which makes sense for me, but feel free to suggest something else. After we all agree about the common language I'll create TRANSLATION.md file.

Style Guide

Maintainer List

• @galnir
• @galtalmor
• @itayyehezkel

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:

• Quick Start (@tesseralis) #12345

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

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
  • Thinking in React

• Installation

  • Start a New React Project
  • Add React to an Existing Project
  • Editor Setup (@galnir) #278
  • React Developer Tools (@galnir) #279

• Describing the UI

  • Your First Component
  • Importing and Exporting Components
  • Writing Markup with JSX
  • JavaScript in JSX with Curly Braces
  • Passing Props to a Component
  • Conditional Rendering
  • Rendering Lists
  • Keeping Components Pure

• Adding Interactivity

  • Responding to Events
  • State: A Component's Memory
  • Render and Commit
  • State as a Snapshot
  • Queueing a Series of State Updates
  • Updating Objects in State
  • Updating Arrays in State

• Managing State

  • Reacting to Input with State
  • Choosing the State Structure
  • Sharing State Between Components
  • Preserving and Resetting State
  • Extracting State Logic into a Reducer
  • Passing Data Deeply with Context
  • Scaling Up with Reducer and Context

• Escape Hatches

  • Referencing Values with Refs
  • 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 (@lidoravitan)
  • useContext (@AvielBitton)
  • useDebugValue
  • useDeferredValue
  • useEffect
  • useId
  • useImperativeHandle
  • useInsertionEffect
  • useLayoutEffect (@Yaronglp)
  • 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

Congrats on almost finishing the Hebrew docs! There are just a couple more things we need to do before we can mark the core pages as complete!

• Change the DocSearch API key #69 . One of the maintainers needs to sign up for DocSearch
• Go over the pages of the site one last time to check for consistency

In the main page we may see:

I think that as Javascript being a world-reknowned programming language, the fifth line should write Javascript and not Javascript in Hebrew!

Which gender should we use for the translation