Malayalam Translation Progress

[gaearon]

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:

- [ ] 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 - @asimkt feat(quickstart): Quick start page  #11

  • Tutorial: Tic Tac Toe
  • Thinking in React

• Installation - @dev-thakku Translate learn/installation #6

  • Start a New React Project
  • Add React to an Existing Project
  • Editor Setup
  • React Developer Tools

• Describing the UI

  • Your First Component (@JACOBIN-SCTCS)
  • 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 (@Amjad-RA)

  • 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
  • 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:

• @adarshm07
• @asimkt

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.

[JACOBIN-SCTCS]

I would like to take up the translation of the page Describing the UI/ Your First Component

[asimkt]

@JACOBIN-SCTCS Please share your PR.

@gaearon I will take care of updating the issue at #2. Could you please close this issue.

[JACOBIN-SCTCS]

@asimkt I think I do not have permission to close this issue. can you do that

[asimkt]

We will wait for @gaearon to do that. Meanwhile we can move the discussion to #2

[gaearon]

@asimkt

What was the purpose of creating a second issue? The issue needs to have "Translation Progress" verbatim in the title to get picked up by our translation progress website code. It also needs to have special comments like <!-- MAIN_CONTENT --> which this issue has and yours doesn't.

It seems like the main problem is that you don't have admin rights to the repo because you have not accepted the invite. Please accept the invite and then use this issue instead of #2. Alternatively, please accept the invite and close this issue, but then make sure that #2 has both the correct title and the special comments to get picked up by our script. You'd also have to rename this issue to not get picked up by the script.

Hope this helps!

[asimkt]

Thanks @gaearon.

Yes, I didn't have edit access to update this issue since I missed the invite. So I checked some other repo, saw people creating another issue, and followed suit.

I've accepted the invitation and closed the other issue now.

[dev-thakku]

Hi @asimkt, @adarshm07,
I would like to translate the learn/Installation page. Could you please assign me that?

[asimkt]

@dev-thakku Done. Please share your MR shortly.

[dev-thakku]

@dev-thakku Done. Please share your MR shortly.

Could you please check the PR #6?

[Amjad-RA]

Hi @gaearon, @asimkt, @JACOBIN-SCTCS
I am interested in translating Adding Interactivity and would like to take up the task.

[asimkt]

Hey @Amjad-RA Please free to contribute and create an MR as mentioned as per the documentation. Let me know if you need any help. If you reply with a confirmation I will update the checklist.

[Amjad-RA]

Hey @Amjad-RA Please free to contribute and create an MR as mentioned as per the documentation. Let me know if you need any help. If you reply with a confirmation I will update the checklist.

@asimkt Please update the checklist and lock the block

[Amjad-RA]

Hello @asimkt, based on our previous conversations in the old PRs, I have concluded that we need to create documentation for beginners who may have limited exposure to English and programming terminologies. Therefore, we should use simple Malayalam and focus on explaining things in a way that a non-technical person can easily understand, rather than just providing a word-by-word translation. Do you agree with this approach?

I also have a suggestion. If possible, we can create and maintain a glossary for common terminologies. This will make the documentation more readable and consistent.
eg:-
User - ആപ്പ് ഉപയോഗിക്കുന്ന ആൾ/ ഉപഭോക്താവ് / യൂസർ -(This is just an example. We need to discuss and finalize the most appropriate wording.)

[asimkt]

@Amjad-RA Totally agree on this point. 🙌

Let's create a glossary. I'm only curious about the timing of when to create. Sharing some thoughts: This is the current status of documentation for reference.

• Here, I've used common terms like components, prop as English words. Should we continue using that? Because eventually developers have to get all other contents in English. If we keep Malayalam words for that, they may have this extra learning curve.

These are the other common words I can think of which needs to be in a glossary:

• Application
• Mockup
• Design
• Programming
• Tutorial

May be we can cover some basic pages and get an alignment on the terminologies later? Otherwise, I feel like we may get delayed on the details instead of putting in the time and effort more efficiently. Once we've covered all the basics, will we create the glossary and share it with future contributors? Please share your thoughts.

[Amjad-RA]

@asimkt, Could you please check the PR #51?

[asimkt]

@asimkt, Could you please check the PR #51?

Looks good as a starting point. As mentioned in that MR, I suppose we will reword some of the section? Some "കട്ടി മലയാളം“ may not work for our usual audiencr. 😄

[Amjad-RA]

@asimkt, Could you please check the PR #51?

Looks good as a starting point. As mentioned in that MR, I suppose we will reword some of the section? Some "കട്ടി മലയാളം“ may not work for our usual audiencr. 😄

Yeah sure, will recheck😄

[tzzkenz]

I would like to take up translation of Importing and Exporting Components