gatsbyjs · wardpeet · Oct 14, 2019 · Oct 9, 2019 · Oct 11, 2019 · Oct 14, 2019
diff --git a/docs/docs/add-404-page.md b/docs/docs/add-404-page.md
@@ -1,5 +1,5 @@
 ---
-title: "Adding a 404 Page"
+title: Adding a 404 Page
 ---
 
 To create a 404 page create a page whose path matches the regex

diff --git a/docs/docs/add-a-manifest-file.md b/docs/docs/add-a-manifest-file.md
@@ -1,5 +1,5 @@
 ---
-title: Add a Manifest File
+title: Adding a Manifest File
 ---
 
 If you've run an [audit with Lighthouse](/docs/audit-with-lighthouse/), you may have noticed a lackluster score in the "Progressive Web App" category. Let's address how you can improve that score.

diff --git a/docs/docs/add-a-service-worker.md b/docs/docs/add-a-service-worker.md
@@ -1,5 +1,5 @@
 ---
-title: Add a Service Worker
+title: Adding a Service Worker
 ---
 
 ## What is a service worker

diff --git a/docs/docs/add-custom-webpack-config.md b/docs/docs/add-custom-webpack-config.md
@@ -1,5 +1,5 @@
 ---
-title: "Adding a Custom webpack Config"
+title: Adding a Custom webpack Config
 ---
 
 _Before creating custom webpack configuration, check to see if there's a Gatsby

diff --git a/docs/docs/add-offline-support-with-a-service-worker.md b/docs/docs/add-offline-support-with-a-service-worker.md
@@ -1,5 +1,5 @@
 ---
-title: Add Offline Support with a Service Worker
+title: Adding Offline Support with a Service Worker
 ---
 
 If you've run an [audit with Lighthouse](/docs/audit-with-lighthouse/), you may have noticed a lackluster score in the "Progressive Web App" category. Let's address how you can improve that score.

diff --git a/docs/docs/add-page-metadata.md b/docs/docs/add-page-metadata.md
@@ -1,5 +1,5 @@
 ---
-title: Adding page metadata
+title: Adding Page Metadata
 ---
 
 If you've run an [audit with Lighthouse](/docs/audit-with-lighthouse/), you may have noticed a lackluster score in the "SEO" category. Let's address how you can improve that score.

diff --git a/docs/docs/add-seo-component.md b/docs/docs/add-seo-component.md
@@ -1,5 +1,5 @@
 ---
-title: "Adding an SEO component"
+title: Adding an SEO Component
 ---
 
 Every site on the web has basic _meta-tags_ like the title, favicon or description of the page in their `<head>` element. This information gets displayed in the browser and is used when someone shares your website, e.g. on Twitter. You can give your users and these websites additional data to embed your website with more data — and that's where this guide for a SEO component comes in. At the end you'll have a component you can place in your layout file and have rich previews for other clients, smartphone users, and search engines.

diff --git a/docs/docs/adding-analytics.md b/docs/docs/adding-analytics.md
@@ -1,5 +1,5 @@
 ---
-title: Adding analytics
+title: Adding Analytics
 ---
 
 ## Why use analytics?

diff --git a/docs/docs/adding-forms.md b/docs/docs/adding-forms.md
@@ -1,5 +1,5 @@
 ---
