additional docs/fixes

gatsbyjs · imjoshin · Sep 5, 2022 · Aug 12, 2022 · Aug 12, 2022 · Aug 12, 2022
commit 6c0767c78bff87cf3f611323f8f217d9613a192d
diff --git a/docs/docs/how-to/cloud/create-a-deploy-to-gatsby-cloud-button.md b/docs/docs/how-to/cloud/create-a-deploy-to-gatsby-cloud-button.md
@@ -1,5 +1,5 @@
 ---
-title: "Creating a Deploy to Gatsby Cloud Button"
+title: "Create a Deploy to Gatsby Cloud Button"
 description: "Learn how to add a deploy button to your Github repository"
 ---
 

diff --git a/docs/docs/how-to/cloud/create-site-from-repository.md b/docs/docs/how-to/cloud/create-site-from-repository.md
@@ -1,5 +1,5 @@
 ---
-title: "Create a Site from a Repository"
+title: "Create a Site From a Repository"
 description: "How to create a Gatsby Cloud site from a repository"
 ---
 

diff --git a/docs/docs/how-to/cloud/deploying-functions-on-gatsby-cloud.md b/docs/docs/how-to/cloud/deploying-functions-on-gatsby-cloud.md
@@ -13,7 +13,7 @@ Functions are a Gatsby core feature and are not specific to Gatsby Cloud. To lea
 
 ### Routing in Gatsby Cloud
 
