[Gatsby] "https://facebook.github.io/react/" -> "https://reactjs.org/" (

#10970)
facebook · Sep 30, 2017 · 0344f7ad5542ff068708e51ede3a08c8039cfe54 · 0344f7a
1 parent ed41745
commit 0344f7ad5542ff068708e51ede3a08c8039cfe54
diff --git a/CHANGELOG.md b/CHANGELOG.md
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -2,4 +2,4 @@
 
 Want to contribute to React? There are a few things you need to know.  
 
-We wrote a **[contribution guide](https://facebook.github.io/react/contributing/how-to-contribute.html)** to help you get started.
+We wrote a **[contribution guide](https://reactjs.org/contributing/how-to-contribute.html)** to help you get started.
diff --git a/README.md b/README.md
@@ -1,16 +1,16 @@
-# [React](https://facebook.github.io/react/) &middot; [![CircleCI Status](https://circleci.com/gh/facebook/react.svg?style=shield&circle-token=:circle-token)](https://circleci.com/gh/facebook/react) [![Coverage Status](https://img.shields.io/coveralls/facebook/react/master.svg?style=flat)](https://coveralls.io/github/facebook/react?branch=master) [![npm version](https://img.shields.io/npm/v/react.svg?style=flat)](https://www.npmjs.com/package/react) [![PRs Welcome](https://img.shields.io/badge/PRs-welcome-brightgreen.svg)](CONTRIBUTING.md#pull-requests)
+# [React](https://reactjs.org/) &middot; [![CircleCI Status](https://circleci.com/gh/facebook/react.svg?style=shield&circle-token=:circle-token)](https://circleci.com/gh/facebook/react) [![Coverage Status](https://img.shields.io/coveralls/facebook/react/master.svg?style=flat)](https://coveralls.io/github/facebook/react?branch=master) [![npm version](https://img.shields.io/npm/v/react.svg?style=flat)](https://www.npmjs.com/package/react) [![PRs Welcome](https://img.shields.io/badge/PRs-welcome-brightgreen.svg)](CONTRIBUTING.md#pull-requests)
 
 React is a JavaScript library for building user interfaces.
 
 * **Declarative:** React makes it painless to create interactive UIs. Design simple views for each state in your application, and React will efficiently update and render just the right components when your data changes. Declarative views make your code more predictable, simpler to understand, and easier to debug.
 * **Component-Based:** Build encapsulated components that manage their own state, then compose them to make complex UIs. Since component logic is written in JavaScript instead of templates, you can easily pass rich data through your app and keep state out of the DOM.
 * **Learn Once, Write Anywhere:** We don't make assumptions about the rest of your technology stack, so you can develop new features in React without rewriting existing code. React can also render on the server using Node and power mobile apps using [React Native](https://facebook.github.io/react-native/).
 
-[Learn how to use React in your own project](https://facebook.github.io/react/docs/getting-started.html).
+[Learn how to use React in your own project](https://reactjs.org/docs/getting-started.html).
 
 ## Examples
 
-We have several examples [on the website](https://facebook.github.io/react/). Here is the first one to get you started:
+We have several examples [on the website](https://reactjs.org/). Here is the first one to get you started:
 
 ```jsx
 class HelloMessage extends React.Component {
@@ -27,19 +27,19 @@ ReactDOM.render(
 
 This example will render "Hello John" into a container on the page.
 
-You'll notice that we used an HTML-like syntax; [we call it JSX](https://facebook.github.io/react/docs/introducing-jsx.html). JSX is not required to use React, but it makes code more readable, and writing it feels like writing HTML. We recommend using [Babel](https://babeljs.io/) with a [React preset](https://babeljs.io/docs/plugins/preset-react/) to convert JSX into native JavaScript for browsers to digest.
+You'll notice that we used an HTML-like syntax; [we call it JSX](https://reactjs.org/docs/introducing-jsx.html). JSX is not required to use React, but it makes code more readable, and writing it feels like writing HTML. We recommend using [Babel](https://babeljs.io/) with a [React preset](https://babeljs.io/docs/plugins/preset-react/) to convert JSX into native JavaScript for browsers to digest.
 
 ## Installation
 
-React is available as the `react` package on [npm](https://www.npmjs.com/). It is also available on a [CDN](https://facebook.github.io/react/docs/installation.html#using-a-cdn).
+React is available as the `react` package on [npm](https://www.npmjs.com/). It is also available on a [CDN](https://reactjs.org/docs/installation.html#using-a-cdn).
 
 React is flexible and can be used in a variety of projects. You can create new apps with it, but you can also gradually introduce it into an existing codebase without doing a rewrite.
 
 The recommended way to install React depends on your project. Here you can find short guides for the most common scenarios:
 
-* [Trying Out React](https://facebook.github.io/react/docs/installation.html#trying-out-react)
-* [Creating a New Application](https://facebook.github.io/react/docs/installation.html#creating-a-new-application)
-* [Adding React to an Existing Application](https://facebook.github.io/react/docs/installation.html#adding-react-to-an-existing-application)
+* [Trying Out React](https://reactjs.org/docs/installation.html#trying-out-react)
+* [Creating a New Application](https://reactjs.org/docs/installation.html#creating-a-new-application)
+* [Adding React to an Existing Application](https://reactjs.org/docs/installation.html#adding-react-to-an-existing-application)
 
 ## Contributing
 
@@ -51,7 +51,7 @@ Facebook has adopted a Code of Conduct that we expect project participants to ad
 
 ### Contributing Guide
 
-Read our [contributing guide](https://facebook.github.io/react/contributing/how-to-contribute.html) to learn about our development process, how to propose bugfixes and improvements, and how to build and test your changes to React.
+Read our [contributing guide](https://reactjs.org/contributing/how-to-contribute.html) to learn about our development process, how to propose bugfixes and improvements, and how to build and test your changes to React.
 
 ### Beginner Friendly Bugs
 

diff --git a/docs/README.md b/docs/README.md
@@ -1,10 +1,10 @@
 # React Documentation & Website
 
-## [Read the React Documentation](https://facebook.github.io/react/)
+## [Read the React Documentation](https://reactjs.org/)
 
 This folder is not the right place to *read* the documentation.
 
-Instead, head over [to the React website](https://facebook.github.io/react/) to read it.
+Instead, head over [to the React website](https://reactjs.org/) to read it.
 
 This folder only contains the source code for the website.
 

diff --git a/docs/_config.yml b/docs/_config.yml
@@ -1,8 +1,8 @@
 ---
 name: React
 description: A JavaScript library for building user interfaces
-url: https://facebook.github.io
-baseurl: /react
+url: https://reactjs.org/
+baseurl: /
 permalink: /blog/:year/:month/:day/:title.html
 paginate_path: /blog/page:num/
 paginate: 5

diff --git a/docs/_layouts/default.html b/docs/_layouts/default.html
@@ -22,8 +22,8 @@
   <meta name="viewport" content="width=device-width, initial-scale=1">
   <meta property="og:title" content="{{ title }}">
   <meta property="og:type" content="{{ type }}">
-  <meta property="og:url" content="https://facebook.github.io/react{{ page.url }}">
-  <meta property="og:image" content="https://facebook.github.io/react/img/logo_og.png">
+  <meta property="og:url" content="https://reactjs.org/{{ page.url }}">
+  <meta property="og:image" content="https://reactjs.org/img/logo_og.png">
   <meta property="og:description" content="{{ description }}">
   <meta property="fb:app_id" content="623268441017527">
 

diff --git a/docs/_posts/2015-07-03-react-v0.14-beta-1.md b/docs/_posts/2015-07-03-react-v0.14-beta-1.md
@@ -7,7 +7,7 @@ This week, many people in the React community are at [ReactEurope](https://www.r
 
 With React 0.14, we're continuing to let React mature and to make minor changes as the APIs continue to settle down. I'll talk only about the two largest changes in this blog post; when we publish the final release we'll be sure to update all of our documentation and include a full changelog.
 
-You can install the new beta with `npm install react@0.14.0-beta1` and `npm install react-dom@0.14.0-beta1`. As mentioned in [Deprecating react-tools](https://facebook.github.io/react/blog/2015/06/12/deprecating-jstransform-and-react-tools.html), we're no longer updating the react-tools package so this release doesn't include a new version of it. Please try the new version out and let us know what you think, and please do file issues on our GitHub repo if you run into any problems.
+You can install the new beta with `npm install react@0.14.0-beta1` and `npm install react-dom@0.14.0-beta1`. As mentioned in [Deprecating react-tools](https://reactjs.org/blog/2015/06/12/deprecating-jstransform-and-react-tools.html), we're no longer updating the react-tools package so this release doesn't include a new version of it. Please try the new version out and let us know what you think, and please do file issues on our GitHub repo if you run into any problems.
 
 ## Two Packages
 

diff --git a/docs/_posts/2016-07-11-introducing-reacts-error-code-system.md b/docs/_posts/2016-07-11-introducing-reacts-error-code-system.md
@@ -13,6 +13,6 @@ In order to make debugging in production easier, we're introducing an Error Code
 
 While we hope you don't see errors often, you can see how it works [here](/docs/error-decoder.html?invariant=109&args[]=Foo). This is what the same error from above will look like:
 
-> Minified React error #109; visit https://facebook.github.io/react/docs/error-decoder.html?invariant=109&args[]=Foo for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
+> Minified React error #109; visit https://reactjs.org/docs/error-decoder.html?invariant=109&args[]=Foo for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
 
 We do this so that the developer experience is as good as possible, while also keeping the production bundle size as small as possible. This feature shouldn't require any changes on your side — use the `min.js` files in production or bundle your application code with `process.env.NODE_ENV === 'production'` and you should be good to go!
diff --git a/docs/_posts/2017-09-26-react-v16.0.md b/docs/_posts/2017-09-26-react-v16.0.md
@@ -71,7 +71,7 @@ See the [documentation for `ReactDOMServer`](/docs/react-dom-server.html) for mo
 
 ### Support for custom DOM attributes
 
-Instead of ignoring unrecognized HTML and SVG attributes, React will now [pass them through to the DOM](https://facebook.github.io/react/blog/2017/09/08/dom-attributes-in-react-16.html). This has the added benefit of allowing us to get rid of most of React's attribute whitelist, resulting in reduced file sizes.
+Instead of ignoring unrecognized HTML and SVG attributes, React will now [pass them through to the DOM](https://reactjs.org/blog/2017/09/08/dom-attributes-in-react-16.html). This has the added benefit of allowing us to get rid of most of React's attribute whitelist, resulting in reduced file sizes.
 
 ### Reduced file size
 
@@ -168,7 +168,7 @@ React 16 includes a number of small breaking changes. These only affect uncommon
 
 * There is no `react/lib/*` and `react-dom/lib/*` anymore. Even in CommonJS environments, React and ReactDOM are precompiled to single files (“flat bundles”). If you previously relied on undocumented React internals, and they don’t work anymore, let us know about your specific case in a new issue, and we’ll try to figure out a migration strategy for you.
 * There is no `react-with-addons.js` build anymore. All compatible addons are published separately on npm, and have single-file browser versions if you need them.
-* The deprecations introduced in 15.x have been removed from the core package. `React.createClass` is now available as `create-react-class`, `React.PropTypes` as `prop-types`, `React.DOM` as `react-dom-factories`, `react-addons-test-utils` as `react-dom/test-utils`, and shallow renderer as `react-test-renderer/shallow`. See [15.5.0](https://facebook.github.io/react/blog/2017/04/07/react-v15.5.0.html) and [15.6.0](https://facebook.github.io/react/blog/2017/06/13/react-v15.6.0.html) blog posts for instructions on migrating code and automated codemods.
+* The deprecations introduced in 15.x have been removed from the core package. `React.createClass` is now available as `create-react-class`, `React.PropTypes` as `prop-types`, `React.DOM` as `react-dom-factories`, `react-addons-test-utils` as `react-dom/test-utils`, and shallow renderer as `react-test-renderer/shallow`. See [15.5.0](https://reactjs.org/blog/2017/04/07/react-v15.5.0.html) and [15.6.0](https://reactjs.org/blog/2017/06/13/react-v15.6.0.html) blog posts for instructions on migrating code and automated codemods.
 * The names and paths to the single-file browser builds have changed to emphasize the difference between development and production builds. For example:
     * `react/dist/react.js` → `react/umd/react.development.js`
     * `react/dist/react.min.js` → `react/umd/react.production.min.js`

diff --git a/docs/docs/cross-origin-errors.md b/docs/docs/cross-origin-errors.md
@@ -8,7 +8,7 @@ permalink: docs/cross-origin-errors.html
 >
 > The following section applies only to the development mode of React. Error handling in production mode is done with regular try/catch statements.
 
-In [development mode](https://facebook.github.io/react/docs/optimizing-performance.html), React uses a global `error` event handler to preserve the "pause on exceptions" behavior of browser DevTools. It also logs errors to the developer console.
+In [development mode](https://reactjs.org/docs/optimizing-performance.html), React uses a global `error` event handler to preserve the "pause on exceptions" behavior of browser DevTools. It also logs errors to the developer console.
 
 If an error is thrown from a [different origin](https://developer.mozilla.org/en-US/docs/Web/Security/Same-origin_policy) the browser will mask its details and React will not be able to log the original error message. This is a security precaution taken by browsers to avoid leaking sensitive information.
 

diff --git a/docs/tutorial/tutorial.md b/docs/tutorial/tutorial.md
@@ -71,7 +71,7 @@ We recommend following [these instructions](http://babeljs.io/docs/editors) to c
 
 ### Help, I'm Stuck!
 
-If you get stuck, check out the [community support resources](https://facebook.github.io/react/community/support.html). In particular, [Reactiflux chat](/community/support.html#reactiflux-chat) is a great way to get quick help. If you don't get a good answer anywhere, please file an issue, and we'll help you out.
+If you get stuck, check out the [community support resources](https://reactjs.org/community/support.html). In particular, [Reactiflux chat](/community/support.html#reactiflux-chat) is a great way to get quick help. If you don't get a good answer anywhere, please file an issue, and we'll help you out.
 
 With this out of the way, let's get started!
 

diff --git a/docs/warnings/unknown-prop.md b/docs/warnings/unknown-prop.md
@@ -7,7 +7,7 @@ The unknown-prop warning will fire if you attempt to render a DOM element with a
 
 There are a couple of likely reasons this warning could be appearing:
 
-1. Are you using `{...this.props}` or `cloneElement(element, this.props)`? Your component is transferring its own props directly to a child element (eg. https://facebook.github.io/react/docs/transferring-props.html). When transferring props to a child component, you should ensure that you are not accidentally forwarding props that were intended to be interpreted by the parent component.
+1. Are you using `{...this.props}` or `cloneElement(element, this.props)`? Your component is transferring its own props directly to a child element (eg. https://reactjs.org/docs/transferring-props.html). When transferring props to a child component, you should ensure that you are not accidentally forwarding props that were intended to be interpreted by the parent component.
 
 2. You are using a non-standard DOM attribute on a native DOM node, perhaps to represent custom data. If you are trying to attach custom data to a standard DOM element, consider using a custom data attribute as described [on MDN](https://developer.mozilla.org/en-US/docs/Web/Guide/HTML/Using_data_attributes).
 

diff --git a/fixtures/dom/src/components/Header.js b/fixtures/dom/src/components/Header.js
@@ -34,7 +34,7 @@ class Header extends React.Component {
         <div className="header__inner">
           <span className="header__logo">
             <img
-              src="https://facebook.github.io/react/img/logo.svg"
+              src="https://reactjs.org/img/logo.svg"
               alt=""
               width="32"
               height="32"

diff --git a/packages/react-art/package.json b/packages/react-art/package.json
@@ -16,7 +16,7 @@
   "bugs": {
     "url": "https://github.com/facebook/react/issues"
   },
-  "homepage": "https://facebook.github.io/react/",
+  "homepage": "https://reactjs.org/",
   "dependencies": {
     "create-react-class": "^15.6.2",
     "fbjs": "^0.8.16",

diff --git a/packages/react-dom/package.json b/packages/react-dom/package.json
@@ -11,7 +11,7 @@
   "bugs": {
     "url": "https://github.com/facebook/react/issues"
   },
-  "homepage": "https://facebook.github.io/react/",
+  "homepage": "https://reactjs.org/",
   "dependencies": {
     "fbjs": "^0.8.16",
     "loose-envify": "^1.1.0",

diff --git a/packages/react-test-renderer/package.json b/packages/react-test-renderer/package.json
@@ -13,7 +13,7 @@
   "bugs": {
     "url": "https://github.com/facebook/react/issues"
   },
-  "homepage": "https://facebook.github.io/react/",
+  "homepage": "https://reactjs.org/",
   "dependencies": {
     "fbjs": "^0.8.16",
     "object-assign": "^4.1.1"

diff --git a/packages/react/README.md b/packages/react/README.md
@@ -1,6 +1,6 @@
 # react
 
-An npm package to get you immediate access to [React](https://facebook.github.io/react/),
+An npm package to get you immediate access to [React](https://reactjs.org/),
 without also requiring the JSX transformer. This is especially useful for cases where you
 want to [`browserify`](https://github.com/substack/node-browserify) your module using
 `React`.

diff --git a/packages/react/package.json b/packages/react/package.json
@@ -5,7 +5,7 @@
     "react"
   ],
   "version": "16.0.0",
-  "homepage": "https://facebook.github.io/react/",
+  "homepage": "https://reactjs.org/",
   "bugs": "https://github.com/facebook/react/issues",
   "license": "MIT",
   "files": [

diff --git a/scripts/error-codes/README.md b/scripts/error-codes/README.md
@@ -1,4 +1,4 @@
-The error code system substitutes React's invariant error messages with error IDs to provide a better debugging support in production. Check out the blog post [here](https://facebook.github.io/react/blog/2016/07/11/introducing-reacts-error-code-system.html).
+The error code system substitutes React's invariant error messages with error IDs to provide a better debugging support in production. Check out the blog post [here](https://reactjs.org/blog/2016/07/11/introducing-reacts-error-code-system.html).
 
 ## Note for cutting a new React release
 1. For each release, we run `yarn build -- --extract-errors` to update the error codes before calling `yarn build`. The build step uses `codes.json` for a production (minified) build; there should be no warning like `Error message "foo" cannot be found` for a successful release.
@@ -11,4 +11,4 @@ The error code system consists of 5 parts:
 - [`extract-errors.js`](https://github.com/facebook/react/blob/master/scripts/error-codes/extract-errors.js) is an node script that traverses our codebase and updates `codes.json`. Use it by calling `yarn build -- --extract-errors`.
 - [`replace-invariant-error-codes.js`](https://github.com/facebook/react/blob/master/scripts/error-codes/replace-invariant-error-codes.js) is a Babel pass that rewrites error messages to IDs for a production (minified) build.
 - [`reactProdInvariant.js`](https://github.com/facebook/react/blob/master/src/shared/utils/reactProdInvariant.js) is the replacement for `invariant` in production. This file gets imported by the Babel plugin and should _not_ be used manually.
-- [`ErrorDecoderComponent`](https://github.com/facebook/react/blob/master/docs/_js/ErrorDecoderComponent.js) is a React component that lives at https://facebook.github.io/react/docs/error-decoder.html. This page takes parameters like `?invariant=109&args[]=Foo` and displays a corresponding error message. Our documentation site's [`Rakefile`](https://github.com/facebook/react/blob/master/docs/Rakefile#L64-L69) has a task (`bundle exec rake copy_error_codes`) for adding the latest `codes.json` to the error decoder page. This task is included in the default `bundle exec rake release` task.
+- [`ErrorDecoderComponent`](https://github.com/facebook/react/blob/master/docs/_js/ErrorDecoderComponent.js) is a React component that lives at https://reactjs.org/docs/error-decoder.html. This page takes parameters like `?invariant=109&args[]=Foo` and displays a corresponding error message. Our documentation site's [`Rakefile`](https://github.com/facebook/react/blob/master/docs/Rakefile#L64-L69) has a task (`bundle exec rake copy_error_codes`) for adding the latest `codes.json` to the error decoder page. This task is included in the default `bundle exec rake release` task.
diff --git a/scripts/release-manager/Readme.md b/scripts/release-manager/Readme.md
@@ -457,7 +457,7 @@ git commit -am 'Rebuild the website'
 git push
 ```
 
-Now open https://facebook.github.io/react/, give it a few minutes, refresh, and behold.
+Now open https://reactjs.org/, give it a few minutes, refresh, and behold.
 
 Don’t forget to switch to `master` for the future development.