Ahmed Abdelbaset 819518cfe3 RTL Languages Support (#6138)
* Update TailwindCSS & Install rtl-detect
1- Update TailwindCSS to use the logical properities such as `ps-1` instead of `pl-1`.
there are logical properities for margin, padding, inset, and text direction.

2- Install `rtl-detect` detect if the language is RTL direction.
Note: this might be uninstalled if we use the manual way to specify rtl language.

* add `siteConfig.isRTL`

* add `dir` attribute to the root element

* edit some tw classes to utilize logical properties
instead of directions properties
(e.g. `pr-0` to `pe-0`)

* edit some tw classes to utilize logical properties
instead of directions properties
(e.g. `pr-0` to `pe-0`)

* edit some tw classes to utilize logical properties
instead of directions properties
(e.g. `pr-0` to `pe-0`)

* edit some tw classes to utilize logical properties
instead of directions properties
(e.g. `pr-0` to `pe-0`)

* Refactor TW classes: Use logical properties over directional properties.

* Revert "Refactor TW classes: Use logical properties over directional properties."

This reverts commit df9620d944.

* Refactor TW classes: Use logical properties over directional properties.

* Refactor TW classes: Use logical properties over directional properties.

* Refactor TW classes: Use logical properties over directional properties.

* Add `start` and `end` directions to the `IconNavArrow`

* Add Note about `isRTL` prop

* Refactor TW classes: Use logical properties over directional properties.

* Refactor TW classes: Use logical properties over directional properties.

* Refactor TW classes: use logical properties over directional properties

* Refactor TW classes: use logical properties over directional properties

* Refactor TW classes: use logical properties over directional properties

* set dir attr of `CodeBlock` to `ltr` even the page dir is `rtl`

* Refactor TW classes: use logical properties over directional properties

* Refactor TW classes: use logical properties over directional properties

* Add `start` and `end` directions to some icons

* Refactor TW classes: use logical properties over directional properties

* Refactor TW classes: use logical properties over directional properties

* Refactor TW classes: use logical properties over directional properties

* Refactor TW classes: use logical properties over directional properties

* set dir attr of `ConsoleBlock` to `ltr` to overwrite the dir of root element

* Refactor TW classes: use logical properties over directional properties

* set dir=ltr on inline code blocks to overwrite <html dir="rtl"> in some languages

* Refactor TW classes: use logical properties over directional properties

* Refactor TW classes: use logical properties over directional properties

* Refactor TW classes: use logical properties over directional properties

* Refactor TW classes: use logical properties over directional properties

* set translate=no, dir=ltr on `TerminalBlock` to overwrite <html dir="rtl"> in rtl languages

* Refactor TW classes: use logical properties over directional properties

* Refactor TW classes: use logical properties over directional properties

* Refactor TW classes: use logical properties over directional properties

* fix some direction styles

* fix arrow directions in rtl

* remove `rtl-detect` and set `siteConfig.isRTL` manually

* fix `Breadcrumbs`'s arrow direction in rtl languages

* fix some directions of the search modal for RTL languages

* hard setting dir=ltr to Sandpack to overwrite rtl languages dir

* Refactor TW classes: use logical properties over directional properties

* remove my notes

* fix: rerverse space-x-* in rtl

* rebase with the main branch

* remove unnecessary alt

* add `start` & `end` display directions to the Chevron Icon

* rebase with the main branch
2023-08-11 15:42:12 -04:00
2023-03-20 23:15:12 +00:00
2023-05-19 17:44:58 +01:00
2023-03-18 22:35:53 +00:00
2023-04-20 19:27:46 +01:00
2023-03-29 23:56:21 +01:00
2023-08-11 15:42:12 -04:00
2023-03-18 22:35:53 +00:00
2023-03-18 22:35:53 +00:00
2023-03-18 22:35:53 +00:00
2023-07-21 19:24:36 -04:00
2023-03-29 22:54:03 +01:00
2023-03-18 22:35:53 +00:00
2023-03-18 22:35:53 +00:00
2023-03-18 22:35:53 +00:00
2023-03-18 22:35:53 +00:00
2023-03-18 22:35:53 +00:00
2023-05-19 17:44:58 +01:00
2023-08-11 15:42:12 -04:00
2023-03-18 22:35:53 +00:00
2023-03-18 22:35:53 +00:00
2023-03-18 22:35:53 +00:00
2023-08-11 15:42:12 -04:00

react.dev

This repo contains the source code and documentation powering react.dev.

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 react.dev repo on your local machine

Installation

  1. cd 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 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 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 react.dev, please see the current translation efforts here.

License

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

Description
The React documentation website
Readme 259 MiB
Languages
TypeScript 59.1%
JavaScript 34.6%
CSS 6.1%
HTML 0.2%