-Functions that are included in a Gatsby project and deployed on Gatsby cloud are available at any build URL. This includes any preview URLs (`gstb.io` domain) or hosting URLs (on `gatsbyjs.io` or your custom domain).
+Functions that are included in a Gatsby project and deployed on Gatsby cloud are available at any build URL. This includes any preview URLs (`gstb.io` domain) or hosting URLs (`gatsbyjs.io` or your custom domain).
 
 ```javascript:title=src/api/hello-world.js
 const sample = (req, res) => {

diff --git a/docs/docs/how-to/cloud/deploying-to-firebase.md b/docs/docs/how-to/cloud/deploying-to-firebase.md
@@ -41,7 +41,7 @@ On the “Firebase Integration” screen choose a Firebase project for deploymen
 
 Firebase allows you to configure customized hosting behavior such as redirects, headers, cache settings, and which files to deploy. You can define these behaviors in a `firebase.json` file. See [Deploying to Firebase](/docs/how-to/previews-deploys-hosting/deploying-to-firebase/) for the Gatsby recommended caching settings.
 
-In order for Gatsby Cloud to use these settings for your Firebase hosting, you’ll need to make sure that your `firebase.json` file ends up in your `public/` directory when your build is complete.
+In order for Gatsby Cloud to use these settings for your Firebase hosting, you’ll need to make sure that your `firebase.json` file ends up in your `/public` directory when your build is complete.
 
 One way you can accomplish this is by adding the following code to your `gatsby-node.js` file:
 

diff --git a/docs/docs/images/contentful-connected-integration.png b/docs/docs/images/contentful-connected-integration.png
diff --git a/docs/docs/images/contentful-quick-connect.png b/docs/docs/images/contentful-quick-connect.png
diff --git a/docs/docs/images/gatsby-cloud-data-sources.png b/docs/docs/images/gatsby-cloud-data-sources.png
diff --git a/docs/docs/reference/cloud/cms-previews.md b/docs/docs/reference/cloud/cms-previews.md
@@ -9,14 +9,14 @@ If your site uses a content management system (CMS), Gatsby Cloud provides a too
 
 A "CMS Preview" is a development build of your site that enables you to make changes in your CMS and see those changes take effect in real-time.
 
-Using CMS Previews requires connecting your site to one of the supported CMSs. Check out the [Connecting to a Content Management System](https://support.gatsbyjs.com/hc/en-us/sections/360011112314-Connecting-to-a-Content-Management-System) tutorials for more information on how to configure your site for CMS Previews.
+Using CMS Previews requires connecting your site to [one of the supported CMSs](/docs/reference/cloud/hosting-and-data-source-integrations). Check out the [Connecting to a Content Management System](https://support.gatsbyjs.com/hc/en-us/sections/360011112314-Connecting-to-a-Content-Management-System) tutorials for more information on how to configure your site for CMS Previews.
 
 ## How CMS Previews are triggered
 
 A CMS Preview build may be triggered when any of the following events occur:
 
 - A change in the connected CMS (such as an autosave while typing, save, or publish action).
-- A Git commit to the production branch configured in "Site Settings"
+- A Git commit to the production branch configured in "Site Settings."
 - Manually clicking the "Trigger Build" or "Restart Preview" button in the Gatsby Cloud user interface.
 - A `POST` request to the Preview Webhook.
 
@@ -46,7 +46,7 @@ Incremental Previews are those noted with the "CLOUD" badge:
 
 This preview builder is only used where incremental previews are not possible. The build process is similar to `gatsby develop` in local development. It is subject to resource timeouts and the preview will not be available until the next build completes after a timeout occurs.
 
-## Preview Extensions
+## Preview extensions
 
 Some CMSs support a preview extension that enables you to view your CMS Preview build without having to leave your CMS. Preview extensions are available for:
 

diff --git a/docs/docs/reference/cloud/hosting-and-data-source-integrations.md b/docs/docs/reference/cloud/hosting-and-data-source-integrations.md
@@ -0,0 +1,48 @@
+---
+title: "Hosting and Data Source Integrations"
+description: "Review the various hosting and CMS platforms available for integration on Gatsby Cloud"
+---
+
+Gatsby Cloud provides integrations for many popular hosting and content management platforms that help make development with Gatsby even more efficient.
+
+## Hosting integrations
+
+Hosting integrations simplify deploying your site to the internet. The following hosting services are officially supported and have automated integrations:
+
+- Azure
+- Amazon Web Services S3
+- Fastly
+- Firebase
+- Google Storage
+- Netlify
+- Vercel
+
+When you set up a hosting integration, your site will automatically be deployed to your chosen service any time a Production Build completes successfully.
+
+## Data source ntegrations
+
+Data source integrations make it easy to connect your site to a content management system (CMS). The following CMS providers are officially supported and can be automatically configured with [Quick Connect](/docs/reference/cloud/quick-connect):
+
+- Contentful
+- Cosmic
+- DatoCMS
+- Sanity
+
+The following CMS providers are also officially supported but require manual configuration:
+
+- Agility
+- Contentstack
+- Drupal
+- Flotiq
+- Kontent
+- Strapi
+- WordPress
+
+Depending on the configuration, whenever you make updates in your CMS, you can automatically trigger Production Builds and CMS Previews for your site.
+
+For details on how to set up a hosting or data source integration, see our [How-To Guides](/docs/how-to/cloud/).
+
+
+
+
+
diff --git a/docs/docs/reference/cloud/quick-connect.md b/docs/docs/reference/cloud/quick-connect.md
@@ -0,0 +1,46 @@
+---
+title: "Quick Connect"
+description: "Automatically configure your CMS integration on Gatsby Cloud using Quick Connect"
+---
+
+Quick Connect is a Gatsby Cloud feature that handles automatically configuring your content management system (CMS) integration. Quick Connect shows up in three places:
+
+- During the "Integrations" step when creating a site from a repository or template.
+- During the "Connect CMS" step when creating a site from a CMS specific template.
+- When setting up a data source integration via "Site Settings".
+
+Quick Connect is available for the following CMS providers:
+
+- Contentful
+- Cosmic
+- DatoCMS
+- Sanity
+- Shopify
+
+## Connecting during site creation
+
+When creating a site from a CMS specific starter, Quick Connect will bootstrap the entire CMS project required to provide content to the new site. All of the content models, content, webhooks, and environment variables will be configured automatically.
+
+When creating a site from a Gatsby project repository, Quick Connect will prompt you to choose the CMS project to associate the site with. For detailed instructions, see the guide for [connecting to your specific CMS](https://support.gatsbyjs.com/hc/en-us/sections/360011112314-Connecting-to-a-Content-Management-System).
+
+## Connecting using Site Settings
+
+You can set up a data source integration for a site you previously created by going to **"Site Settings > Data Sources"**.
+
+![Data sources available for Quick Connect](../../images/gatsby-cloud-data-sources.png)
+
+Clicking **"Connect"** will start the setup process for the data source integration. You will be prompted to authorize Gatsby Cloud to connect to your CMS by logging in to your CMS account or providing an authentication token.
+
+![Contentful Quick Connect authorization screen](../../images/contentful-quick-connect.png)
+
+Once authorized, Quick Connect will automatically configure webhooks, environment variables, and the preview extension (where applicable) for your CMS. 
+
+![Connected Contentful integration](../../images/contentful-connected-integration.png)
+
+Quick Connect assumes some default environment variable names for things like access tokens and project IDs, so you may need to modify them to match the variable names in your project. Again, see the guide for [connecting to your specific CMS](https://support.gatsbyjs.com/hc/en-us/sections/360011112314) for more information. Also, see the [Managing Environment Variables](/docs/reference/cloud/managing-environment-variables/) guide.
+
+
+
+
+
+