Merge branch 'master' of github.com:gatsbyjs/gatsby into prettier

* 'master' of github.com:gatsbyjs/gatsby: (103 commits) chore(showcase): add AntdSite (gatsbyjs#16376) docs: Fix typos in docs/blog (gatsbyjs#16366) chore(starters): add gatsby-starter-fashion-portfolio (gatsbyjs#16333) chore(showcase): Add Fourpost (gatsbyjs#16390) Docs: Fix a markdown syntax error in recipes.md (gatsbyjs#16371) docs: Update building-a-theme.md (gatsbyjs#16364) fix: update dependency @theme-ui/prism to ^0.2.29 (gatsbyjs#16385) chore: update dependency gatsby to ^2.13.51 (gatsbyjs#16375) Fix www build fix: update dependency @theme-ui/typography to ^0.2.29 (gatsbyjs#16386) fix: update dependency gatsby-plugin-theme-ui to ^0.2.29 (gatsbyjs#16387) fix: update dependency theme-ui to ^0.2.29 (gatsbyjs#16388) fix(www): fallback to github & unpkg to get README.md (gatsbyjs#16322) fix(www): replace \n into newlines for guess (gatsbyjs#16382) fix(gatsby): always use publicLoader for window.___loader (gatsbyjs#16122) feat(docs): Document what breaking changes are for themes (gatsbyjs#16302) docs: Link mapping to @link (gatsbyjs#16152) fix(gatsby): Add findMatchPath to the default loader (gatsbyjs#16334) feat(gatsby): Allow custom resolver context (gatsbyjs#16359) feat(docs): Add docs for @nodeInterface extension (gatsbyjs#16356) ...
lipis · Aug 5, 2019 · 1f25f34 · 1f25f34
2 parents 719a22d + 05e67ca
commit 1f25f34
Show file tree

Hide file tree

Showing 338 changed files with 6,986 additions and 3,612 deletions.
diff --git a/.circleci/config.yml b/.circleci/config.yml
@@ -318,6 +318,17 @@ workflows:
             branches:
               only:
                 - master
+      - manual_www_approval:
+          type: approval
+      - build_www:
+          context: build_www
+          requires:
+            - manual_www_approval
+      - deploy_www:
+          requires:
+            - build_www
+          context: build_www
+
   www_deploy:
     triggers:
       - schedule:

diff --git a/.github/actions/high-priority-prs/src/filter.js b/.github/actions/high-priority-prs/src/filter.js
@@ -12,7 +12,11 @@ const filter = (queues, team) => {
       return pr.reviewRequests.nodes
         .map(node => {
           if (node.requestedReviewer) {
-            tools.log.info(`Review request for team ${node.requestedReviewer.name} on PR: ${pr.title}`)
+            tools.log.info(
+              `Review request for team ${node.requestedReviewer.name} on PR: ${
+                pr.title
+              }`
+            )
             return node.requestedReviewer.id
           }
         })

diff --git a/.github/actions/high-priority-prs/src/index.js b/.github/actions/high-priority-prs/src/index.js
@@ -21,17 +21,19 @@ const start = async function() {
   const data = await fetch()
   if (data) {
     const queues = processData(data)
-    await Promise.all(teams.map(team => {
-      if (team.name === `core`) {
-        // send report of all PRs (without filtering) to Core
-        tools.log.info(`-> Reporting for ${team.name} team`)
-        return report({ queues, channelId: team.channelId })
-      } else {
-        // send filtered reports to respective teams
-        tools.log.info(`-> Reporting for ${team.name} team`)
-        return report(filter(queues, team))
-      }
-    }))
+    await Promise.all(
+      teams.map(team => {
+        if (team.name === `core`) {
+          // send report of all PRs (without filtering) to Core
+          tools.log.info(`-> Reporting for ${team.name} team`)
+          return report({ queues, channelId: team.channelId })
+        } else {
+          // send filtered reports to respective teams
+          tools.log.info(`-> Reporting for ${team.name} team`)
+          return report(filter(queues, team))
+        }
+      })
+    )
   }
 }
 

diff --git a/.github/actions/high-priority-prs/src/process-data.js b/.github/actions/high-priority-prs/src/process-data.js
@@ -122,9 +122,11 @@ const processData = (data, now = new Date()) => {
   prs.nodes.forEach(pr => {
     pr.participants = {}
     pr.participants.nodes = _.uniqBy(
-      pr.comments.nodes.filter(c => c.author.url != pr.author.url).map(c => {
-        return { url: c.author.url }
-      }),
+      pr.comments.nodes
+        .filter(c => c.author.url != pr.author.url)
+        .map(c => {
+          return { url: c.author.url }
+        }),
       node => node.url
     )
   })
@@ -230,7 +232,7 @@ const report = ({ queues, channelId }) => {
         channel: channelId,
         blocks: report,
       })
-      
+
       // When ok is false we should throw
       // @see https://api.slack.com/methods/chat.postMessage#response
       if (!res.ok) {

diff --git a/CODEOWNERS b/CODEOWNERS
@@ -8,10 +8,11 @@
 # The website auto-deploys, so we need an extra check to avoid shenanigans.
 /www/                                           @gatsbyjs/website
 
-# Themes 
+# Themes
 
 /docs/docs/themes/                              @gatsbyjs/themes-core
 /themes/                                        @gatsbyjs/themes-core
+/packages/gatsby-plugin-mdx/                    @gatsbyjs/themes-core
 /packages/gatsby/src/bootstrap/load-themes      @gatsbyjs/themes-core
 /packages/gatsby/src/bootstrap/index.js         @gatsbyjs/themes-core
 /packages/gatsby/src/internal-plugins/webpack-theme-component-shadowing/   @gatsbyjs/themes-core
diff --git a/docs/blog/2017-05-31-introduction-to-gatsby/index.md b/docs/blog/2017-05-31-introduction-to-gatsby/index.md
@@ -3,7 +3,7 @@ title: Introduction to Gatsby
 date: 2018-05-31
 author: Michelle Barker
 excerpt: "In case you haven’t heard about it, Gatsby is the latest hot thing in static site generators"
-tags: ["css", "graphql", "blog"]
+tags: ["cutting-edge-experiences", "graphql", "blogs"]
 canonicalLink: https://css-irl.info/introduction-to-gatsby/
 publishedAt: css-irl.info
 ---

diff --git a/docs/blog/2017-07-19-creating-a-blog-with-gatsby/index.md b/docs/blog/2017-07-19-creating-a-blog-with-gatsby/index.md
@@ -9,7 +9,7 @@ imageTitle: "Old typewriter"
 canonicalLink: "https://objectpartners.com/2017/07/19/creating-a-static-blog-with-gatsby/"
 publishedAt: "Object Partners, Inc."
 excerpt: "In this post, we'll take a deep dive into Gatsby and some of the new 1.0 features by creating a static blog. Let's get on it!"
-tags: ["getting-started", "blog", "markdown"]
+tags: ["getting-started", "blogs", "markdown"]
 ---
 
 Gatsby is an incredible static site generator that allows for React to be used

diff --git a/docs/blog/2017-09-18-gatsby-modern-static-generation/index.md b/docs/blog/2017-09-18-gatsby-modern-static-generation/index.md
@@ -4,7 +4,7 @@ date: 2017-09-18
 image: "code-image.jpg"
 author: "Kostas Bariotis"
 excerpt: "In this post, I will talk about static site generators -- how they have evolved and why I switched from a Ghost powered site to Gatsby.js, a modern static site generator."
-tags: ["ghost", "wordpress", "caching"]
+tags: ["ghost", "wordpress"]
 ---
 
 In this post, I will talk about static site generators -- how they have evolved

diff --git a/docs/blog/2017-09-21-community-roundup-1/index.md b/docs/blog/2017-09-21-community-roundup-1/index.md
@@ -5,7 +5,7 @@ author: "Kyle Mathews"
 image: "on-the-trail.jpg"
 showImageInArticle: true
 typora-copy-images-to: ./
-tags: ["v1", "tutorials", "plugins"]
+tags: ["v1", "getting-started", "plugins"]
 ---
 
 It's been a wild 77 days since Gatsby 1.0.0 was released into the world on July

diff --git a/docs/blog/2017-10-01-migrating-my-blog-from-hexo-to-gatsby/index.md b/docs/blog/2017-10-01-migrating-my-blog-from-hexo-to-gatsby/index.md
@@ -4,7 +4,7 @@ date: 2017-10-01
 image: "hexo-to-gatsby.png"
 author: "Ian Sinnott"
 excerpt: "How I migrated my blog to Gatsby and how you can do the same."
-tags: ["hexo", "getting-started", "markdown"]
+tags: ["getting-started", "markdown"]
 ---
 
 _This article was originally posted on

diff --git a/docs/blog/2017-10-03-smartive-goes-gatsby/index.md b/docs/blog/2017-10-03-smartive-goes-gatsby/index.md
@@ -4,7 +4,7 @@ date: 2017-10-03
 image: "smartive-loves-gatsby.png"
 author: "Moreno Feltscher"
 excerpt: "At smartive we always saw the potential of static site generators. We recently made the switch to Gatsby.js for our company site. A decision we don’t regret. Here’s why."
-tags: ["company-site", "ci"]
+tags: ["case-studies", "blogs", "deployment"]
 ---
 
 _This article was originally published on

diff --git a/docs/blog/2017-10-16-making-website-building-fun/index.md b/docs/blog/2017-10-16-making-website-building-fun/index.md
@@ -3,7 +3,7 @@ title: "Making website building fun"
 date: 2017-10-16
 author: "Kyle Mathews"
 typora-copy-images-to: ./
-tags: ["right-building-blocks", "gatsby-image", "react", "graphql", "plugins"]
+tags: ["web-building-blocks", "gatsby-image", "react", "graphql", "plugins"]
 ---
 
 I still remember the first non-trivial React component I built in 2014—not long

diff --git a/...og/2017-10-20-from-wordpress-to-developing-in-react-starting-to-see-it/index.md b/...og/2017-10-20-from-wordpress-to-developing-in-react-starting-to-see-it/index.md
@@ -2,7 +2,7 @@
 title: From WordPress to Developing in React — Starting to See It
 date: 2017-10-20
 author: "Benjamin Read"
-tags: ["React", "getting-started", "wordpress"]
+tags: ["react", "getting-started", "wordpress"]
 ---
 
 As a frontend designer I've always prided myself on being a HTML and CSS

diff --git a/...og/2017-10-29-my-search-for-the-perfect-universal-javaScript-framework/index.md b/...og/2017-10-29-my-search-for-the-perfect-universal-javaScript-framework/index.md
@@ -2,7 +2,7 @@
 title: My search for the perfect universal JavaScript framework
 date: 2017-10-29
 author: "Tal Bereznitskey"
-tags: ["react", "ssr", "static"]
+tags: ["react", "ssr"]
 ---
 
 It was 2010 when [Backbone.js](http://backbonejs.org) came out. Finally I could

diff --git a/docs/blog/2017-11-08-migrate-from-jekyll-to-gatsby/index.md b/docs/blog/2017-11-08-migrate-from-jekyll-to-gatsby/index.md
@@ -2,7 +2,7 @@
 title: "Migrate from Jekyll to Gatsby"
 date: 2017-11-08
 author: "Nahuel Scotti"
-tags: ["jekyll", "markdown", "getting-started", "ci"]
+tags: ["jekyll", "markdown", "getting-started", "deployment"]
 ---
 
 ## A bit of history

diff --git a/docs/blog/2017-12-06-gatsby-plus-contentful-plus-netlify/index.md b/docs/blog/2017-12-06-gatsby-plus-contentful-plus-netlify/index.md
@@ -11,7 +11,7 @@ tags:
     "algolia",
     "getting-started",
     "hosting",
-    "ci",
+    "deployment",
     "performance",
   ]
 ---

diff --git a/docs/blog/2017-12-20-introducing-the-gatsby-ux-research-program/index.md b/docs/blog/2017-12-20-introducing-the-gatsby-ux-research-program/index.md
@@ -2,7 +2,7 @@
 title: Introducing the Gatsby UX Research Program
 date: 2017-12-20
 author: "Shannon Soper"
-tags: ["ux"]
+tags: ["ux", "user-testing"]
 ---
 
 ## How this all started
@@ -71,15 +71,34 @@ The second most common pain point is GraphQL. About half of our interviewees sai
 Other salient feedback includes that people who have used WordPress for a long time are looking for other solutions and want Gatsby to play well with many kinds of CMSs. Finally, almost every interviewee loves the Gatsby development experience because it is smooth and fast. Here are some fun quotes:
 
 <Pullquote citation="Alec Lomas, AZ, frontend dev and design">
-You guys are pretty much nailing it. Just keep killin’ it, I guess!
+  You guys are pretty much nailing it. Just keep killin’ it, I guess!
 </Pullquote>
 
 <Pullquote citation="David Luhr, UT, UX">
-I’ve played around with static sites in Jekyll in the past, but I’ve always hit a pain point with how much functionality I could build into the different includes and partials and things that were starting to become popular with different templating languages. So I’ve always loved React for all the encapsulation of style and functionality. And components--but I never really knew how to use it. And Gatsby has been that first opportunity where everything comes together, everything can be in one system. My background is really design focused, so I think of a component library along those lines. Until Gatsby, I never really had a way to see how I could use that across all of our pages instead of relying on a content management library that was kind of slow to develop in.
+  I’ve played around with static sites in Jekyll in the past, but I’ve always
+  hit a pain point with how much functionality I could build into the different
+  includes and partials and things that were starting to become popular with
+  different templating languages. So I’ve always loved React for all the
+  encapsulation of style and functionality. And components--but I never really
+  knew how to use it. And Gatsby has been that first opportunity where
+  everything comes together, everything can be in one system. My background is
+  really design focused, so I think of a component library along those lines.
+  Until Gatsby, I never really had a way to see how I could use that across all
+  of our pages instead of relying on a content management library that was kind
+  of slow to develop in.
 </Pullquote>
 
 <Pullquote citation="Juliette Pichot, Germany, web developer">
-If you ever decide to sell to consumers, I really think that the speed / responsiveness of Gatsby is a really good selling point. Like when I tried to sell my idea of building the new site in Gatsby (which would take a little longer compared to building it in Squarespace) to my husband, I simply showed him how quick it is to navigate around a Gatsby site and he was instantly sold. The explicit awareness that website speed matters a lot is currently kinda limited to Silicon Valley etc, but the benefits are definitely apparent as well to the average consumer. Pair that with stats around how speed increases conversions and it'd definitely be a pretty appealing offer to people.
+  If you ever decide to sell to consumers, I really think that the speed /
+  responsiveness of Gatsby is a really good selling point. Like when I tried to
+  sell my idea of building the new site in Gatsby (which would take a little
+  longer compared to building it in Squarespace) to my husband, I simply showed
+  him how quick it is to navigate around a Gatsby site and he was instantly
+  sold. The explicit awareness that website speed matters a lot is currently
+  kinda limited to Silicon Valley etc, but the benefits are definitely apparent
+  as well to the average consumer. Pair that with stats around how speed
+  increases conversions and it'd definitely be a pretty appealing offer to
+  people.
 </Pullquote>
 
 ## So what does this all mean?

diff --git a/...-boston-gov-used-gatsby-to-be-selected-as-an-amazon-hq2-candidate-city/index.md b/...-boston-gov-used-gatsby-to-be-selected-as-an-amazon-hq2-candidate-city/index.md
@@ -2,7 +2,7 @@
 title: How Boston.gov used Gatsby to be selected as an Amazon HQ2 candidate city
 date: 2018-01-18
 author: "Sam Bhagwat"
-tags: ["case-studies", "component-library", "iteration-speed"]
+tags: ["case-studies", "building-sites-faster"]
 ---
 
 [Boston.gov](http://boston.gov) is a small team with a huge responsibility: ten people tasked with the digital presence of New England’s most iconic city.

diff --git a/docs/blog/2018-02-16-bright-future-for-the-web/index.md b/docs/blog/2018-02-16-bright-future-for-the-web/index.md
@@ -3,7 +3,7 @@ title: Gatsby And The JAMstack - A Bright Future For The Web
 date: 2018-02-16
 image: "bright-future.jpg"
 author: "Ryan Wiemer"
-tags: ["markdown", "JAMstack", "netlify", "contentful"]
+tags: ["markdown", "jamstack", "netlify", "contentful"]
 ---
 
 _This article was originally published on

diff --git a/docs/blog/2018-02-28-documentation-project/index.md b/docs/blog/2018-02-28-documentation-project/index.md
@@ -2,7 +2,7 @@
 title: Introducing the Gatsby Documentation Project
 author: Shannon Soper
 date: 2018-02-28
-tags: ["ux", "documentation", "community"]
+tags: ["user-testing", "documentation", "community"]
 ---
 
 People really like Gatsby docs and Gatsby. In fact, we’ve talked about tracking the number of curse words and endearingly pejorative terms that people use when tweeting about Gatsby. Here’s a sampling:

diff --git a/docs/blog/2018-03-07-why-we-created-the-plugin-library/index.md b/docs/blog/2018-03-07-why-we-created-the-plugin-library/index.md
@@ -67,7 +67,7 @@ We _didn't_ like these things in some of the above libraries:
 Here’s a sampling of screenshots that many community members contributed to and gave feedback about. It’s rewarding to see how much the design has progressed (and will keep progressing).
 
 <video controls="controls" autoplay="true" loop="true">
-  <source type="video/mp4" src="/images/gatsby-plugin-library-compressed.mp4"></source>
+  <source type="video/mp4" src="/images/gatsby-plugin-library-compressed.mp4" />
   <p>Your browser does not support the video element.</p>
 </video>
 

diff --git a/docs/blog/2018-03-29-migration-from-wordpress-to-gatsby/index.md b/docs/blog/2018-03-29-migration-from-wordpress-to-gatsby/index.md
@@ -24,7 +24,7 @@ The results of a [Lighthouse audit](https://www.vojtechruzicka.com/chrome-audit-
 
 ![lighthouse audit before](./chrome-audit-score-before.jpg)
 
-Especially the performance. With such long page load times, many users just leave before the page fully loads. Especially when on mobile and low-quality connections. Another issue is security. With a significant part of web powered by WordPress, it is a target of automated attacks all the time. That means constant fear of losing your precious blog. And it's internal database storing all the content was pretty much a black box for me. And of course, there's cost involved. As I didn't want to manage my installation, keep it updated and in good shape, I paid for hosted solution. Last but not least, Wordpress is built with PHP, which I am not familiar with and it is something I am not eager to learn. That means that any customizations or tweaks are out of the question for me.
+Especially the performance. With such long page load times, many users just leave before the page fully loads. Especially when on mobile and low-quality connections. Another issue is security. With a significant part of web powered by WordPress, it is a target of automated attacks all the time. That means constant fear of losing your precious blog. And its internal database storing all the content was pretty much a black box for me. And of course, there's cost involved. As I didn't want to manage my installation, keep it updated and in good shape, I paid for hosted solution. Last but not least, Wordpress is built with PHP, which I am not familiar with and it is something I am not eager to learn. That means that any customizations or tweaks are out of the question for me.
 
 Long story short, I decided to get rid of WordPress and replace it with a much more lightweight solution. There was a brief moment where I considered using Medium instead, but I decided I value control of my own content more. After listening to a very inspiring lightning talk by [Ladislav Prskavec](https://twitter.com/abtris/) about JAM Stack, I decided its time to give it a try.
 

diff --git a/.../blog/2018-04-25-how-gatsby-changes-teams-website-development-workflow/index.md b/.../blog/2018-04-25-how-gatsby-changes-teams-website-development-workflow/index.md
@@ -3,7 +3,7 @@ title: How Gatsby Changes Teams' Website Development Workflow
 date: 2018-04-25
 author: "Sam Bhagwat"
 excerpt: Gatsby is more than just a new website framework -- it changes the way your team works together.
-tags: ["collaboration"]
+tags: ["gatsby-for-teams"]
 ---
 
 Gatsby is more than just a new website framework -- creating websites in Gatsby is a fundamentally different paradigm than in a CMS-specific framework.

diff --git a/docs/blog/2018-05-11-six-reasons-i-chose-gatsby/index.md b/docs/blog/2018-05-11-six-reasons-i-chose-gatsby/index.md
@@ -3,7 +3,7 @@ title: Six Reasons I Chose Gatsby
 date: 2018-05-11
 author: Ray Gesualdo
 excerpt: "Spoiler alert: I'm a big fan of Gatsby."
-tags: ["react", "graphql", "plugins"]
+tags: ["react", "graphql", "plugins", "developer-experience"]
 canonicalLink: https://www.raygesualdo.com/posts/six-reasons-i-chose-gatsby/
 publishedAt: raygesualdo.com
 ---

diff --git a/docs/blog/2018-05-24-launching-new-gatsby-company/index.md b/docs/blog/2018-05-24-launching-new-gatsby-company/index.md
@@ -2,6 +2,7 @@
 title: Announcing new Gatsby Company
 date: 2018-05-24
 author: "Kyle Mathews"
+tags: ["gatsby-inc"]
 ---
 
 Together with my co-founder, [Sam Bhagwat](https://twitter.com/calcsam), I’m thrilled to announce the formation of [Gatsby Inc.](https://www.gatsbyjs.com/) Based on the open source project Gatsby I founded, Gatsby the company will make feature-rich and blazing-fast websites easier to build and run.

diff --git a/docs/blog/2018-06-08-gatsby-marketers-managers-agencies-teams/index.md b/docs/blog/2018-06-08-gatsby-marketers-managers-agencies-teams/index.md
@@ -2,6 +2,7 @@
 title: Gatsby for Marketers, Managers, Agencies and Teams
 date: 2018-06-08
 author: "Linda Watkins"
+tags: ["marketing"]
 ---
 
 A few years ago, I worked at a small startup on an agile marketing team. This startup built website management tools and they had many customers come to them with stories of hosting headaches. I saw first-hand the hosting hassles that companies face.

diff --git a/docs/blog/2018-06-18-why-narative-loves-gatsby/index.md b/docs/blog/2018-06-18-why-narative-loves-gatsby/index.md
@@ -2,7 +2,7 @@
 title: Why Narative loves Gatsby
 date: 2018-06-18
 author: "Dennis Brotzky"
-tags: ["gatsby", "narative", "graphql", "blog", "agency"]
+tags: ["graphql", "blogs", "agencies"]
 excerpt: "Redefining how Narative builds page based websites with Gatsby"
 canonicalLink: "https://medium.com/narative/why-narative-loves-gatsbyjs-825b6b3bc9a4"
 ---

diff --git a/docs/blog/2018-07-07-graphic-design-class/index.md b/docs/blog/2018-07-07-graphic-design-class/index.md
@@ -2,7 +2,13 @@
 title: Learning how to code with Gatsby
 date: 2018-07-07
 author: "Shannon Soper"
-tags: ["college", "case study", "design", "getting-started"]
+tags:
+  [
+    "learning-to-code",
+    "case-studies",
+    "cutting-edge-experiences",
+    "getting-started",
+  ]
 ---
 
 ## Graphic Design Students at the Art Institute
@@ -56,7 +62,8 @@ Structure of the class:
 3.  _Taught them Gatsby._ Learning NextJS wasn’t as smooth as I would have liked but once we jumped to learn GatsbyJS, some interesting things happened. A light when on. They were excited.
 
 <Pullquote>
-Once we jumped to learn GatsbyJS, some interesting things happened. A light when on. They were excited.
+  Once we jumped to learn GatsbyJS, some interesting things happened. A light
+  when on. They were excited.
 </Pullquote>
 
 ### What do your students like about Gatsby?

diff --git a/docs/blog/2018-07-17-announcing-gatsby-preview/index.md b/docs/blog/2018-07-17-announcing-gatsby-preview/index.md
@@ -2,7 +2,7 @@
 title: Announcing Gatsby Preview
 date: 2018-07-17
 author: "Sam Bhagwat"
-tags: ["contentful", "preview", "product"]
+tags: ["contentful", "gatsby-preview", "gatsby-cloud", "gatsby-inc"]
 ---
 
 Today we’re excited to announce our first commercial offering, a hosted Gatsby preview service for teams, with [Contentful](https://www.contentful.com/) as our initial integration.
@@ -32,6 +32,6 @@ We’re incredibly excited to launch our first commercial service and to continu
 Before you go, take a look at a GIF of Gatsby Preview in action on [our own website](https://gatsbyjs.com):
 
 <video controls="controls" autoplay="true" loop="true">
-  <source type="video/mp4" src="./gatsby-contentful-preview.mp4"></source>
+  <source type="video/mp4" src="./gatsby-contentful-preview.mp4" />
   <p>Your browser does not support the video element.</p>
 </video>
diff --git a/docs/blog/2018-07-20-why-we-built-the-site-showcase/index.md b/docs/blog/2018-07-20-why-we-built-the-site-showcase/index.md
@@ -2,7 +2,7 @@
 title: Why We Created the Site Showcase
 date: 2018-07-20
 author: Shannon Soper
-tags: ["documentation", "launch"]
+tags: ["documentation", "releases"]
 ---
 
 We recently finished the first phase of the [Site Showcase](/showcase/), which is a searchable, filterable library of sites built with Gatsby!

diff --git a/docs/blog/2018-07-31-docs-redesign/index.md b/docs/blog/2018-07-31-docs-redesign/index.md
@@ -2,7 +2,7 @@
 title: Introducing the Docs IA Redesign
 date: 2018-07-31
 author: Shannon Soper
-tags: ["documentation", "launch"]
+tags: ["documentation", "releases"]
 ---
 
 We've been working on a new design for the docs sidebar. You can see it live on at [www.gatsbyjs.org/docs/](/docs/)!