Coder Social home page Coder Social logo

reactjs / az.react.dev Goto Github PK

View Code? Open in Web Editor NEW
43.0 8.0 26.0 151.34 MB

🇦🇿 React documentation website in Azerbaijani

Home Page: https://az.react.dev

License: Creative Commons Attribution 4.0 International

JavaScript 32.40% CSS 7.39% HTML 0.28% Shell 0.01% TypeScript 59.92%
reactjs translation azerbaijani-translation azerbaijan

az.react.dev's Introduction

React Azerbaijani Documentation

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

🇦🇿 Azerbaijani Version | 📖 Glossary | 💅 Style Guide | ✅ Progress: 100%

Getting started

Prerequisites

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

Installation

  1. cd az.react.dev to go into the project root
  2. yarn to install the website's npm dependencies

Running locally

  1. yarn dev to start the development server (powered by Next.js)
  2. open http://localhost:3000 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 az.react.dev 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. (This will run Prettier, ESLint and validate types.)

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 az.react.dev 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 az.react.dev, please see the current translation efforts at isreacttranslatedyet.com.

If you would like to add a new term or change an existing one please change make you changes to glossary.md file in the repository and make a PR. In this documentation, all the terms are consistent across the documentation; so, when making a PR, let us know the decision behind the change.

License

Content submitted to az.react.dev is CC-BY-4.0 licensed, as found in the LICENSE-DOCS.md file.

az.react.dev's People

Contributors

acdlite avatar alexkrolick avatar azizaismayilova avatar bvaughn avatar chenglou avatar daniel15 avatar danilowoz avatar dependabot[bot] avatar gaearon avatar gasimgasimzada avatar harish-sethuraman avatar jimfb avatar koba04 avatar kohei-takata avatar lex111 avatar marocchino avatar mcsheffrey avatar petehunt avatar react-translations-bot avatar reactjs-translation-bot avatar rickhanlonii avatar robhrt7 avatar sebmarkbage avatar smikitky avatar sophiebits avatar tesseralis avatar vjeux avatar yangshun avatar zpao avatar zqran avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

az.react.dev's Issues

New Azerbaijani Translation Progress

Maintainer List

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:

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 (@vugartaghiyev)

  • Installation (@nasirmovlamov)

    • Start a New React Project (@nasirmovlamov)
    • Add React to an Existing Project
    • Editor Setup
    • React Developer Tools
  • 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
    • 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.

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

Awaiting Reviews

Terms Question: Should we be translating React terms such as "props", "state", and "lifecycle"?

I am asking this because, currently I have translated these values and as I read through them, it makes it harder to catch the actual name of it. My suggestion it to keep singular values and add azerbaijani suffixes:

  • prop and proplar
  • state and state-li komponent (stateful component)
  • lifecycle metodları (lifecycle methods)

What do you guys think? In documentation and tutorial, we are already explaining what they are in Azerbaijani using simpler terms. So, I think explaining them in Azerbaijani while making people remember the naming this way would make future conversations easier in React community.

Translate style guide

I have merged the style guide and localized the source codes, which is enough for now but it is important for us to translate this guide in Azerbaijani for newcomers.

Azerbaijani Translation Progress

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. Take only one page at a time.
  3. Clone this repo, translate your page, and submit a pull request!

Before contributing, read the glossary 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:

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.

Basics

API Reference

Navigation

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

Next Steps

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

Installation

Hooks

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

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.

Advanced Guides

FAQ

Testing

Concurrent Mode (Experimental)

Contributing

Priority: Low

Components

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

Other

Config

Translation of "pattern"

Should we keep "pattern" in English or we can translate it as "şablon" in Azerbaijani and add to the Glossary in any case.

Discord Server

For the time being, aside from PRs and issues, in order to communicate more efficiently for things such as what words to use or just general talk, I have created a Discord server: https://discord.gg/qvySJTz.

Glossary of Terms

THIS PAGE WILL NO LONGER BE UPDATED. GLOSSARY IS NOW MOVED TO ITS OWN FILE. IF YOU WANT TO MAKE CHANGES TO THIS FILE, FORK THE REPO, EDIT glossary.md FILE, AND CREATE A PR WITH THE EXPLANATION FOR THE CHANGE / ADDITION.

Glossary of Terms

How to use React with suffixes?

  • React-i
  • React-ə
  • React ilə
  • React-lə
  • React-də

How to use API with suffixes?

I think it makes more sense to keep API as it is pronounced in English: https://www.youtube.com/watch?v=gZTn6AQDy1g

So, we should use suffixes like this:

  • API-ı
  • API-a
  • API ilə
  • API-la
  • API-da

Also make sure to write API, not APİ

React Terms

English Azərbaycanca
class component klas komponent
controlled component kontrol olunan komponent
click tıklamaq
context
component komponent
fragments fraqmentlər
functional component funskional komponent
portal portal
properties parametrlər
prop(s) prop(lar)
lifecycle lifecycle
ref ref
render render etmək
state
(in context of React components)
state
state
(in general context)
vəziyyət
stateful component state-li komponent
uncontrolled component kontrolsuz komponent

Other Terms

English Azərbaycanca
accessibility imkanlılıq
anchor anker təqi
application applikasiya
array massiv
arrow function arrow funkiyası
asynchronous asinxron
attributes atributlar
bug baq
bundle paket
callback
child uşaq
class klas
composition kompozisiya
conditional rendering şərtli render
constructor konstuktor
crash çökmə
current cari
data məlumat
debug dibaq
declarative deklarativ
DOM DOM
elements elementlər
embedding expressions
expression ifadə
external plugins xarici pluginlər
extent genişləndirmək
extention genişlənmə
event handler hadisə işləyicisi
example nümunə
framework freymvork
guide təlimat
hierarchy ierarxiya
higher order function yüksək dərəcəli funskiya
immutability dəyişməzlik
imperative imperativ
implementation tətbiq
import import
inheritance varislik
initialize inisializasiya
instance instansiya (computer term)
interact qarşılıqlı təsir etmək
item element
keyboard klaviatur
library kitabxana
local lokal
map uzlaşdırmaq
maintainer saxlayıcı
mock
nested
node nod
note qeyd
operator operator
output nəticə
package paket
parent valideyn
pattern pattern
plain sadə
polyfill polifil
pooling pulinq
power dəstəkləmək
private privat
propagate yaymaq
refactor refaktor
reference referans
reset sıfırlamaq
reuse təkrar istifadə
runtime icra müddəti
stack stek
syntax sintaksis
technology stack texnologiya steki
tip məsləhət
Tick
tool alət
tutorial dərslik
UI UI (not Azerbaijani İ)
user istifadəçi
Web Veb
wrapped component əhatə olan komponent
native nativ

Translation of the term "Classes"

This issue is created to discuss if we should be using "siniflər", "class-lar", or "klaslar"? Currently, we have been using "klaslar" to refer to classes; however, this might not be the best option. I want to hear your opinions.

Comments in Azerbaijani are more than welcome!

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.