reactjs/ur.reactjs.org

(Work in progress) React documentation website in Urdu

reactjs.org

This repo contains the source code and documentation powering reactjs.org.

Getting started

Prerequisites

1. Git
2. Node: any 12.x version starting with v12.0.0 or greater
3. Yarn v1: See Yarn website for installation instructions
4. A fork of the repo (for any contributions)
5. A clone of the reactjs.org repo on your local machine

Installation

1. cd ur.reactjs.org to go into the project root
2. yarn to install the website's npm dependencies

Running locally

1. yarn dev to start the hot-reloading development server (powered by Gatsby)
2. open http://localhost:8000 to open the site in your favorite browser

Contributing

Guidelines

The documentation is divided into several sections with a different tone and purpose. If you plan to write more than a few sentences, you might find it helpful to get familiar with the contributing guidelines for the appropriate sections.

Create a branch

1. git checkout main from any folder in your local ur.reactjs.org repository
2. git pull origin main to ensure you have the latest main code
3. git checkout -b the-name-of-my-branch (replacing the-name-of-my-branch with a suitable name) to create a branch

Make the change

1. Follow the "Running locally" instructions
2. Save the files and check in the browser
3. Changes to React components in src will hot-reload
4. Changes to markdown files in content will hot-reload
5. If working with plugins, you may need to remove the .cache directory and restart the server

Test the change

1. If possible, test any visual changes in all latest versions of common browsers, on both desktop and mobile.
2. Run yarn check-all from the project root. (This will run Prettier, ESLint, and Flow.)

Push it

1. git add -A && git commit -m "My message" (replacing My message with a commit message, such as Fix header logo on Android) to stage and commit your changes
2. git push my-fork-name the-name-of-my-branch
3. Go to the reactjs.org repo and you should see recently pushed branches.
4. Follow GitHub's instructions.
5. If possible, include screenshots of visual changes. A preview build is triggered after your changes are pushed to GitHub.

Translation

If you are interested in translating reactjs.org, please see the current translation efforts at translations.reactjs.org.

If your language does not have a translation and you would like to create one, please follow the instructions at reactjs.org Translations.

Troubleshooting

• yarn reset to clear the local cache

License

Content submitted to reactjs.org is CC-BY-4.0 licensed, as found in the LICENSE-DOCS.md file.

ur.reactjs.org's Issues

Translate Handling Events Page.

I would like to contribute and translate this page.

Thanks!

Add RTL support

Since Urdu is written right-to-left, one of the important things is to give these docs a RTL support.

I started with few bits in this regard in what currently is a throw-away branch for issue #2 . It seems like a relatively straightforward approach to achieve that. This work does not block anything else around it, especially translation of content. I would suggest to keep it like so.

I also checked other projects with RTL requirements such as Arabic And Persian. There are quite a few things to learn from those too. Please feel free to pick this if you want to have a go. If no one picks it then I'll extend my work into this in few days.

Helpful resources

• reactjs/ar.react.dev#8

Glossary - فہرست

Adding a list of commonly used translations

Term	Translation
Apps	ایپس
Browser	براوزر
Component	جزو
Declarative	اعلامیہ
Elements	عناصر
Editor	مدیر
Immutability	ناقابل تغیر
Locally	مقامی طور پر
Method	طریقہ
Overview	جائزہ
Playgrounds	کھیل کا میدان
Step-by-step	قدم باقدم
Tutorial	سبق
Text	متن
Try it on Codepen	میں دیکھیں CodePen
Value	حاصل
View	ملاحظہ کریں

Content that does not need to be translated:

No translation required
API
array
bundle
class
constructor
context
Create React App
DOM
fragments
HTML
Hooks
JavaScript
MDN
Tick
package
props
portal
Parent
Render
ref
React
React Native
strings
state
Web（Encounter capitalized Web, don't translate）
widgets
UI
key

Above list is heavily based on the lists in Hindi and Arabic translation projects.

Linux Urdu Translation? Linux Manto

Anyone know anyone who would be interested, here is the link:
https://github.com/pakistan-dev-for-covid-19/Linux-Manto

Linux-Manto

Linux Transaltion into Urdu

Based on:

-> GNU
-> Linux
-> Ubuntu/Mint

Saadat Hasan Manto
https://en.wikipedia.org/wiki/Saadat_Hasan_Manto

Name: Linux Manto (Manto Written in Urdu)
Reason: Manto sounds simliar to ubuntu or ubuntu based distros
Logo

Code Name: Pyasa Kawa (Thirsty Crow) Based on 20.04 / Linux Manto 20.04
I am starting working on this project out of neccisity so hence the name Thristy Crow

Logo Name: Linux Manto

Code names: Urdu writers, poets, artists (First version is Manto)

