chore: Change .org to .com links (#26993)

gatsbyjs · Sep 23, 2020 · 1b87ef6349709a2513554e372518ead859b789c1 · 1b87ef6
1 parent 510370d
commit 1b87ef6349709a2513554e372518ead859b789c1
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
@@ -4,7 +4,7 @@
 -->
 
 <!--
-  Is this a blog post? Check out the docs at https://www.gatsbyjs.org/contributing/blog-contributions/, and please mention if the blog post is pre-approved
+  Is this a blog post? Check out the docs at https://www.gatsbyjs.com/contributing/blog-contributions/, and please mention if the blog post is pre-approved
   by someone from Gatsby.
 -->
 

diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md
@@ -1,3 +1,3 @@
 # Gatsby Contributor Covenant Code of Conduct
 
-Please check out the [Code of Conduct](https://www.gatsbyjs.org/contributing/code-of-conduct/) page on the Gatsby site.
+Please check out the [Code of Conduct](https://www.gatsbyjs.com/contributing/code-of-conduct/) page on the Gatsby site.
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -1,3 +1,3 @@
 ## How to Contribute
 
-For information related to contributing to Gatsby, please check out the [How to Contribute](https://www.gatsbyjs.org/contributing/how-to-contribute/) section of the documentation at the Gatsby site.
+For information related to contributing to Gatsby, please check out the [How to Contribute](https://www.gatsbyjs.com/contributing/how-to-contribute/) section of the documentation at the Gatsby site.
diff --git a/docs/contributing/gatsby-style-guide.md b/docs/contributing/gatsby-style-guide.md
@@ -161,7 +161,7 @@ In tutorials that are meant for beginners, use as few hyperlinks as possible to
 
 ### Use relative hyperlinks for local links
 
-When referencing another page within [gatsbyjs.org](https://www.gatsbyjs.org/) hyperlinks should use relative paths (not include the full domain). This guarantees that all links function when running locally or in preview.
+When referencing another page within [gatsbyjs.com](https://www.gatsbyjs.com/) hyperlinks should use relative paths (not include the full domain). This guarantees that all links function when running locally or in preview.
 
 ```markdown
 <!-- Good -->
@@ -170,7 +170,7 @@ When referencing another page within [gatsbyjs.org](https://www.gatsbyjs.org/) h
 
 <!-- Bad -->
 
-[Gatsby's glossary](https://www.gatsbyjs.org/docs/glossary)
+[Gatsby's glossary](https://www.gatsbyjs.com/docs/glossary)
 ```
 
 Note: Links to Gatsby Cloud/Gatsby Inc. are located at [gatsbyjs.com](https://www.gatsbyjs.com/) and should be referenced using an absolute path (domain included). See also [Referencing Gatsby Cloud](#referencing-gatsby-cloud)
@@ -348,7 +348,7 @@ You may also choose to include line highlighting in your code snippets, using th
 module.exports = {
   siteMetadata: {
     title: `GatsbyJS`, // highlight-line
-    siteUrl: `https://www.gatsbyjs.org`,
+    siteUrl: `https://www.gatsbyjs.com`,
   },
 }
 ```
@@ -358,7 +358,7 @@ module.exports = {
 module.exports = {
   siteMetadata: {
     title: `GatsbyJS`, // highlight-line
-    siteUrl: `https://www.gatsbyjs.org`,
+    siteUrl: `https://www.gatsbyjs.com`,
   },
 }
 ```
@@ -371,7 +371,7 @@ module.exports = {
   siteMetadata: {
     title: `GatsbyJS`,
     // highlight-next-line
-    siteUrl: `https://www.gatsbyjs.org`,
+    siteUrl: `https://www.gatsbyjs.com`,
   },
 }
 ```
@@ -382,7 +382,7 @@ module.exports = {
   siteMetadata: {
     title: `GatsbyJS`,
     // highlight-next-line
-    siteUrl: `https://www.gatsbyjs.org`,
+    siteUrl: `https://www.gatsbyjs.com`,
   },
 }
 ```
@@ -395,7 +395,7 @@ module.exports = {
   // highlight-start
   siteMetadata: {
     title: `GatsbyJS`,
-    siteUrl: `https://www.gatsbyjs.org`,
+    siteUrl: `https://www.gatsbyjs.com`,
   },
   // highlight-end
 }
