Skip to content
(Work in progress) React documentation website in Arabic
Branch: master
Clone or download
Latest commit 45d4730 Apr 17, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
.circleci no cache fallback Jul 11, 2018
.github Update Mar 9, 2018
content Merge pull request #67 from aminebenkeroum/error-boundaries Apr 17, 2019
examples Document class contextType as the primary consuming mechanism (#1283) Oct 23, 2018
flow-typed Upgrade to Gatsby v2 (#1104) Sep 19, 2018
gatsby fix: prevent gatsby file detection from breaking path field (#1226) Oct 3, 2018
plugins Replace keys when inserting style/script tags Feb 6, 2019
scripts try again Feb 7, 2019
src Merge branch 'master' of into … Apr 5, 2019
static Add /tutorial redirect Dec 29, 2018
.eslintignore Updated .eslintignore Nov 7, 2017
.eslintrc Added fbjs eslint config, fixed lint errors and warnings Oct 9, 2017
.flowconfig Added some basic Flow types to get things started Oct 5, 2017
.gitignore Rename Title && adding the link Mar 23, 2019
.prettierrc Moved Prettier config to config file Oct 5, 2017 Added COC Oct 16, 2018 Let contributors know we're using Hsoub's translation Mar 11, 2019 Moved the CC license file to cover docs only Oct 7, 2017 Final touche Mar 15, 2019
crowdin.yaml Updates CrowdIn configuration to use /lang/folder/ Nov 17, 2017
gatsby-browser.js Expose react as global (#1501) Jan 2, 2019
gatsby-config.js fix try it on CodePen Feb 23, 2019
gatsby-node.js Upgrade to Gatsby v2 (#1104) Sep 19, 2018
package.json Bump React versions Mar 28, 2019
yarn.lock Bump React versions Mar 28, 2019

This repo contains the source code and documentation powering (Work in Progress)

Getting started


  1. Git
  2. Node: any 8.x version starting with 8.4.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 repo on your local machine


  1. cd 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



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.


  1. Check that no one else has claimed your page in the checklist and comments of Arabic Translation Progress and the pull requests.
  2. Comment at Arabic Translation Progress with the name of the page you would like to translate. Please take only one page at a time.
  3. Fork and Setup Repo, translate your page, and submit a pull request!

Before contributing, read the glossary and style guide to understand how to translate various technical and React-specific terms.

And use Hsoub's translation as a reference.

Fork and Setup Repo

  1. Fork the repo
  2. Clone forked repo on your local machine
  3. cd to go into the project root
  4. git remote add upstream to add original repo as an upstream
  5. yarn to install the website's npm dependencies

Create a branch

  1. git checkout master from any folder in your local repository
  2. git pull upstream master 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 Fixed header logo on Android) to stage and commit your changes
  2. git push origin the-name-of-my-branch
  3. Go to the repo and you should see recently pushed branches.
  4. Follow GitHub's instructions.
  5. If possible, include screenshots of visual changes. A Netlify build will also be automatically created once you make your PR so other people can see your change.


If you are interested in translating, please see the current translation efforts at

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


  • yarn reset to clear the local cache


Content submitted to is CC-BY-4.0 licensed, as found in the file.

You can’t perform that action at this time.