Translate Conditional Rendering page

cc @asheerrizvi

[Beta] Translate React docs

Hi everyone,

Here is the list of pages from new beta docs that will be translated into Urdu in this repo.

React Docs Beta

More information at reactjs/react.dev#4135

The new beta docs currently live inside beta directory.

• ✅ Installation (note: a lot of content here is similar to old website)
  • ✅ Start a New React Project
  • ✅ Add React to a Website
  • ✅ Editor Setup
  • ✅ React Developer Tools
• 🔴 Quick Start (don't translate the index page yet, it will change)
  • ✅ Thinking in React
• 🔴 Describing the UI (don't translate the index page yet, it might change)
  • ✅ 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 (don't translate the index page yet, it might change)
  • ✅ 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 (don't translate the index page yet, it might change)
  • ✅ 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 (not written yet)
  • ✅ Referencing Values with Refs
  • ✅ Manipulating the DOM with Refs

[Beta] Add rtl support in beta docs

Helpful resource https://github.com/reactjs/ar.reactjs.org/pull/8/files

State and Lifecycle

Translate State ad Lifecycle to Urdu

Translate Introducing JSX page

Translate Hello World page

Tutorial Page Urdu Translation

Need to Translate Tutorial page to urdu.

Add guidelines, style guide and glossary

This is a place for ideas and discussions around translation guidelines, glossary and possibly a style guide (low priority).

Translate Lists and Keys page

I want to work on the translation of this page /docs/lists-and-keys.html
cc: @jabranr

.md file to urdu converter

Hi guy's ! this is not a issue but a contribution to all urdu docs .
i have created a vscode extension for ur.reactjs.org community this extension will automatically convert .md files written in english or any other language to urdu .
Extension name : md2urdu (you can simply install it from extension panel in vscode)
github : https://github.com/viveksharmaui/.md2urdu-vscode-extension
vscode marketplace : https://marketplace.visualstudio.com/items?itemName=vivek.md2urdu
Extension activation command : ctrl+shift+p (convert any text in .md file to urdu)
I have tested this extension and it is working good ,
If you wanna contribute you are alway's welcome .
Extension is written in typescript

.

Home Page

Components and Props

I want to translate components and props docs in urdu .

Urdu Translation Progress

Maintainer List

• @jabranr
• @armujahid
• @ahmadawais
• @abdullah1908

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
• RTL Support (#4)

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 (@Sanaullahbugti) #9
• Tutorial (@shahzad31) #10

Basics

• Hello World (@jabranr) #2
• Introducing JSX (@arximughal) #5
• Rendering Elements (@owais4321) #11
• Components and Props (@viveksharmaui) #13
• State and Lifecycle (@aaftab1441) #15
• Handling Events (#22)
• Conditional Rendering (@asheerrizvi) (#26)
• Lists and Keys
• Forms
• Lifting State Up
• Composition vs Inheritance
• Thinking in React

API Reference

• React
• React.Component
• ReactDOM
• ReactDOMServer
• DOM Elements
• SyntheticEvent
• Test Utilities
• Shallow Renderer
• Test Renderer
• JS Environment Requirements
• Glossary

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
• Add React to a Website
• Create a New React App
• CDN Links

Hooks

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

• Introducing Hooks
• Hooks at a Glance
• Using the State Hook
• Using the Effect Hook
• Rules of Hooks
• Building Your Own Hooks
• Hooks API Reference
• Hooks FAQ

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
• 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
• Optimizing Performance
• Portals
• React Without ES6
• React Without JSX
• Reconciliation
• Refs and the DOM
• Render Props
• Static Type Checking
• Strict Mode
• Typechecking With PropTypes
• Uncontrolled Components
• Web Components

FAQ

• APIs and AJAX
• Babel, JSX, and Build Steps
• Passing Functions to Components
• Component State
• Styling and CSS
• File Structure
• 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
• CodeExample
• ErrorDecoder
• LayoutFooter
• LayoutHeader
• MarkdownPage

Additional Translations

These are not the primary translation targets.

• Blog

Community

• Courses (@mhkasif) #21

Urdu translation no longer being maintained

@jabranr are you no longer maintaining the repo? can i be a maintainer in the repo.

Translate Courses page

Hello members,

I would like to play my part in translating content/community files.
out of which I've translated courses.md file,
and looking forward to translate more.

It would be great if you give me a chance.

Thanks

Translating Rendering Elements page

I want to translate rendering Elements page into Urdu

Update layout and styling to comply with RTL

Good example for this are Arabic translation or any other RTL based translations. The objective is to use CSS mostly for this and HTML changes are for any last thing that cannot be achieved by HTML.

This would provide a readable layout for the pages currently being translated and also better output for reviewing a pull request.