@@ -407,7 +407,7 @@ module.exports = {
   // highlight-start
   siteMetadata: {
     title: `GatsbyJS`,
-    siteUrl: `https://www.gatsbyjs.org`,
+    siteUrl: `https://www.gatsbyjs.com`,
   },
   // highlight-end
 }

diff --git a/docs/contributing/how-to-make-a-reproducible-test-case.md b/docs/contributing/how-to-make-a-reproducible-test-case.md
@@ -17,7 +17,7 @@ A reproducible test case is a great way to share a specific environment that cau
 ## Steps to create a reproducible test case
 
 - Create a new Gatsby site with a starter, the official `hello-world` starter is a great 'barebones' starting point here: `gatsby new bug-repro https://github.com/gatsbyjs/gatsby-starter-hello-world`
-- Add any Gatsby plugins that relate to the issue. For example, if you're having problems with Gatsby MDX you should install and configure [`gatsby-plugin-mdx`](https://www.gatsbyjs.org/packages/gatsby-plugin-mdx/). Only add plugins that are needed to demonstrate the problem.
+- Add any Gatsby plugins that relate to the issue. For example, if you're having problems with Gatsby MDX you should install and configure [`gatsby-plugin-mdx`](https://www.gatsbyjs.com/packages/gatsby-plugin-mdx/). Only add plugins that are needed to demonstrate the problem.
 - Add the code needed to recreate the error you've seen.
 - Publish the code (your GitHub account is a good place to do this) and then link to it when [creating an issue](/contributing/how-to-file-an-issue/).
 

diff --git a/docs/contributing/how-to-run-a-gatsby-workshop.md b/docs/contributing/how-to-run-a-gatsby-workshop.md
@@ -4,7 +4,7 @@ title: How to Run a Gatsby Workshop
 
 Running a workshop focused on Gatsby.js is a fantastic way to teach a group of people how to create fast, accessible websites with in-person (or virtual) instruction.
 
