mirror of
https://github.com/reactjs/react.dev.git
synced 2026-02-24 20:53:08 +00:00
476373718b
Disclaimer: I'm an organiser of React Summit, React Advanced London and React Day Berlin - changes proposed in this PR is a small effort to actualise the list of events next to updating our own event dates Next to updating own conference dates, I've made following changes: * Removed 2020 events that, based on the current information from their websites, are cancelled or postponed without a new date * Moved 2020 events that have actually ran to the "past events" section * Updated dates of some events in 2020 that have not announced their cancellation, but moved dates within this year What I didn't do: * I haven't added 2020 cancelled events with their assumed 2021 dates, as it's up to organizers to confirm those and re-add * To stay consistent with point above - I'm also not adding our (GitNation - React Summit, React Advanced) cancelled event dates that moved to 2021 * Conferences that have a past dates, but has not clear statement on the website about cancellation have not been removed, but rather moved to "past events" section The information is relevant as of today's date - during these hard times plans do change frequently, so some information may be outdated by the time this PR is merged. I'll be happy to provide amends until it's merged.
reactjs.org
This repo contains the source code and documentation powering reactjs.org.
Getting started
Prerequisites
- Git
- Node: any 12.x version starting with v12.0.0 or greater
- Yarn: See Yarn website for installation instructions
- A fork of the repo (for any contributions)
- A clone of the reactjs.org repo on your local machine
Installation
cd reactjs.orgto go into the project rootyarnto install the website's npm dependencies
Running locally
yarn devto start the hot-reloading development server (powered by Gatsby)open http://localhost:8000to 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
git checkout masterfrom any folder in your localreactjs.orgrepositorygit pull origin masterto ensure you have the latest main codegit checkout -b the-name-of-my-branch(replacingthe-name-of-my-branchwith a suitable name) to create a branch
Make the change
- Follow the "Running locally" instructions
- Save the files and check in the browser
- Changes to React components in
srcwill hot-reload - Changes to markdown files in
contentwill hot-reload - If working with plugins, you may need to remove the
.cachedirectory and restart the server
Test the change
- If possible, test any visual changes in all latest versions of common browsers, on both desktop and mobile.
- Run
yarn check-allfrom the project root. (This will run Prettier, ESLint, and Flow.)
Push it
git add -A && git commit -m "My message"(replacingMy messagewith a commit message, such asFix header logo on Android) to stage and commit your changesgit push my-fork-name the-name-of-my-branch- Go to the reactjs.org repo and you should see recently pushed branches.
- Follow GitHub's instructions.
- 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.
Translation
If you are interested in translating reactjs.org, please see the current translation efforts at isreacttranslatedyet.com.
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 resetto clear the local cache
License
Content submitted to reactjs.org is CC-BY-4.0 licensed, as found in the LICENSE-DOCS.md file.