This repo contains the source code and documentation powering [ht.reactjs.org] which is the Haitian Creole translation of reactjs.org.

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 reactjs.org repo on your local machine

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

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

If you are interested in translating reactjs.org to Haitian Creole, check the translation progress here. Also, when translating any content, make sure to follow our Glossary.

You've cloned the repo, created your branch, and are armed with your favorite beverage to power you through a coding sprint, now what. The following diagram, highlights the primary files and directories you will modify in order to successfully translate documentation that gets rendered on the site.

.
├── CODE_OF_CONDUCT.md
├── GLOSSARY.md
├── README.md
├── content
│   ├── home/
│   ├── docs/
│   ├── blog/
│   ├── tutorial/
│   ├── 404.md
│   ...
├── src
│   ├── pages/
│   ...

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. git checkout main from any folder in your local 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

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

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.)

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 Netlify build will also be automatically created once you make your PR so other people can see your change.

• yarn reset to clear the local cache

• ❌ Home Page
• ❌ Tutorial
• ❌ Hello World
• ❌ Introducing JSX
• ❌ Rendering Elements
• ❌ Components and Props
• ❌ State and Lifecycle
• ❌ Handling Events
• ❌ Conditional Rendering
• ❌ Lists and Keys
• ❌ Forms
• ❌ Lifting State Up
• ❌ Composition vs Inheritance
• ❌ Thinking in React
• ❌ React
• ❌ React.Component
• ❌ ReactDOM
• ❌ ReactDOMServer
• ❌ DOM Elements
• ❌ SyntheticEvent
• ❌ Test Utilities
• ❌ Shallow Renderer
• ❌ Test Renderer
• ❌ JS Environment Requirements
• ❌ Glossary
• ❌ tutorial/nav.yml
• ❌ docs/nav.yml

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