chore(docs): 🔒 Fix missing HTTPS on graphql.org links. (#22210)

Author: jbampton

docs/blog/2017-02-21-1-0-progress-update-where-came-from-where-going/index.md

@@ -59,7 +59,7 @@ framework:
 
 - [React](https://reactjs.org/) from Facebook for building UIs
 - [Webpack](https://webpack.js.org/) for bundling JavaScript and CSS
-- [GraphQL](http://graphql.org/) from Facebook for declarative data queries
+- [GraphQL](https://graphql.org/) from Facebook for declarative data queries
 
 While designing Gatsby, I wanted a synthesis of two of my favorite developer
 experiences. The simplicity of building sites with markdown and static site

docs/blog/2017-10-05-portfolio-site-gatsby-wordpress/index.md

@@ -61,7 +61,7 @@ I was skeptical at first: would I have to parse large amounts of JSON to get the
 data I needed? I have never even interacted with the WordPress REST API, how
 will I query it?
 
-The answer... [GraphQL](http://graphql.org/). Gatsby ships with it and through
+The answer... [GraphQL](https://graphql.org/). Gatsby ships with it and through
 an npm install of a
 [gatsby-source plugin](/docs/plugins/) of your choice
 and a tiny bit of a config, you can start querying in no time. I was amazed with

docs/blog/2017-10-20-from-wordpress-to-developing-in-react-starting-to-see-it/index.md

@@ -88,7 +88,7 @@ Beautiful.
 ## GraphQL: SQL-like data queries
 
 One thing I particularly love about Gatsby.js is its inclusion of
-[GraphQL](http://graphql.org/). Like SQL, you
+[GraphQL](https://graphql.org/). Like SQL, you
 use GraphQL to query your data, whether from the WordPress API, Contentful or
 Markdown, and extract a dataset to display in your template.
 

docs/blog/2017-11-08-migrate-from-jekyll-to-gatsby/index.md

@@ -25,7 +25,7 @@ but this was extremely slow.
 Some weeks ago, one of my colleagues at work told me about
 [Gatsby](/) Since I was already learning
 [React](https://reactjs.org/) and had started looking at
-[GraphQL](http://graphql.org/) (after attending a talk at
+[GraphQL](https://graphql.org/) (after attending a talk at
 [Nordic.js](http://nordicjs.com/))—I was very interested in giving it a try.
 
 ## Migrating from Jekyll to Gatsby

docs/blog/2017-12-07-taking-gatsby-for-a-spin/index.md

@@ -21,7 +21,7 @@ GatsbyJS is based on React which means that you'll be writing almost everything
 
 ### GraphQL
 
-Gatsby was my first introduction to [GraphQL](http://graphql.org/learn/) and I'm loving it already. GraphQL is a query language used by Gatsby to let you connect to all kinds of APIs. With it as an abstraction layer, you can pull in all the data you can think of and utilize it in your app. Gatsby comes with plugins to pull in data from several APIs, CMS systems and local files. With GraphQL, you're able to query data from all these sources in a clear and readable way. The data is instantly available in your components and that's just super cool. Also, it comes with a browser-based IDE called Graph*i*QL which starts along with your development environment. You can use it to see which queries are available, test them out, and see what data these queries return.
+Gatsby was my first introduction to [GraphQL](https://graphql.org/learn/) and I'm loving it already. GraphQL is a query language used by Gatsby to let you connect to all kinds of APIs. With it as an abstraction layer, you can pull in all the data you can think of and utilize it in your app. Gatsby comes with plugins to pull in data from several APIs, CMS systems and local files. With GraphQL, you're able to query data from all these sources in a clear and readable way. The data is instantly available in your components and that's just super cool. Also, it comes with a browser-based IDE called Graph*i*QL which starts along with your development environment. You can use it to see which queries are available, test them out, and see what data these queries return.
 
 ![Screenshot of GraphiQl](./grahiql_screenshot.png "GraphiQL")
 

docs/blog/2018-02-16-bright-future-for-the-web/index.md

@@ -24,7 +24,7 @@ It was for those reasons that I was hesitant to pull the trigger on a static sit
 
 One day after airing my grievances about the current state of static site generators on Slack a fellow developer recommend that I check out Gatsby. Gatsby is yet another static site generator but what really set it apart for me was how it was built with [React](https://reactjs.org/) and emphasized a rich plugin system. This was a big plus for me as I was itching to learn more about React and the plugin system alleviated some initial pain that I would have had dealing with mundane tasks. Out of the box you get a fantastic development environment with live reloading that required almost no configuration. With Gatsby specific plugins and React components it can handle pretty much anything you throw at it.
 
-Next came integrating the statically generated site with data stored in a CMS. Again Gatsby was well suited for this and I was able to easily integrate with Contentful via the [gatsby-source-contentful](/packages/gatsby-source-contentful/) plugin. Contentful is an example of a [headless CMS](/docs/headless-cms/), meaning that is is not tied to any particular technology or language. Contentful allows you to store content using a pleasant user interface and it can then output the data via an API. Best of all Contentful puts you in the driver seat and lets you define your own content model however you see fit. Think [WordPress Advanced Custom Fields](https://www.advancedcustomfields.com/) on steroids. With the content stored in Contentful Gatsby then uses the Contentful API along with the awesome power of [GraphQL](http://graphql.org/) to query data at build time. Cool stuff!
+Next came integrating the statically generated site with data stored in a CMS. Again Gatsby was well suited for this and I was able to easily integrate with Contentful via the [gatsby-source-contentful](/packages/gatsby-source-contentful/) plugin. Contentful is an example of a [headless CMS](/docs/headless-cms/), meaning that is is not tied to any particular technology or language. Contentful allows you to store content using a pleasant user interface and it can then output the data via an API. Best of all Contentful puts you in the driver seat and lets you define your own content model however you see fit. Think [WordPress Advanced Custom Fields](https://www.advancedcustomfields.com/) on steroids. With the content stored in Contentful Gatsby then uses the Contentful API along with the awesome power of [GraphQL](https://graphql.org/) to query data at build time. Cool stuff!
 
 The final piece of the puzzle was determining where to host the website. I had recently experimented with Netlify on a somewhat [pointless website for my dog](https://www.doggoforhire.com/) and I was impressed by its ease of use and how they offered a fully featured developer tier for free. In no time I was able to get my Gatsby powered website up and running on Netlify. Then with the help of webhooks I was able to have Contentful tell Netlify to “rebuild” the website whenever a new post was published. Finally with Netlify’s form handling functionality I hooked up a contact form all without a single line of backend code or even a database.
 

docs/blog/2018-04-11-trying-out-gatsby-at-work-and-co/index.md

@@ -73,7 +73,7 @@ Here’s a `modules` field on a `ContentPage` currently in use on production:
 
 ![modules field](./modules.png)
 
-Figuring out how to set this up in GraphQL took some trial and error, but we settled on using [inline fragments](http://graphql.org/learn/queries/#inline-fragments).
+Figuring out how to set this up in GraphQL took some trial and error, but we settled on using [inline fragments](https://graphql.org/learn/queries/#inline-fragments).
 
 The GraphQL looks like this:
 

docs/blog/2018-2-27-why-i-upgraded-my-website-to-gatsbyjs-from-jekyll/index.md

@@ -44,7 +44,7 @@ It offers much much more, however. Gatsby lets me leverage all the modern tools
 
 Let me briefly give a high level overview of how Gatsby works from my short experience using it.
 
-Developing the application is the same as developing a React application, with useful things like [hot module replacement](https://webpack.js.org/guides/hot-module-replacement/) to aid easy development already set up by Gatsby. What’s different is that there is a framework in place to use [GraphQL](http://graphql.org/) queries to pull content into the client side browser environment. React components can define a query and the component will be hydrated with the result of the query as props when it is rendered.
+Developing the application is the same as developing a React application, with useful things like [hot module replacement](https://webpack.js.org/guides/hot-module-replacement/) to aid easy development already set up by Gatsby. What’s different is that there is a framework in place to use [GraphQL](https://graphql.org/) queries to pull content into the client side browser environment. React components can define a query and the component will be hydrated with the result of the query as props when it is rendered.
 
 For example, I defined a `PostTemplate` which will be used to render pages for articles.
 

docs/blog/2018-2-6-choosing-a-back-end/index.md

@@ -21,7 +21,7 @@ Gatsby pitches as a “Blazing-fast static site generator for React”. So if I
 I found Gatsby a real pleasure. You can find tutorials on their site for setup and once you see the code it’s fairly simple. I can personally recommend [Scott Tolinski’s series - available on Youtube](https://www.youtube.com/watch?v=b2H7fWhQcdE&list=PLLnpHn493BHHfoINKLELxDch3uJlSapxg). Gatsby nicely wraps up React and React Router with a nice folder structure, webkit, ES6, Sass support and - importantly - GraphQL.
 
 > **What-QL?** GraphQL is a query language for APIs. Where in the WordPress Days I’d have to get the whole post just to display the title, with GraphQL I can tell the API to give me just the title.
-> [Their site is pretty handy too](http://graphql.org/).
+> [Their site is pretty handy too](https://graphql.org/).
 
 I got the site setup pretty quickly after learning about it. There’s a tonne of tutorials and instructional material around. And you can use as much or as little React as you want. There’s also a [massive list of available plugins](/docs/plugins/), which is only going to grow.
 

docs/blog/2018-3-03-case-study-mike-johnston/index.md

@@ -42,7 +42,7 @@ One way to sidestep a great deal of these concerns is to make use of as much sta
 
 ## WordPress Integration with Triggered Builds
 
-To connect with the content, we used Gatsby’s supported WordPress REST API plugin. This uses WordPress’s API discovery to identify all available endpoints, and then retrieves all content available from each one. It then makes the data available in its own [GraphQL](http://graphql.org/) schema, which it uses to power the build system API. This ends up being a novel and quite effective way to make it easy for frontend developers to integrate with the data generated by the build system. Using a guided graphical query system, developers can discover the data available to them and test out different ways of querying and mutating it before they ever use it in their React components.
+To connect with the content, we used Gatsby’s supported WordPress REST API plugin. This uses WordPress’s API discovery to identify all available endpoints, and then retrieves all content available from each one. It then makes the data available in its own [GraphQL](https://graphql.org/) schema, which it uses to power the build system API. This ends up being a novel and quite effective way to make it easy for frontend developers to integrate with the data generated by the build system. Using a guided graphical query system, developers can discover the data available to them and test out different ways of querying and mutating it before they ever use it in their React components.
 
 Using the custom fields and post types, we built out a structure for managing content in a variety of different places on the site using the WordPress admin. Media is made available via the REST API, and Gatsby downloads each file used in the build locally so that it can apply image processing and responsive sizing. Using small custom scripts in the Gatsby project root, developers can turn WordPress content into GraphQL data that they can use anywhere on a page.
 

docs/blog/gatsbygram-case-study/index.md

@@ -223,7 +223,7 @@ pages.
 
 As you can see above, when defining a page, we can set "context" data, which is
 passed as a `prop` to the component and as a
-[GraphQL variable](http://graphql.org/learn/queries/#variables) in our `GraphQL`
+[GraphQL variable](https://graphql.org/learn/queries/#variables) in our `GraphQL`
 query. For the
 "[post template](https://github.com/gatsbyjs/gatsby/blob/master/examples/gatsbygram/src/templates/post-page.js)",
 we pass the id to the post. Below we use that id to query our `GraphQL` schema

docs/docs/graphql-concepts.md

@@ -114,14 +114,14 @@ as we do and find it useful for all your projects.
 When starting out with GraphQL, we recommend the following two tutorials:
 
 - https://www.howtographql.com/
-- http://graphql.org/learn/
+- https://graphql.org/learn/
 
 [The official Gatsby tutorial](/tutorial/part-four/) also includes an introduction to using GraphQL specifically with Gatsby.
 
 ## How do GraphQL and Gatsby work together?
 
 One of the great things about GraphQL is how flexible it is. People use GraphQL
-with [many different programming languages](http://graphql.org/code/) and for web and native apps.
+with [many different programming languages](https://graphql.org/code/) and for web and native apps.
 
 Most people run GraphQL on a server to respond live to requests for
 data from clients. You define a schema (a schema is a formal way of describing
@@ -232,7 +232,7 @@ See also the following blog posts:
 
 ### Fragments
 
-Notice that in the above example for [querying images](#images), we used `...GatsbyImageSharpFixed`, which is a GraphQL Fragment, a reusable set of fields for query composition. You can read more about them [here](http://graphql.org/learn/queries/#fragments).
+Notice that in the above example for [querying images](#images), we used `...GatsbyImageSharpFixed`, which is a GraphQL Fragment, a reusable set of fields for query composition. You can read more about them [here](https://graphql.org/learn/queries/#fragments).
 
 If you wish to define your own fragments for use in your application, you can use named exports to export them in any JavaScript file, and they will be automatically processed by Gatsby for use in your GraphQL queries.
 
@@ -367,7 +367,7 @@ export const query = graphql`
 
 ### Getting started with GraphQL
 
-- http://graphql.org/learn/
+- https://graphql.org/learn/
 - https://www.howtographql.com/
 - https://reactjs.org/blog/2015/05/01/graphql-introduction.html
 - https://services.github.com/on-demand/graphql/

docs/docs/graphql.md

@@ -3,7 +3,7 @@ title: GraphQL & Gatsby
 overview: true
 ---
 
-When building with Gatsby, you access your data through a query language named [GraphQL](http://graphql.org/). GraphQL allows you to declaratively express your data needs. This is done with `queries`, queries are the representation of the data you need. A query looks like this:
+When building with Gatsby, you access your data through a query language named [GraphQL](https://graphql.org/). GraphQL allows you to declaratively express your data needs. This is done with `queries`, queries are the representation of the data you need. A query looks like this:
 
 ```graphql
 {

docs/docs/migrating-from-v0-to-v1.md

@@ -291,7 +291,7 @@ control over what data they got. In v1, templates and pages can query for
 exactly the data they need.
 
 There will be a more in-depth tutorial and GraphQL-specific documentation soon
-but in the meantime, check out http://graphql.org/ and play around on Gatsby's
+but in the meantime, check out https://graphql.org/ and play around on Gatsby's
 built-in GraphQL IDE (Graph*i*QL) which can be reached when you start the
 development server.
 

docs/tutorial/part-four/index.md

@@ -70,7 +70,7 @@ If you're building a small site, one efficient way to build it is to pull in uns
 
 There are many options for loading data into React components. One of the most
 popular and powerful of these is a technology called
-[GraphQL](http://graphql.org/).
+[GraphQL](https://graphql.org/).
 
 GraphQL was invented at Facebook to help product engineers _pull_ needed data into
 components.

docs/tutorial/part-zero/index.md

@@ -303,7 +303,7 @@ It’s not necessary to be an expert with these already — if you’re not, don
 
 ### What is a website?
 
-For a comprehensive introduction to what a website is -- including an intro to HTML and CSS -- check out “[**Building your first web page**](https://learn.shayhowe.com/html-css/building-your-first-web-page/)”. It’s a great place to start learning about the web. For a more hands-on introduction to [**HTML**](https://www.codecademy.com/learn/learn-html), [**CSS**](https://www.codecademy.com/learn/learn-css), and [**JavaScript**](https://www.codecademy.com/learn/introduction-to-javascript), check out the tutorials from Codecademy. [**React**](https://reactjs.org/tutorial/tutorial.html) and [**GraphQL**](http://graphql.org/graphql-js/) also have their own introductory tutorials.
+For a comprehensive introduction to what a website is -- including an intro to HTML and CSS -- check out “[**Building your first web page**](https://learn.shayhowe.com/html-css/building-your-first-web-page/)”. It’s a great place to start learning about the web. For a more hands-on introduction to [**HTML**](https://www.codecademy.com/learn/learn-html), [**CSS**](https://www.codecademy.com/learn/learn-css), and [**JavaScript**](https://www.codecademy.com/learn/introduction-to-javascript), check out the tutorials from Codecademy. [**React**](https://reactjs.org/tutorial/tutorial.html) and [**GraphQL**](https://graphql.org/graphql-js/) also have their own introductory tutorials.
 
 ### Learn more about the command line
 

packages/gatsby-source-shopify/README.md

@@ -470,6 +470,6 @@ available.
 [gatsby]: https://www.gatsbyjs.org/
 [shopify]: https://www.shopify.com/
 [shopify-storefront-api]: https://help.shopify.com/api/custom-storefronts/storefront-api
-[graphql-inline-fragments]: http://graphql.org/learn/queries/#inline-fragments
+[graphql-inline-fragments]: https://graphql.org/learn/queries/#inline-fragments
 [gatsby-plugin-sharp]: https://github.com/gatsbyjs/gatsby/blob/master/packages/gatsby-plugin-sharp
 [gatsby-image-fragments]: https://github.com/gatsbyjs/gatsby/blob/master/packages/gatsby-image#gatsby-transformer-sharp

packages/gatsby-source-wordpress/README.md

@@ -446,7 +446,7 @@ To access those fields, instead of using their field name, you need to use
 your WordPress pages you would need to use `page_builder_page`).
 
 To access data stored in these fields, you need to use GraphQL
-[inline fragments](http://graphql.org/learn/queries/#inline-fragments). This
+[inline fragments](https://graphql.org/learn/queries/#inline-fragments). This
 require you to know types of nodes. The easiest way to get the types of nodes is to use
 `___GraphiQL` debugger and run the below query (adjust post type and field name):
 

packages/gatsby/src/query/query-watcher.js

@@ -146,7 +146,7 @@ const updateStateAndRunQueries = (isFirstRun, { parentSpan } = {}) => {
 
         If you're more experienced with GraphQL, you can also export GraphQL
         fragments from components and compose the fragments in the Page component
-        query and pass data down into the child component — http://graphql.org/learn/queries/#fragments
+        query and pass data down into the child component — https://graphql.org/learn/queries/#fragments
 
       `)
     }