-title: Adding forms
+title: Adding Forms
 ---
 
 Gatsby is built on top of React. So anything that is possible with a React form is possible in Gatsby. Additional details about how to create React forms can be found in the [React forms documentation](https://reactjs.org/docs/forms.html) (which happens to be built with Gatsby!)

diff --git a/docs/docs/adding-pagination.md b/docs/docs/adding-pagination.md
@@ -1,5 +1,5 @@
 ---
-title: Adding pagination
+title: Adding Pagination
 ---
 
 A page displaying a list of content gets longer as the amount of content grows.

diff --git a/docs/docs/adding-search-with-algolia.md b/docs/docs/adding-search-with-algolia.md
@@ -1,5 +1,5 @@
 ---
-title: Adding search with Algolia
+title: Adding Search with Algolia
 ---
 
 Once you've added some content to your site, you'll want to make it easy for your visitors to find what they're looking for. This guide will run you through the process of setting up a custom search experience powered by [Algolia](https://www.algolia.com) on any Gatsby site. You'll be writing functional components that rely on React Hooks so following this guide requires you to be using [React 16.8](https://reactjs.org/blog/2019/02/06/react-v16.8.0) or higher.

diff --git a/docs/docs/adding-search-with-elasticlunr.md b/docs/docs/adding-search-with-elasticlunr.md
@@ -1,5 +1,5 @@
 ---
-title: Adding search with elasticlunr
+title: Adding Search with Elasticlunr
 ---
 
 This is a stub. Help our community expand it.

diff --git a/docs/docs/adding-search-with-js-search.md b/docs/docs/adding-search-with-js-search.md
@@ -1,5 +1,5 @@
 ---
-title: Adding search with js-search
+title: Adding Search with JS Search
 ---
 
 ## Prerequisites

diff --git a/docs/docs/adding-search.md b/docs/docs/adding-search.md
@@ -1,5 +1,5 @@
 ---
-title: "Adding search"
+title: Adding Search
 overview: true
 ---
 

diff --git a/docs/docs/adding-website-functionality.md b/docs/docs/adding-website-functionality.md
@@ -1,5 +1,5 @@
 ---
-title: Adding website functionality
+title: Adding Website Functionality
 overview: true
 ---
 

diff --git a/docs/docs/api-proxy.md b/docs/docs/api-proxy.md
@@ -1,5 +1,5 @@
 ---
-title: "Proxying API Requests in Development"
+title: Proxying API Requests in Development
 ---
 
 ## Resources

diff --git a/docs/docs/awesome-gatsby-resources.md b/docs/docs/awesome-gatsby-resources.md
@@ -1,5 +1,5 @@
 ---
-title: "Awesome Gatsby Resources"
+title: Awesome Gatsby Resources
 ---
 
 A curated list of interesting Gatsby community projects and learning resources.

diff --git a/docs/docs/building-apps-with-gatsby.md b/docs/docs/building-apps-with-gatsby.md
@@ -1,5 +1,5 @@
 ---
-title: "Building Apps with Gatsby"
+title: Building Apps with Gatsby
 ---
 
 Gatsby is an excellent framework for building web apps. You can use Gatsby to create personalized, logged-in experiences with two different approaches.

diff --git a/docs/docs/caching.md b/docs/docs/caching.md
@@ -1,5 +1,5 @@
 ---
-title: "Caching Static Sites"
+title: Caching Static Sites
 ---
 
 An important part of creating a very fast website is setting up proper HTTP caching. HTTP caching allows browsers to cache resources from a website so that when the user returns to a site, very few parts of the website have to be downloaded.

diff --git a/docs/docs/client-only-routes-and-user-authentication.md b/docs/docs/client-only-routes-and-user-authentication.md
@@ -1,5 +1,5 @@
 ---
-title: "Client-Only Routes & User Authentication"
+title: Client-only Routes & User Authentication
 ---
 
 Often you want to create a site with client-only portions that are gated by authentication.

diff --git a/docs/docs/coming-from-react-to-gatsby.md b/docs/docs/coming-from-react-to-gatsby.md
@@ -1,5 +1,5 @@
 ---
-title: "Coming from React to Gatsby: What You Need to Know"
+title: Coming from React to Gatsby: What You Need to Know
 ---
 
 This is a stub. Help our community expand it.

diff --git a/docs/docs/creating-a-source-plugin.md b/docs/docs/creating-a-source-plugin.md
@@ -1,5 +1,5 @@
 ---
-title: "Creating a Source Plugin"
+title: Creating a Source Plugin
 ---
 
 There are two types of plugins that work within Gatsby's data system: "source"

diff --git a/docs/docs/creating-and-modifying-pages.md b/docs/docs/creating-and-modifying-pages.md
@@ -1,5 +1,5 @@
 ---
-title: "Creating and Modifying Pages"
+title: Creating and Modifying Pages
 ---
 
 Gatsby makes it easy to programmatically control your pages.

diff --git a/docs/docs/creating-global-styles.md b/docs/docs/creating-global-styles.md
@@ -1,5 +1,5 @@
 ---
-title: Creating global styles
+title: Creating Global Styles
 ---
 
 Creating global styles for your Gatsby site depends on your styling approach, so we've moved the instructions to the relevant guides:

diff --git a/docs/docs/debugging-the-build-process.md b/docs/docs/debugging-the-build-process.md
@@ -1,5 +1,5 @@
 ---
-title: Debugging the build process
+title: Debugging the Build Process
 ---
 
 Gatsby's `build` and `develop` steps run as a Node.js application which you can debug using standard tools for Node.js applications.

diff --git a/docs/docs/environment-variables.md b/docs/docs/environment-variables.md
@@ -1,5 +1,5 @@
 ---
-title: "Environment Variables"
+title: Environment Variables
 ---
 
 ## Environments and Environment Variables

diff --git a/docs/docs/first-professional-project.md b/docs/docs/first-professional-project.md
@@ -1,5 +1,5 @@
 ---
-title: "First Professional Project"
+title: First Professional Project
 ---
 
 The most important professional Gatsby project you or your organization will ever ship is your first project.

diff --git a/docs/docs/gatsby-in-the-enterprise.md b/docs/docs/gatsby-in-the-enterprise.md
@@ -1,5 +1,5 @@
 ---
-title: "Building With Gatsby in the Enterprise"
+title: Building With Gatsby in the Enterprise
 ---
 
 Some Gatsby advocates may be working inside “enterprise” software development organizations. Others may work at agencies which work closely with such organizations.

diff --git a/docs/docs/gatsby-source-filesystem-programmatic-import.md b/docs/docs/gatsby-source-filesystem-programmatic-import.md
@@ -1,5 +1,5 @@
 ---
-title: gatsby-source-filesystem programmatic import
+title: gatsby-source-filesystem Programmatic Import
 issue: https://github.com/gatsbyjs/gatsby/issues/9018
 ---
 

diff --git a/docs/docs/headless-cms.md b/docs/docs/headless-cms.md
@@ -1,5 +1,5 @@
 ---
-title: What is a Headless CMS and how to source content from one
+title: What is a Headless CMS and How to Source Content from One
 overview: true
 ---
 

diff --git a/docs/docs/importing-assets-into-files.md b/docs/docs/importing-assets-into-files.md
@@ -1,5 +1,5 @@
 ---
-title: "Importing Assets Directly Into Files"
+title: Importing Assets Directly Into Files
 ---
 
 There are two major ways to import assets, such as images, fonts, and files, into a Gatsby site. The default path is to import the file directly into a Gatsby template, page, or component. The alternative path, which makes sense for some edge cases, is to use the [static folder](/docs/static-folder).

diff --git a/docs/docs/interactive-pages.md b/docs/docs/interactive-pages.md
@@ -1,5 +1,5 @@
 ---
-title: Interactive pages
+title: Interactive Pages
 ---
 
 This is a stub. Help our community expand it.

diff --git a/docs/docs/linking-and-prefetching-with-gatsby.md b/docs/docs/linking-and-prefetching-with-gatsby.md
@@ -1,5 +1,5 @@
 ---
-title: Linking and prefetching with Gatsby
+title: Linking and Prefetching with Gatsby
 ---
 
 This is a stub. Help our community expand it.

diff --git a/docs/docs/linking-between-pages.md b/docs/docs/linking-between-pages.md
@@ -1,5 +1,5 @@
 ---
-title: Linking between pages
+title: Linking Between Pages
 ---
 
 This guide covers how to link between pages in a Gatsby site.

diff --git a/docs/docs/local-https.md b/docs/docs/local-https.md
@@ -1,5 +1,5 @@
 ---
-title: "Local HTTPS"
+title: Local HTTPS
 ---
 
 Gatsby provides an easy way to use a local HTTPS server during development, thanks to [devcert](https://github.com/davewasmer/devcert). When you enable the `https` option, a private key and certificate file will be created for your project and used by the development server.

diff --git a/docs/docs/location-data-from-props.md b/docs/docs/location-data-from-props.md
@@ -1,5 +1,5 @@
 ---
-title: "Location Data from Props"
+title: Location Data from Props
 ---
 
 ## What is location data

diff --git a/docs/docs/page-query.md b/docs/docs/page-query.md
@@ -1,5 +1,5 @@
 ---
-title: Querying data in pages with GraphQL
+title: Querying Data in Pages with GraphQL
 ---
 
 Gatsby's `graphql` tag enables page components to retrieve data via a GraphQL query.

diff --git a/docs/docs/performance-tracing.md b/docs/docs/performance-tracing.md
@@ -1,5 +1,5 @@
 ---
-title: "Performance tracing"
+title: "Performance Tracing"
 ---
 
 Gatsby allows a build to be traced, enabling you to find which plugins or parts of the build are taking the longest. The trace information can be viewed in any [OpenTracing](http://opentracing.io/) compatible tool such as [Jaeger](https://www.jaegertracing.io/). You can also use Zipkin compatible tools such as [Zipkin](https://zipkin.io/) or [Honeycomb](https://www.honeycomb.io/).

diff --git a/docs/docs/preoptimizing-images.md b/docs/docs/preoptimizing-images.md
@@ -1,5 +1,5 @@
 ---
-title: Preoptimizing your Images
+title: Preoptimizing Your Images
 ---
 
 Gatsby ships with excellent image optimization capabilities (see the [Image Tutorial](/tutorial/image-tutorial/) for more info). However, this image optimization can come with a cost. It can be fairly CPU intensive, and in some cases may lead to long build times. As a means of debugging and perhaps improving your overall build performance, it _may_ be helpful to pre-optimize your (extremely large) images.

diff --git a/docs/docs/progressive-web-app.md b/docs/docs/progressive-web-app.md
@@ -1,5 +1,5 @@
 ---
-title: Progressive web apps (PWAs)
+title: Progressive Web Apps (PWAs)
 ---
 
 ## What is a progressive web app?

diff --git a/docs/docs/quick-start.md b/docs/docs/quick-start.md
@@ -1,5 +1,5 @@
 ---
-title: "Quick Start"
+title: Quick Start
 ---
 
 This quick start is intended for intermediate to advanced developers. For a gentler intro to Gatsby, [head to our tutorial](/tutorial/)!

diff --git a/docs/docs/reach-router-and-gatsby.md b/docs/docs/reach-router-and-gatsby.md
@@ -1,5 +1,5 @@
 ---
-title: "@reach/router and Gatsby"
+title: @reach/router and Gatsby
 ---
 
 This is a stub. Help our community expand it.

diff --git a/docs/docs/releases-and-migration.md b/docs/docs/releases-and-migration.md
@@ -1,5 +1,5 @@
 ---
-title: "Releases & Migration"
+title: Releases & Migration
 overview: true
 ---
 

diff --git a/docs/docs/remark-plugin-tutorial.md b/docs/docs/remark-plugin-tutorial.md
@@ -1,5 +1,5 @@
 ---
-title: "Remark Plugin Tutorial"
+title: Remark Plugin Tutorial
 ---
 
 [`gatsby-transformer-remark`](/packages/gatsby-transformer-remark) empowers developers to translate Markdown into HTML to be consumed via Gatsby's GraphQL API. Blogs and other content based sites can highly benefit from functionality enabled with this plugin. With this plugin, authors of content for the site don't need to worry about how the site is written or structured but can rather focus on writing engaging posts and content!

diff --git a/docs/docs/rendering-sidebar-navigation-dynamically.md b/docs/docs/rendering-sidebar-navigation-dynamically.md
@@ -1,5 +1,5 @@
 ---
-title: Rendering sidebar navigation dynamically
+title: Rendering Sidebar Navigation Dynamically
 issue: https://github.com/gatsbyjs/gatsby/issues/9779
 ---
 

diff --git a/docs/docs/schema-connections.md b/docs/docs/schema-connections.md
@@ -1,5 +1,5 @@
 ---
-title: Schema connections
+title: Schema Connections
 ---
 
 > This documentation isn't up to date with the latest [schema customization changes](/docs/schema-customization).

diff --git a/docs/docs/schema-customization.md b/docs/docs/schema-customization.md
@@ -1,4 +1,6 @@
-# Customizing the GraphQL Schema
+---
+title: Schema Customization
+---
 
 One of Gatsby's main strengths is the ability to query data from a variety of
 sources in a uniform way with GraphQL. For this to work, a GraphQL Schema must

diff --git a/docs/docs/starters.md b/docs/docs/starters.md
@@ -1,5 +1,5 @@
 ---
-title: "Gatsby Starters"
+title: Gatsby Starters
 ---
 
 The Gatsby CLI tool lets you install **starters**, which are boilerplate Gatsby sites maintained by the community and intended for jump-starting development quickly.

diff --git a/docs/docs/testing-components-with-graphql.md b/docs/docs/testing-components-with-graphql.md
@@ -1,5 +1,5 @@
 ---
-title: Testing components with GraphQL
+title: Testing Components with GraphQL
 ---
 
 If you try to run unit tests on components that use GraphQL queries, you will

diff --git a/docs/docs/testing-css-in-js.md b/docs/docs/testing-css-in-js.md
@@ -1,5 +1,5 @@
 ---
-title: "Testing CSS-in-JS"
+title: Testing CSS-in-JS
 ---
 
 Popular CSS-in-JS libraries like [styled-components](https://github.com/styled-components/styled-components) or [emotion](https://github.com/emotion-js/emotion) can also be tested with the help of [jest-styled-components](https://github.com/styled-components/jest-styled-components) or [jest-emotion](https://github.com/emotion-js/emotion/tree/master/packages/jest-emotion) respectively. These packages improve Jest's built-in snapshot testing experience and are a great way to help avoid unintended changes to your website's UI. Please refer to your package's documentation to see if it also offers testing capabilities.

diff --git a/docs/docs/testing-react-components.md b/docs/docs/testing-react-components.md
@@ -1,5 +1,5 @@
 ---
-title: "Testing React components"
+title: Testing React Components
 ---
 
 _The recommended testing framework is [Jest](https://jestjs.io/). This guide assumes that you followed the [Unit testing](/docs/unit-testing) guide to setup Jest._

diff --git a/docs/docs/third-party-graphql.md b/docs/docs/third-party-graphql.md
@@ -1,5 +1,5 @@
 ---
-title: "Using third-party GraphQL APIs"
+title: Using Third-party GraphQL APIs
 ---
 
 Gatsby v2 introduces a simple way to integrate any GraphQL API into Gatsby's GraphQL. You can integrate both third-party APIs, like GitHub's, APIs of services like GraphCMS or your custom GraphQL API.

diff --git a/docs/docs/what-is-a-plugin.md b/docs/docs/what-is-a-plugin.md
@@ -1,5 +1,5 @@
 ---
-title: "What is a Plugin?"
+title: What is a Plugin?
 ---
 
 Gatsby plugins are Node.js packages that implement Gatsby APIs. For larger, more complex sites, plugins let you modularize your site customizations into site-specific plugins.

diff --git a/docs/docs/winning-over-marketers.md b/docs/docs/winning-over-marketers.md
@@ -1,5 +1,5 @@
 ---
-title: "Winning Over Marketers"
+title: Winning Over Marketers
 ---
 
 Some things that marketers care about include:

diff --git a/docs/docs/winning-over-stakeholders.md b/docs/docs/winning-over-stakeholders.md
@@ -1,5 +1,5 @@
 ---
-title: "Winning Over Stakeholders"
+title: Winning Over Stakeholders
 ---
 
 Any website project has multiple stakeholders, such as developers, marketers, content creators, engineering leaders, executives, and clients.