gatsbyjs · Jul 15, 2020 · Jul 15, 2020 · Jul 15, 2020 · Jul 16, 2020 · Jul 16, 2020
diff --git a/CODEOWNERS b/CODEOWNERS
@@ -4,6 +4,7 @@
 # All docs must be reviewed by the docs team.
 /docs/                                          @gatsbyjs/learning
 **/README.md                                    @gatsbyjs/learning
+dictionary.txt                                  @gatsbyjs/learning
 
 # Benchmarks
 /benchmarks/                                    @duffn @pvdz @smthomas
@@ -16,7 +17,6 @@
 
 # Themes
 
-/docs/docs/themes/                              @gatsbyjs/themes-core
 /packages/gatsby-plugin-mdx/                    @gatsbyjs/themes-core
 /packages/gatsby/src/bootstrap/load-themes      @gatsbyjs/themes-core
 /packages/gatsby-recipes/                       @gatsbyjs/themes-core

diff --git a/dictionary.txt b/dictionary.txt
@@ -29,6 +29,7 @@
 18F
 1920s
 1990s
+1GB
 1M
 1pm
 1px
@@ -66,6 +67,7 @@
 4g
 5-10X
 500M
+500mb
 500ms
 500px
 50k
@@ -95,7 +97,6 @@
 a11y
 A11y
 Abhishek
-about-uncentered
 Abramov
 ACF
 Acquia
@@ -1883,8 +1884,8 @@ Swartz
 Syfy
 symlink
 syntaxes
-Systemizing
 systemizing
+Systemizing
 tachyons
 Tachyons
 Tada
@@ -1983,6 +1984,7 @@ Ultra-schnellen
 un-transpiled
 Unbundling
 uncached
+uncentered
 uncheck
 uncollapse
 uncomment
@@ -2089,11 +2091,12 @@ webhook
 webhooks
 WebP
 webpack
-Webpack
+*Webpack
 webpack-merge
 webpack-runtime
 WebpackError
 webpacks
+*Webpacks
 webpage
 webpages
 WebPagetest
@@ -2118,7 +2121,6 @@ wireframe-level
 Wirth
 Wiseman
 wishlist
-with-layout2
 with-navigation2
 Woah
 WooCommerce

