From 10421fb8b223c3598df5db8f0aa52ddc5684e302 Mon Sep 17 00:00:00 2001 From: kindavishal Date: Wed, 26 Jun 2019 10:06:44 +0530 Subject: [PATCH 1/3] Fixes broken link from Gatsbygram --- docs/blog/gatsbygram-case-study/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/blog/gatsbygram-case-study/index.md b/docs/blog/gatsbygram-case-study/index.md index bcc7732ed8a26..5d1260facad30 100644 --- a/docs/blog/gatsbygram-case-study/index.md +++ b/docs/blog/gatsbygram-case-study/index.md @@ -374,7 +374,7 @@ generates all the configuration for you. Normally page resources are pre-cached with a service worker. But as several browsers (Safari/Microsoft Edge) still don't support Service Workers, the -[Gatsby `` component](/packages/gatsby/) pre-caches resources for +[Gatsby `` component](https://www.gatsbyjs.org/docs/linking-between-pages/#the-gatsby-link-component) pre-caches resources for pages it links to by loading them into memory. ## Plugins From cf6db01d502bea58c79be025850cca7e03082600 Mon Sep 17 00:00:00 2001 From: kindavishal Date: Wed, 26 Jun 2019 14:02:37 +0530 Subject: [PATCH 2/3] fix(docs): fix broken developer-blog link --- docs/docs/gatsby-vendor-partnership.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docs/gatsby-vendor-partnership.md b/docs/docs/gatsby-vendor-partnership.md index 32fbb17acf9ea..937d0881289b2 100644 --- a/docs/docs/gatsby-vendor-partnership.md +++ b/docs/docs/gatsby-vendor-partnership.md @@ -76,7 +76,7 @@ Depending on your size and reach, there are a few ways we can work together. 1. **Sharing your Gatsby-related content on Twitter.** After you publish your content, and blog about it, just tweet about it and we’re happy to retweet your content to the Gatsby community. We currently (March 2019) have an audience of over 22,000 on Twitter and a typical tweet is seen by around 7,000 developers. -2. **Blogging about your integration.** Our [gatsbyjs.org](gatsbyjs.org) developer blog is open to quality posts from key partners to share about how to use our solutions together. A typical blog post gets 3,000 reads in the first 7 days, and around 10,000 reads over the course of a year. +2. **Blogging about your integration.** Our [gatsbyjs.org](https://www.gatsbyjs.org/blog/) developer blog is open to quality posts from key partners to share about how to use our solutions together. A typical blog post gets 3,000 reads in the first 7 days, and around 10,000 reads over the course of a year. If you’re an established vendor adding a Gatsby integration, we’d love for you to tell that story on our blog (eg [Kentico Cloud](/blog/2018-12-19-kentico-cloud-and-gatsby-take-you-beyond-static-websites/)). Here is a [guide to posting this in the blog](/docs/how-to-contribute/#contributing-to-the-blog). From 1c89911f6efe979f1bc5325658f9a344de370896 Mon Sep 17 00:00:00 2001 From: kindavishal Date: Wed, 26 Jun 2019 14:05:30 +0530 Subject: [PATCH 3/3] Revert "fix(docs): fix broken developer-blog link" This reverts commit cf6db01d502bea58c79be025850cca7e03082600. --- docs/docs/gatsby-vendor-partnership.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docs/gatsby-vendor-partnership.md b/docs/docs/gatsby-vendor-partnership.md index 937d0881289b2..32fbb17acf9ea 100644 --- a/docs/docs/gatsby-vendor-partnership.md +++ b/docs/docs/gatsby-vendor-partnership.md @@ -76,7 +76,7 @@ Depending on your size and reach, there are a few ways we can work together. 1. **Sharing your Gatsby-related content on Twitter.** After you publish your content, and blog about it, just tweet about it and we’re happy to retweet your content to the Gatsby community. We currently (March 2019) have an audience of over 22,000 on Twitter and a typical tweet is seen by around 7,000 developers. -2. **Blogging about your integration.** Our [gatsbyjs.org](https://www.gatsbyjs.org/blog/) developer blog is open to quality posts from key partners to share about how to use our solutions together. A typical blog post gets 3,000 reads in the first 7 days, and around 10,000 reads over the course of a year. +2. **Blogging about your integration.** Our [gatsbyjs.org](gatsbyjs.org) developer blog is open to quality posts from key partners to share about how to use our solutions together. A typical blog post gets 3,000 reads in the first 7 days, and around 10,000 reads over the course of a year. If you’re an established vendor adding a Gatsby integration, we’d love for you to tell that story on our blog (eg [Kentico Cloud](/blog/2018-12-19-kentico-cloud-and-gatsby-take-you-beyond-static-websites/)). Here is a [guide to posting this in the blog](/docs/how-to-contribute/#contributing-to-the-blog).