chore(docs): Old occurrences of gatbyjs.org (#34402)

* ✏️ Typo: gatbyjs.org -> gatsbyjs.com

* change gatsbyjs.org instances to gatsby.com in /docs

* ⚡️ Use relative links to make use of gatsby-link

docs/contributing/gatsby-style-guide.md

@@ -42,8 +42,8 @@ If the content is already somewhere else on the .org site, feel free to copy and
 
 Possible sources of great research materials:
 
-- blogposts (on gatsbyjs.org and other sites)
-- docs (on gatsbyjs.org and other sites)
+- blogposts (on gatsbyjs.com and other sites)
+- docs (on gatsbyjs.com and other sites)
 - video tutorials
 - Discord or Twitter conversations
 - search engine results
@@ -495,7 +495,7 @@ Attributes:
 
 - intermediate to advanced at React
 - frontend developer
-- prefer using a search engine and/or `ctrl + f` to find things on the gatsbyjs.org site
+- prefer using a search engine and/or `ctrl + f` to find things on the gatsbyjs.com site
 
 Looking for:
 

docs/contributing/managing-pull-requests.md

@@ -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.com).
+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.com](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.
 

docs/contributing/where-to-participate.md

@@ -7,7 +7,7 @@ We want contributing to Gatsby to be fun, enjoyable, and educational for anyone
 - Blogging, speaking about, or creating tutorials about one of Gatsby's many features. Mention [@gatsbyjs on Twitter](https://twitter.com/gatsbyjs) and/or email `devrel [at] gatsbyjs [dot] com` so we can give pointers and tips (if you want them 😄) and help you spread the word. Please add your blog posts and videos of talks to our [Awesome Gatsby](/docs/awesome-gatsby-resources/) page.
 - Presenting at meetups and conferences about your Gatsby projects. Your unique challenges and successes in building things with Gatsby can provide great speaking material. We'd love to review your talk abstract/CFP, so get in touch with us if you'd like some help!
 - [Submitting new feature ideas through an RFC](/blog/2018-04-06-introducing-gatsby-rfc-process/)
-- Submitting new documentation; titles in the side navigation on [docs](/docs) which are lighter in color on gatsbyjs.org are stubs and need contributions
+- Submitting new documentation; titles in the side navigation on [docs](/docs) which are lighter in color on gatsbyjs.com are stubs and need contributions
 - Tweeting about things you [#buildwithgatsby](https://twitter.com/search?q=%23buildwithgatsby) (make sure to use the hashtag and/or @ mention us!)
 - Submitting documentation updates, enhancements, designs, or bug fixes
 - Submitting spelling or grammar fixes

docs/docs/how-to/styling/using-web-fonts.md

@@ -18,7 +18,7 @@ Some examples of web font services include [Google Fonts](https://fonts.google.c
 
 ### How to use Web Font Loader with Typekit
 
-You can add Typekit Web Fonts to your project by using the [gatsby-plugin-web-font-loader](https://www.gatsbyjs.org/packages/gatsby-plugin-web-font-loader/?=font) and your [Adobe Fonts project id](https://fonts.adobe.com/my_fonts#web_projects-section). For example, this is how you can add Futura to your project.
+You can add Typekit Web Fonts to your project by using the [gatsby-plugin-web-font-loader](/plugins/gatsby-plugin-web-font-loader/?=font) and your [Adobe Fonts project id](https://fonts.adobe.com/my_fonts#web_projects-section). For example, this is how you can add Futura to your project.
 
 First, install the Gatsby plugin with npm:
 

docs/docs/using-gatsby-professionally/winning-over-marketers.md

@@ -51,4 +51,4 @@ A perception marketers often have of developers is that they are not very busine
 
 The explanations above -- whether you use them word-for-word or restate them in your own and your organization's language -- are intended to demonstrate concern for the business as a whole, so marketers see you as a trusted partner.
 
-_Want to read more on this topic? Check out [How to Talk About Gatsby To Your Clients And Team](https://www.gatsbyjs.com/blog/2019-03-07-sell-gatsby-to-clients/) by [Linda Watkins](https://www.gatsbyjs.org/contributors/linda-watkins/)._
+_Want to read more on this topic? Check out [How to Talk About Gatsby To Your Clients And Team](https://www.gatsbyjs.com/blog/2019-03-07-sell-gatsby-to-clients/) by [Linda Watkins](https://www.gatsbyjs.com/contributors/linda-watkins/)._

packages/gatsby-source-wordpress/docs/community-and-support.md

@@ -2,7 +2,7 @@
 
 Fortunately there are very strong WPGraphQL and Gatsby communities!
 
-Check out this [GatsbyJS page](https://www.gatsbyjs.org/contributing/community/) or this [WPGraphQL page](https://www.wpgraphql.com/community-and-support/) on community for more information about each community.
+Check out this [GatsbyJS page](https://www.gatsbyjs.com/contributing/community/) or this [WPGraphQL page](https://www.wpgraphql.com/community-and-support/) on community for more information about each community.
 
 The WPGraphQL Slack is a great place to get help. Feel free to [open an issue in this repo](https://github.com/gatsbyjs/gatsby/issues/new) as well (after you've searched for a previously existing issue).
 

packages/gatsby-source-wordpress/docs/getting-started.md

@@ -4,7 +4,7 @@ If you've had previous experience with Gatsby or you like to move fast, you can
 
 ## Quick start
 
-1. [Install Node, Gatsby, and gatsby-cli](https://www.gatsbyjs.org/docs/)
+1. [Install Node, Gatsby, and gatsby-cli](https://www.gatsbyjs.com/docs/)
 2. Install [a starter](https://github.com/gatsbyjs/gatsby-starter-wordpress-blog) `gatsby new my-wordpress-gatsby-site https://github.com/gatsbyjs/gatsby-starter-wordpress-blog`
 3. Install and activate both of the following plugins in a live WordPress instance.
 

packages/gatsby-source-wordpress/docs/migrating-from-other-wp-source-plugins.md

@@ -6,7 +6,7 @@ From what we've seen migrating is a fairly painless process as the GraphQL schem
 
 **Note**: If you're using Gatsby Cloud and you have `gatsby-source-wordpress@v3` and `gatsby-source-wordpress` installed in the same site, only the experimental plugin will receive webhook updates when updating content.
 
-[Graphiql](https://www.gatsbyjs.org/docs/running-queries-with-graphiql/) is your best friend when migrating from the last major version of this plugin. Run `gatsby develop` and visit `http://localhost:8000/___graphiql`
+[Graphiql](https://www.gatsbyjs.com/docs/running-queries-with-graphiql/) is your best friend when migrating from the last major version of this plugin. Run `gatsby develop` and visit `http://localhost:8000/___graphiql`
 
 Any node list queries such as `allWordpressPage { nodes { title } }` will need to be updated to match the new WordPress types in the Gatsby schema. The new pattern for type names is `Wp` and then the capitalized type such as `Page`. So to replace the node list query above, you would write `allWpPage { nodes { title } }`.
 
@@ -60,7 +60,7 @@ So your query would change to look like this:
 
 ### `gatsby-source-graphql` and inline fragments
 
-Any inline fragments will need to be updated since type names have changed. Use Gatsby's [Graphiql](https://www.gatsbyjs.org/docs/running-queries-with-graphiql/) at `http://localhost:8000/___graphiql` with `gatsby develop` running to determine how your inline fragment typenames should be modified.
+Any inline fragments will need to be updated since type names have changed. Use Gatsby's [Graphiql](https://www.gatsbyjs.com/docs/running-queries-with-graphiql/) at `http://localhost:8000/___graphiql` with `gatsby develop` running to determine how your inline fragment typenames should be modified.
 
 ### `gatsby-source-graphql` and `gatsby-plugin-image`
 

packages/gatsby-source-wordpress/docs/problems-with-v3.md

@@ -4,7 +4,7 @@
 
 - The inflexibility and lack of an enforced schema for this API made proper node caching technically possible but functionally impossible. It also made it impossible to know beforehand the shape and type of data to expect which made it impossible to programmatically determine how to use the returned data.
 - The REST API is largely untyped, and REST does not enforce typing even if it was.
-  - This means Gatsby needed to use [inference](https://www.gatsbyjs.org/docs/glossary/#inference) to automatically build GraphQL types for the data that was returned from WP. The big issue with this is: if all data of a type is removed from WP, your Gatsby site's GraphQL queries will break because no data means Gatsby can no longer can infer the data structure. This led to a lot of odd and counterintuitive issues and a poor developer/content creator experience.
+  - This means Gatsby needed to use [inference](https://www.gatsbyjs.com/docs/glossary/#inference) to automatically build GraphQL types for the data that was returned from WP. The big issue with this is: if all data of a type is removed from WP, your Gatsby site's GraphQL queries will break because no data means Gatsby can no longer can infer the data structure. This led to a lot of odd and counterintuitive issues and a poor developer/content creator experience.
   - If we were to manually write out types for the entire core WP REST API so that we no longer needed to use inference, any custom WP REST plugins would not work and would require a lot of additional tedious and error prone work to support these plugins changing their data structure over time.
 - REST does not have a popularly used standard way of implementing connections between nodes
   - For example if you fetch 100 posts, you will also be fetching repeated data if each post includes data about the posts author including their name and email, etc. Perhaps all the posts had the same author and so we fetched 100x more data than we needed to.

packages/gatsby-source-wordpress/docs/tutorials/building-a-new-site-wordpress-and-gatsby.md

@@ -13,7 +13,7 @@ gatsby new wordpress-tutorial-site
 cd wordpress-tutorial-site
 ```
 
-Install the `gatsby-source-wordpress` plugin. For extra reading on the plugin’s features and examples of GraphQL queries not included in this tutorial, see the [`gatsby-source-wordpress` plugin’s README file](https://www.gatsbyjs.org/packages/gatsby-source-wordpress).
+Install the `gatsby-source-wordpress` plugin. For extra reading on the plugin’s features and examples of GraphQL queries not included in this tutorial, see the [`gatsby-source-wordpress` plugin’s README file](https://www.gatsbyjs.com/packages/gatsby-source-wordpress).
 
 ```shell
 npm install gatsby-source-wordpress
@@ -176,7 +176,7 @@ To do this, you need to:
 1. Create pages for each blog post
 2. Link up the title on the index page with the post page.
 
-If you haven't already, please read through [Part 7](https://www.gatsbyjs.org/tutorial/part-7/) of the foundational tutorial, as it goes through the concept and examples of this process with Markdown instead of WordPress.
+If you haven't already, please read through [Part 7](https://www.gatsbyjs.com/docs/tutorial/part-7/) of the foundational tutorial, as it goes through the concept and examples of this process with Markdown instead of WordPress.
 
 ### Creating pages for each blog post
 
@@ -207,7 +207,7 @@ exports.createPages = ({ graphql, actions }) => {
 }
 ```
 
-Next, [stop and restart](https://www.gatsbyjs.org/tutorial/part-0/#view-your-site-locally) the `gatsby develop` environment. As you watch the terminal you should see two Post objects log to the terminal.
+Next, [stop and restart](https://www.gatsbyjs.com/docs/tutorial/part-0/#view-your-site-locally) the `gatsby develop` environment. As you watch the terminal you should see two Post objects log to the terminal.
 
 Excellent! As explained in Part 7 of the tutorial, this `createPages` export is one of the Gatsby "workhorses" and allows us to create your blog posts (or pages, or custom post types, etc.) from your WordPress install.
 

packages/gatsby-source-wordpress/docs/tutorials/configuring-previews-legacy.md

@@ -4,7 +4,7 @@ Once configured in the GatsbyJS settings page in wp-admin, Previews will work ou
 
 ### Connecting Preview
 
-To get started, set up a Preview instance on [Gatsby Cloud](https://www.gatsbyjs.com/) or set up your [self-hosted Preview instance](https://www.gatsbyjs.org/docs/running-a-gatsby-preview-server/). If you want to try out Preview but aren't sure whether you want to subscribe to Gatsby Cloud or self-host, you can start a free 2 week Gatsby Cloud trial with no credit card to help you make up your mind!
+To get started, set up a Preview instance on [Gatsby Cloud](https://www.gatsbyjs.com/) or set up your [self-hosted Preview instance](https://www.gatsbyjs.com/docs/running-a-gatsby-preview-server/). If you want to try out Preview but aren't sure whether you want to subscribe to Gatsby Cloud or self-host, you can start a free 2 week Gatsby Cloud trial with no credit card to help you make up your mind!
 
 #### WordPress Settings
 

packages/gatsby-source-wordpress/docs/why-use-this-plugin.md

@@ -16,18 +16,18 @@ Some highlights:
 - A componentized architecture for your front-end code with React (better maintainability)
 - A simpler way of asking for data with GraphQL (no need to remember dozens of data retrieval functions)
 - Client-side state management with React opens up the doors to creating an app-like or full on app experience for your users
-- [Gatsby is committed to ensuring we are as accessible as possible out of the box](https://www.gatsbyjs.org/blog/2019-04-18-gatsby-commitment-to-accessibility/)
+- [Gatsby is committed to ensuring we are as accessible as possible out of the box](https://www.gatsbyjs.com/blog/2019-04-18-gatsby-commitment-to-accessibility/)
 
 Additionally, this plugin is a great reason to use Gatsby with WordPress. Many of the complex and difficult aspects of going decoupled with WordPress have been abstracted for you behind the scenes, so you can work on building awesome apps and sites instead of reinventing the wheel to get decoupled WordPress working in your project.
 
-Check out this page on [convincing developers why Gatsby is awesome](https://www.gatsbyjs.org/docs/winning-over-developers/#specific-benefits). It's meant for developers who want to convince their coworkers to use Gatsby, but it actually does a great job of describing directly to you the main reasons why using Gatsby is a great idea :)
+Check out this page on [convincing developers why Gatsby is awesome](https://www.gatsbyjs.com/docs/winning-over-developers/#specific-benefits). It's meant for developers who want to convince their coworkers to use Gatsby, but it actually does a great job of describing directly to you the main reasons why using Gatsby is a great idea :)
 
 ### Related information:
 
 - [ReactJS](https://reactjs.org/)
-- [Gatsy Site Showcase](https://www.gatsbyjs.org/showcase/)
-- [Gatsby Case Study Blog posts](https://www.gatsbyjs.org/blog/tags/case-studies/)
-- [How Tinder is using WordPress with Gatsby](https://www.gatsbyjs.org/blog/2020-04-07-LA-2020-Boss/)
+- [Gatsy Site Showcase](https://www.gatsbyjs.com/showcase/)
+- [Gatsby Case Study Blog posts](https://www.gatsbyjs.com/blog/tags/case-studies/)
+- [How Tinder is using WordPress with Gatsby](https://www.gatsbyjs.com/blog/2020-04-07-la-2020-boss/)
 - [Zac Gordon on what Gatsby is and why to use it](https://www.youtube.com/watch?v=GuvAMcsoreI)
 
 ## Why use this plugin instead of X source plugin?

scripts/i18n/README.md

@@ -79,4 +79,4 @@ Usage:
 yarn run-all [script name]
 ```
 
-The `run-all` script runs the script provided in the argument across all languages for which there are translations of gatbyjs.org, listed in /www/src/i18n.json.
+The `run-all` script runs the script provided in the argument across all languages for which there are translations of gatsbyjs.com, listed in /www/src/i18n.json.