diff --git a/docs/blog/100days/performance/index.md b/docs/blog/100days/performance/index.md
@@ -14,7 +14,7 @@ _Learn more about [#100DaysOfGatsby here](/blog/100days)!_
 
 ## Make Your Site Faster Than The Competition’s
 
-Over the last few weeks we’ve helped you get your site production-ready by focusing on [SEO](/blog/100days/seo/) and [accessibility](/blog/100days/accessibility/). This week we purposely saved “performance” for last, because the features we are inviting you to add to your site can have a positive impact on your search engine rankings (SEO), and your user's ability to consume your content (accessiblity).
+Over the last few weeks we’ve helped you get your site production-ready by focusing on [SEO](/blog/100days/seo/) and [accessibility](/blog/100days/accessibility/). This week we purposely saved “performance” for last, because the features we are inviting you to add to your site can have a positive impact on your search engine rankings (SEO), and your user's ability to consume your content (accessibility).
 
 If you embrace and master all of the resources we have shared in the last three weeks, you’ll create web projects that are noticeably faster, more usable, and will help your clients reach their business goals!
 

diff --git a/docs/blog/100days/use-themes/index.md b/docs/blog/100days/use-themes/index.md
@@ -18,7 +18,7 @@ For the final two challenges you will explore using and creating Gatsby Themes!
 
 So far you’ve created a Gatsby site from scratch, and added features for usage on a single site. Gatsby Themes opens up the possibility to leverage good ideas from the Gatsby ecosystem, and share your own configurations and designs. You can think of Gatsby Themes as handy website kits that can be shared, customized, and stacked together.
 
-Before you dive into creating a theme, our resources below will point you to the philosophy behind Gatsby Themes and common use cases. Then we’ll show you how to use a theme in your poject. And next week you'll explore creating your own theme!
+Before you dive into creating a theme, our resources below will point you to the philosophy behind Gatsby Themes and common use cases. Then we’ll show you how to use a theme in your project. And next week you'll explore creating your own theme!
 
 ### Gatsby Theme Usage Resources
 

diff --git a/docs/blog/2018-08-01-partner-program/index.md b/docs/blog/2018-08-01-partner-program/index.md
@@ -5,42 +5,14 @@ author: Linda Watkins
 tags: ["partner-program", "agencies"]
 ---
 
-import HubspotForm from "@components/hubspot-form"
-
-In the business of building websites or web apps for clients? Get the support you need and the visibility you deserve. Gatsby’s Partner Program is here!
+In the business of building websites or web apps for clients? Get the support you need and the visibility you deserve. The [Gatsby Partner Program](https://www.gatsbyjs.com/partner/) is here!
 
 ## Grow with Gatsby
 
-Gatsby is growing like gangbusters due to the contributions of this great open source community—thank you! We’ve been hearing from more and more agencies and website development shops about how they’re embracing Gatsby to build blazing-fast websites and web apps for their clients. We want to support these efforts and help you get the word out about your amazing work.
+Gatsby is growing like gangbusters due to the contributions of this great open source community—thank you! We’ve been hearing from more and more agencies and website development companies about how they’re embracing Gatsby to build blazing-fast websites and web apps for their clients. We want to support these efforts and help you get the word out about your amazing work.
 
 ## Gatsby Partner Program
 
-With that in mind, we’re happy to announce Gatsby’s Partner Program. Partner with Gatsby to get your agency or client websites highlighted on the [Gatsby Site Showcase](/showcase/) to generate more visibility to your work. We’ll also be building out the partner program in the coming months to add more benefits like training for developers, joint case studies, free swag, and more. To show interest in the program, there are a few simple steps to get started.
-
-## Steps to get started:
-
-Step 1: Build a client (or agency) website with Gatsby.
-
-Step 2: Submit your Gatsby client or agency website to the [Site Showcase](/contributing/site-showcase-submissions/).
-
-Step 3: Fill out the form below to let us know you’re interested in learning more about future developments to Gatsby’s Partner Program.
-
-So what’s next for partners?
-
-We’ll have a lot more features and benefits coming soon. Future additions to the program will include:
-
-- Lead capture form on your agency’s [Site Showcase](/showcase/) page so people can get in touch with you directly
-- Live training for developers (in-person or virtual)
-- Joint case studies that are highlighted on the Gatsby blog, website, and other channels
-- Dedicated pages on [Gatsbyjs.org](https://github.com/gatsbyjs/rfcs/blob/8bb84d8a4ed495678ae76645f940a03ad562a7d1/text/0008--individual-agency-company-pages.md#agency-pages) highlighting partners & showcasing the sites they've built with Gatsby
-- Free swag! Exclusive partner swag coming soon.
-
-Fill out the form below to let us know your interest in the Gatsby Partner Program!
-
-### Partner application form:
+With that in mind, we’re happy to announce Gatsby’s Partner Program. Partner with Gatsby to get access to sales and marketing materials, a view into the Gatsby roadmap, revenue share for referrals, access to sales and tech support, and more.
 
-<HubspotForm
-  portalId="4731712"
-  formId="bbad5044-d31d-4473-bd57-62cb64fdc811"
-  sfdcCampaignId="701f4000000VDrYAAW"
-/>
+Learn more and apply to the [Gatsby Partner Program](https://www.gatsbyjs.com/partner/).
diff --git a/docs/blog/2020-04-15-announcing-gatsby-recipes/index.md b/docs/blog/2020-04-15-announcing-gatsby-recipes/index.md
@@ -30,7 +30,7 @@ We want there to be 10s of thousands of recipes you can search, run, and remix p
 
 ## Human-friendly automation
 
-Recipes are written in [MDX](https://mdxjs.com/)—a combination of Markdown and React components—readable by both humans and machines. (Other “infrastructure as code” automations, like AWS CloudFormation, use kinda-sorta legible YAML templates that favor the machines). We picked MDX to make Gatsby Recipes instructions and explanations easily readable for humans while using React components syntax to _declare_ to Gatsby Recipes the desired state of the world. This means Gatsby Recipes read like actual little recipes. Writing and using them could be...dare we say it..._fun_.
+Recipes are written in [MDX](https://mdxjs.com/)—a combination of Markdown and React components—readable by both humans and machines. (Other “[infrastructure as code](/docs/glossary/infrastructure-as-code/)” automations, like AWS CloudFormation, use kinda-sorta legible YAML templates that favor the machines). We picked MDX to make Gatsby Recipes instructions and explanations easily readable for humans while using React components syntax to _declare_ to Gatsby Recipes the desired state of the world. This means Gatsby Recipes read like actual little recipes. Writing and using them could be...dare we say it..._fun_.
 
 We take a lot of inspiration from literate programming tools like [Eve](http://witheve.com/deepdives/literate.html) and [HyperCard](https://en.wikipedia.org/wiki/HyperCard).
 

diff --git a/docs/blog/2020-05-21-gatsby-recipes/index.md b/docs/blog/2020-05-21-gatsby-recipes/index.md
@@ -40,11 +40,11 @@ The reason this will cause Storybook to error is because the `<Link />` componen
 
 Storybook has anticipated this issue, fortunately, and so there is a method whereby you can write your own webpack config and pass it on to combine it with the default Storybook webpack config. This then aids in the transpiling of any ES6 code located in `node_modules` to CommonJS.
 
-If (like me) Webpack scares you a little bit, you’ll likely want to avoid writing any Webpack config and just get on with developing your UI. You could try not creating any `.stories` that include a `<Link />` component but this will only get you so far.
+If (like me) webpack scares you a little bit, you’ll likely want to avoid writing any webpack config and just get on with developing your UI. You could try not creating any `.stories` that include a `<Link />` component but this will only get you so far.
 
 You may at some point also wish to create a story for a component that contains a `useStaticQuery` hook, and if you do that you’ll again see Storybook errors but this time relating to GraphQL queries. The reason for this is because the Gatsby build processes remove any GraphQL queries when you run either of the build processes; `gatsby develop` or `gatsby build`.
 
-So, as mentioned before, when you spin up Storybook these Gatsby-specific build processes are simply not run. In order to to strip out GraphQL queries we need to use Webpack again and utilize a package called `babel-plugin-remove-graphql-queries`.
+So, as mentioned before, when you spin up Storybook these Gatsby-specific build processes are simply not run. In order to to strip out GraphQL queries we need to use webpack again and utilize a package called `babel-plugin-remove-graphql-queries`.
 
 And if (like me) Babel also scares you a little bit, you might be having a think about giving up using Storybook and Gatsby all together.
 

diff --git a/docs/blog/2020-06-18-Gatsby-cli-survey-2/index.md b/docs/blog/2020-06-18-Gatsby-cli-survey-2/index.md
@@ -15,7 +15,7 @@ Our second set of results from the Gatsby Command Line Survey have been collecte
 
 You may have seen this in the command line recently:![screen shot of command line survey first question in Mac text editor](./image1.png)
 
-See this previous blogpost, ["Gatsby's First Survey Goes Command Line (and here is what users have to say so far)"](https://www.gatsbyjs.org/blog/2020-04-17-gatsby-survey-goes-command-line/) for answers to the following questions:
+See this previous blogpost, ["Gatsby's First Survey Goes Command Line (and here is what users have to say so far)"](/blog/2020-04-17-gatsby-survey-goes-command-line/) for answers to the following questions:
 
 - How can I take this survey?
 - What are the survey questions?
@@ -71,6 +71,6 @@ Requests for incremental builds and complaints about slow builds have decreased
 
 Thank you again to all who have responded to the survey so far; your responses help guide the focus of the community to answer real-world needs. If you haven't filled out the survey yet, you can run `gatsby feedback` at any time after upgrading your version of `gatsby` in a project's `package.json` file, and then rerunning dependency and install commands. We would love to hear from you!
 
-Otherwise, wait to see the survey appear in a CLI near you! The plan is to do this every 3 months, at the most, and then report results. (If you'd like to opt out, visit [https://www.gatsbyjs.org/docs/CLI-feedback/#how-to-opt-out](/docs/telemetry/#how-to-opt-out/)).
+Otherwise, wait to see the survey appear in a CLI near you! The plan is to do this every 3 months, at the most, and then report results. (If you'd like to opt out, see the [Telemetry Docs](/docs/telemetry/#how-to-opt-out)).
 
 If you haven't used Gatsby yet, try it out and let us know what you think! You can install the Gatsby CLI using `npm install -g gatsby-cli` ([see the Quickstart Guide for more details](/docs/quick-start/)).
diff --git a/docs/blog/2020-07-15-Little-Caesars-Delivers-with-Gatsby/index.md b/docs/blog/2020-07-15-Little-Caesars-Delivers-with-Gatsby/index.md
@@ -11,7 +11,7 @@ tags:
 
 ![A group of people eating Little Caesars pizza in an office](./little-caesars-busted.png)
 
-Starting from a single, family-owned restaurant in 1959, Little Caesars has grown into the third-largest pizza chain in the world. Today the company has stores in all 50 U.S. states, plus and 26 additional countries and territories. Little Caesars runs more than 20 websites to support all of those stores with marketing content and easy online pizza ordering.
+Starting from a single, family-owned restaurant in 1959, Little Caesars has grown into the third-largest pizza chain in the world. Today the company has stores in all 50 U.S. states, plus 26 additional countries and territories. Little Caesars runs more than 20 websites to support all of those stores with marketing content and easy online pizza ordering.
 
 The company's existing site architecture, however, was far from streamlined, and this impeded both performance and development. The Little Caesars technical team decided that the best approach for providing an outstanding customer experience across all those different sites would be a unified ordering platform with scalability built in.
 
@@ -68,6 +68,6 @@ Little Caesars new Gatsby-based architecture turned out to be a gift that keeps
 
 “That definitely contributed to our bottom line in Canada when the pandemic hit,” he continues, but there was another payoff that the team savored even more: “Leadership presented us with an impossible task, and we turned around and said ‘We’re already prepared for that, here you go!’”
 
-Customers now enjoy a single, unified, and responsive web experience that lets them find what they want quickly. But the move to a new website framework behind the scenes was pretty much invisible to customers. “We had some feedback about the site being speedy, but we had no major support issues — and that’s a very good thing,” says Smith.
+Customers now enjoy a single, unified, and responsive web experience that lets them find what they want quickly. But the move to a new website framework behind the scenes was pretty much invisible to customers. “We heard feedback about the site being speedy, but no major support issues — and that’s a very good thing,” says Smith.
 
 _Hungry for more? [Check out this webinar](https://www.gatsbyjs.com/gatsby-themes/) to learn how you can streamline development of your new site with Gatsby themes._
diff --git a/docs/blog/2020-07-16-Gatsby-Days-Reconfigured-Trevor-Blades/index.md b/docs/blog/2020-07-16-Gatsby-Days-Reconfigured-Trevor-Blades/index.md
@@ -0,0 +1,25 @@
+---
+title: "Gatsby Days Video: The Gatsby Developer Experience Experience"
+date: 2020-07-16
+author: Michelle Gienow
+excerpt: "For his Gatsby Days Reloaded presentation, Trevor Blades delves into Gatsby’s wide-ranging plugin ecosystem for a look at some of his personal favorites: plugins that particularly enhance the local development experience."
+tags:
+  - plugins
+  - gatsby-days
+  - wordpress
+  - graphqL
+---
+
+_After much thought and discussion, the Gatsby team has decided not to hold Virtual Gatsby Days in the way we originally planned. While we were very much looking forward to our first digital community gathering, we feel now is not the time to take attention and space away from the Black Lives Matter movement._
+
+_Transforming Gatsby Days from a live event into a content series keeps the focus on more important events while sharing the amazing speakers and learning opportunities in a way the community can access when the time is right for each of us. All of the product and program announcements planned for Gatsby Days have been rolled up into [an initial blog post](/blog/2020-06-23-Reconfiguring-Gatsby-Days/), and now we are following with a video series to present the speakers who had been scheduled to share their knowledge during the event. We hope you enjoy._ 💜
+
+_We look forward to seeing you at our next Gatsby Days, planned for October, though it’s difficult to say right now exactly what form that will take. Follow [Gatsby on Twitter](https://twitter.com/gatsbyjs) to keep up with announcements around our fall Gatsby Days planning, calls for proposals, when registration starts, and other developments._
+
+Trevor Blades is a Senior Software Engineer at [Apollo GraphQL](https://www.apollographql.com/) where he works on the developer experience team. The DX team creates content to help people get up and running with GraphQL -- blog posts, documentation and tutorials, community events like [GraphQL Summit Worldwide](https://summit.graphql.com/) -- and Trevor’s main job is creating websites so all this content has a place to live. These sites are all built with Gatsby, and Trevor says Gatsby’s amazing local development experience is a major reason. Trevor’s Gatsby Days Reconfigured presentation delves into Gatsby’s wide-ranging plugin ecosystem for a look at some of Trevor’s favorites.
+
+Trevor walks through some Gatsby plugins that he finds particularly add value to the local development experience, like `gatsby-plugin-ngrok-tunneling` which exposes a publicly accessible URL for your local development environment. This plugin allows you to generate a link that remote collaborators can copy-paste to see what’s going on in your local dev environment and even click in around for themselves -- really useful when you’re trying to debug a group project locally while everyone’s working from home. He ends with a quick look at finding your Developer Happy Place with the new [`gatsby-source-wordpress-experimental`](https://www.gatsbyjs.org/packages/gatsby-source-wordpress/) plugin. _(Update: Since Trevor recorded his presentation, the Gatsby WordPress source plugin has now been officially [released in beta](https://www.gatsbyjs.org/blog/2020-07-07-wordpress-source-beta/). Trevor's overview is still a great introduction, though!)_
+
+https://www.youtube.com/watch?v=pLhrYfTXA7U
+
+See the slides (with code samples) at [experience.trevorblades.com](https://experience.trevorblades.com/#0), join him for live coding every Wednesday on [Twitch TV](http://twitch.tv/trevorblades) or find Trevor on Twitter [@trevorblades](https://twitter.com/trevorblades?lang=en) to chat about _your_ favorite Gatsby plugins!
diff --git a/docs/contributing/submit-to-starter-library.md b/docs/contributing/submit-to-starter-library.md
@@ -10,7 +10,9 @@ To get your site added to the starter library, follow the two steps below.
 
 1. If this is your first contribution to the Gatsby open source repo, follow the [Contribution guidelines](/contributing/code-contributions/).
 
-2. Edit the [`starters.yml`](https://github.com/gatsbyjs/gatsby/blob/master/docs/starters.yml) file by adding your starter information to the bottom of the list in the following format:
+2. Make sure that your submission is unique as we want to give the original authors credit and therefore won't merge starters with slight modifications of already existing starters.
+
+3. Edit the [`starters.yml`](https://github.com/gatsbyjs/gatsby/blob/master/docs/starters.yml) file by adding your starter information to the bottom of the list in the following format:
 
 ```yaml:title=docs/starters.yml
 - url: Link to a demo of your starter