-We on the Gatsby team have run a number of in-person workshops, and you can read about some of our [initial findings](https://www.gatsbyjs.org/blog/2018-05-31-open-sourcing-gatsby-workshops/). If you are interested in running a workshop yourself, we welcome you to do so and offer this page of resources to help you.
+We on the Gatsby team have run a number of in-person workshops, and you can read about some of our [initial findings](https://www.gatsbyjs.com/blog/2018-05-31-open-sourcing-gatsby-workshops/). If you are interested in running a workshop yourself, we welcome you to do so and offer this page of resources to help you.
 
 Share your ideas and report how these workshops go for you in the [Open source repo](https://github.com/gatsbyjs/gatsby) through issues and PRs (if you ran into problems with the workshops and/or have ideas of how to improve them) or [Twitter](https://twitter.com/gatsbyjs) if you want to share an upcoming workshop you're running.
 

diff --git a/docs/contributing/how-to-write-a-tutorial.md b/docs/contributing/how-to-write-a-tutorial.md
@@ -6,7 +6,7 @@ In contrast to recipes and reference guides, tutorials are step-by-step instruct
 
 ## Near perfect example of a tutorial
 
-[Main Gatsby tutorial](https://www.gatsbyjs.org/tutorial/)
+[Main Gatsby tutorial](https://www.gatsbyjs.com/tutorial/)
 
 ## What should a tutorial be about?
 
@@ -22,7 +22,7 @@ Topics should be chosen based on these priorities:
 
 ## Length of a tutorial
 
-If a tutorial is longer than 3 8.5x11” pages or has more than about 5 headers and you’re finding yourself creating a Table of Contents at the top, it will probably be easier to read and easier for readers to complete if you turn it into a multi-page tutorial, like the [main Gatsby tutorial](https://www.gatsbyjs.org/tutorial/).
+If a tutorial is longer than 3 8.5x11” pages or has more than about 5 headers and you’re finding yourself creating a Table of Contents at the top, it will probably be easier to read and easier for readers to complete if you turn it into a multi-page tutorial, like the [main Gatsby tutorial](https://www.gatsbyjs.com/tutorial/).
 
 If you have a tutorial that falls into this category, it is likely a big enough project that you’ll benefit from the feedback process provided by creating an [RFC (Request for Comments) document](https://github.com/gatsbyjs/rfcs).
 

diff --git a/docs/contributing/managing-pull-requests.md b/docs/contributing/managing-pull-requests.md
@@ -18,7 +18,7 @@ For an introduction on what Pull Requests are and how to file one, check out the
 
 Some general things we verify in a pull request are:
 
-- Links ought to be relative instead of absolute when linking to docs (`/docs/some-reference/` instead of `https://www.gatsbyjs.org/docs/some-reference/`)
+- Links ought to be relative instead of absolute when linking to docs (`/docs/some-reference/` instead of `https://www.gatsbyjs.com/docs/some-reference/`)
 - Language ought to be inclusive and accessible
 - Issues and Requests for Comments (RFCs) (if any) that this PR addresses ought to be linked to
 
@@ -73,7 +73,7 @@ For PRs that add a blog post, we ought to check:
 
 ## Automated Checks
 
-Our repository on [GitHub](https://github.com/gatsbyjs/gatsby) has several automated CI checks that are run automatically for all PRs. These include tests, linting and even preview builds for [gatsbyjs.org](https://www.gatsbyjs.org).
+Our repository on [GitHub](https://github.com/gatsbyjs/gatsby) has several automated CI checks that are run automatically for all PRs. These include tests, linting and even preview builds for [gatsbyjs.org](https://www.gatsbyjs.com).
 
 We want all of these checks to pass. While we'll sometimes review a work in progress PR with some failed checks, a PR is only ready to ship when all the tests have passed.
 

diff --git a/docs/contributing/submit-to-plugin-library.md b/docs/contributing/submit-to-plugin-library.md
@@ -11,7 +11,7 @@ In order to add your plugin to the [Plugin Library](/plugins/), you need to:
 3. **Include a `keywords` field** in your plugin's `package.json`, containing `gatsby` and `gatsby-plugin`. If your plugin is a theme, please also include `gatsby-theme`.
 4. Document your plugin with a README, using the contributing [plugin template](/contributing/how-to-write-a-plugin-readme/) for reference.
 
-After doing so, Algolia will take up to 12 hours to add it to the library search index (the exact time necessary is still unknown), and wait for the daily rebuild of https://gatsbyjs.org to automatically include your plugin page to the website. Then, all you have to do is share your wonderful plugin with the community!
+After doing so, Algolia will take up to 12 hours to add it to the library search index (the exact time necessary is still unknown), and wait for the daily rebuild of https://www.gatsbyjs.com to automatically include your plugin page to the website. Then, all you have to do is share your wonderful plugin with the community!
 
 ## Notes
 

diff --git a/docs/contributing/translation/translators.md b/docs/contributing/translation/translators.md
@@ -10,7 +10,7 @@ Once a language repository is created and someone on the Gatsby team has assigne
 
 ### Use English as the source
 
-The [gatsbyjs.org](https://gatsbyjs.org) website is written first in English and should be considered the source material for all translations (as opposed to starting from another translation). When a repository is created, it will provide a copy of the docs to be translated which you can then update through [pull requests](/contributing/how-to-open-a-pull-request/) against them in the relevant language.
+The [gatsbyjs.com](https://www.gatsbyjs.com) website is written first in English and should be considered the source material for all translations (as opposed to starting from another translation). When a repository is created, it will provide a copy of the docs to be translated which you can then update through [pull requests](/contributing/how-to-open-a-pull-request/) against them in the relevant language.
 
 Changes to the meaning of a text or code example should be done in the main [English repo](https://github.com/gatsbyjs/gatsby/), and then translated afterwards to keep the content aligned across languages.
 

diff --git a/docs/docs/adding-comments.md b/docs/docs/adding-comments.md
@@ -46,7 +46,7 @@ Here are the steps for adding Disqus comments to your own blog:
 npm install disqus-react
 ```
 
-3. Add the shortname from step 1 as something like `GATSBY_DISQUS_NAME` to your `.env` and `.env.example` files so that people forking your repo will know that they need to supply this value to get comments to work. (You need to prefix the environment variable with `GATSBY_` in order to [make it available to client-side code](https://www.gatsbyjs.org/docs/environment-variables/#client-side-javascript).)
+3. Add the shortname from step 1 as something like `GATSBY_DISQUS_NAME` to your `.env` and `.env.example` files so that people forking your repo will know that they need to supply this value to get comments to work. (You need to prefix the environment variable with `GATSBY_` in order to [make it available to client-side code](https://www.gatsbyjs.com/docs/environment-variables/#client-side-javascript).)
 
 ```text:title=.env.example
 # enables Disqus comments for blog posts

diff --git a/docs/docs/adding-search-with-algolia.md b/docs/docs/adding-search-with-algolia.md
@@ -559,7 +559,7 @@ const Layout = ({ location, title, children }) => {
       <footer>
         © {new Date().getFullYear()}, Built with
         {` `}
-        <a href="https://www.gatsbyjs.org">Gatsby</a>
+        <a href="https://www.gatsbyjs.com">Gatsby</a>
       </footer>
     </div>
   )

diff --git a/docs/docs/answering-it-security.md b/docs/docs/answering-it-security.md
@@ -12,7 +12,7 @@ If security engineers are interested in your project, some talking points that c
 
 It's helpful to emphasize to security personnel that these benefits were a factor in why Gatsby was selected for the project. You chose Gatsby, in part, because it is _more_ secure.
 
-Read about security in Gatsby: [https://www.gatsbyjs.org/blog/2019-04-06-security-for-modern-web-frameworks/](/blog/2019-04-06-security-for-modern-web-frameworks/)
+Read about security in Gatsby: [https://www.gatsbyjs.com/blog/2019-04-06-security-for-modern-web-frameworks/](/blog/2019-04-06-security-for-modern-web-frameworks/)
 
 ---
 

diff --git a/docs/docs/building-an-ecommerce-site-with-shopify.md b/docs/docs/building-an-ecommerce-site-with-shopify.md
@@ -4,7 +4,7 @@ title: Building an E-commerce site with Shopify
 
 In this tutorial, you will setup a new Gatsby website that fetches product data from [Shopify](https://www.shopify.com). The site displays a list of all products on a product listing page, and a page for every product in the store.
 
-If you are already comfortable with Gatsby and Shopify, you might want to check out the [Gatsby Shopify starter](https://www.gatsbyjs.org/starters/AlexanderProd/gatsby-shopify-starter/), which provides many of the same features as this example.
+If you are already comfortable with Gatsby and Shopify, you might want to check out the [Gatsby Shopify starter](https://www.gatsbyjs.com/starters/AlexanderProd/gatsby-shopify-starter/), which provides many of the same features as this example.
 
 ## Setting up your Shopify account
 
@@ -15,7 +15,7 @@ If you are already comfortable with Gatsby and Shopify, you might want to check
 
 ## Set up the Gatsby Shopify plugin
 
-1. If you do not already have one ready, [create a Gatsby site](https://www.gatsbyjs.org/docs/quick-start).
+1. If you do not already have one ready, [create a Gatsby site](https://www.gatsbyjs.com/docs/quick-start).
 
 2. Install the [`gatsby-source-shopify`](/packages/gatsby-source-shopify/) plugin and [`shopify-buy`](https://github.com/Shopify/js-buy-sdk) package.
 

diff --git a/docs/docs/creating-and-modifying-pages.md b/docs/docs/creating-and-modifying-pages.md
@@ -263,4 +263,4 @@ Page context is serialized before being passed to pages. This means it can't be
 
 ## Creating Client-only routes
 
-In specific cases, you might want to create a site with client-only portions that are gated by authentication. For more on how to achieve this, refer to [client-only routes & user authentication](https://www.gatsbyjs.org/docs/client-only-routes-and-user-authentication/).
+In specific cases, you might want to create a site with client-only portions that are gated by authentication. For more on how to achieve this, refer to [client-only routes & user authentication](https://www.gatsbyjs.com/docs/client-only-routes-and-user-authentication/).
diff --git a/docs/docs/debugging-replace-renderer-api.md b/docs/docs/debugging-replace-renderer-api.md
@@ -21,7 +21,7 @@ If multiple plugins implement `replaceRenderer`, the build script will warn you:
 ```text
 warning replaceRenderer API found in these plugins:
 warning plugin-name-a, default-site-plugin
-warning This might be an error, see: https://www.gatsbyjs.org/docs/debugging-replace-renderer-api/
+warning This might be an error, see: https://www.gatsbyjs.com/docs/debugging-replace-renderer-api/
 
 warning Duplicate replaceRenderer found, skipping gatsby-ssr.js for plugin: plugin-name-a
 ```

diff --git a/docs/docs/end-to-end-testing.md b/docs/docs/end-to-end-testing.md
@@ -169,7 +169,7 @@ describe("Accessibility tests", () => {
 
     cy.focused()
       .should("have.text", "Gatsby")
-      .should("have.attr", "href", "https://www.gatsbyjs.org")
+      .should("have.attr", "href", "https://www.gatsbyjs.com")
       .should("not.have.css", "outline-width", "0px")
   })
   // highlight-end

diff --git a/docs/docs/gatsby-config.md b/docs/docs/gatsby-config.md
@@ -26,7 +26,7 @@ When you want to reuse common pieces of data across the site (for example, your
 module.exports = {
   siteMetadata: {
     title: `Gatsby`,
-    siteUrl: `https://www.gatsbyjs.org`,
+    siteUrl: `https://www.gatsbyjs.com`,
     description: `Blazing fast modern site generator for React`,
   },
 }

diff --git a/docs/docs/gatsby-core-philosophy.md b/docs/docs/gatsby-core-philosophy.md
@@ -81,9 +81,9 @@ We believe the most high-impact way to make the web better is to make it high-qu
 
 One key way Gatsby makes the content web high-quality by default is to neatly bundle the modern JavaScript ecosystem.
 
-Traditional CMS development [presents many challenges](https://www.gatsbyjs.org/blog/2018-10-11-rise-of-modern-web-development/#traditional-cms-development-presents-challenges) such as walled-garden development, difficult-to-maintain local environments, and a challenging target environment.
+Traditional CMS development [presents many challenges](https://www.gatsbyjs.com/blog/2018-10-11-rise-of-modern-web-development/#traditional-cms-development-presents-challenges) such as walled-garden development, difficult-to-maintain local environments, and a challenging target environment.
 
-Modern web development [bundles advances](https://www.gatsbyjs.org/blog/2018-10-11-rise-of-modern-web-development/#modern-frameworks-offer-stability-and-faster-development) in **performance** (bundle splitting, asset prefetching, offline support, image optimization, or server side rendering), **developer experience** (componentization via React, transpilation via Babel, webpack, hot reloading), **accessibility**, and **security** together.
+Modern web development [bundles advances](https://www.gatsbyjs.com/blog/2018-10-11-rise-of-modern-web-development/#modern-frameworks-offer-stability-and-faster-development) in **performance** (bundle splitting, asset prefetching, offline support, image optimization, or server side rendering), **developer experience** (componentization via React, transpilation via Babel, webpack, hot reloading), **accessibility**, and **security** together.
 
 Gatsby's goal is to bundle these advances in an easy to use package. We're open to any and all advances being made in the modern JavaScript world and would love to incorporate them into Gatsby!
 

diff --git a/docs/docs/gatsby-link.md b/docs/docs/gatsby-link.md
@@ -407,4 +407,4 @@ However, if the page has previously loaded, it will not re-request `app-data.jso
 
 - [Authentication tutorial for client-only routes](/tutorial/authentication-tutorial/)
 - [Routing: Getting Location Data from Props](/docs/location-data-from-props/)
-- [`gatsby-plugin-catch-links`](https://www.gatsbyjs.org/packages/gatsby-plugin-catch-links/) to automatically intercept local links in Markdown files for `gatsby-link` like behavior
+- [`gatsby-plugin-catch-links`](https://www.gatsbyjs.com/plugins/gatsby-plugin-catch-links/) to automatically intercept local links in Markdown files for `gatsby-link` like behavior
diff --git a/docs/docs/glossary/markdown.md b/docs/docs/glossary/markdown.md
@@ -21,7 +21,7 @@ Markdown, by contrast, only defines a syntax for a small subset of HTML elements
 ```markdown
 # Markdown!
 
-You can use Markdown to create documents for [Gatsby](https://www.gatsbyjs.org/).
+You can use Markdown to create documents for [Gatsby](https://www.gatsbyjs.com/).
 
 <figure class="chart">
   <object data="chart.svg" type="image/svg+xml"></object>
@@ -37,7 +37,7 @@ When converted to HTML, the preceding Markdown will become the markup below.
 <h1>Markdown!</h1>
 <p>
   You can use Markdown to create documents for
-  <a href="https://www.gatsbyjs.org/">Gatsby</a>.
+  <a href="https://www.gatsbyjs.com/">Gatsby</a>.
 </p>
 <figure class="chart">
   <object data="chart.svg" type="image/svg+xml"></object>
@@ -55,7 +55,7 @@ npm install --save gatsby-source-filesystem gatsby-transformer-remark
 
 The `gatsby-source-filesystem` plugin reads files from your computer. The `gatsby-transformer-remark` plugin makes the contents of your Markdown files available to GraphQL.
 
-You can also try a [Gatsby starter](https://www.gatsbyjs.org/starters/?c=Markdown) package that has Markdown support already included.
+You can also try a [Gatsby starter](https://www.gatsbyjs.com/starters/?c=Markdown) package that has Markdown support already included.
 
 ## Learn more about Markdown
 

diff --git a/docs/docs/glossary/mdx.md b/docs/docs/glossary/mdx.md
@@ -14,7 +14,7 @@ Markdown defines a plain text syntax for HTML elements such as `h1`, `strong`, a
 ```markdown
 # Hello world!
 
-You can use Markdown to create documents for [Gatsby](https://www.gatsbyjs.org/).
+You can use Markdown to create documents for [Gatsby](https://www.gatsbyjs.com/).
 
 <figure class="chart">
   <object data="chart.svg" type="image/svg+xml"></object>
@@ -42,7 +42,7 @@ import { Figure } from './components/Figure';
 
 # Hello world!
 
-You can use Markdown to create documents for [Gatsby](https://www.gatsbyjs.org/).
+You can use Markdown to create documents for [Gatsby](https://www.gatsbyjs.com/).
 
 <Figure data="chart.svg" caption="MDX adoption has increased 120% since last year." />
 ```