diff --git a/benchmarks/source-kontent/.env.template b/benchmarks/source-kontent/.env.template new file mode 100644 index 0000000000000..fe5ef633ea68e --- /dev/null +++ b/benchmarks/source-kontent/.env.template @@ -0,0 +1,4 @@ +BENCHMARK_KONTENT_PROJECT_ID=4d1eb9ae-c95e-00e1-da99-692832fe675c +BENCHMARK_KONTENT_LANGUAGE_CODENAMES=default +BENCHMARK_KONTENT_MANAGEMENT_KEY= +BENCHMARK_KONTENT_DATASET_SIZE= \ No newline at end of file diff --git a/benchmarks/source-kontent/.gitignore b/benchmarks/source-kontent/.gitignore new file mode 100644 index 0000000000000..95b1bbb9d70c8 --- /dev/null +++ b/benchmarks/source-kontent/.gitignore @@ -0,0 +1,70 @@ +# Logs +logs +*.log +npm-debug.log* +yarn-debug.log* +yarn-error.log* + +# Runtime data +pids +*.pid +*.seed +*.pid.lock + +# Directory for instrumented libs generated by jscoverage/JSCover +lib-cov + +# Coverage directory used by tools like istanbul +coverage + +# nyc test coverage +.nyc_output + +# Grunt intermediate storage (http://gruntjs.com/creating-plugins#storing-task-files) +.grunt + +# Bower dependency directory (https://bower.io/) +bower_components + +# node-waf configuration +.lock-wscript + +# Compiled binary addons (http://nodejs.org/api/addons.html) +build/Release + +# Dependency directories +node_modules/ +jspm_packages/ + +# Typescript v1 declaration files +typings/ + +# Optional npm cache directory +.npm + +# Optional eslint cache +.eslintcache + +# Optional REPL history +.node_repl_history + +# Output of 'npm pack' +*.tgz + +# dotenv environment variable files +.env.development +.env.production + +# gatsby files +.cache/ +public + +# Mac files +.DS_Store + +# Yarn +yarn-error.log +.pnp/ +.pnp.js +# Yarn Integrity file +.yarn-integrity diff --git a/benchmarks/source-kontent/.prettierignore b/benchmarks/source-kontent/.prettierignore new file mode 100644 index 0000000000000..58d06c368a2ae --- /dev/null +++ b/benchmarks/source-kontent/.prettierignore @@ -0,0 +1,4 @@ +.cache +package.json +package-lock.json +public diff --git a/benchmarks/source-kontent/.prettierrc b/benchmarks/source-kontent/.prettierrc new file mode 100644 index 0000000000000..48e90e8d4025f --- /dev/null +++ b/benchmarks/source-kontent/.prettierrc @@ -0,0 +1,7 @@ +{ + "endOfLine": "lf", + "semi": false, + "singleQuote": false, + "tabWidth": 2, + "trailingComma": "es5" +} diff --git a/benchmarks/source-kontent/LICENSE b/benchmarks/source-kontent/LICENSE new file mode 100644 index 0000000000000..20f91f2b3c52b --- /dev/null +++ b/benchmarks/source-kontent/LICENSE @@ -0,0 +1,21 @@ +MIT License + +Copyright (c) 2018 gatsbyjs + +Permission is hereby granted, free of charge, to any person obtaining a copy +of this software and associated documentation files (the "Software"), to deal +in the Software without restriction, including without limitation the rights +to use, copy, modify, merge, publish, distribute, sublicense, and/or sell +copies of the Software, and to permit persons to whom the Software is +furnished to do so, subject to the following conditions: + +The above copyright notice and this permission notice shall be included in all +copies or substantial portions of the Software. + +THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR +IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, +FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE +AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER +LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, +OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE +SOFTWARE. diff --git a/benchmarks/source-kontent/README.md b/benchmarks/source-kontent/README.md new file mode 100644 index 0000000000000..ab54010fb35c9 --- /dev/null +++ b/benchmarks/source-kontent/README.md @@ -0,0 +1,7 @@ +# Kontent Will it Build Example + +Example site for Kontent as a source for "Will It Build". +Should/Will be generalized into e.g. a theme. + +Queries the title, body and a cover image from Kontent. Creates pages for that and displays those three things as "Articles". +Those individual article pages and the homepage share a common "Layout" component (in src/components) that can be swapped (layout_1.js and layout_2.js) to simulate a code change in multiple pages. diff --git a/benchmarks/source-kontent/gatsby-browser.js b/benchmarks/source-kontent/gatsby-browser.js new file mode 100644 index 0000000000000..a2ee774cf8a8c --- /dev/null +++ b/benchmarks/source-kontent/gatsby-browser.js @@ -0,0 +1 @@ +import "./styles.css" \ No newline at end of file diff --git a/benchmarks/source-kontent/gatsby-config.js b/benchmarks/source-kontent/gatsby-config.js new file mode 100644 index 0000000000000..99de4732d44f3 --- /dev/null +++ b/benchmarks/source-kontent/gatsby-config.js @@ -0,0 +1,23 @@ +require("dotenv").config({ + path: `.env.${process.env.NODE_ENV}`, +}) + + +module.exports = { + siteMetadata: { + siteTitle: `Gatsby Kontent Benchmark`, + }, + plugins: [ + `gatsby-plugin-benchmark-reporting`, + `gatsby-plugin-sharp`, + `gatsby-transformer-sharp`, + { + resolve: '@kentico/gatsby-source-kontent', + options: { + projectId: process.env.BENCHMARK_KONTENT_PROJECT_ID, // Fill in your Project ID + languageCodenames: process.env.BENCHMARK_KONTENT_LANGUAGE_CODENAMES && process.env.BENCHMARK_KONTENT_LANGUAGE_CODENAMES.split(',') + }, + }, + `@rshackleton/gatsby-transformer-kontent-image`, + ], +} diff --git a/benchmarks/source-kontent/gatsby-node.js b/benchmarks/source-kontent/gatsby-node.js new file mode 100644 index 0000000000000..0985a47953952 --- /dev/null +++ b/benchmarks/source-kontent/gatsby-node.js @@ -0,0 +1,31 @@ +exports.createPages = async ({ actions, graphql, reporter }) => { + const { createPage } = actions + + const result = await graphql(` + { + articles: allKontentItemArticle { + nodes { + elements { + slug { + value + } + } + } + } + } + `) + + if (result.errors) { + reporter.panicOnBuild(result.errors) + } + + result.data.articles.nodes.map(article => { + createPage({ + path: "/" + article.elements.slug.value, + component: require.resolve(`./src/templates/article.js`), + context: { + slug: article.elements.slug.value, + } + }) + }) +} \ No newline at end of file diff --git a/benchmarks/source-kontent/package.json b/benchmarks/source-kontent/package.json new file mode 100644 index 0000000000000..64ce303e4adcb --- /dev/null +++ b/benchmarks/source-kontent/package.json @@ -0,0 +1,41 @@ +{ + "name": "kontent-gatsby-benchmark", + "description": "Example site for Kontent as a source for \"Will It Build\"", + "version": "0.1.0", + "license": "MIT", + "scripts": { + "build": "gatsby build", + "build:send": "cross-env BENCHMARK_REPORTING_URL=true gatsby build", + "develop": "gatsby develop", + "format": "prettier --write \"**/*.{js,jsx,json,md}\"", + "start": "npm run develop", + "serve": "gatsby serve", + "data-update": "cross-env NODE_ENV=production node update-article.js" + }, + "dependencies": { + "@kentico/gatsby-source-kontent": "^6.0.1", + "@rshackleton/gatsby-transformer-kontent-image": "^2.0.0", + "dotenv": "^8.2.0", + "gatsby": "^2.19.7", + "gatsby-image": "^2.2.40", + "gatsby-plugin-benchmark-reporting": "^0.0.2", + "gatsby-plugin-sharp": "^2.4.5", + "gatsby-transformer-sharp": "^2.3.14", + "react": "^16.12.0", + "react-dom": "^16.12.0" + }, + "devDependencies": { + "@kentico/kontent-delivery": "^9.1.1", + "@kentico/kontent-management": "^0.3.19", + "cross-env": "^7.0.0", + "prettier": "^1.19.1", + "rxjs": "^6.5.5" + }, + "repository": { + "type": "git", + "url": "https://github.com/gatsbyjs/gatsby-starter-hello-world" + }, + "bugs": { + "url": "https://github.com/gatsbyjs/gatsby/issues" + } +} diff --git a/benchmarks/source-kontent/src/components/layout_1.js b/benchmarks/source-kontent/src/components/layout_1.js new file mode 100644 index 0000000000000..f0d2249625bee --- /dev/null +++ b/benchmarks/source-kontent/src/components/layout_1.js @@ -0,0 +1,12 @@ +import React from "react" + +const Layout = ({ children }) => ( + <> +
+

Header A

+
+
{children}
+ +) + +export default Layout diff --git a/benchmarks/source-kontent/src/components/layout_2.js b/benchmarks/source-kontent/src/components/layout_2.js new file mode 100644 index 0000000000000..19aef17261ffe --- /dev/null +++ b/benchmarks/source-kontent/src/components/layout_2.js @@ -0,0 +1,12 @@ +import React from "react" + +const Layout = ({ children }) => ( + <> +
+

Header B

+
+
{children}
+ +) + +export default Layout diff --git a/benchmarks/source-kontent/src/pages/index.js b/benchmarks/source-kontent/src/pages/index.js new file mode 100644 index 0000000000000..1743b184e6109 --- /dev/null +++ b/benchmarks/source-kontent/src/pages/index.js @@ -0,0 +1,42 @@ +import React from "react" +import { Link, graphql } from "gatsby" +import Layout from "../components/layout_1" + +const Index = ({ data }) => { + return ( + + {data.site.siteMetadata.siteTitle} + + + ) +} + +export default Index + +export const query = graphql` + { + site { + siteMetadata { + siteTitle + } + } + articles: allKontentItemArticle { + nodes { + elements { + title { + value + } + slug { + value + } + } + } + } + } +` diff --git a/benchmarks/source-kontent/src/templates/article.js b/benchmarks/source-kontent/src/templates/article.js new file mode 100644 index 0000000000000..d941604ac9248 --- /dev/null +++ b/benchmarks/source-kontent/src/templates/article.js @@ -0,0 +1,45 @@ +import React from "react" +import { graphql, Link } from "gatsby" +import Img from "gatsby-image" +import Layout from "../components/layout_1" + +const Article = ({ data }) => { + return ( + + Go back to index page +
+

{data.article.elements.title.value}

+ {data.article.elements.image.value.length > 0 ? ( + + ) : ( +
Image can't be displayed
+ )} +
+
+ + ) +} + +export default Article + +export const query = graphql` + query($slug: String!){ + article: kontentItemArticle(elements: {slug: {value: {eq: $slug }}}) { + elements { + title{ + value + } + content { + value + } + image{ + value { + fluid(maxWidth: 960) { + ...KontentAssetFluid + } + } + } + } + } + } +` \ No newline at end of file diff --git a/benchmarks/source-kontent/styles.css b/benchmarks/source-kontent/styles.css new file mode 100644 index 0000000000000..929e2fd10d2d0 --- /dev/null +++ b/benchmarks/source-kontent/styles.css @@ -0,0 +1,4 @@ +main { + max-width: 960px; + margin: 0 auto; +} diff --git a/benchmarks/source-kontent/update-article.js b/benchmarks/source-kontent/update-article.js new file mode 100644 index 0000000000000..e2ecd3efde4c6 --- /dev/null +++ b/benchmarks/source-kontent/update-article.js @@ -0,0 +1,59 @@ +const { ManagementClient } = require('@kentico/kontent-management'); +const { DeliveryClient } = require('@kentico/kontent-delivery'); + +require("dotenv").config({ + path: `.env.${process.env.NODE_ENV}`, +}); + + +(async () => { + + const dClient = new DeliveryClient({ + projectId: process.env.BENCHMARK_KONTENT_PROJECT_ID, + }) + + const mClient = new ManagementClient({ + projectId: process.env.BENCHMARK_KONTENT_PROJECT_ID, // ID of your Kentico Kontent project + apiKey: process.env.BENCHMARK_KONTENT_MANAGEMENT_KEY, // Management API token + }); + + try { + + const randomDoc = Math.floor(Math.random() * (Number(process.env.BENCHMARK_KONTENT_DATASET_SIZE) || 512)) + + const article = await dClient + .items() + .type('article') + .limitParameter(1) + .elementsParameter(['title']) + .equalsFilter('elements.article_number', randomDoc) + .toPromise() + .then(response => response.getFirstItem()); + + await mClient.createNewVersionOfLanguageVariant() + .byItemCodename(article.system.codename) + .byLanguageCodename(article.system.language) + .toPromise(); + + const languageVariant = await mClient.upsertLanguageVariant() + .byItemCodename(article.system.codename) + .byLanguageCodename(article.system.language) + .withElements([{ + element: { + codename: "title" + }, + value: article.title.value + "!" + }]) + .toPromise() + + await mClient + .publishOrScheduleLanguageVariant() + .byItemId(languageVariant.data.item.id) + .byLanguageId(languageVariant.data.language.id) + .withoutData() + .toPromise(); + } catch (error) { + console.error(error); + process.exit(1); + } +})() diff --git a/docs/blog/2017-10-03-smartive-goes-gatsby/index.md b/docs/blog/2017-10-03-smartive-goes-gatsby/index.md index 7818b08ced670..041c31ce26da8 100644 --- a/docs/blog/2017-10-03-smartive-goes-gatsby/index.md +++ b/docs/blog/2017-10-03-smartive-goes-gatsby/index.md @@ -45,7 +45,7 @@ deep knowledge of React we started looking for an alternative based on that hot new thing. The first thing that caught our attention was -[Next.js](https://github.com/zeit/next.js/), as seemingly everyone going for a +[Next.js](https://github.com/vercel/next.js/), as seemingly everyone going for a server-side rendered React app was using it. After some days hacking on our app we encountered some issues, especially when it came to frontend rendering. We chose [prismic.io](https://prismic.io/) for our backend system which served all diff --git a/docs/blog/2017-10-29-my-search-for-the-perfect-universal-javaScript-framework/index.md b/docs/blog/2017-10-29-my-search-for-the-perfect-universal-javaScript-framework/index.md index 1467a7474b4cd..34cd3bdd084cc 100644 --- a/docs/blog/2017-10-29-my-search-for-the-perfect-universal-javaScript-framework/index.md +++ b/docs/blog/2017-10-29-my-search-for-the-perfect-universal-javaScript-framework/index.md @@ -55,7 +55,7 @@ used to tweak my configuration all the time to achieve better performance, but Gatsby allows me to outsource the configuration and optimization and get a super fast website with zero work. -I’ll also mention [next.js](https://github.com/zeit/next.js) which is quite +I’ll also mention [next.js](https://github.com/vercel/next.js/) which is quite similar and supports both SSR for dynamic content and exporting to static pages. And don't forget [Netlify](https://www.netlify.com) who is doing an amazing job at building and hosting static websites. diff --git a/docs/blog/2017-11-06-migrate-hugo-gatsby/index.md b/docs/blog/2017-11-06-migrate-hugo-gatsby/index.md index 171625acf66a9..81f1d6fbe4d0e 100644 --- a/docs/blog/2017-11-06-migrate-hugo-gatsby/index.md +++ b/docs/blog/2017-11-06-migrate-hugo-gatsby/index.md @@ -21,7 +21,7 @@ and reusable. - Content migration - Programmatic page creation in Gatsby - Manage styles with - [`Typography.js`](http://kyleamathews.github.io/typography.js/) + [`Typography.js`](https://kyleamathews.github.io/typography.js/) - Automatic pagination - Tag pages - Add an admin panel with [NetlifyCMS](https://www.netlifycms.org/) @@ -165,7 +165,7 @@ Now that the system displays the content, it's time to style it. I decided to go for the [`typography.js` route](/tutorial/part-two/#typographyjs). The approach is well documented and you can also see -[previews of the themes online](http://kyleamathews.github.io/typography.js/). +[previews of the themes online](https://kyleamathews.github.io/typography.js/). Steps were: 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 index b520e23170fb9..6b8d1aff9214f 100644 --- a/docs/blog/2018-05-24-launching-new-gatsby-company/index.md +++ b/docs/blog/2018-05-24-launching-new-gatsby-company/index.md @@ -55,7 +55,7 @@ I was hooked on being able to ship production code so quickly. Life was good. Then in 2013, React.js was released. -I first heard about React from [David Nolen’s blog post introducing his ClojureScript wrapper of React Om](http://swannodette.github.io/2013/12/17/the-future-of-javascript-mvcs). I was completely fascinated by his analysis; his identification of DOM manipulation code as a major contributor to application complexity and slowdowns resonated with me. I started reading everything I could find on React and soon became a huge fan. +I first heard about React from [David Nolen’s blog post introducing his ClojureScript wrapper of React Om](https://swannodette.github.io/2013/12/17/the-future-of-javascript-mvcs). I was completely fascinated by his analysis; his identification of DOM manipulation code as a major contributor to application complexity and slowdowns resonated with me. I started reading everything I could find on React and soon became a huge fan. Early in 2014, I left Pantheon to explore new opportunities. I dove deeper into React and built a number of sample applications and was astounded at how productive I was. Problems that used to take me weeks to solve in Backbone.js took me hours in React.js. Not only was I productive; my code felt remarkably simple. With Backbone.js, I always felt I was one or two slip-ups from the whole application spiraling out of control. With React, elegant and simple solutions seemed to come naturally from using the library. Again, I could feel things in web land were changing in a very big way. diff --git a/docs/blog/2018-06-07-build-a-gatsby-blog-using-the-cosmic-js-source-plugin/index.md b/docs/blog/2018-06-07-build-a-gatsby-blog-using-the-cosmic-js-source-plugin/index.md index 7a90d2be6e3e7..9747b29308cec 100644 --- a/docs/blog/2018-06-07-build-a-gatsby-blog-using-the-cosmic-js-source-plugin/index.md +++ b/docs/blog/2018-06-07-build-a-gatsby-blog-using-the-cosmic-js-source-plugin/index.md @@ -424,7 +424,7 @@ Restart the Gatsby server, then visit the detail page by clicking on URLs displa In addition to the code covered in this tutorial, we also implemented `src/components/bio.js` to display author information & `src/layouts/index.js` to [create a generic layout](/tutorial/part-three/#our-first-layout-component) for the blog. -The source code for this tutorial is available [on GitHub](https://github.com/cosmicjs/gatsby-blog-cosmicjs). To see it live, clone the repository, and run (`cd gatsby-blog-cosmicjs && npm i && npm run develop`) or check out the [demo on Netlify](https://gatsby-blog-cosmicjs.netlify.com/). +The source code for this tutorial is available [on GitHub](https://github.com/cosmicjs/gatsby-blog-cosmicjs). To see it live, clone the repository, and run (`cd gatsby-blog-cosmicjs && npm i && npm run develop`) or check out the [demo on Netlify](https://gatsby-blog-cosmicjs.netlify.app/). The static website generated by Gatsby can easily be published on services like Netlify, S3/CloudFront, GitHub Pages, GitLab Pages, Heroku, etc. diff --git a/docs/blog/2018-07-07-graphic-design-class/index.md b/docs/blog/2018-07-07-graphic-design-class/index.md index 579ed839cdd12..e0000a3915ae8 100644 --- a/docs/blog/2018-07-07-graphic-design-class/index.md +++ b/docs/blog/2018-07-07-graphic-design-class/index.md @@ -25,13 +25,13 @@ However, in his current class _nobody has dropped out_. And every single one of [Melany Dierks](http://mywetpaintstudio.com/) ([source](https://github.com/reguv760/mmd-site2)) -[![Image of graphic designer's site](graphic-design-2.png)](http://myceevee.netlify.com/) +[![Image of graphic designer's site](graphic-design-2.png)](https://myceevee.netlify.app/) -[Khabarovsk](http://myceevee.netlify.com/) ([source](https://github.com/msergushova/myceevee)) +[Khabarovsk](https://myceevee.netlify.app/) ([source](https://github.com/msergushova/myceevee)) -[![Image of graphic designer's site](graphic-design-3.png)](https://trudesignsongatsby.netlify.com/) +[![Image of graphic designer's site](graphic-design-3.png)](https://trudesignsongatsby.netlify.app/) -[TruDesigns](https://trudesignsongatsby.netlify.com/) ([source](https://github.com/trudesigns/newStuff)) +[TruDesigns](https://trudesignsongatsby.netlify.app/) ([source](https://github.com/trudesigns/newStuff)) After our initial phone conversation, Phil responded to a series of interview questions via email. diff --git a/docs/blog/2018-10-03-gatsby-perf/index.md b/docs/blog/2018-10-03-gatsby-perf/index.md index ff2852cfcfe07..75079ccd62811 100644 --- a/docs/blog/2018-10-03-gatsby-perf/index.md +++ b/docs/blog/2018-10-03-gatsby-perf/index.md @@ -63,7 +63,7 @@ WebPagetest allows you to collect performance measurements in running on a _real ![WebPagetest](./images/webpagetest.png) -Running a test in WebPagetest will pull up the specified site on the browser/network specified, and then collect performance measurements that can be reviewed and analyzed. These tests can serve as a baseline that can be compared against after changes are made, e.g. like a change in comparing the Gatsby v1 site to the Gatsby v2 site 🤓 Additionally, it's helpful to run these tests fairly often after meaningful changes and features are added to your web site, to ensure that you're guarding against performance regressions! For your consideration, check out Gatsby v1's metrics in WebPagetest. +Running a test in WebPagetest will pull up the specified site on the browser/network specified, and then collect performance measurements that can be reviewed and analyzed. These tests can serve as a baseline that can be compared against after changes are made, e.g. like a change in comparing the Gatsby v1 site to the Gatsby v2 site 🤓 Additionally, it's helpful to run these tests fairly often after meaningful changes and features are added to your website, to ensure that you're guarding against performance regressions! For your consideration, check out Gatsby v1's metrics in WebPagetest. [![WebPagetest v1](./images/webpagetest-v1.png)][webpagetestv1-results] @@ -129,9 +129,9 @@ Gatsby v2 is an iterative approach to improving the solid foundational base that [speed-index]: https://sites.google.com/a/webpagetest.org/docs/using-webpagetest/metrics/speed-index [lighthouse]: https://www.google.com/search?q=google+audit&ie=utf-8&oe=utf-8&client=firefox-b-1-ab [gatsby-v1-repo]: https://github.com/dschau/gatsby-v1 -[gatsby-v1-netlify]: https://gatsby-v1-perf.netlify.com/ +[gatsby-v1-netlify]: https://gatsby-v1-perf.netlify.app/ [gatsby-v2-repo]: https://github.com/dschau/gatsby-v2 -[gatsby-v2-netlify]: https://gatsby-v2-perf.netlify.com/ +[gatsby-v2-netlify]: https://gatsby-v2-perf.netlify.app/ [gatsby-source-wordpress]: /packages/gatsby-source-wordpress [gatsby-plugin-typescript]: /packages/gatsby-plugin-typescript [migration-guide]: /docs/migrating-from-v1-to-v2/ diff --git a/docs/blog/2018-10-26-export-a-drupal-site-to-gatsby/index.md b/docs/blog/2018-10-26-export-a-drupal-site-to-gatsby/index.md index 84b2130152c57..240573260af65 100644 --- a/docs/blog/2018-10-26-export-a-drupal-site-to-gatsby/index.md +++ b/docs/blog/2018-10-26-export-a-drupal-site-to-gatsby/index.md @@ -126,7 +126,7 @@ To have comments on your site you can use a service like [Disqus](https://disqus ```javascript const Database = require("better-sqlite3") const fs = require("fs") -const yourSite = "http://username.github.io/yoursite/" +const yourSite = "https://username.github.io/yoursite/" if (process.argv.length < 3) { usage() diff --git a/docs/blog/2018-11-07-gatsby-for-apps/index.md b/docs/blog/2018-11-07-gatsby-for-apps/index.md index 1fc6418043d1f..4b4201423da14 100644 --- a/docs/blog/2018-11-07-gatsby-for-apps/index.md +++ b/docs/blog/2018-11-07-gatsby-for-apps/index.md @@ -245,6 +245,6 @@ We can't wait to see what you build. [gatsby-source-wordpress]: /packages/gatsby-source-wordpress/ [gatsby-transformer-yaml]: /packages/gatsby-transformer-yaml/ [gatsby-plugins]: /plugins -[gatsby-mail-app]: https://gatsby-mail.netlify.com +[gatsby-mail-app]: https://gatsby-mail.netlify.app [gatsby-mail-repo]: https://github.com/dschau/gatsby-mail [apollo-boost]: https://github.com/apollographql/apollo-client/tree/master/packages/apollo-boost diff --git a/docs/blog/2018-12-04-per-link-gatsby-page-transitions-with-transitionlink/index.md b/docs/blog/2018-12-04-per-link-gatsby-page-transitions-with-transitionlink/index.md index c4127326cf041..f72b1d37b6520 100644 --- a/docs/blog/2018-12-04-per-link-gatsby-page-transitions-with-transitionlink/index.md +++ b/docs/blog/2018-12-04-per-link-gatsby-page-transitions-with-transitionlink/index.md @@ -15,7 +15,7 @@ TransitionLink is a simple way of declaring a page transition via props on a Lin TransitionLink is compatible with declarative react animation libraries like [react-pose](https://popmotion.io/pose/) and [react-spring](https://react-spring.surge.sh/). It's also compatible with imperative animation libraries like [gsap](https://greensock.com) and [anime.js](http://animejs.com/) -Check it out [in use](https://gatsby-plugin-transition-link.netlify.com/). +Check it out [in use](https://gatsby-plugin-transition-link.netlify.app/). ## The story diff --git a/docs/blog/2018-12-17-turning-the-static-dynamic/index.md b/docs/blog/2018-12-17-turning-the-static-dynamic/index.md index 8c47b5e89078e..f447de2eb0497 100644 --- a/docs/blog/2018-12-17-turning-the-static-dynamic/index.md +++ b/docs/blog/2018-12-17-turning-the-static-dynamic/index.md @@ -12,7 +12,7 @@ excerpt: Gatsby is great for not only static sites but also traditional web appl > A: Gatsby can be used to build fully dynamic sites, which surprises some people because of it’s label as a “static site generator”. It’s fully equipped to be a powerful alternative to create-react-app and other similar solutions with the addition of easy pre-rendering and perf baked in. — biscarch -Even though Dustin [recently wrote about Gatsby for Apps](/blog/2018-11-07-gatsby-for-apps/) and open sourced his [Gatsby Mail](https://gatsby-mail.netlify.com/) demo, I do still find people constantly having to explain that Gatsby is "not just for sites". +Even though Dustin [recently wrote about Gatsby for Apps](/blog/2018-11-07-gatsby-for-apps/) and open sourced his [Gatsby Mail](https://gatsby-mail.netlify.app/) demo, I do still find people constantly having to explain that Gatsby is "not just for sites". Today I'd like to show you how you can incrementally add functionality to a Gatsby static site with Netlify Functions, and then add authentication with Netlify Identity to begin a proper Gatsby app. @@ -75,7 +75,10 @@ For more info or configuration options (e.g. in different branches and build env 4. **Proxy the emulated functions for local development**: Head to `gatsby-config.js` and add this to your `module.exports`: ```jsx:title=gatsby-config.js -var proxy = require("http-proxy-middleware") +const { createProxyMiddleware } = require("http-proxy-middleware") //v1.x.x +// Use implicit require for v0.x.x of 'http-proxy-middleware' +// const proxy = require('http-proxy-middleware') +// be sure to replace 'createProxyMiddleware' with 'proxy' where applicable module.exports = { // for avoiding CORS while developing Netlify Functions locally @@ -83,7 +86,7 @@ module.exports = { developMiddleware: app => { app.use( "/.netlify/functions/", - proxy({ + createProxyMiddleware({ target: "http://localhost:9000", pathRewrite: { "/.netlify/functions/": "", @@ -392,4 +395,4 @@ It's 5 steps each to turn your static Gatsby sites into dynamic, authenticated, - **Code:** https://github.com/sw-yx/jamstack-hackathon-starter - **Starter:** https://www.gatsbyjs.org/starters/jamstack-hackathon-starter -- **Live Demo:** https://jamstack-hackathon-starter.netlify.com/ +- **Live Demo:** https://jamstack-hackathon-starter.netlify.app/ diff --git a/docs/blog/2019-02-11-gatsby-themes-livestream-and-example/index.md b/docs/blog/2019-02-11-gatsby-themes-livestream-and-example/index.md index 029b62124b4be..3249c0a34eca9 100644 --- a/docs/blog/2019-02-11-gatsby-themes-livestream-and-example/index.md +++ b/docs/blog/2019-02-11-gatsby-themes-livestream-and-example/index.md @@ -45,7 +45,7 @@ The code we built is [available on GitHub](https://github.com/jlengstorf/livestr - Post: [Introducing Gatsby Themes](/blog/2018-11-11-introducing-gatsby-themes/) - Post: [Why Themes](/blog/2019-01-31-why-themes/) - [`gatsby-plugin-page-creator`](/packages/gatsby-plugin-page-creator/) -- [`gatsby-mdx` getting started docs](https://gatsby-mdx.netlify.com/getting-started) +- [`gatsby-mdx` getting started docs](https://gatsby-mdx.netlify.app/getting-started) - [`gatsby-source-filesystem`](/packages/gatsby-source-filesystem/) - [John Otander on Twitter](https://twitter.com/4lpine) - [Jason Lengstorf on Twitter](https://twitter.com/jlengstorf) diff --git a/docs/blog/2019-02-26-getting-started-with-gatsby-themes/index.md b/docs/blog/2019-02-26-getting-started-with-gatsby-themes/index.md index ed803b384a939..3312a1d6eccbe 100644 --- a/docs/blog/2019-02-26-getting-started-with-gatsby-themes/index.md +++ b/docs/blog/2019-02-26-getting-started-with-gatsby-themes/index.md @@ -95,7 +95,7 @@ You will want to make Gatsby, React, and ReactDom peer dependencies in the _them > MDX is markdown for the component era. It lets you write JSX embedded inside markdown. That's a great combination because it allows you to use markdown's often terse syntax (such as # heading) for the little things and JSX for more advanced components. -Read more about Gatsby+MDX [here.](https://gatsby-mdx.netlify.com/) +Read more about Gatsby+MDX [here.](https://gatsby-mdx.netlify.app/) In your _theme_ directory, add src/pages/index.mdx diff --git a/docs/blog/2019-04-19-your-website-should-be-built-with-gatsby/index.md b/docs/blog/2019-04-19-your-website-should-be-built-with-gatsby/index.md index 6fe5b8e41c204..cc7b549b3850b 100644 --- a/docs/blog/2019-04-19-your-website-should-be-built-with-gatsby/index.md +++ b/docs/blog/2019-04-19-your-website-should-be-built-with-gatsby/index.md @@ -34,7 +34,7 @@ We’ve covered the basics, stick around as we dive into the details. ### The Landscape -We’ve grown high expectations for web sites since their humble beginnings in the early 90s. Primarily, most websites are attached to diverse set data sources - a Content Management System (CMS) like WordPress or Shopify, a social feed from Instagram or Twitter, or high-resolution images hosted in a repository like Cloudinary. +We’ve grown high expectations for websites since their humble beginnings in the early 90s. Primarily, most websites are attached to diverse set data sources - a Content Management System (CMS) like WordPress or Shopify, a social feed from Instagram or Twitter, or high-resolution images hosted in a repository like Cloudinary. This is fantastic, the CMS allows anyone to publish content to the web without having to continually hire a web developer. Pulling content from our social feeds means that we don’t have to duplicate content, and it promotes all the different mediums through which users can engage with our brand. diff --git a/docs/blog/2019-07-03-using-themes-for-distributed-docs/index.md b/docs/blog/2019-07-03-using-themes-for-distributed-docs/index.md index bba096832ed21..307bbce567e3a 100644 --- a/docs/blog/2019-07-03-using-themes-for-distributed-docs/index.md +++ b/docs/blog/2019-07-03-using-themes-for-distributed-docs/index.md @@ -45,7 +45,7 @@ Using [MDX](/docs/mdx/), we’re able to write rich documentation by including R ![Rendering components in MDX](./images/mdx-components.png) -`gatsby-plugin-mdx` also allows us to replace Markdown elements with custom React components using the [`components` prop on the `MDXProvider` component](https://gatsby-mdx.netlify.com/api-reference/mdx-provider). We use this feature to enhance our code blocks with copy buttons, filenames, and multiple language options. +`gatsby-plugin-mdx` also allows us to replace Markdown elements with custom React components using the [`components` prop on the `MDXProvider` component](https://gatsby-mdx.netlify.app/api-reference/mdx-provider). We use this feature to enhance our code blocks with copy buttons, filenames, and multiple language options. ![Enhanced code blocks](./images/code-blocks.gif) diff --git a/docs/blog/2019-07-23-google-sheets-gatsby-acroyoga-video-explorer/index.md b/docs/blog/2019-07-23-google-sheets-gatsby-acroyoga-video-explorer/index.md index 192450b7cae64..3a23a6508b14e 100644 --- a/docs/blog/2019-07-23-google-sheets-gatsby-acroyoga-video-explorer/index.md +++ b/docs/blog/2019-07-23-google-sheets-gatsby-acroyoga-video-explorer/index.md @@ -8,7 +8,7 @@ tags: - gatsby-image --- -I recently prototyped an [Acroyoga](https://en.wikipedia.org/wiki/Acroyoga)-focused side project, called ['AcroTags'](https://acrotagsgatsbyblog.netlify.com), using Gatsby and the Google Sheets API. The site was as fun to build and populate with data as it is to use for discovering Acroyoga videos. This post will explore why and how I made this site and cover the specific code I used to get Gatsby and Google Sheets to work nicely together. I hope this tutorial and the code samples allow you to quickly prototype your next idea using this very simple and powerful stack. +I recently prototyped an [Acroyoga](https://en.wikipedia.org/wiki/Acroyoga)-focused side project, called ['AcroTags'](https://acrotagsgatsbyblog.netlify.app), using Gatsby and the Google Sheets API. The site was as fun to build and populate with data as it is to use for discovering Acroyoga videos. This post will explore why and how I made this site and cover the specific code I used to get Gatsby and Google Sheets to work nicely together. I hope this tutorial and the code samples allow you to quickly prototype your next idea using this very simple and powerful stack. ## Background on an Acroyoga obsession and the Need for a Video Explorer Site @@ -20,7 +20,7 @@ I've long found it challenging to find just the right video to work on. Sometime My requirements for this Acroyoga videos site is that it be simple to add data to, load fast on mobile, and be generally intuitive to use. For this reason, I'm using Gatsby (and of course, React) and the Google Sheets API for this site. This simple stack will allow me to build a fast loading application that consumes data from a Google Sheet. -As such, this article will show how I built this site. I'll show only the code samples that are Gatsby and Google Sheets specific but you can see all of the code in this repo: https://github.com/kpennell/acrotagsgatsbyblog. Finally, if you want to check out the demo app, that can be found here: https://acrotagsgatsbyblog.netlify.com. +As such, this article will show how I built this site. I'll show only the code samples that are Gatsby and Google Sheets specific but you can see all of the code in this repo: https://github.com/kpennell/acrotagsgatsbyblog. Finally, if you want to check out the demo app, that can be found here: https://acrotagsgatsbyblog.netlify.app. ## Creating a Basic Gatsby Setup with Material-UI diff --git a/docs/blog/2019-08-07-theme-jam/index.md b/docs/blog/2019-08-07-theme-jam/index.md index 89716387d3cd2..66363f8de0c1a 100644 --- a/docs/blog/2019-08-07-theme-jam/index.md +++ b/docs/blog/2019-08-07-theme-jam/index.md @@ -65,7 +65,7 @@ Two of the themes we received stood out especially. As we reviewed, we all took Vojtěch combined data sourcing from [Simplecast](https://simplecast.com/)’s API, beautiful design, and an explorable UX to create this powerful theme for podcasters. -**Check out the theme: [source code](https://github.com/vojtaholik/gatsby-theme-simplecast) · [demo](https://gatsby-theme-simplecast.netlify.com/)** +**Check out the theme: [source code](https://github.com/vojtaholik/gatsby-theme-simplecast) · [demo](https://gatsby-theme-simplecast.netlify.app/)** ### Allan’s Prismic-Powered Legal Pages Theme @@ -73,7 +73,7 @@ Vojtěch combined data sourcing from [Simplecast](https://simplecast.com/)’s A Allan turned something boring (required legal pages) into something beautiful by pulling common legal pages — such as a “terms & conditions” page — from [Prismic](https://prismic.io/) and putting them into a gorgeous UI. This theme highlights theme composability: combine this theme with others to quickly add required legal pages to any Gatsby site! -**Check out the theme: [source code](https://github.com/littleplusbig/gatsby-theme-legals-prismic) · [demo](https://gatsby-theme-legals.netlify.com/)** +**Check out the theme: [source code](https://github.com/littleplusbig/gatsby-theme-legals-prismic) · [demo](https://gatsby-theme-legals.netlify.app/)** ## Thanks to the Entire Community diff --git a/docs/blog/2019-09-26-announcing-gatsby-15m-series-a-funding-round/index.md b/docs/blog/2019-09-26-announcing-gatsby-15m-series-a-funding-round/index.md index 0d866db55525b..e449b5142b60e 100644 --- a/docs/blog/2019-09-26-announcing-gatsby-15m-series-a-funding-round/index.md +++ b/docs/blog/2019-09-26-announcing-gatsby-15m-series-a-funding-round/index.md @@ -18,7 +18,7 @@ With Gatsby, we’re reinventing website technology so people can create sites t Gatsby strips away much of the complexity that plagues website development. Teams tell us that they can build stunning sites 3-5x faster with Gatsby—and have a lot more fun in the process. -The web is an incredible medium. Anyone, anywhere can produce a site and ship their ideas to the world. [Individuals, teams, and organizations are turning to Gatsby to create web sites and apps that stand out](https://www.gatsbyjs.org/blog/tags/case-studies)[.](https://www.gatsbyjs.org/blog/tags/case-studies) +The web is an incredible medium. Anyone, anywhere can produce a site and ship their ideas to the world. [Individuals, teams, and organizations are turning to Gatsby to create websites and apps that stand out](https://www.gatsbyjs.org/blog/tags/case-studies)[.](https://www.gatsbyjs.org/blog/tags/case-studies) ## From the CMS to the content mesh diff --git a/docs/blog/2019-11-14-announcing-gatsby-cloud/index.md b/docs/blog/2019-11-14-announcing-gatsby-cloud/index.md index f1a2dfae85e67..998adb2b44f9f 100644 --- a/docs/blog/2019-11-14-announcing-gatsby-cloud/index.md +++ b/docs/blog/2019-11-14-announcing-gatsby-cloud/index.md @@ -55,7 +55,7 @@ Let's step back and discuss why we're building Gatsby and how our new Cloud plat For most of the history of the web, the dominant web architecture has been the LAMP stack e.g., applications like WordPress. But the last decade has seen the rise of two enormous trends—cloud computing and JavaScript-rich web apps (driven by component frameworks like React). Gatsby was founded around the idea that web architectures are converging on these two ideas and will be foundational for decades to come. -Gatsby provides the building blocks for a modern web site: +Gatsby provides the building blocks for a modern website: - **JavaScript Component Library**. Gatsby sites are React apps, so you can create high-quality, dynamic web apps, from blogs to e-commerce sites to user dashboards. - **Load Data From Anywhere**. Gatsby pulls in data from any data source, whether it's Markdown files, a headless CMS like Contentful or WordPress, or a REST or GraphQL API. Use source plugins to load your data, then develop using Gatsby's uniform GraphQL interface. diff --git a/docs/blog/2020-04-13-upgrading-to-jamstack-with-agility/index.md b/docs/blog/2020-04-13-upgrading-to-jamstack-with-agility/index.md index e3467d5ee6f8f..aa35661859eea 100644 --- a/docs/blog/2020-04-13-upgrading-to-jamstack-with-agility/index.md +++ b/docs/blog/2020-04-13-upgrading-to-jamstack-with-agility/index.md @@ -241,7 +241,7 @@ async function handleRequest(request) { let path = url.pathname //secondary domain... - const secDomain = "https://my-new-website.netlify.com" + const secDomain = "https://my-new-website.netlify.app" if ( path == "/" || //redirect the home page... diff --git a/docs/blog/2020-04-20-paulie-scanlons-journey-of-100-days/index.md b/docs/blog/2020-04-20-paulie-scanlons-journey-of-100-days/index.md index c07976865a4bb..d2b7617048f15 100644 --- a/docs/blog/2020-04-20-paulie-scanlons-journey-of-100-days/index.md +++ b/docs/blog/2020-04-20-paulie-scanlons-journey-of-100-days/index.md @@ -46,11 +46,11 @@ I believe this project has legs, but I also need to do a bit more work on it bef ## 2. gatsby-theme-terminal -This was my second attempt at developing a theme and after making a bit of a mess of my first one [gatsby-theme-gatstats](https://gatsby-theme-gatstats.netlify.com/) I went back to the drawing board and decided to see if it was possible to write a theme with **zero components**. This is an odd concept if you're coming form WordPress, but with this theme all I'm providing are some neat little data components that help you query the nodes from GraphQL. Plus a very light skin that styles all markdown and all components provided by Theme UI Components. If you've read above about Skin UI this theme is essentially Skin UI but with some extra bits thrown in. +This was my second attempt at developing a theme and after making a bit of a mess of my first one [gatsby-theme-gatstats](https://gatsby-theme-gatstats.netlify.app/) I went back to the drawing board and decided to see if it was possible to write a theme with **zero components**. This is an odd concept if you're coming form WordPress, but with this theme all I'm providing are some neat little data components that help you query the nodes from GraphQL. Plus a very light skin that styles all markdown and all components provided by Theme UI Components. If you've read above about Skin UI this theme is essentially Skin UI but with some extra bits thrown in. Having worked on Gatsby Themes for about a year now I think this approach can be really powerful. Component shadowing is awesome, don't get me wrong, but if you decouple the "components" from a theme and just provide _data_ and _styles_ the user then has full control over their UI. No more hacking over the top of CSS and no real need to shadow a "component" to change the way it looks or functions. This approach means you can just build anything you want using the components from Theme UI and boom 💥 you've got yourself a totally custom blog, site or application. -[View demo](https://gatsby-theme-terminal.netlify.com/) | +[View demo](https://gatsby-theme-terminal.netlify.app/) | [GitHub](https://github.com/PaulieScanlon/gatsby-theme-terminal) | [Blog post](https://paulie.dev/posts/2020/02/gatsby-theme-terminal/) @@ -58,7 +58,7 @@ Having worked on Gatsby Themes for about a year now I think this approach can be ## 3. gatsby-starter-terminal -It seems fitting that if I want folks to use my theme: [gatsby-theme-terminal](https://gatsby-theme-terminal.netlify.com/) I should give them a helping hand. So here's a starter to... er... get you started 🤗 +It seems fitting that if I want folks to use my theme: [gatsby-theme-terminal](https://gatsby-theme-terminal.netlify.app/) I should give them a helping hand. So here's a starter to... er... get you started 🤗 It's a pretty bare bones example of how to use the theme but it does demonstrate how to use component shadowing for the logo and how to provide a custom Theme UI object to style the theme your way. _I believe the 2 stars it has on GitHub speak for themselves_ 🌟😂. @@ -80,7 +80,7 @@ I've created a [PR](https://github.com/system-ui/theme-ui/pull/669) for Theme UI (If anyone in Gatsby Admin happens to read this, again, I'm available to help build it.) -[View demo](https://gatsby-plugin-prop-shop.netlify.com/prop-shop/) | +[View demo](https://gatsby-plugin-prop-shop.netlify.app/prop-shop/) | [GitHub](https://github.com/PaulieScanlon/gatsby-plugin-prop-shop) | [Blog post](https://paulie.dev/posts/2020/02/prop-shop/) @@ -104,7 +104,7 @@ Spotting a gap in the market I developed this plugin to bring all the same embed That's all possible with this plugin. There are few shortcomings with the way the props are required for each of the components and I do hope to develop this further so it's easier to use but for now if you want to embed Twitter, YouTube Instagram and many more in to your `.mdx` without imports, this is the plugin for you! -[View Demo](https://gatsby-mdx-embed.netlify.com/) | +[View Demo](https://gatsby-mdx-embed.netlify.app/) | [GitHub](https://github.com/PaulieScanlon/gatsby-mdx-embed) | [Blog post](https://paulie.dev/posts/2020/01/gatsby-mdx-embed/) @@ -116,7 +116,7 @@ OK, true confession, I started building this plugin before the challenge came ab This plugin was a head first dive into the [Markdown Abstract Syntax Tree](https://github.com/syntax-tree/mdast) and allowed me to understand what markdown and MDX do under the hood. Using visitor patterns I was able to bring responsive mobile first layouts to tired old single column markdown files. -[View Demo](https://gatsby-remark-grid-system.netlify.com/) | +[View Demo](https://gatsby-remark-grid-system.netlify.app/) | [GitHub](https://github.com/PaulieScanlon/gatsby-remark-grid-system) | [Blog post](https://paulie.dev/posts/2019/12/26/gatsby-remark-grid-system/) @@ -124,13 +124,13 @@ This plugin was a head first dive into the [Markdown Abstract Syntax Tree](https ## 8. gatsby-mdx-routes -Again, officially speaking, I started this plugin before the challenge started. However, I did continue to develop it over the course of the 100 days and released multiple updates as new requirements became clear. I've also used this plugin in my theme [gatsby-theme-terminal](https://gatsby-theme-terminal.netlify.com/). +Again, officially speaking, I started this plugin before the challenge started. However, I did continue to develop it over the course of the 100 days and released multiple updates as new requirements became clear. I've also used this plugin in my theme [gatsby-theme-terminal](https://gatsby-theme-terminal.netlify.app/). -Extracting navigation routes for locally sourced `.mdx` files using GraphQL in your project isn't a huge task in itself. But I try to be helpful, so this plugin aims to separate the business logic of _finding_, _sorting_ and _listing_ routes from _styling_ those routes as links or lists. It was the start of my thinking process about separation of concerns which I then used more effectively in [gatsby-theme-terminal](https://gatsby-theme-terminal.netlify.com/) +Extracting navigation routes for locally sourced `.mdx` files using GraphQL in your project isn't a huge task in itself. But I try to be helpful, so this plugin aims to separate the business logic of _finding_, _sorting_ and _listing_ routes from _styling_ those routes as links or lists. It was the start of my thinking process about separation of concerns which I then used more effectively in [gatsby-theme-terminal](https://gatsby-theme-terminal.netlify.app/) There are a few areas where it doesn't quite perform, namely in the recursive pattern, but developing this plugin really enhanced my JavaScript knowledge. And, dare I say it, but I think I finally understand [Array.prototype.reduce()](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/reduce) -[View Demo](https://gatsby-mdx-routes.netlify.com/) | +[View Demo](https://gatsby-mdx-routes.netlify.app/) | [GitHub](https://github.com/PaulieScanlon/gatsby-mdx-routes) | [Blog post](https://paulie.dev/posts/2019/12/12/gatsby-mdx-routes/) @@ -144,7 +144,7 @@ I developed this plugin back in December 2019 and as my following grew so to did So if you do want big tables in your blog but don't want neverending page scrolls, then keep it sticky with [gatsby-remark-sticky-table](https://github.com/PaulieScanlon/gatsby-remark-sticky-table) -[View Demo](https://gatsby-remark-sticky-table.netlify.com/) | +[View Demo](https://gatsby-remark-sticky-table.netlify.app/) | [GitHub](https://github.com/PaulieScanlon/gatsby-remark-sticky-table) | [Blog post](https://paulie.dev/posts/2019/11/24/gatsby-remark-sticky-table/) @@ -160,8 +160,8 @@ Knowing what I know now, post my 100 Days journey, I think it's time to retire t (Apologies in advance if you're using this theme. They'll be an update soon about how to migrate). -[View Demo](https://gatsby-theme-gatstats.netlify.com/) | -[Storybook](https://gatsby-theme-gatstats.netlify.com/storybook/) +[View Demo](https://gatsby-theme-gatstats.netlify.app/) | +[Storybook](https://gatsby-theme-gatstats.netlify.app/storybook/) [GitHub](https://github.com/PaulieScanlon/gatsby-theme-gatstats) | [Blog post](https://paulie.dev/posts/2019/11/12/gatsby-theme-gatstats/) diff --git a/docs/blog/2020-05-12-strapi-instant-content-preview-plugin/index.md b/docs/blog/2020-05-12-strapi-instant-content-preview-plugin/index.md index 0a8412a92c11a..b2dfc4beee5b2 100644 --- a/docs/blog/2020-05-12-strapi-instant-content-preview-plugin/index.md +++ b/docs/blog/2020-05-12-strapi-instant-content-preview-plugin/index.md @@ -15,9 +15,9 @@ tags: Strapi is the #1 open source headless CMS frontend developers all over the world love. You can easily and quickly manage your content through an API and it's made entirely with Node & React. Gatsby developers will feel right at home in a Javascript environment that they know like the back of their hand. -A lot of developers in the community are already familiar with setting up Gatsby with Strapi, and happy with how easy it is to combine the two. People really appreciate how [the Gatsby source plugin](https://www.gatsbyjs.org/packages/gatsby-source-strapi/) works great for easily and seamlessly pulling any Strapi content into any Gatsby application. +A lot of developers in the community are already familiar with setting up Gatsby with Strapi, and happy with how easy it is to combine the two. People really appreciate how [the Gatsby source plugin](/packages/gatsby-source-strapi/) works great for easily and seamlessly pulling any Strapi content into any Gatsby application. -However, with the arrival of [Gatsby Preview](<[https://www.gatsbyjs.com/preview/](https://www.gatsbyjs.com/preview/)>), things got even better between Strapi and Gatsby! +However, with the arrival of [Gatsby Preview](https://www.gatsbyjs.com/preview/), things got even better between Strapi and Gatsby! Gatsby Preview gives you a live URL where you can see changes made in a CMS before publishing -- sort of like “hot reloading” but for content editing! To take maximum advantage of Preview, then, we shipped a new version of our original using [Strapi Webhooks](https://strapi.io/blog/webhooks) to instantly rebuild Gatsby applications on Gatsby Cloud as content changes. No manual rebuilds -- create, update or delete content and then instantly see what it really looks like to end users. @@ -50,7 +50,7 @@ Now it's time to deploy your Gatsby app! ![https://raw.githubusercontent.com/strapi/strapi-starter-gatsby-blog/master/medias/create-a-new-site.png](https://raw.githubusercontent.com/strapi/strapi-starter-gatsby-blog/master/medias/create-a-new-site.png "Gatsby Cloud landing page with selected option") -(Deploying your Gatsby site on Gatsby Cloud means builds are now faster than ever, thanks to Gatsby's brand new [Incremental Builds feature](https://www.gatsbyjs.org/blog/2020-04-22-announcing-incremental-builds/) for data changes! +(Deploying your Gatsby site on Gatsby Cloud means builds are now faster than ever, thanks to Gatsby's brand new [Incremental Builds feature](/blog/2020-04-22-announcing-incremental-builds/) for data changes! 2. When asked to select the repository you want to use: @@ -62,9 +62,9 @@ Now it's time to deploy your Gatsby app! ![https://raw.githubusercontent.com/strapi/strapi-starter-gatsby-blog/master/medias/skip.png](https://raw.githubusercontent.com/strapi/strapi-starter-gatsby-blog/master/medias/skip.png "screen shot of sample cut and paste webhook url") -4. Paste your Strapi `API_URL` for both of your Builds Environment variables and Preview Environment variables. That usually means pasting the url of your Strapi instances deployed on Heroku (eg: https://your-app.herokuapp.com) +4. Paste your Strapi `API_URL` for both of your Builds Environment variables and Preview Environment variables. That usually means pasting the url of your Strapi instances deployed on Heroku (eg: `https://your-app.herokuapp.com`) -_Note: Be sure to paste your Heroku url without the trailing slash (eg: "https://your-app.herokuapp.com" and not "https://your-app.herokuapp.com/")._ +_Note: Be sure to paste your Heroku url without the trailing slash (eg: `https://your-app.herokuapp.com` and not `https://your-app.herokuapp.com/`)._ ![https://raw.githubusercontent.com/strapi/strapi-starter-gatsby-blog/master/medias/env.png](https://raw.githubusercontent.com/strapi/strapi-starter-gatsby-blog/master/medias/env.png "screen shot of environment variables form") diff --git a/docs/blog/2020-05-21-gatsby-recipes/index.md b/docs/blog/2020-05-21-gatsby-recipes/index.md index 30113ed5af976..040458385370e 100644 --- a/docs/blog/2020-05-21-gatsby-recipes/index.md +++ b/docs/blog/2020-05-21-gatsby-recipes/index.md @@ -15,7 +15,7 @@ Recipes can be used to automate npm installs, run npm scripts, add config option Gatsby ships with a number of default Recipes, but it’s also really easy to create your own! In this post we are going to look at writing a Recipe to install `gatsby-plugin-google-analytics` and add it to your project’s plugins. But first let’s take a look at why Recipes are so very useful and how I got started with doing some for tasks I found particularly taxing. -(You can read more about Recipes [here](https://www.gatsbyjs.org/blog/2020-04-15-announcing-gatsby-recipes/), the experimental README is [here](https://github.com/gatsbyjs/gatsby/blob/master/packages/gatsby-recipes/README.md) and, to track the conversation, [here’s](https://github.com/gatsbyjs/gatsby/issues/22991) the Umbrella Issue on GitHub). +(You can read more about [Recipes](/blog/2020-04-15-announcing-gatsby-recipes/), the experimental [README](https://github.com/gatsbyjs/gatsby/blob/master/packages/gatsby-recipes/README.md) and, to track the conversation, [the Umbrella Issue on GitHub](https://github.com/gatsbyjs/gatsby/issues/22991)). ## Recipes: What’s all the fuss about? @@ -25,10 +25,10 @@ I’m a React UI Developer and I work on a lot of Greenfield Component Library b To get the two playing nicely together it requires a little under the hood knowledge about Gatsby and Storybook, and this knowledge supplies the foundation for writing a Recipe to handle it: -- Gatsby is written in ES6 and isn’t transpiled to CommonJs until either the `gatsby develop` or `gatsby build` processes are run. -- Storybook requires all module code to be transpiled to CommonJs +- Gatsby is written in ES6 and isn’t transpiled to CommonJS until either the `gatsby develop` or `gatsby build` processes are run. +- Storybook requires all module code to be transpiled to CommonJS. -The problem here is when you run Storybook it has no knowledge of the Gatsby build processes and will only transpile “your” ES6 code to CommonJs. This is mostly fine apart from when you attempt to create a story for a Gatsby component, or a story that embeds or composes a Gatsby component. One such component is `` +The problem here is when you run Storybook it has no knowledge of the Gatsby build processes and will only transpile “your” ES6 code to CommonJS. This is mostly fine apart from when you attempt to create a story for a Gatsby component, or a story that embeds or composes a Gatsby component. One such component is `` For example: @@ -38,7 +38,7 @@ import { Link } from ‘gatsby’ The reason this will cause Storybook to error is because the `` component comes from Gatsby / `node_modules` which, as mentioned above, is (as yet) un-transpiled ES6 code. -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. +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 `` component but this will only get you so far. @@ -52,17 +52,17 @@ And if (like me) Babel also scares you a little bit, you might be having a think ## Recipes to the rescue -It’s for precisely this reason I created two of my own Recipes to automate the setup of Storybook and its Webpack config for both JavaScript and TypeScript Gatsby projects. +It’s for precisely this reason I created two of my own Recipes to automate the setup of Storybook and its webpack config for both JavaScript and TypeScript Gatsby projects. If you haven’t installed the latest Gatsby CLI run this 👇 -```sh +```shell npm install -g gatsby-cli@latest ``` Now you can now run 👇 -```sh +```shell gatsby recipes ``` @@ -82,15 +82,15 @@ If you’re interested, here is where you can read more about my Recipes👇 ## Fancy writing your own Recipe? -The Recipe we’re going to write will install `gatsby-plugin-google-analytics` and add it to the plugins array in `gatsby-config.js` +The Recipe we’re going to write will install `gatsby-plugin-google-analytics` and add it to the plugins array in `gatsby-config.js`. This recipe will utilize two of the Recipe components/providers. The first is `` the second is `` -You can read more about the components/providers [here](https://github.com/gatsbyjs/gatsby/blob/master/packages/gatsby-recipes/README.md#developing-recipes) +You can read more about the components/providers in the [Gatsby Recipes README](https://github.com/gatsbyjs/gatsby/blob/master/packages/gatsby-recipes/README.md#developing-recipes). To get things started you can clone this bare bones repo which has just the bits we need to create and test your very first Recipe: -```sh +```shell git clone https://github.com/PaulieScanlon/gatsby-recipe-google-analytics.git ``` @@ -98,12 +98,10 @@ Or clone from the repo here: [https://github.com/PaulieScanlon/gatsby-recipe-goo Once you have the repo cloned locally, create a new file at the root of the project and call it `gatsby-recipe-ga.mdx` and add the following MDX -```javascript -// gatsby-recipe-ga.mdx - +```mdx:title=gatsby-recipe-ga.mdx # Add `gatsby-plugin-google-analytics` to Gatsby Project -More info about the plugin can be found here: 👉 [gatsby-plugin-google-analytics](https://www.gatsbyjs.org/packages/gatsby-plugin-google-analytics/) +More info about the plugin can be found here: 👉 [gatsby-plugin-google-analytics](/packages/gatsby-plugin-google-analytics/) --- @@ -140,15 +138,14 @@ All done: 🍻 Head over to `gatsby-config.js` to complete the setup by amending or removing the plugin options. You will need a Google Analytics `trackingId` -You can read more about how to use the plugin here: 👉 [How to use](https://www.gatsbyjs.org/packages/gatsby-plugin-google-analytics/#how-to-use) - +You can read more about how to use the plugin here: 👉 [How to use](/packages/gatsby-plugin-google-analytics/#how-to-use) ``` ## Running your first Recipe Now that you’ve written your first Recipe, it’s time to run it! 👇 -```sh +```shell gatsby recipes ./gatsby-recipe-ga.mdx ``` @@ -164,7 +161,7 @@ Imagine if Recipes could be used over and over again to automate really monotono One such task might be creating new components. On any typical project this would be my component setup preference. -```javascript +```text ├─ ComponentName └─ index.ts └─ ComponentName.tsx @@ -174,11 +171,11 @@ One such task might be creating new components. On any typical project this woul Of course within each of those files are a number of imports, exports, interfaces, function declarations and tests. Doing this each and every time you create a new component is tedious and can sometimes be prone to human error. -Also, and especially on larger teams, these preferences for how files should be named -- and/or how the imports, exports and declarations should be written is rarely documented in a “style guide” because that alone is also a rather tiresome task! but in my experience it's something that's rather crucial to have "locked down" at the start of a project. +Also, and especially on larger teams, these preferences for how files should be named -- and/or how the imports, exports and declarations should be written is rarely documented in a “style guide” because that alone is also a rather tiresome task! But in my experience it's something that's rather crucial to have "locked down" at the start of a project. In early 2018 I attempted to solve this problem by creating a node module aimed at automating the React “component” creation process, [node-tiny-template](https://www.npmjs.com/package/node-tiny-template): -![landing page for the Node Tiny Template](node-tiny-template.jpg "Node Tiny Template") +![landing page for the Node Tiny Template](./node-tiny-template.jpg "Node Tiny Template") The CLI args allow you to pass in the “component name” which can then be used for the function declaration, the imports, the exports and test names, etc. diff --git a/docs/blog/2020-05-22-happy-fifth-bday-gatsby/index.md b/docs/blog/2020-05-22-happy-fifth-bday-gatsby/index.md index d6034f46dd7a0..97b256a7aab7f 100644 --- a/docs/blog/2020-05-22-happy-fifth-bday-gatsby/index.md +++ b/docs/blog/2020-05-22-happy-fifth-bday-gatsby/index.md @@ -11,8 +11,8 @@ tags: The web is an incredible place. I’m so happy I get to help build it. I’ve been building websites and web apps for a long time now, and I spent a lot of that time thinking about and experimenting with what a perfect toolset for building for the web would look like. Five years ago those thoughts coalesced into the unveiling of a nascent framework I had decided to call Gatsby: -> There's a lot of static site generators out there and I've played with several and written my own for my blog. They're all pretty much the same and not particularly interesting. I think a React.js based SSG can push the state of the art in three ways — easy no-page transitions, react.js style components, and leveraging the growing react.js ecosystem of tools and components. -> Most stuff on the web are sites, not apps. And react.js components are just as powerful for sites as they are for apps so a kickass tool for building react.js sites would be very valuable. +> There's a lot of static site generators out there and I've played with several and written my own for my blog. They're all pretty much the same and not particularly interesting. I think a React based SSG can push the state of the art in three ways — easy no-page transitions, React style components, and leveraging the growing React ecosystem of tools and components. +> Most stuff on the web are sites, not apps. And React components are just as powerful for sites as they are for apps so a kickass tool for building React sites would be very valuable. -- Opened as Issue #1, “Braindump of ideas,” by @KyleAMathews on the brand new Gatsbyjs/Gatsby GitHub repo, May 22, 2015. @@ -32,7 +32,7 @@ So I set out to create a framework that would be: - No reload page transitions. The initial html page would load followed quickly by a js bundle with the content for the rest of the site. - Smart code splitting - Themes that are installable separately -- Support for markdown/Asciidoctor/other text formats +- Support for Markdown/Asciidoctor/other text formats - Plugins support - Hot reloading built in - A Docker image that autobuilds/server site. @@ -42,17 +42,17 @@ Some of these things, ok lots of these things, are well known and appreciated pa ## Contemplating composable websites -A couple months after that Issue #1 braindump I was messing around with an issue in the Reduxjs/redux repo -- discussing the possibility of using a static site generator to spin up a site to host Redux documentation on GH pages. The conversation led to another turning point moment in Gatsby’s evolution: +A couple months after that Issue #1 braindump I was messing around with an issue in the `reduxjs/redux` repo -- discussing the possibility of using a static site generator to spin up a site to host Redux documentation on GitHub Pages. The conversation led to another turning point moment in Gatsby’s evolution: > Woah. Just had an idea. What do you think about the idea of "composable" websites? Gatsby is already doing this to some extent as it has fallbacks for most critical files you need, though you can override them easily. But we could extend that concept further to something like Object.assign(Gatsby, website_base, actual_website). -> So in practice how this would work is there'd be a base documentation site hosted on github. When you want a new docs site you'd just set the github url for the base site and then start adding markdown files. Anything else you'd want to modify could be set in the site config file. +> So in practice how this would work is there'd be a base documentation site hosted on GitHub. When you want a new docs site you'd just set the GitHub url for the base site and then start adding Markdown files. Anything else you'd want to modify could be set in the site config file. -This idea of “composable” websites eventually resulted in Gatsby Themes, plugins that include a gatsby-config.js file and add pre-configured functionality, data sourcing, and/or UI code to Gatsby sites. Essentially, modules that can be put together to form a single, holistic Gatsby site. Which in turn led to Gatsby Recipes as a way to address the challenge of translating an idea -- “I want to do x” -- to how “x” is done in Gatsby. Recipes help users take the literally thousands of plugins and themes that the Gatsby open source ecosystem now offers, and apply them to accomplishing desired tasks in the CLI while also enabling them to automate the process. +This idea of “composable” websites eventually resulted in Gatsby Themes, plugins that include a `gatsby-config.js` file and add pre-configured functionality, data sourcing, and/or UI code to Gatsby sites. Essentially, modules that can be put together to form a single, holistic Gatsby site. Which in turn led to Gatsby Recipes as a way to address the challenge of translating an idea -- “I want to do x” -- to how “x” is done in Gatsby. Recipes help users take the literally thousands of plugins and themes that the Gatsby open source ecosystem now offers, and apply them to accomplishing desired tasks in the CLI while also enabling them to automate the process. Gatsby is a great tool for so very many diverse and creative projects and it has been a genuine thrill over the past five years to see what's been built with it. And how many people have been busy building: as of now, our repo shows there are 200k public Gatsby sites on GitHub. 200k / ( 365 days \* 5 years old) = 110 sites a day 🎉! -![screen shot of user count on gatsby github repository](https://lh6.googleusercontent.com/m_BAZRYXtxDgy4f4oxrtxMgtbGnIxlCpfXJUHS6oCoE_c1kTOslsjJFvJ1wKWkYjvWkwbIJuNBnNng78Z5je9se6KDleT5YEatR7N-0-NTB-VFLvfu3s-4CN7RTcIRMVZ6GOM55P) +![Screen shot of user count on Gatsby GitHub repository](https://lh6.googleusercontent.com/m_BAZRYXtxDgy4f4oxrtxMgtbGnIxlCpfXJUHS6oCoE_c1kTOslsjJFvJ1wKWkYjvWkwbIJuNBnNng78Z5je9se6KDleT5YEatR7N-0-NTB-VFLvfu3s-4CN7RTcIRMVZ6GOM55P) ## Many hands @@ -71,4 +71,4 @@ It’s truly exciting to look back to see how far we have come in the last five So no matter what happens over the next five years, there are things that will not alter. Gatsby the open source framework is always going to be open source. Always going to be free, always going to be supported, and always with the community as co-pilot. -_Ready to dive in for even more Gatsby goodness? Join us at our first-ever virtual Gatsby Days, two half days of speakers, demos, and All Things Gatsby coming up on June 2 & 3rd. Register now: https://www.gatsbyjs.com/virtual-gatsby-days-registration/_ +_Ready to dive in for even more Gatsby goodness? Join us at our first-ever Virtual Gatsby Days, two half days of speakers, demos, and All Things Gatsby coming up on June 2 & 3rd. Register now: https://www.gatsbyjs.com/virtual-gatsby-days-registration/_ diff --git a/docs/blog/2020-05-27-announcing-series-b-funding/index.md b/docs/blog/2020-05-27-announcing-series-b-funding/index.md index ac23a7f9a79ab..d0df2c2b23545 100644 --- a/docs/blog/2020-05-27-announcing-series-b-funding/index.md +++ b/docs/blog/2020-05-27-announcing-series-b-funding/index.md @@ -21,7 +21,7 @@ It's time for a new way to build the web. Gatsby was designed from the very beginning as a decoupled architecture for building websites by quickly and seamlessly gluing together modular best-fit services. Acting as the orchestration layer, Gatsby lets developers access the most productive and powerful technologies and practices currently available -- tools like Git, React, and GraphQL for hyper-efficient API-propelled data exchange to create websites and apps that can run anywhere. Gatsby sites are inherently secure (no servers and no database equals almost no attack surface), instantly scalable, and performant out of the box. -We're also revolutionizing the build process. Gatsby empowers front end developers to harness powerful methodologies like continuous deployment to build and iterate quickly, getting sites and features in front of users fast. Gatsby's open source framework is endlessly flexible and extensible, thanks to our enormous plugin ecosystem -- [over 2000 plugins](https://www.gatsbyjs.org/plugins/) and growing daily. Since Gatsby sites are faster to build and easier to change, experimentation becomes easy and low cost, opening the door to continuous innovation. +We're also revolutionizing the build process. Gatsby empowers front end developers to harness powerful methodologies like continuous deployment to build and iterate quickly, getting sites and features in front of users fast. Gatsby's open source framework is endlessly flexible and extensible, thanks to our enormous plugin ecosystem -- [over 2000 plugins](/plugins/) and growing daily. Since Gatsby sites are faster to build and easier to change, experimentation becomes easy and low cost, opening the door to continuous innovation. Our developer community is growing over 10 percent month-over-month, and over 200,000 sites on GitHub alone have been built with Gatsby. [Online academies like Udemy](https://www.techrepublic.com/article/top-5-workplace-learning-trends-in-2020/) are reporting that Gatsby is among the most popular emerging tech skills professionals are looking to learn. And devs are using these skills to build some seriously cool projects, both personal and professional. Visually driven sites like [Spotify.Design](https://spotify.design/) have come to Gatsby for blazing fast page loads on image-rich pages, while [Little Caesars](https://littlecaesars.com/), the third largest pizza delivery chain in the world, chose Gatsby to make sure hungry customers enjoy the fastest possible ordering experience. @@ -29,7 +29,7 @@ Our developer community is growing over 10 percent month-over-month, and over 20 From the start, Gatsby was designed for building sites and apps that would be fast no matter where they run. After five years of refining Gatsby's open source framework, that goal has largely been satisfied...though we will of course continue working to capture every last possible microsecond of performance gain while helping teams make smart performance decisions. -> Page speed performance is a key metric for us in delivering an unparalleled shopping experience. Using Gatsby has allowed us to increase our page performance by 5-10x -- an exponential improvement not only for our customers, but for our team too. -- **Jeff Gnatek, Head of engineering, Butcherbox** +> Page speed performance is a key metric for us in delivering an unparalleled shopping experience. Using Gatsby has allowed us to increase our page performance by 5-10x -- an exponential improvement not only for our customers, but for our team too. -- **Jeff Gnatek, Head of engineering, ButcherBox** To take these performance gains to the next level we launched [Gatsby Cloud](https://www.gatsbyjs.com/), specialized cloud infrastructure built for teams who want their Gatsby sites functioning at full potential. With features like real-time previews, seamless deployments, and parallelized builds, Gatsby Cloud grants serious velocity for both developers and content creators. @@ -51,15 +51,15 @@ We also just launched [Willit.build](https://willit.build/), a website providing **Easy administration** -Gatsby needs to be easy to use, no matter where you're starting from. Gatsby can do an incredible number of things thanks to an ecosystem of thousands of plugins and themes. With this incredible variety, though, comes the challenge of discovering how exactly to go about executing your choices. Gatsby's vast documentation can answer almost any question, and also we've already mapped out many of the workflows you can do with Gatsby. Now, what if you could just tell Gatsby what it is you want to do, and voilà! A few clicks later, Gatsby gets it all set up and running for you. We've [released an experimental version of this as Gatsby Recipes](https://www.gatsbyjs.org/blog/2020-04-15-announcing-gatsby-recipes/) -- a user-friendly infrastructure-as-code inspired approach we're developing with the community. +Gatsby needs to be easy to use, no matter where you're starting from. Gatsby can do an incredible number of things thanks to an ecosystem of thousands of plugins and themes. With this incredible variety, though, comes the challenge of discovering how exactly to go about executing your choices. Gatsby's vast documentation can answer almost any question, and also we've already mapped out many of the workflows you can do with Gatsby. Now, what if you could just tell Gatsby what it is you want to do, and voilà! A few clicks later, Gatsby gets it all set up and running for you. We've [released an experimental version of this as Gatsby Recipes](/blog/2020-04-15-announcing-gatsby-recipes/) -- a user-friendly infrastructure-as-code inspired approach we're developing with the community. No matter what that future looks like, though, we will also continue to double down on improving our developer experience for those already comfortable administering Gatsby from the command line. **Access for all** -Ultimately, we want to make Gatsby usable for everyone -- we want all Gatsby users to feel like [you belong here](https://www.gatsbyjs.org/docs/gatsby-core-philosophy/#you-belong-here). +Ultimately, we want to make Gatsby usable for everyone -- we want all Gatsby users to feel like [you belong here](/docs/gatsby-core-philosophy/#you-belong-here). -This includes things like providing [built-in support](https://www.gatsbyjs.org/docs/making-your-site-accessible/) for features like [accessible routing](https://www.gatsbyjs.org/blog/2020-02-10-accessible-client-side-routing-improvements/) and regularly sharing [best practices on accessibility](https://www.youtube.com/watch?v=qmcclQ7UPLk) with the community. It also means expanding our support for other languages through [localizing our documentation](https://www.gatsbyjs.org/contributing/translation/), an effort that now has over 340 contributors across 22 languages working together. +This includes things like providing [built-in support](/docs/making-your-site-accessible/) for features like [accessible routing](/blog/2020-02-10-accessible-client-side-routing-improvements/) and regularly sharing [best practices on accessibility](https://www.youtube.com/watch?v=qmcclQ7UPLk) with the community. It also means expanding our support for other languages through [localizing our documentation](/contributing/translation/), an effort that now has over 340 contributors across 22 languages working together. Making Gatsby available to everyone also means including users who aren't as comfortable on the command line or with code. That is why we are working towards a low-code (or even eventually no-code) approach to Gatsby, including exploring GUI-based features like a [Desktop](https://github.com/gatsbyjs/gatsby/issues/4201) app and other visual interfaces like [Admin](https://github.com/gatsbyjs/gatsby/pull/22713) and [Blocks UI](https://blocks-ui.com/). The possibilities of where we can take this are endless, and we're looking forward to working with the community to define what an equally eloquent and powerful low-code experience will look like for the web. @@ -69,19 +69,19 @@ One thing that remains unchanged since Day Zero is our commitment to open source - **Open-source staffing level.** We now have 22 full-time employees working on open-source code and documentation -- roughly ⅓ of our full-time staff and ½ of our engineering staff. -- **Continued development.** Since our Series A announcement, we've shipped [many](https://github.com/gatsbyjs/gatsby/pull/20729) [improvements](https://github.com/gatsbyjs/gatsby/pull/20102) to Gatsby, including [support for Incremental Builds](https://www.gatsbyjs.org/blog/2020-04-22-announcing-incremental-builds/) in Gatsby Cloud, [better offline support](https://twitter.com/gatsbyjs/status/1175063002015514626), [UI improvements to documentation](https://www.gatsbyjs.org/blog/2019-08-07-gazette-august/#learning), [structured logging](https://github.com/gatsbyjs/gatsby/pull/14973), [asset prefixing](https://www.gatsbyjs.org/docs/asset-prefix/), [schema rebuilding](https://github.com/gatsbyjs/gatsby/issues/18939), [accessibility improvements to routing](https://www.gatsbyjs.org/blog/2020-02-10-accessible-client-side-routing-improvements/), [improved screenreader support](https://github.com/gatsbyjs/gatsby/issues/5581#issuecomment-575752718), and more. +- **Continued development.** Since our Series A announcement, we've shipped [many](https://github.com/gatsbyjs/gatsby/pull/20729) [improvements](https://github.com/gatsbyjs/gatsby/pull/20102) to Gatsby, including [support for Incremental Builds](/blog/2020-04-22-announcing-incremental-builds/) in Gatsby Cloud, [better offline support](https://twitter.com/gatsbyjs/status/1175063002015514626), [UI improvements to documentation](/blog/2019-08-07-gazette-august/#learning), [structured logging](https://github.com/gatsbyjs/gatsby/pull/14973), [asset prefixing](/docs/asset-prefix/), [schema rebuilding](https://github.com/gatsbyjs/gatsby/issues/18939), [accessibility improvements to routing](/blog/2020-02-10-accessible-client-side-routing-improvements/), [improved screenreader support](https://github.com/gatsbyjs/gatsby/issues/5581#issuecomment-575752718), and more. - **Support the ecosystem.** We employ the lead maintainers of [MDX](https://mdxjs.com/), [WPGraphQL](https://www.wpgraphql.com/), and [GraphiQL](https://github.com/graphql/graphiql), so they can continue to work on key projects that benefit more than just Gatsby. In addition, we have an active [OpenCollective](https://opencollective.com/gatsbyjs) where we contribute to key open source projects we rely on. -- **Commercialization.** We're building a sustainable revenue base to [support our thriving open source community](https://www.gatsbyjs.org/blog/2020-02-11-founding-organizations/) by providing teams and enterprises purpose-built infrastructure for running their Gatsby sites with [Gatsby Cloud](https://gatsbyjs.com). +- **Commercialization.** We're building a sustainable revenue base to [support our thriving open source community](/blog/2020-02-11-founding-organizations/) by providing teams and enterprises purpose-built infrastructure for running their Gatsby sites with [Gatsby Cloud](https://gatsbyjs.com). - **Access.** Gatsby's open source framework will always be free. We also offer a permanent free tier on Gatsby Cloud for individuals. This guarantees community access to the best platform for building and deploying Gatsby sites. ## Let's build together -Community got us here. Gatsby's open source community has invested its endless creativity into creating plugins, Gatsby Themes, and new [Gatsby Recipes](https://www.gatsbyjs.org/docs/recipes/) to evolve and extend what's possible for devs to build with Gatsby. +Community got us here. Gatsby's open source community has invested its endless creativity into creating plugins, Gatsby Themes, and new [Gatsby Recipes](/docs/recipes/) to evolve and extend what's possible for devs to build with Gatsby. -At the same time, developers don't work alone: Creating and maintaining a website and its content is the work of many hands. Gatsby enables collaboration through an approach we call [the content mesh](https://www.gatsbyjs.org/blog/2018-10-04-journey-to-the-content-mesh/), so content creators, editors, designers and marketers can work with their  favorite tools. Gatsby's integrations with CMSs like WordPress, Contentful, and Drupal mean that developers can build modern websites while preserving their content creators' specialized workflows. +At the same time, developers don't work alone: Creating and maintaining a website and its content is the work of many hands. Gatsby enables collaboration through an approach we call [the content mesh](/blog/2018-10-04-journey-to-the-content-mesh/), so content creators, editors, designers and marketers can work with their  favorite tools. Gatsby's integrations with CMSs like WordPress, Contentful, and Drupal mean that developers can build modern websites while preserving their content creators' specialized workflows. The web is an incredible medium. Anyone, anywhere can produce a site and ship their ideas to the world. We're committed to making Gatsby the way to build on the web -- for everyone.. Security, performance, accessibility, and access to the tools and workflows you prefer should be the default for how the web is built, not afterthoughts. diff --git a/docs/blog/2020-05-29-gazette/index.md b/docs/blog/2020-05-29-gazette/index.md index 818787d5232b5..8a14e6dd43d62 100644 --- a/docs/blog/2020-05-29-gazette/index.md +++ b/docs/blog/2020-05-29-gazette/index.md @@ -19,7 +19,7 @@ In May we also announced our [series B round of funding round](/blog/2020-05-27- Your content editors can now enjoy “instant preview” with Strapi and Gatsby Cloud! If you're new to Strapi, it’s a JavaScript-based, open source CMS. and a great pair for Gatsby projects. The Gatsby starter the Strapi team made for this project is gorgeous 😍 . -![Strapi blog screenshot](/strapi-blog.png) +![Strapi blog screenshot](./strapi-blog.png) Give Strapi a try with [this step-by-step tutorial](/blog/2020-05-12-strapi-instant-content-preview-plugin/). @@ -27,7 +27,7 @@ Give Strapi a try with [this step-by-step tutorial](/blog/2020-05-12-strapi-inst The nice thing about running your project on Gatsby Cloud is that you can go to sleep, wake up, and your site builds have gotten faster without you having to do anything. We're like a CI/CD tooth fairy. -For example, AgilityCMS is [seeing 5 second builds](https://twitter.com/AgilityCMS/status/1257711270532452354) for their own 500-page website! How can this be? Some say it's [unicorn magic](https://twitter.com/3cordguy/status/1257079916434251780). +For example, Agility CMS is [seeing 5 second builds](https://twitter.com/AgilityCMS/status/1257711270532452354) for their own 500-page website! How can this be? Some say it's [unicorn magic](https://twitter.com/3cordguy/status/1257079916434251780). Again, you can take a peek at our build time benchmarks at [Will It Build](https://willit.build). @@ -39,7 +39,7 @@ Thanks to a [collaboration with the Chrome team](https://web.dev/granular-chunki How? By bundling a dependency that is used in at least 2 pages, Gatsby can chunk them together so you don't have to download duplicate libraries over and over again. -This won't benefit first-page load, but it improves page navigation as your site needs less Javascript for the next route. Gatsby projects like Ghost’s website saw a 35% reduction in the overall JavaScript they shipped to browsers. +This won't benefit first-page load, but it improves page navigation as your site needs less JavaScript for the next route. Gatsby projects like Ghost’s website saw a 35% reduction in the overall JavaScript they shipped to browsers. ### Faster, and Faster Configuration @@ -47,29 +47,29 @@ When we launched the alpha of Gatsby Recipes in April, it caused a stir in the W If you missed the initial launch, Paul Scanlon can bring you up-to-speed with ["Gatsby Recipes - What’s All the Fuss About?"](/blog/2020-05-21-gatsby-recipes/). Also, since the launch there’s been an avalanche of official and community made Recipes, including scripts for configuring: -- React libraries like[React Helmet](https://raw.githubusercontent.com/gatsbyjs/gatsby/master/packages/gatsby-recipes/recipes/gatsby-plugin-react-helmet.mdx) and [Preact](https://raw.githubusercontent.com/gatsbyjs/gatsby/master/packages/gatsby-recipes/recipes/preact.mdx) +- React libraries like [React Helmet](https://raw.githubusercontent.com/gatsbyjs/gatsby/master/packages/gatsby-recipes/recipes/gatsby-plugin-react-helmet.mdx) and [Preact](https://raw.githubusercontent.com/gatsbyjs/gatsby/master/packages/gatsby-recipes/recipes/preact.mdx) - Themes and Starters, like [gatsby-theme-blog](https://raw.githubusercontent.com/gatsbyjs/gatsby/master/packages/gatsby-recipes/recipes/gatsby-theme-blog.mdx) and [gatsby-theme-notes-starter](https://raw.githubusercontent.com/gatsbyjs/gatsby/master/packages/gatsby-recipes/recipes/gatsby-theme-notes.mdx) - Advanced configs, like [headless WordPress](https://raw.githubusercontent.com/gatsbyjs/gatsby/master/packages/gatsby-recipes/recipes/wordpress.mdx) and [Progressive WebApps](https://raw.githubusercontent.com/gatsbyjs/gatsby/master/packages/gatsby-recipes/recipes/pwa.mdx) -Learn how to develop your own Gatsby Recipes [here](https://github.com/gatsbyjs/gatsby/tree/master/packages/gatsby-recipes). And if you’re looking for ideas, I could really use a Recipe that spins up placeholder sites for all of the unused domains I purchased last year. And for all of the domains I’m going to purchase - and not use - this year. +Learn how to develop your own Gatsby Recipes from the [Gatsby Recipes README](https://github.com/gatsbyjs/gatsby/tree/master/packages/gatsby-recipes). And if you’re looking for ideas, I could really use a Recipe that spins up placeholder sites for all of the unused domains I purchased last year. And for all of the domains I’m going to purchase - and not use - this year. ### TypeScript Support Gatsby loves the TypeScript community. When you pass one of them, you know exactly what type of person you’re dealing with. -This month we made the Gatsby Typescript plugin part of core Gatsby, so you no longer need to install it to enable TypeScript support in your project. Read our [updated TypeScrip docs](/docs/typescript/) and the Pull Request that enacted this change(https://github.com/gatsbyjs/gatsby/pull/23547). Also [join the Twitter conversation](https://twitter.com/gatsbyjs/status/1258427651066400768). +This month we made the Gatsby TypeScript plugin part of core Gatsby, so you no longer need to install it to enable TypeScript support in your project. Read our [updated TypeScript docs](/docs/typescript/) and the Pull Request that enacted this change (https://github.com/gatsbyjs/gatsby/pull/23547). Also [join the Twitter conversation](https://twitter.com/gatsbyjs/status/1258427651066400768). ### GraphQL Tracing -In may we continued to improve our error messaging (see example [here](https://github.com/gatsbyjs/gatsby/pull/24186) and [here](https://github.com/gatsbyjs/gatsby/pull/23741)). But what about slow GraphQL queries? Well, Gatsby now supports performance tracing using the opentracing standard. You can to [enable tracing for GraphQL queries](/docs/performance-tracing/). This is useful because it allows you to debug why querying may be slow in your Gatsby project. +In may we continued to improve our error messaging (see example [here](https://github.com/gatsbyjs/gatsby/pull/24186) and [here](https://github.com/gatsbyjs/gatsby/pull/23741)). But what about slow GraphQL queries? Well, Gatsby now supports performance tracing using the OpenTracing standard. You can to [enable tracing for GraphQL queries](/docs/performance-tracing/). This is useful because it allows you to debug why querying may be slow in your Gatsby project. ## 👩‍🚀 New in the Gatsby Community ### Gatsby Days is June 2 - 3 -[Register to attend](https://www.gatsbyjs.com/resources/gatsby-days/) our first ever virtual Gatsby Days! +[Register to attend](https://www.gatsbyjs.com/resources/gatsby-days/) our first ever Virtual Gatsby Days! We have a superb [lineup of speakers](/blog/2020-05-13-virtual-gatsby-day-speakers/) from the Gatsby community. And you’ll hear from Gatsby co-founder Kyle Mathews about what’s coming next. @@ -107,13 +107,13 @@ And special thanks to our long time community member, **Horacio Herrera** for ma ### Gatsby Themes & Plugins -Many exciting Gatsby Themes and Plugins premiered in May. There was [Gatsby Theme Catalyst](https://www.gatsbyjs.org/blog/2020-05-14-introducing-gatsby-theme-catalyst/), Eric Howey exciting exploration in theme architecture. Aravind Balla [launched gatsby-theme-andy](https://twitter.com/aravindballa/status/1260878161920716804), an ambitious theme for power note-taking. And Trevor Harmon [dropped gatsby-theme-shopify-manager](https://thetrevorharmon.com/blog/introducing-gatsby-theme-shopify-manager), a living demonstration of the talk he delivered at Gatsby Days LA, [“Sell Things Fast With Gatsby and Shopify”](https://www.youtube.com/watch?v=tUtuGAFOjYI). +Many exciting Gatsby Themes and Plugins premiered in May. There was [Gatsby Theme Catalyst](/blog/2020-05-14-introducing-gatsby-theme-catalyst/), Eric Howey exciting exploration in theme architecture. Aravind Balla [launched gatsby-theme-andy](https://twitter.com/aravindballa/status/1260878161920716804), an ambitious theme for power note-taking. And Trevor Harmon [dropped gatsby-theme-shopify-manager](https://thetrevorharmon.com/blog/introducing-gatsby-theme-shopify-manager), a living demonstration of the talk he delivered at Gatsby Days LA, [“Sell Things Fast With Gatsby and Shopify”](https://www.youtube.com/watch?v=tUtuGAFOjYI). All of the Gatsby Themes above are worth using and studying to accelerate your own work! ### Azure Static Web Apps -Microsoft debuted [Azure Static Web Apps](https://azure.microsoft.com/en-us/services/app-service/static/) at the Build Conference, and we're excited to see provide first-class support for Gatsby projects. Follow along our new doc so you can [deploy your Gatsby site to Azure](https://www.gatsbyjs.org/docs/deploying-to-azure/). +Microsoft debuted [Azure Static Web Apps](https://azure.microsoft.com/en-us/services/app-service/static/) at the Build Conference, and we're excited to see provide first-class support for Gatsby projects. Follow along our new doc so you can [deploy your Gatsby site to Azure](/docs/deploying-to-azure/). ### GraphQL for WordPress is growing! diff --git a/docs/blog/2020-06-11-you-belong-here-commitment/index.md b/docs/blog/2020-06-11-you-belong-here-commitment/index.md new file mode 100644 index 0000000000000..76a4cd211fe64 --- /dev/null +++ b/docs/blog/2020-06-11-you-belong-here-commitment/index.md @@ -0,0 +1,46 @@ +--- +title: You Belong Here +date: 2020-06-11 +author: Bianca Feliciano Nedjar +excerpt: "This is a pivotal time for the fight against systemic racism and injustice in the US. It has also sparked a lot of difficult reflection and realizations from those of us who would be allies: the understanding that we all own a piece of this. That we can, and we must, do better. At Gatsby we have been asking ourselves some hard questions about how we need to change so we can become better allies." +tags: + - announcements + - diversity-and-inclusion + - community +--- + +A little more than two weeks ago, George Floyd was murdered. The days since then have marked a pivotal moment in the fight against systemic racism and injustice in the United States. We've witnessed a broad and representative cross-section of Americans take to the streets day after day in peaceful protest, demanding change. We are watching our communities turn pain into reflection and start to hold themselves responsible, asking how we got here and how we move forward. And we are awakening to wide recognition that we all own a piece of this -- that we can, and we must, do better. At Gatsby we have been asking ourselves some hard questions about how we need to change so we can become better allies. + +It is no secret that the tech industry is primarily white and male. As an industry built around innovation and disruption, tech has failed to do either when it comes to advancing equity. Our sector has failed to ensure fairness in hiring practices and career development for gender and racial/ethnic minorities, and all other underrepresented groups. At the root of this problem are conscious and unconscious biases deeply ingrained in our systems and culture. Implicit biases that reinforce privilege and cause us to fear rather than accept our differences. Until we recognize the power of those biases, until we begin the hard work of naming and deconstructing them to build genuine equity in the workplace, nothing will change. It is not enough to stand in solidarity with those who have been historically disenfranchised. We must now actively work to ensure equity, opportunity and advancement and remove any barriers blocking the way. But how best to do this? + +This is the conversation we are having at Gatsby. And it's not a new one. We are fortunate to be a community of knowledgeable and passionate individuals who have worked to raise matters of inequity and call for accountability both within and outside of our organization. But in reckoning with the pain of the Black community we have come face to face with the ways we have failed to be the allies we want to be.  By failing to actualize aggressive action within our our organization we have reinforced the inequality our team members experience outside of Gatsby. Worse, this failure diminishes the promise of psychological safety inherent in calling ourselves a community. + +We are ready to change from within, deeply and permanently. + +We don't have all the answers. In fact, we're still trying to ensure we are asking the right questions. What we do have right now, though, is humility. We have the humility to accept that we have fallen short of living our stated core value: You belong here. We have the humility to require more from ourselves and each other. And we have the humility to know that, even so, there are times we will falter or fail in that pursuit. Yet we are steadfast in our commitment to keep trying. + +So, where do we go from here? As we move forward we believe it is important to commit ourselves publicly to this work. + +## Our Commitment + +**We commit to inclusion:** To understanding and challenging our own biases so that we can create a community that promotes interpersonal risk-taking and protects everyone's ability to contribute meaningfully without fear of harm to their self image, status or career. + +- **We commit to bringing in the experts** and partnering with Diversity & Inclusion leaders to evaluate organizational needs. And then implement programming with the intent of deconstructing bias, facilitating meaningful conversations, and building the necessary skills to identify, address and correct exclusionary behaviors or inequitable practices in real time. + +- **We commit to creating safe spaces** for all team members to share and understand their experience, and empower each other to call for change when necessary, fostering psychological safety and creating a culture of feedback and candor. + +- **We commit to expanding our organizational identity** by incorporating and celebrating the culture and values of all Gatsbyites. + +- **We commit to evaluating policies** pertaining to compensation, performance reviews and career advancement to determine if there is disparate impact on the basis of gender, race/ethnicity, age, family status, mental health or other factors and taking action where needed. + +**We commit to diversity:** To building a community of individuals whose unique perspectives and skills enrich our collective identity and make us a more effective and powerful team. + +- **We commit to a data-driven assessment** of our full-cycle talent acquisition process. From job descriptions to compensation, we want to understand where we lose talent from underrepresented groups. + +- **We commit to making impactful changes** to our interviewing practices by experimenting with iterations of blind recruitment and the Rooney rule. We want to remove any and all obstacles to a fair and equitable recruitment process. + +- **We commit to refining our employer brand** to ensure that [our core values](https://www.gatsbyjs.org/docs/gatsby-core-philosophy/) are represented in every touchpoint in the recruitment process and that our approach is differentiated so that it speaks to the experiences of all identities. This will allow candidates to make the best decision for themselves when it comes to joining our team. + +To make these intentions are made visible both inside and outside of Gatsby, **we commit to building measurable objectives** by which to assess our progress in both diversity and inclusion so that we may hold ourselves accountable. And, finally, **we commit to periodically publishing the results** of these objectives to show the community what we are doing and continue to invite further conversations. + +This is in no way a final or finished statement, but rather the foundation of all the work to come. An initial step taken humbly in the hope that you will hold us accountable as we learn and grow in this process. We hope you join us in the journey. Because you belong here. diff --git a/docs/blog/author.yaml b/docs/blog/author.yaml index 520e1c9616754..483ee6368200d 100644 --- a/docs/blog/author.yaml +++ b/docs/blog/author.yaml @@ -430,3 +430,6 @@ bio: "Dad all the time, mental health therapist full time, web developer in my spare time. I listen and care." avatar: avatars/eric-howey.jpg twitter: "@erchwy" +- id: Bianca Feliciano Nedjar + bio: "Director of Employee Engagement and Development at Gatsby; Likes consuming mass quantities of television and film, dining al fresco and Reddit." + avatar: avatars/bianca-nedjar.jpg diff --git a/docs/blog/avatars/bianca-nedjar.jpg b/docs/blog/avatars/bianca-nedjar.jpg new file mode 100644 index 0000000000000..2522cabe9a99c Binary files /dev/null and b/docs/blog/avatars/bianca-nedjar.jpg differ diff --git a/docs/blog/gatsbygram-case-study/index.md b/docs/blog/gatsbygram-case-study/index.md index 4918955675c06..52de43cbbda8e 100644 --- a/docs/blog/gatsbygram-case-study/index.md +++ b/docs/blog/gatsbygram-case-study/index.md @@ -553,8 +553,8 @@ npm run develop While writing this post I scraped a few accounts and published their resulting "Gatsbygram" sites: -- https://iceland-gatsbygram.netlify.com -- https://tinyhouses-gatsbygram.netlify.com +- https://iceland-gatsbygram.netlify.app +- https://tinyhouses-gatsbygram.netlify.app _With thanks to Sam Bhagwatt, Sunil Pai, Nolan Lawson, Nik Graf, Jeff Posnick, and Addy Osmani for their reviews._ diff --git a/docs/docs/ab-testing-with-google-analytics-and-netlify.md b/docs/docs/ab-testing-with-google-analytics-and-netlify.md index b78c2ae6de88c..3d31ee70196af 100644 --- a/docs/docs/ab-testing-with-google-analytics-and-netlify.md +++ b/docs/docs/ab-testing-with-google-analytics-and-netlify.md @@ -6,7 +6,7 @@ Learn how to create an A/B test (otherwise known as a split test) with Google An ## Creating an A/B test with Netlify -An A/B test compares changes on a web page. If you are creating an A/B test with Netlify, you can [use multiple Git branches containing variations of your site](https://docs.netlify.com/site-deploys/split-testing/#run-a-branch-based-test). If you are not familiar with Git branches, visit the [Git Guide](http://rogerdudler.github.io/git-guide/), which explains Git in detail. +An A/B test compares changes on a web page. If you are creating an A/B test with Netlify, you can [use multiple Git branches containing variations of your site](https://docs.netlify.com/site-deploys/split-testing/#run-a-branch-based-test). If you are not familiar with Git branches, visit the [Git Guide](https://rogerdudler.github.io/git-guide/), which explains Git in detail. Let’s say you read on Twitter that users spend more time on webpages with blue headers. You have a hunch that this might be correct, but you want some data to verify this claim. diff --git a/docs/docs/adding-page-transitions-with-plugin-transition-link.md b/docs/docs/adding-page-transitions-with-plugin-transition-link.md index 71a7ccefe1dfc..7f4be77523508 100644 --- a/docs/docs/adding-page-transitions-with-plugin-transition-link.md +++ b/docs/docs/adding-page-transitions-with-plugin-transition-link.md @@ -38,7 +38,7 @@ import TransitionLink from "gatsby-plugin-transition-link" ## Predefined transitions -You can use the `AniLink` component to add page transitions without having to define your own custom transitions. It's a wrapper around `TransitionLink` that provides 4 predefined transitions: `fade`, `swipe`, `cover`, and `paintDrip`. You can preview them at [this demo site](https://gatsby-plugin-transition-link.netlify.com/). +You can use the `AniLink` component to add page transitions without having to define your own custom transitions. It's a wrapper around `TransitionLink` that provides 4 predefined transitions: `fade`, `swipe`, `cover`, and `paintDrip`. You can preview them at [this demo site](https://gatsby-plugin-transition-link.netlify.app/). To use AniLink, you will need to install the `gsap` animation library: @@ -165,6 +165,6 @@ As always, check out [the installation docs](https://transitionlink.tylerbarnes. - [Official documentation](https://transitionlink.tylerbarnes.ca/docs/) - [Source code for plugin](https://github.com/TylerBarnes/gatsby-plugin-transition-link) -- [Demo site](https://gatsby-plugin-transition-link.netlify.com/) +- [Demo site](https://gatsby-plugin-transition-link.netlify.app/) - [Blog post: 'Per-Link Gatsby page transitions with TransitionLink'](/blog/2018-12-04-per-link-gatsby-page-transitions-with-transitionlink/) - [Using transition-link with react-spring](https://github.com/TylerBarnes/gatsby-plugin-transition-link/issues/34) diff --git a/docs/docs/adding-pagination.md b/docs/docs/adding-pagination.md index deaf68bbfef6d..8fbb6df1c47aa 100644 --- a/docs/docs/adding-pagination.md +++ b/docs/docs/adding-pagination.md @@ -128,6 +128,6 @@ The path for the first page is `/blog`, following pages will have a path of the ## Other resources -- Follow this [step-by-step tutorial](https://nickymeuleman.netlify.com/blog/gatsby-pagination/) to add links to the previous/next page and the traditional page-navigation at the bottom of the page +- Follow this [step-by-step tutorial](https://nickymeuleman.netlify.app/blog/gatsby-pagination/) to add links to the previous/next page and the traditional page-navigation at the bottom of the page - See [gatsby-paginated-blog](https://github.com/NickyMeuleman/gatsby-paginated-blog) [(demo)](https://nickymeuleman.github.io/gatsby-paginated-blog/) for an extension of the official [gatsby-starter-blog](https://github.com/gatsbyjs/gatsby-starter-blog) with pagination in place diff --git a/docs/docs/audit-with-lighthouse.md b/docs/docs/audit-with-lighthouse.md index d592c91373614..2b2b56b43e821 100644 --- a/docs/docs/audit-with-lighthouse.md +++ b/docs/docs/audit-with-lighthouse.md @@ -32,13 +32,13 @@ Once this starts, you can now view your site at `http://localhost:9000`. Now run your first Lighthouse test. -1. Open the site in Chrome (if you didn't already do so) and then open up the Chrome DevTools. +1. Open the site in Chrome (if you didn't already do so) and then open up the Chrome DevTools. (Lighthouse is also available for Firefox from [Firefox Add-ons](https://addons.mozilla.org/en-GB/firefox/addon/google-lighthouse/). ) -2. Click on the "Audits" tab where you'll see a screen that looks like: +2. Click on the "Audits" tab, this may be a "Lighthouse" tab depending on which version you are using. You should see a screen that looks like: ![Lighthouse audit start](./images/lighthouse-audit.png) -3. Click "Perform an audit..." (All available audit types should be selected by default). Then click "Run audit". (It'll then take a minute or so to run the audit). Once the audit is complete, you should see results that look like this: +3. Choose whether to audit on Mobile or Desktop and then click "Generate Report". You will also see a list of all available audits that you can choose to run for this report. Once the audit starts it'll take around a minute depending on the site speed and which audits were selected. When that is complete, you should see results that look like this: ![Lighthouse audit results](./images/lighthouse-audit-results.png) diff --git a/docs/docs/building-a-contact-form.md b/docs/docs/building-a-contact-form.md index 0e786ced61cb0..02ec86aac77cc 100644 --- a/docs/docs/building-a-contact-form.md +++ b/docs/docs/building-a-contact-form.md @@ -78,8 +78,9 @@ Setting this up only involves adding a few form attributes: ```diff:title=src/pages/contact.js -
-+ ++ + ++ ... ``` diff --git a/docs/docs/building-a-site-with-authentication.md b/docs/docs/building-a-site-with-authentication.md index aa3d6cafd8cb7..a21d2d0276ebf 100644 --- a/docs/docs/building-a-site-with-authentication.md +++ b/docs/docs/building-a-site-with-authentication.md @@ -110,7 +110,7 @@ If you want more information about authenticated areas with Gatsby, this (non-ex - [Making a site with user authentication](/tutorial/authentication-tutorial), an advanced Gatsby tutorial - [Gatsby repo "simple auth" example](https://github.com/gatsbyjs/gatsby/tree/master/examples/simple-auth) -- [Live version of the "simple auth" example](https://simple-auth.netlify.com/) +- [Live version of the "simple auth" example](https://simple-auth.netlify.app/) - [A Gatsby email _application_](https://github.com/DSchau/gatsby-mail), using React Context API to handle authentication - [Add Authentication to your Gatsby apps with Auth0](/blog/2019-03-21-add-auth0-to-gatsby-livestream/) (livestream with Jason Lengstorf) - [Add Authentication to your Gatsby apps with Okta](https://www.youtube.com/watch?v=7b1iKuFWVSw&t=9s) diff --git a/docs/docs/client-only-routes-and-user-authentication.md b/docs/docs/client-only-routes-and-user-authentication.md index 748e690e7693d..670a6f4155ac5 100644 --- a/docs/docs/client-only-routes-and-user-authentication.md +++ b/docs/docs/client-only-routes-and-user-authentication.md @@ -157,5 +157,5 @@ One result of this method is that the client is completely unaware of the logic ## Additional resources - [Gatsby repo "simple auth" example](https://github.com/gatsbyjs/gatsby/blob/master/examples/simple-auth/) - a demo implementing user authentication and restricted client-only routes -- [Live version of the "simple auth" example](https://simple-auth.netlify.com/) +- [Live version of the "simple auth" example](https://simple-auth.netlify.app/) - [The Gatsby store](https://github.com/gatsbyjs/store.gatsbyjs.org) which also implements an authenticated flow diff --git a/docs/docs/data-fetching.md b/docs/docs/data-fetching.md index aaface2e71294..8b0c5154732f1 100644 --- a/docs/docs/data-fetching.md +++ b/docs/docs/data-fetching.md @@ -19,7 +19,7 @@ Compiling pages at build time is useful when your website content won't change o ## Combining build time and client runtime data -To illustrate a combination of build time and client runtime data, this guide uses code from a [small example site](https://gatsby-data-fetching.netlify.com). It uses the [`gatsby-source-graphql`](/packages/gatsby-source-graphql/) plugin to fetch data from GitHub's GraphQL API at build time for static content like the name and URL to a repository, and the [`fetch` API](https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API) to retrieve more dynamic data from the GitHub API on the [client-side](/docs/glossary#client-side) like star counts when the page loads in the browser. +To illustrate a combination of build time and client runtime data, this guide uses code from a [small example site](https://gatsby-data-fetching.netlify.app). It uses the [`gatsby-source-graphql`](/packages/gatsby-source-graphql/) plugin to fetch data from GitHub's GraphQL API at build time for static content like the name and URL to a repository, and the [`fetch` API](https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API) to retrieve more dynamic data from the GitHub API on the [client-side](/docs/glossary#client-side) like star counts when the page loads in the browser. Reasons to fetch certain data at build time vs. client runtime will vary, but in this example the repo's name and URL are much less likely to change between builds of the site. The repo's star counts, on the other hand, are likely to change often and would benefit from a client-side request to the GitHub API to stay current between static site builds. > Check out the code from the [full example here](https://github.com/gatsbyjs/gatsby/tree/master/examples/data-fetching). @@ -216,7 +216,7 @@ The repo's star count is fetched at runtime; if you refresh the page, this numbe You may be interested in other projects (both used in production and proof-of-concepts) that illustrate this usage: -- [Live example](https://gatsby-data-fetching.netlify.com) of the code used in this guide +- [Live example](https://gatsby-data-fetching.netlify.app) of the code used in this guide - [Gatsby store](https://github.com/gatsbyjs/store.gatsbyjs.org): with static product pages at build time and client-side interactions for e-commerce features - [Gatsby mail](https://github.com/DSchau/gatsby-mail): a client-side email application - [Example repo fetching data using Apollo](https://github.com/jlengstorf/gatsby-with-apollo) diff --git a/docs/docs/deploying-to-azure.md b/docs/docs/deploying-to-azure.md index 9691812777d73..1acb81b1843c5 100644 --- a/docs/docs/deploying-to-azure.md +++ b/docs/docs/deploying-to-azure.md @@ -4,7 +4,7 @@ title: Deploying to Azure This guide walks through how to deploy and host your next Gatsby site on Azure. -Azure is a great option for deploying Gatsby sites. Azure is a large cloud platform with hundreds of services working together to give you serverless, databases, AI, and static web site hosting. The Azure Static Web Apps service is meant to be used with static web sites. It provides features like hosting, [CDN](/docs/glossary/content-delivery-network/), authentication/authorization, [continuous deployment](/docs/glossary/continuous-deployment/) with Git-triggered builds, HTTPS, the ability to add a serverless API, and much more. +Azure is a great option for deploying Gatsby sites. Azure is a large cloud platform with hundreds of services working together to give you serverless, databases, AI, and static website hosting. The Azure Static Web Apps service is meant to be used with static websites. It provides features like hosting, [CDN](/docs/glossary/content-delivery-network/), authentication/authorization, [continuous deployment](/docs/glossary/continuous-deployment/) with Git-triggered builds, HTTPS, the ability to add a serverless API, and much more. ## Prerequisites @@ -20,7 +20,7 @@ Azure Static Web Apps service currently supports GitHub. In order to use the Azu `git init`. 2. Next, create a file called `.gitignore` in the root of your project and give it the following content: - ```bash + ```text node_modules build ``` @@ -29,7 +29,7 @@ Azure Static Web Apps service currently supports GitHub. In order to use the Azu 3. Finally, add the change and commit it. - ```bash + ```shell git add . git commit -m "adding Gatsby project" ``` @@ -44,7 +44,7 @@ Azure Static Web Apps service currently supports GitHub. In order to use the Azu 4. Finally, add your GitHub repository as a remote and push. Type the following commands to accomplish that (replacing `` with your GitHub user name): - ```bash + ```shell git remote add origin https://github.com//gatsby-app.git git push -u origin master ``` diff --git a/docs/docs/deploying-to-surge.md b/docs/docs/deploying-to-surge.md index dc1cd755b3154..c4d4e525503ed 100644 --- a/docs/docs/deploying-to-surge.md +++ b/docs/docs/deploying-to-surge.md @@ -44,7 +44,7 @@ You're done! Your terminal will output the address of the domain where your site ## Step 4: Bonus - Remembering a domain -To ensure future deploys are sent to the same location, you can store the domain name in a [`CNAME`](https://surge.sh/help/remembering-a-domain) file that is added your project. First, create a [`static` directory](https://www.gatsbyjs.org/docs/static-folder/) at the root of your Gatsby project if it doesn't already exist. Then put a file named `CNAME` (no file extension) in the `static` directory. +To ensure future deploys are sent to the same location, you can store the domain name in a [`CNAME`](https://surge.sh/help/remembering-a-domain) file that is added your project. First, create a [`static` directory](/docs/static-folder/) at the root of your Gatsby project if it doesn't already exist. Then put a file named `CNAME` (no file extension) in the `static` directory. Assuming your site was deployed to `https://my-cool-domain.surge.sh`, the following command will add the file for you: diff --git a/docs/docs/deploying-to-vercel.md b/docs/docs/deploying-to-vercel.md index 27408e677cf91..01bb71cf09fac 100644 --- a/docs/docs/deploying-to-vercel.md +++ b/docs/docs/deploying-to-vercel.md @@ -28,4 +28,4 @@ Your site will now deploy, and you will receive a link similar to the following: ## References: -- [Example Project](https://github.com/zeit/now/tree/master/examples/gatsby) +- [Example Project](https://github.com/vercel/vercel/tree/master/examples/gatsby) diff --git a/docs/docs/glossary/jamstack.md b/docs/docs/glossary/jamstack.md index 8082b01f474b4..09a76cf06c747 100644 --- a/docs/docs/glossary/jamstack.md +++ b/docs/docs/glossary/jamstack.md @@ -21,7 +21,7 @@ A JAMStack backend is a content API that returns JSON or XML. This API can be a ### Advantages of a JAMStack architecture -JAMStack sites, such as those created with Gatsby, offer four key advantages over other web site architectures. +JAMStack sites, such as those created with Gatsby, offer four key advantages over other website architectures. - **Speed**: JAMStack sites lack the overhead caused by software and database layers. As a result, they render and load more quickly than sites that use monolithic architectures. - **Hosting flexibility**: Because they're static files, JAMStack sites can be hosted anywhere. You can use traditional web server software, such as Apache or Nginx. For the best performance and security, you can use an object storage service and content delivery network such as [Netlify](/docs/deploying-to-netlify), [Render](/docs/deploying-to-render), or Amazon Web Services' [S3 and Cloudfront](/docs/deploying-to-s3-cloudfront). diff --git a/docs/docs/glossary/node.md b/docs/docs/glossary/node.md index ba5d75e5a7985..b7368d6e74557 100644 --- a/docs/docs/glossary/node.md +++ b/docs/docs/glossary/node.md @@ -25,10 +25,10 @@ You'll use npm to install Gatsby and its dependencies. Type `npm install -g gats ## Learn more about Node.js -- [Node.js](https://nodejs.org/en/) official web site +- [Node.js](https://nodejs.org/en/) official website - [Introduction to Node.js](https://nodejs.dev) - [NodeSchool](https://nodeschool.io/) offers online and in-person Node.js workshops -- [V8](https://v8.dev/) developer blog web site +- [V8](https://v8.dev/) developer blog website diff --git a/docs/docs/glossary/progressive-enhancement.md b/docs/docs/glossary/progressive-enhancement.md index 583305b29545d..b2b285836157a 100644 --- a/docs/docs/glossary/progressive-enhancement.md +++ b/docs/docs/glossary/progressive-enhancement.md @@ -7,7 +7,7 @@ Learn what _progressive enhancement_ is and how Gatsby builds sites using progre ## What is progressive enhancement? -_Progressive enhancement_ is a strategy for building web sites in which core functionality is available to all browsers, while non-critical enhancements are available to capable browsers. For example, a progressively-enhanced form submission might trigger a `fetch` network request in browsers that support the Fetch API, and a traditional form submission with a full page reload in browsers that do not. +_Progressive enhancement_ is a strategy for building websites in which core functionality is available to all browsers, while non-critical enhancements are available to capable browsers. For example, a progressively-enhanced form submission might trigger a `fetch` network request in browsers that support the Fetch API, and a traditional form submission with a full page reload in browsers that do not. Progressive enhancement can also ensure that your site is usable even if JavaScript fails to load. Poor network conditions, firewalls, and some browser settings can prevent JavaScript from executing. If your site relies entirely on JavaScript and client-side rendering, visitors may see a blank screen while waiting for JavaScript to load. @@ -19,7 +19,7 @@ Gatsby uses [server-side rendering](/docs/glossary/server-side-rendering/) and a When a site visitor requests their first URL from your site, the initial response will be server-rendered HTML, along with linked JavaScript, CSS, and images. If their browser is capable, React will hydrate the DOM, adding event listeners and state. Subsequent URL requests become DOM updates managed by React. If hydration fails, however, your site still works. Subsequent URL requests will instead trigger a network request and a full-page load. -Gatsby helps you build blazing-fast web sites and applications that work with the latest browsers, without excluding older ones. +Gatsby helps you build blazing-fast websites and applications that work with the latest browsers, without excluding older ones. ### Learn more diff --git a/docs/docs/glossary/react.md b/docs/docs/glossary/react.md index 1315b9afb8a72..1c144ea65f996 100644 --- a/docs/docs/glossary/react.md +++ b/docs/docs/glossary/react.md @@ -11,7 +11,7 @@ React is a code library for building web-based user interfaces. It's written usi Facebook first released React in 2013. The company still maintains the project, along with a community of contributors. It's free to use and open source under the terms of the [MIT License](https://github.com/facebook/react/blob/master/LICENSE). -Where publishing tools such as WordPress and Jekyll rely on a system of template files to create a UI, React uses [components](/docs/glossary#component). Components are contained chunks of JavaScript, CSS, and HTML or SVG that can be reused, shared, and combined to create a web site or application. +Where publishing tools such as WordPress and Jekyll rely on a system of template files to create a UI, React uses [components](/docs/glossary#component). Components are contained chunks of JavaScript, CSS, and HTML or SVG that can be reused, shared, and combined to create a website or application. Components may be purely presentational. For example, you might create a `Logo` component that's just an SVG image. Or a component may encapsulate functionality. An `InputBox` component might include an input control, a label, and some simple validation. @@ -19,8 +19,8 @@ Components are also _composable_, which is a fancy way of saying that you can us React components respond to changes in _state_. In React, _state_ is a set of properties and values that determine how a component looks or behaves. State can change in response to user activity, such as a click or key press. State can also change as the result of a completed network request. When a value in a component's state changes, the component is the only part of the UI that changes. In other words, React can update part of a page or an entire view without requiring a full page reload. -Gatsby bundles React, [webpack](/docs/glossary#webpack), [GraphQL](/docs/glossary#graphql), and other tools into a single framework for building web sites. With Gatsby, you get a head start on meeting your SEO, accessibility, and performance requirements. Rather than installing and configuring a development environment from scratch, you can install Gatsby and start building. +Gatsby bundles React, [webpack](/docs/glossary#webpack), [GraphQL](/docs/glossary#graphql), and other tools into a single framework for building websites. With Gatsby, you get a head start on meeting your SEO, accessibility, and performance requirements. Rather than installing and configuring a development environment from scratch, you can install Gatsby and start building. ### Learn more about React -- [React](https://reactjs.org/) Official web site +- [React](https://reactjs.org/) Official website diff --git a/docs/docs/glossary/server-side-rendering.md b/docs/docs/glossary/server-side-rendering.md index cec3ebc0e5169..6eed248baea70 100644 --- a/docs/docs/glossary/server-side-rendering.md +++ b/docs/docs/glossary/server-side-rendering.md @@ -3,7 +3,7 @@ title: Server Side Rendering disableTableOfContents: true --- -Learn what server side rendering is and why it's preferable to client-side (browser) rendering. You'll also learn how Gatsby uses server-side rendering to create static web sites. +Learn what server side rendering is and why it's preferable to client-side (browser) rendering. You'll also learn how Gatsby uses server-side rendering to create static websites. ## What is Server-Side rendering? diff --git a/docs/docs/glossary/static-site-generator.md b/docs/docs/glossary/static-site-generator.md index 5f1a3c28ae7ee..20f064b2f6834 100644 --- a/docs/docs/glossary/static-site-generator.md +++ b/docs/docs/glossary/static-site-generator.md @@ -15,7 +15,7 @@ Static site generators, on the other hand, generate HTML pages during a [build]( > Note: It's also possible to use Gatsby [without GraphQL](/docs/using-gatsby-without-graphql/), using the `createPages` API. -You can also use static site generators to create [JAMStack](/docs/glossary/#jamstack) sites. JAMStack is a modern web site architecture that uses JavaScript, content APIs, and markup. Gatsby, for example, can use the [WordPress REST API](/docs/sourcing-from-wordpress/) as a data source. +You can also use static site generators to create [JAMStack](/docs/glossary/#jamstack) sites. JAMStack is a modern website architecture that uses JavaScript, content APIs, and markup. Gatsby, for example, can use the [WordPress REST API](/docs/sourcing-from-wordpress/) as a data source. ### Advantages of static site generators diff --git a/docs/docs/glossary/webpack.md b/docs/docs/glossary/webpack.md index dc65033b17ca6..9d95fc6bf9453 100644 --- a/docs/docs/glossary/webpack.md +++ b/docs/docs/glossary/webpack.md @@ -3,7 +3,7 @@ title: webpack disableTableOfContents: true --- -Learn what webpack is, how it works, and how Gatsby uses it to accelerate web site development. +Learn what webpack is, how it works, and how Gatsby uses it to accelerate website development. ## What is webpack? diff --git a/docs/docs/headless-cms.md b/docs/docs/headless-cms.md index a4f6d7a549266..8b31a4ecc709d 100644 --- a/docs/docs/headless-cms.md +++ b/docs/docs/headless-cms.md @@ -48,6 +48,7 @@ Here are more resources for guides, plugins, and starters for CMS systems you ca | [Gentics Mesh](https://getmesh.io) | [guide](/docs/sourcing-from-gentics-mesh) | | | | [Seams-CMS](https://seams-cms.com/) | [guide](/docs/sourcing-from-seams-cms) | | | | [Builder.io](https://www.builder.io/) | [guide](/docs/sourcing-from-builder-io/) | [docs](/packages/@builder.io/gatsby/) | [starter](https://github.com/BuilderIO/gatsby-starter-builder) | +| [Flotiq](https://flotiq.com/) | [guide](/docs/sourcing-from-flotiq/) | [docs](/packages/gatsby-source-flotiq) | [starter](https://github.com/flotiq/gatsby-starter-blog) | ## How to add new guides to this section diff --git a/docs/docs/how-gatsby-works-with-github-pages.md b/docs/docs/how-gatsby-works-with-github-pages.md index e6dc627d52bd0..17cf7b2a435bf 100644 --- a/docs/docs/how-gatsby-works-with-github-pages.md +++ b/docs/docs/how-gatsby-works-with-github-pages.md @@ -62,6 +62,14 @@ When you run `npm run deploy` all contents of the `public` folder will be moved For a repository named like `username.github.io`, you don't need to specify `pathPrefix` and your website needs to be pushed to the `master` branch. +> :warning: Keep in mind that GitHub Pages forces deployment of user/organization pages to the `master` branch. So if you use `master` for development you need to do one of these: +> +> - Change the default branch from `master` to something else, and use `master` as a site deployment directory only: +> 1. To create a new branch called `source` run this command: +> `git checkout -b source master` +> 2. Change the default branch in your repository settings ("Branches" menu item) from `master` to `source` +> - Have a separate repository for your source code (so `username.github.io` is used only for deployment and not really for tracking your source code) + ```json:title=package.json { "scripts": { diff --git a/docs/docs/images/lighthouse-audit-results.png b/docs/docs/images/lighthouse-audit-results.png index fcac46065117d..e78ea8a6341dc 100644 Binary files a/docs/docs/images/lighthouse-audit-results.png and b/docs/docs/images/lighthouse-audit-results.png differ diff --git a/docs/docs/images/lighthouse-audit.png b/docs/docs/images/lighthouse-audit.png index bd07b84ad2ce0..57e2903347ff9 100644 Binary files a/docs/docs/images/lighthouse-audit.png and b/docs/docs/images/lighthouse-audit.png differ diff --git a/docs/docs/localization-i18n.md b/docs/docs/localization-i18n.md index fd10f18dff519..22d2400d565f2 100644 --- a/docs/docs/localization-i18n.md +++ b/docs/docs/localization-i18n.md @@ -50,4 +50,4 @@ This framework also has experimental support for the React suspense API and it s - [Gatsby i18n articles](https://www.gatsbyjs.org/blog/tags/i-18-n/) -- [W3C's i18n resources](http://w3c.github.io/i18n-drafts/getting-started/contentdev.en#reference) +- [W3C's i18n resources](https://w3c.github.io/i18n-drafts/getting-started/contentdev.en#reference) diff --git a/docs/docs/node-apis.md b/docs/docs/node-apis.md index 5944dc894b30d..ea951b5e2c323 100644 --- a/docs/docs/node-apis.md +++ b/docs/docs/node-apis.md @@ -9,9 +9,15 @@ Gatsby gives plugins and site builders many APIs for controlling your site's dat ## Async plugins -If your plugin performs async operations (disk I/O, database access, calling remote APIs, etc.) you must either return a promise or use the callback passed to the 3rd argument. Gatsby needs to know when plugins are finished as some APIs, to work correctly, require previous APIs to be complete first. See [Debugging Async Lifecycles](/docs/debugging-async-lifecycles/) for more info. +If your plugin performs async operations (disk I/O, database access, calling remote APIs, etc.) you must either return a promise (explicitly using `Promise` API or implicitly using `async`/`await` syntax) or use the callback passed to the 3rd argument. Gatsby needs to know when plugins are finished as some APIs, to work correctly, require previous APIs to be complete first. See [Debugging Async Lifecycles](/docs/debugging-async-lifecycles/) for more info. ```javascript +// Async/await +exports.createPages = async () => { + // do async work + const result = await fetchExternalData() +} + // Promise API exports.createPages = () => { return new Promise((resolve, reject) => { @@ -21,7 +27,7 @@ exports.createPages = () => { // Callback API exports.createPages = (_, pluginOptions, cb) => { - // do Async work + // do async work cb() } ``` diff --git a/docs/docs/prpl-pattern.md b/docs/docs/prpl-pattern.md index ebe58a65eb767..8b1124e420840 100644 --- a/docs/docs/prpl-pattern.md +++ b/docs/docs/prpl-pattern.md @@ -4,7 +4,7 @@ title: PRPL Pattern ## What is PRPL? -PRPL is a web site architecture developed by Google for building websites and +PRPL is a website architecture developed by Google for building websites and apps that work exceptionally well on smartphones and other devices with unreliable network connections. diff --git a/docs/docs/recipes/gitlab-continuous-integration.md b/docs/docs/recipes/gitlab-continuous-integration.md index ff36f5eba5695..9bfeac8b4fab5 100644 --- a/docs/docs/recipes/gitlab-continuous-integration.md +++ b/docs/docs/recipes/gitlab-continuous-integration.md @@ -23,7 +23,7 @@ gatsby new {your-project-name} ```shell cd {your-project-name} -yarn develop +gatsby develop ``` 3. Stop your development server (`Ctrl + C` on your command line in most cases) diff --git a/docs/docs/recipes/querying-data.md b/docs/docs/recipes/querying-data.md index 97bda661731f8..4c3bbda66a9ea 100644 --- a/docs/docs/recipes/querying-data.md +++ b/docs/docs/recipes/querying-data.md @@ -482,4 +482,4 @@ export default IndexPage ### Additional resources - Guide on [client-data fetching](/docs/data-fetching/) -- Live [example site](https://gatsby-data-fetching.netlify.com/) using this example +- Live [example site](https://gatsby-data-fetching.netlify.app/) using this example diff --git a/docs/docs/seo.md b/docs/docs/seo.md index 22b158447b3c8..b6bedab313ed7 100644 --- a/docs/docs/seo.md +++ b/docs/docs/seo.md @@ -48,22 +48,26 @@ Some examples using react-helmet: Google uses structured data that it finds on the web to understand the content of the page, as well as to gather information about the web and the world in general. -For example, here is a structured data snippet in the [JSON-LD format](https://developers.google.com/search/docs/guides/intro-structured-data) (JavaScript Object Notation for Linked Data) that might appear on the contact page of a company called Spooky Technologies, describing their contact information: +For example, here is a structured data snippet (added with `react-helmet`) in the [JSON-LD format](https://developers.google.com/search/docs/guides/intro-structured-data) (JavaScript Object Notation for Linked Data), that might appear on the contact page of a company called Spooky Technologies, describing their contact information: ```html - + + + ``` When using structured data, you'll need to test during development and the [Structured Data Testing Tool](https://search.google.com/structured-data/testing-tool) from Google is one recommended method. diff --git a/docs/docs/sourcing-from-flotiq.md b/docs/docs/sourcing-from-flotiq.md new file mode 100644 index 0000000000000..2997d28482966 --- /dev/null +++ b/docs/docs/sourcing-from-flotiq.md @@ -0,0 +1,252 @@ +--- +title: Sourcing from Flotiq +--- + +This guide will help you understand how to set up Gatsby to pull data from [Flotiq](https://flotiq.com). + +Flotiq is a headless CMS with a primary focus on developer experience and integration capabilities. Flotiq's cloud-based dashboard allows you to easily design your content types and work with your data, but Flotiq also provides support for powerful integrations. One of Flotiq's key principles is to provide an effortless way to consume your content in the applications you build. It's solved by supporting technologies like OpenAPI 3.0 or Zapier as well as by providing customized API docs and SDK libraries based on your content types. + +Using a website generator like Gatsby to consume content stored in Flotiq is one of the most frequent use cases. The integration is enabled by the [gatsby-source-flotiq](https://github.com/flotiq/gatsby-source-flotiq) source plugin, which bridges the dynamic REST API of your Flotiq account with Gatsby's GraphQL. + +> This guide will reference the [gatsby-starter-blog](https://github.com/flotiq/gatsby-starter-blog) blog starter, but remember to check out the more advanced starters prepared to work with Flotiq: +> +> - [Recipe website Gatsby starter](https://github.com/flotiq/gatsby-starter-recipes) +> - [Event calendar Gatsby starter](https://github.com/flotiq/gatsby-starter-event-calendar) +> - [Project portfolio Gatsby starter](https://github.com/flotiq/gatsby-starter-projects) +> - [Simple blog Gatsby starter](https://github.com/flotiq/gatsby-starter-blog) +> - [Gatsby and Snipcart boilerplate, sourcing products from Flotiq](https://github.com/flotiq/gatsby-starter-products) +> - [Gatsby and Snipcart, e-commerce with products and categories from Flotiq](https://github.com/flotiq/gatsby-starter-products-with-categories) + +## Setup + +### Quickstart using a Flotiq starter + +1. **Start project from template using Gatsby CLI** + + ```shell + gatsby new my-blog-starter https://github.com/flotiq/gatsby-starter-blog + ``` + +2. **Set up "Blog Post" Content Type in Flotiq** + + Create your [Flotiq.com](https://flotiq.com) account. Next, create the `Blog Post` Content Type straight from the `Type definitions` page. + + _Note: You can also define the `Blog Post` Content Type using the [Flotiq REST API](https://flotiq.com/docs/API/)._ + +3. **Configure application** + + The next step is to configure your application to know from where it has to fetch the data. + + You need to create a file called `.env` inside the root project directory, with the following structure. The Read-Only API key can be copied from the Flotiq user settings menu, under API Keys. + + ```shell:title=.env + GATSBY_FLOTIQ_BASE_URL=https://api.flotiq.com + GATSBY_FLOTIQ_API_KEY=YOUR FLOTIQ API KEY + ``` + +4. **Start developing** + + Navigate into your new site’s directory and start it up. + + ```shell + cd my-blog-starter/ + npm install + gatsby develop + ``` + + If you wish to import example blog posts to your account, before running `gatsby develop` run this Node.js script provided by Flotiq. + + _Note: You need to put your Full Access API key in `.env` for import to work, but this can be swapped back to the Read Only API key afterwards. You don't need the Blog Post content type already in your account. If you already have posts with ids `blogpost-1` and `blogpost-2` they will be overwritten._ + + ```shell + node ./.flotiq/importExample.js + ``` + + It will add 1 image and 2 blog posts to your Flotiq account. + +### Setting up the Flotiq source plugin in a Gatsby project + +The Blog starter you've just set up uses the [gatsby-source-flotiq](https://github.com/flotiq/gatsby-source-flotiq) source plugin to pull content from Flotiq. + +Here are the steps to use this source plugin in other Gatsby projects: + +> If you're using the provided starter - all the following steps have been already taken care of, you can dive into the relevant project files to verify how it's been done. + +1. Install the plugin: + ```shell + npm install --save gatsby-source-flotiq + ``` +2. Provide API credentials in `.env` (see above for more details) +3. Register the source plugin in `gatsby-config.js`: + Make sure your `gatsby-config.js` contains the following configuration: + + ```javascript:title=gatsby-config.js + // required to pull the variables from .env + require("dotenv").config() + + module.exports = { + // ... + plugins: [ + { + resolve: "gatsby-source-flotiq", + options: { + baseUrl: process.env.GATSBY_FLOTIQ_BASE_URL, + authToken: process.env.GATSBY_FLOTIQ_API_KEY, + }, + }, + ], + // ... + } + ``` + +By default the source plugin will pull all the data you've stored in Flotiq. In some cases, e.g. when building sites that have thousands of pages - you'll likely want to limit the amount of pulled data during development. You can do that either by narrowing down the scope to specific content types or by limiting the number of pulled objects (see the `includeTypes` and `objectLimit` options). The source plugin will do its best to resolve any dependencies for you. + +> You can find more details about how to configure the Flotiq source plugin in the [plugin's README](https://github.com/flotiq/gatsby-source-flotiq). + +## Accessing Flotiq data in Gatsby + +Once you finish configuring your environment you can start developing. The source plugin will pull all the content from your Flotiq account and create respective Gatsby GraphQL nodes. It will also preserve the relations you've setup in Flotiq, so the GraphQL nodes will be automatically linked. + +For example, if you define a relation between `BlogPost` and `Category` content types in Flotiq - they will retain their relationship in Gatsby's GraphQL, so you can retrieve that in a query: + +```graphql +query { + allBlogPost { + nodes { + id + slug + category { + name + } + } + } +} +``` + +The next step is implementing these queries in your `gatsby-node.js` file: + +```javascript:title=gatsby-node.js +const path = require(`path`) +const { createFilePath } = require(`gatsby-source-filesystem`) +exports.createPages = async ({ graphql, actions }) => { + const { createPage } = actions + + const blogPost = path.resolve(`./src/templates/blog-post.js`) + const result = await graphql(` + query GetBlogPosts { + allBlogpost(sort: { fields: flotiqInternal___createdAt, order: DESC }) { + edges { + node { + headerImage { + extension + id + } + content + id + slug + title + } + } + } + } + `) + + if (result.errors) { + throw result.errors + } + + // Create blog posts pages. + const posts = result.data.allBlogpost.edges + posts.forEach((post, index) => { + const previous = index === posts.length - 1 ? null : posts[index + 1].node + const next = index === 0 ? null : posts[index - 1].node + + createPage({ + path: post.node.slug, + component: blogPost, + context: { + slug: post.node.slug, + previous, + next, + }, + }) + }) +} + +exports.onCreateNode = ({ node, actions, getNode }) => { + const { createNodeField } = actions + + if (node.internal.type === `MarkdownRemark`) { + const value = createFilePath({ node, getNode }) + createNodeField({ + name: `slug`, + node, + value, + }) + } +} +``` + +Now you'll want to let Gatsby create appropriate pages for your Content Objects. This example uses a `blogPost` component as a template: + +```javascript:title=blog-post.js +import React from "react" +import { graphql } from "gatsby" + +class BlogPostTemplate extends React.Component { + render() { + const post = this.props.data.blogpost + const siteTitle = this.props.data.site.siteMetadata.title + const { previous, next } = this.props.pageContext + + return ( +
+
+

{post.title}

+
+ {post.headerImage && post.headerImage[0] && ( + ${post.title} + )} +
+
+ ) + } +} + +export default BlogPostTemplate + +export const pageQuery = graphql` + query BlogPostBySlug($slug: String!) { + site { + siteMetadata { + title + } + } + blogpost(slug: { eq: $slug }) { + id + title + content + headerImage { + extension + id + } + } + } +` +``` + +## Deployment + +Once you're finished with your website there are several ways to deploy it. You can use any hosting provider you choose - Netlify, Heroku, AWS S3, Cloudflare, etc. + +If you're using Gatsby Cloud, you can use the Flotiq integration to streamline your workflow by providing live updates in preview and push-button deployments. + +You can read the relevant [Flotiq Gatsby Cloud integration](https://flotiq.com/docs/panel/Plugins/Gatsby-cloud-integration/) documentation page to learn more. + +## Summary + +This guide has gone through the key points of setting up a Gatsby starter, configuring it to work with Flotiq, and kicking off your development process. Remember to check out other [Flotiq Gatsby starters](https://github.com/flotiq/?q=gatsby-starter) already prepared to kick start your next project. You can also join the [Flotiq Discord channel](https://discord.gg/FwXcHnX) if you need any help! diff --git a/docs/docs/sourcing-from-prismic.md b/docs/docs/sourcing-from-prismic.md index 83c3dec8c446d..66260b854205d 100644 --- a/docs/docs/sourcing-from-prismic.md +++ b/docs/docs/sourcing-from-prismic.md @@ -58,6 +58,8 @@ _Note: If you want to locally build your project you'll also have to create a `. Now you need to configure the plugin (See all [available options](https://www.npmjs.com/package/gatsby-source-prismic#how-to-use)). The `repositoryName` is the name you have entered at the creation of the repository (you'll also find it as the subdomain in the URL). The `linkResolver` function is used to process links in your content. Fields with rich text formatting or links to internal content use this function to generate the correct link URL. The document node, field key (i.e. API ID), and field value are provided to the function. This allows you to use different [link resolver logic](https://prismic.io/docs/javascript/query-the-api/link-resolving) for each field if necessary. +Remember also to add an object of Prismic custom type JSON schemas. You can copy it from Prismic's JSON editor tab in your custom type page. It's important to keep the name of JSON file **the same** as your custom type's API ID. More information can be found in the [Prismic documentation](https://user-guides.prismic.io/en/articles/380227-introduction-to-custom-type-building) and [Source Plugin README](/packages/gatsby-source-prismic/#providing-json-schemas). + Add the following to register the plugin: ```javascript:title=gatsby-config.js @@ -73,6 +75,7 @@ module.exports = { repositoryName: `your-repository-name`, accessToken: `${process.env.API_KEY}`, linkResolver: ({ node, key, value }) => post => `/${post.uid}`, + page: require("./src/schemas/page.json"), }, }, ], diff --git a/docs/docs/third-party-graphql.md b/docs/docs/third-party-graphql.md index d9b90ed34ab4f..ebe562b9c694d 100644 --- a/docs/docs/third-party-graphql.md +++ b/docs/docs/third-party-graphql.md @@ -101,3 +101,4 @@ exports.createPages = async ({ actions, graphql }) => { - [Example with Hasura](https://github.com/hasura/graphql-engine/tree/master/community/sample-apps/gatsby-postgres-graphql) - [Example with AWS AppSync](https://github.com/aws-samples/aws-appsync-gatsby-sample) - [Example with Dgraph](https://github.com/dgraph-io/gatsby-dgraph-graphql) +- [Example with Drupal](https://github.com/smthomas/gatsby-drupal-graphql) diff --git a/docs/docs/using-cloudinary-image-service.md b/docs/docs/using-cloudinary-image-service.md index c890a70259c5c..dcd57ee0052e3 100644 --- a/docs/docs/using-cloudinary-image-service.md +++ b/docs/docs/using-cloudinary-image-service.md @@ -8,7 +8,7 @@ In this guide you will take a look at the [gatsby-source-cloudinary](/packages/g Plugins are generally used to abstract functionality in Gatsby. In this case, the `gatsby-source-cloudinary` plugin is a [source plugin](/docs/creating-a-source-plugin/) which helps to connect Cloudinary media storage capabilities to your site. -> Here's a [demo site that uses the gatsby-source-cloudinary](https://gsc-sample.netlify.com) showcasing optimized images in a masonry grid, served from Cloudinary. +> Here's a [demo site that uses the gatsby-source-cloudinary](https://gsc-sample.netlify.app) showcasing optimized images in a masonry grid, served from Cloudinary. ## The problem with handling images on the web @@ -88,7 +88,7 @@ Here's a [link to the README](https://github.com/Chuloo/gatsby-source-cloudinary After sourcing media files from Cloudinary, you will be able to leverage Cloudinary’s media transformation capabilities. To do so, use `gatsby-transformer-cloudinary` which is a type of [transformer plugin](/docs/creating-a-transformer-plugin/) that is used to change image formats, styles and dimensions. It also optimizes images for minimal file size alongside high visual quality for an improved user experience and minimal bandwidth. -Here's a [demo site that uses the gatsby-transformer-plugin](https://gatsby-transformer-cloudinary.netlify.com/fluid/) +Here's a [demo site that uses the gatsby-transformer-plugin](https://gatsby-transformer-cloudinary.netlify.app/fluid/) ### Prerequisites diff --git a/docs/sites.yml b/docs/sites.yml index 1f8cc835f4c60..f17ba700ec99f 100644 --- a/docs/sites.yml +++ b/docs/sites.yml @@ -1597,8 +1597,8 @@ - title: Lisa Ye's Blog description: | Simple blog/portofolio for a fashion designer. Gatsby_v2 + Netlify cms - main_url: https://lisaye.netlify.com/ - url: https://lisaye.netlify.com/ + main_url: https://lisaye.netlify.app/ + url: https://lisaye.netlify.app/ categories: - Blog - Portfolio @@ -2085,8 +2085,8 @@ built_by_url: https://www.michaeluloth.com featured: false - title: Pomegranate Opera - main_url: https://pomegranateopera.netlify.com - url: https://pomegranateopera.netlify.com + main_url: https://pomegranateopera.netlify.app + url: https://pomegranateopera.netlify.app description: Pomegranate Opera is a lesbian opera written by Amanda Hale & Kye Marshall. Site designed by Stephen Bell. categories: - Gallery @@ -2105,8 +2105,8 @@ built_by_url: https://www.michaeluloth.com featured: false - title: Artist.Center - main_url: https://artistcenter.netlify.com - url: https://artistcenter.netlify.com + main_url: https://artistcenter.netlify.app + url: https://artistcenter.netlify.app description: The marketing page for Artist.Center, a soon-to-launch platform designed to connect opera singers to opera companies. Site designed by Stephen Bell. categories: - Music @@ -2368,8 +2368,8 @@ built_by: Hudl built_by_url: https://www.hudl.com/ - title: Subtle UI - main_url: https://subtle-ui.netlify.com/ - url: https://subtle-ui.netlify.com/ + main_url: https://subtle-ui.netlify.app/ + url: https://subtle-ui.netlify.app/ source_url: https://github.com/ryanwiemer/subtle-ui description: > A collection of clever yet understated user interactions found on the web. @@ -4147,8 +4147,8 @@ - title: re-geo description: > re-geo is react based geo cities style component. - main_url: https://re-geo.netlify.com/ - url: https://re-geo.netlify.com/ + main_url: https://re-geo.netlify.app/ + url: https://re-geo.netlify.app/ source_url: https://github.com/sadnessOjisan/re-geo-lp categories: - Open Source @@ -4413,7 +4413,7 @@ url: https://arctica.io main_url: https://arctica.io description: > - Arctica specialises in purpose-built web sites and progressive web applications with user optimal experiences, tailored to meet the objectives of your business. + Arctica specialises in purpose-built websites and progressive web applications with user optimal experiences, tailored to meet the objectives of your business. categories: - Portfolio - Agency @@ -4585,7 +4585,7 @@ url: https://gmartinez.dev/ source_url: https://github.com/nephlin7/gmartinez.dev description: > - Personal web site for show my skills and my works. + Personal website for show my skills and my works. categories: - Web Development - Portfolio @@ -4827,8 +4827,8 @@ built_by_url: https://www.web-hart.com featured: false - title: nicdougall.com - url: https://nicdougall.netlify.com/ - main_url: https://nicdougall.netlify.com/ + url: https://nicdougall.netlify.app/ + main_url: https://nicdougall.netlify.app/ source_url: https://github.com/riencoertjens/nicdougall.com description: > Athlete website with Netlify CMS for blog content. @@ -5553,8 +5553,8 @@ built_by: Acto built_by_url: https://www.acto.dk/ - title: Gatsby GitHub Stats - url: https://gatsby-github-stats.netlify.com - main_url: https://gatsby-github-stats.netlify.com + url: https://gatsby-github-stats.netlify.app + main_url: https://gatsby-github-stats.netlify.app source_url: https://github.com/lannonbr/gatsby-github-stats/ description: > Statistics Dashboard for Gatsby GitHub repository @@ -6070,8 +6070,8 @@ built_by: Daniel Spajic featured: false - title: Cosmotory - url: https://cosmotory.netlify.com/ - main_url: https://cosmotory.netlify.com/ + url: https://cosmotory.netlify.app/ + main_url: https://cosmotory.netlify.app/ description: > This is the educational blog containing various courses,learning materials from various authors from all over the world. categories: @@ -6081,7 +6081,7 @@ - Open Source - Education built_by: Hanishraj B Rao. - built_by_url: https://hanishrao.netlify.com/ + built_by_url: https://hanishrao.netlify.app/ featured: false - title: Armorblox | Security Powered by Understanding url: https://www.armorblox.com @@ -6439,8 +6439,8 @@ built_by: afc163 built_by_url: https://github.com/afc163 - title: ReactStudy Blog - url: https://elated-lewin-51cf0d.netlify.com - main_url: https://elated-lewin-51cf0d.netlify.com + url: https://elated-lewin-51cf0d.netlify.app + main_url: https://elated-lewin-51cf0d.netlify.app description: > Belong to your own blog by gatsby categories: @@ -6449,8 +6449,8 @@ built_by_url: https://github.com/97thjingba featured: false - title: George - main_url: https://kind-mestorf-5a2bc0.netlify.com - url: https://kind-mestorf-5a2bc0.netlify.com + main_url: https://kind-mestorf-5a2bc0.netlify.app + url: https://kind-mestorf-5a2bc0.netlify.app description: > shiny new web built with Gatsby categories: @@ -6764,8 +6764,8 @@ built_by_url: https://github.com/Abhith featured: false - title: Mr & Mrs Wilkinson - url: https://thewilkinsons.netlify.com/ - main_url: https://thewilkinsons.netlify.com/ + url: https://thewilkinsons.netlify.app/ + main_url: https://thewilkinsons.netlify.app/ source_url: https://github.com/davemullenjnr/the-wilkinsons description: > A one-page wedding photography showcase using Gatsby Image and featuring a lovely hero and intro section. @@ -6991,8 +6991,8 @@ built_by_url: https://www.thedelta.io featured: false - title: GatsbyFinds - main_url: https://gatsbyfinds.netlify.com - url: https://gatsbyfinds.netlify.com + main_url: https://gatsbyfinds.netlify.app + url: https://gatsbyfinds.netlify.app description: > GatsbyFinds is a website built ontop of Gatsby v2 by providing developers with a showcase of all the latest projects made with the beloved GatsbyJS. categories: @@ -7137,8 +7137,8 @@ built_by_url: https://www.nts.live featured: false - title: BALAJIRAO676 - main_url: https://thebalajiraoecommerce.netlify.com/ - url: https://thebalajiraoecommerce.netlify.com/ + main_url: https://thebalajiraoecommerce.netlify.app/ + url: https://thebalajiraoecommerce.netlify.app/ featured: false categories: - Blog @@ -7275,8 +7275,8 @@ built_by_url: https://www.pixelize.com.au featured: false - title: VS Code GitHub Stats - url: https://vscode-github-stats.netlify.com - main_url: https://vscode-github-stats.netlify.com + url: https://vscode-github-stats.netlify.app + main_url: https://vscode-github-stats.netlify.app source_url: https://github.com/lannonbr/vscode-github-stats/ description: > Statistics Dashboard for VS Code GitHub repository @@ -7328,8 +7328,8 @@ - title: Roman Kravets description: > Portfolio of Roman Kravets. Web Developer, HTML & CSS Coder. - main_url: https://romkravets.netlify.com/ - url: https://romkravets.netlify.com/ + main_url: https://romkravets.netlify.app/ + url: https://romkravets.netlify.app/ categories: - Portfolio - Open Source @@ -7354,8 +7354,8 @@ - title: Gatsby Bomb description: > A fan made version of the website Giantbomb, fully static and powered by Gatsby JS and the GiantBomb API. - main_url: https://gatsbybomb.netlify.com - url: https://gatsbybomb.netlify.com + main_url: https://gatsbybomb.netlify.app + url: https://gatsbybomb.netlify.app categories: - App - Entertainment @@ -7806,8 +7806,8 @@ built_by: Cade Kynaston built_by_url: https://cade.codes - title: diff001a's blog - main_url: https://diff001a.netlify.com/ - url: https://diff001a.netlify.com/ + main_url: https://diff001a.netlify.app/ + url: https://diff001a.netlify.app/ description: > This is diff001a's blog which contains blogs related to programming. categories: @@ -7850,8 +7850,8 @@ built_by_url: https://thecouch.nyc featured: false - title: MyPrograming Steps - main_url: https://mysteps.netlify.com/ - url: https://mysteps.netlify.com/ + main_url: https://mysteps.netlify.app/ + url: https://mysteps.netlify.app/ description: > FrontEnd Tutorial Information featured: false @@ -7952,8 +7952,8 @@ built_by: Handsome Creative built_by_url: https://www.hellohandsome.com.au - title: Fuzzy String Matching - main_url: https://fuzzy-string-matching.netlify.com - url: https://fuzzy-string-matching.netlify.com + main_url: https://fuzzy-string-matching.netlify.app + url: https://fuzzy-string-matching.netlify.app source_url: https://github.com/jdemieville/fuzzyStringMatching description: > This site is built to assess the performance of various approximate string matching algorithms aka fuzzy string searching. @@ -8478,8 +8478,8 @@ built_by_url: https://github.com/isamrish featured: false - title: Jarod Peachey - main_url: https://jarodpeachey.netlify.com - url: https://jarodpeachey.netlify.com + main_url: https://jarodpeachey.netlify.app + url: https://jarodpeachey.netlify.app source_url: https://github.com/jarodpeachey/portfolio description: > Jarod Peachey is a front-end developer focused on building modern and fast websites for everyone. @@ -10713,7 +10713,7 @@ main_url: https://xn--28jma5da5l6e.com/en/ source_url: https://github.com/dondoko-susumu/website-v2 description: > - The Web site of Dondoko Susumu, a Japanese cartoonist. His cartoons have been posted. It is internationalized into 12 languages. + The Website of Dondoko Susumu, a Japanese cartoonist. His cartoons have been posted. It is internationalized into 12 languages. categories: - Blog - Entertainment @@ -10779,7 +10779,7 @@ featured: false - title: Que Jamear description: >- - A directory with a map of food delivery services + A directory with a map of food delivery services to be used during the health emergency caused by covid 19. main_url: https://quejamear.com/encebollados url: https://quejamear.com/encebollados diff --git a/docs/starters.yml b/docs/starters.yml index bf2504836ea36..79e470d870960 100644 --- a/docs/starters.yml +++ b/docs/starters.yml @@ -1,4 +1,4 @@ -- url: https://ghost-balsa.draftbox.co/ +- url: https://ghost-balsa-preview.draftbox.co/ repo: https://github.com/draftbox-co/gatsby-ghost-balsa-starter description: A Gatsby starter for creating blogs from headless Ghost CMS. tags: @@ -33,7 +33,7 @@ - Using the new gatsby-wordpress-source@v4 - Responsive design - Works well with Gatsby Cloud incremental updates -- url: https://22boxes-gatsby-uno.netlify.com/ +- url: https://22boxes-gatsby-uno.netlify.app/ repo: https://github.com/iamtherealgd/gatsby-starter-22boxes-uno description: A Gatsby starter for creating blogs and showcasing your work tags: @@ -46,8 +46,8 @@ - Work page with blog type content management - Personal webiste to create content and put your portfolio items - Landing pages for your work items, not just links -- url: https://gatsby-wordpress-libre.netlify.com/ - repo: https://github.com/armada-inc/gatsby-wordpress-libre-starter +- url: https://wp-libre-preview.draftbox.co/ + repo: https://github.com/draftbox-co/gatsby-wordpress-libre-starter description: A Gatsby starter for creating blogs from headless WordPress CMS. tags: - Blog @@ -65,7 +65,7 @@ - Sitemap Generation - XML Sitemaps - Progressive Web App -- url: https://delog-w3layouts.netlify.com/ +- url: https://delog-w3layouts.netlify.app/ repo: https://github.com/W3Layouts/gatsby-starter-delog description: A Gatsby Starter built with Netlify CMS to launch your dream blog with a click. tags: @@ -99,7 +99,7 @@ - Offline Support - RSS Feed - Composable and extensible -- url: https://gatsby-theme-sky-lite.netlify.com +- url: https://gatsby-theme-sky-lite.netlify.app repo: https://github.com/vim-labs/gatsby-theme-sky-lite-starter description: A lightweight Gatsby starter with Material-UI and MDX Markdown support. tags: @@ -111,7 +111,7 @@ - MDX - MaterialUI Components - React Icons -- url: https://authenticaysh.netlify.com/ +- url: https://authenticaysh.netlify.app/ repo: https://github.com/seabeams/gatsby-starter-auth-aws-amplify description: Full-featured Auth with AWS Amplify & AWS Cognito tags: @@ -146,7 +146,7 @@ features: - Comes with React Helmet for adding site meta tags - Includes plugins for offline support out of the box -- url: https://gatsby-netlify-cms.netlify.com/ +- url: https://gatsby-netlify-cms.netlify.app/ repo: https://github.com/netlify-templates/gatsby-starter-netlify-cms description: n/a tags: @@ -230,7 +230,7 @@ - Resume - Redux for managing statement (with redux-saga / reselect) -- url: https://gatsby-tailwind-emotion-starter.netlify.com/ +- url: https://gatsby-tailwind-emotion-starter.netlify.app/ repo: https://github.com/muhajirdev/gatsby-tailwind-emotion-starter description: A Gatsby Starter with Tailwind CSS + Emotion JS tags: @@ -239,7 +239,7 @@ - Eslint Airbnb without semicolon and without .jsx extension - Offline support - Web App Manifest -- url: https://gatsby-starter-redux-firebase.netlify.com/ +- url: https://gatsby-starter-redux-firebase.netlify.app/ repo: https://github.com/muhajirdev/gatsby-starter-redux-firebase description: A Gatsby + Redux + Firebase Starter. With Authentication tags: @@ -335,7 +335,7 @@ - Styling:None features: - Same as official gatsby-starter-blog but with all styling removed -- url: https://gatsby-starter-github-api.netlify.com/ +- url: https://gatsby-starter-github-api.netlify.app/ repo: https://github.com/lundgren2/gatsby-starter-github-api description: Single page starter based on gatsby-source-github-api tags: @@ -346,7 +346,7 @@ - List your GitHub repositories - GitHub GraphQL API v4 -- url: https://gatsby-starter-bloomer.netlify.com/ +- url: https://gatsby-starter-bloomer.netlify.app/ repo: https://github.com/Cethy/gatsby-starter-bloomer description: n/a tags: @@ -356,7 +356,7 @@ - Bulma CSS Framework with its Bloomer react components - Font-Awesome icons - Includes a simple fullscreen hero w/ footer example -- url: https://gatsby-starter-bootstrap-netlify.netlify.com/ +- url: https://gatsby-starter-bootstrap-netlify.netlify.app/ repo: https://github.com/konsumer/gatsby-starter-bootstrap-netlify description: n/a tags: @@ -364,7 +364,7 @@ - CMS:Netlify features: - Very similar to gatsby-starter-netlify-cms, slightly more configurable (e.g. set site-title in gatsby-config) with Bootstrap/Bootswatch instead of bulma -- url: https://gatstrap.netlify.com/ +- url: https://gatstrap.netlify.app/ repo: https://github.com/jaxx2104/gatsby-starter-bootstrap description: n/a tags: @@ -386,7 +386,7 @@ - CSS modules - Prettier & eslint to format & check the code - Jest -- url: https://gatsby-starter-business.netlify.com/ +- url: https://gatsby-starter-business.netlify.app/ repo: https://github.com/v4iv/gatsby-starter-business description: n/a tags: @@ -432,7 +432,7 @@ - Used CSS Modules, easy to manipulate - FontAwsome Library for icons - Responsive Design, optimized for Mobile devices -- url: https://gatsby-starter-contentful-i18n.netlify.com/ +- url: https://gatsby-starter-contentful-i18n.netlify.app/ repo: https://github.com/mccrodp/gatsby-starter-contentful-i18n description: i18n support and language switcher for Contentful starter repo tags: @@ -443,7 +443,7 @@ - Localization (Multilanguage) - Dynamic content from Contentful CMS - Integrates i18n plugin starter and using-contentful repos -- url: https://cranky-edison-12166d.netlify.com/ +- url: https://cranky-edison-12166d.netlify.app/ repo: https://github.com/datocms/gatsby-portfolio description: n/a tags: @@ -454,7 +454,7 @@ - Contents and media from DatoCMS - Custom Sass style - SEO -- url: https://gatsby-deck.netlify.com/ +- url: https://gatsby-deck.netlify.app/ repo: https://github.com/fabe/gatsby-starter-deck description: n/a tags: @@ -463,7 +463,7 @@ - Create presentations/slides using Gatsby. - Offline support. - Page transitions. -- url: https://gatsby-starter-default-i18n.netlify.com/ +- url: https://gatsby-starter-default-i18n.netlify.app/ repo: https://github.com/angeloocana/gatsby-starter-default-i18n description: n/a tags: @@ -482,7 +482,7 @@ - Simple one page site that’s perfect for personal portfolios - Fully Responsive - Styling with SCSS -- url: https://gatsby-docs-starter.netlify.com/ +- url: https://gatsby-docs-starter.netlify.app/ repo: https://github.com/ericwindmill/gatsby-starter-docs description: n/a tags: @@ -550,7 +550,7 @@ - Normalize css (7.0). - Feather icons. - Font styles taken from Tachyons. -- url: https://gcn.netlify.com/ +- url: https://gcn.netlify.app/ repo: https://github.com/ryanwiemer/gatsby-starter-gcn description: A starter template to build amazing static websites with Gatsby, Contentful and Netlify tags: @@ -592,7 +592,7 @@ - A no-frills Gatsby install - No plugins, no boilerplate - Great for advanced users -- url: https://gatsby-starter-hello-world-tailwind-css.netlify.com/ +- url: https://gatsby-starter-hello-world-tailwind-css.netlify.app/ repo: https://github.com/ohduran/gatsby-starter-hello-world-tailwind-css description: hello world + Tailwind CSS tags: @@ -628,7 +628,7 @@ - ESLint (google config) - Prettier code styling - webpack `BundleAnalyzerPlugin` -- url: https://gatsby-starter-i18n-lingui.netlify.com/ +- url: https://gatsby-starter-i18n-lingui.netlify.app/ repo: https://github.com/dcroitoru/gatsby-starter-i18n-lingui description: n/a tags: @@ -638,7 +638,7 @@ - Message extraction - Avoids code duplication - generates pages for each locale - Possibility of translated paths -- url: https://lumen.netlify.com/ +- url: https://lumen.netlify.app/ repo: https://github.com/alxshelepenok/gatsby-starter-lumen description: A minimal, lightweight and mobile-first starter for creating blogs uses Gatsby. tags: @@ -736,7 +736,7 @@ - Single Page, Responsive Site - Custom grid made with CSS Grid - Styling with SCSS -- url: https://portfolio-bella.netlify.com/ +- url: https://portfolio-bella.netlify.app/ repo: https://github.com/LekoArts/gatsby-starter-portfolio-bella description: A portfolio starter for Gatsby. The target audience are designers and photographers. The light themed website shows your work with large images & big typography. The Onepage is powered by the Headless CMS Prismic.io. and has programmatically created pages for your projects. General settings and colors can be changed in a config & theme file. tags: @@ -807,7 +807,7 @@ - Google Analytics Support - SEO (Sitemap, OpenGraph tags, Twitter tags) - Offline Support & WebApp Manifest -- url: https://gatsby-starter-procyon.netlify.com/ +- url: https://gatsby-starter-procyon.netlify.app/ repo: https://github.com/danielmahon/gatsby-starter-procyon description: n/a tags: @@ -879,7 +879,7 @@ - Lightbox style React photo gallery - Fully Responsive - Styling with SCSS -- url: https://gatsby-starter-strict.netlify.com/ +- url: https://gatsby-starter-strict.netlify.app/ repo: https://github.com/kripod/gatsby-starter-strict description: n/a tags: @@ -894,7 +894,7 @@ - Integration with Visual Studio Code - Pre-configured auto-formatting on file save - Based on gatsby-starter-default -- url: https://gatsby-tachyons.netlify.com/ +- url: https://gatsby-tachyons.netlify.app/ repo: https://github.com/pixelsign/gatsby-starter-tachyons description: no description yet tags: @@ -924,7 +924,7 @@ - Responsive Design, optimized for Mobile devices - Seo Friendly - Uses Flexbox -- url: https://gatsby-starter-typescript-plus.netlify.com/ +- url: https://gatsby-starter-typescript-plus.netlify.app/ repo: https://github.com/resir014/gatsby-starter-typescript-plus description: This is a starter kit for Gatsby.js websites written in TypeScript. It includes the bare essentials for you to get started (styling, Markdown parsing, minimal toolset). tags: @@ -944,7 +944,7 @@ - Language:TypeScript features: - TypeScript -- url: https://fabien0102-gatsby-starter.netlify.com/ +- url: https://fabien0102-gatsby-starter.netlify.app/ repo: https://github.com/fabien0102/gatsby-starter description: n/a tags: @@ -959,7 +959,7 @@ - Jest/Enzyme testing - Storybook - Markdown linting -- url: https://gatsby-starter-wordpress.netlify.com/ +- url: https://gatsby-starter-wordpress.netlify.app/ repo: https://github.com/GatsbyCentral/gatsby-starter-wordpress description: Gatsby starter using WordPress as the content source. tags: @@ -995,7 +995,7 @@ - Baseline grid built in with modular scale across viewports. - Abstract measurements utilize REM for spacing. - One font to rule them all, Helvetica. -- url: https://gatsby-starter-blog-grommet.netlify.com/ +- url: https://gatsby-starter-blog-grommet.netlify.app/ repo: https://github.com/Ganevru/gatsby-starter-blog-grommet description: Gatsby v2 starter for creating a blog. Based on Grommet v2 UI. tags: @@ -1015,7 +1015,7 @@ - styled-components - TypeScript and ESLint (typescript-eslint) - lint-staged and husky - for linting before commit -- url: https://happy-pare-dff451.netlify.com/ +- url: https://happy-pare-dff451.netlify.app/ repo: https://github.com/fhavrlent/gatsby-contentful-typescript-starter description: Contentful and TypeScript starter based on default starter. tags: @@ -1028,7 +1028,7 @@ - TypeScript - CSS in JS (Emotion) - CMS:Contentful -- url: https://xylo-gatsby-bulma-starter.netlify.com/ +- url: https://xylo-gatsby-bulma-starter.netlify.app/ repo: https://github.com/xydac/xylo-gatsby-bulma-starter description: Gatsby v2 Starter with Bulma based on default starter. tags: @@ -1064,7 +1064,7 @@ - ESLint - Prettier - Travis CI -- url: https://gatsby-starter-blog-jumpalottahigh.netlify.com/ +- url: https://gatsby-starter-blog-jumpalottahigh.netlify.app/ repo: https://github.com/jumpalottahigh/gatsby-starter-blog-jumpalottahigh description: Gatsby v2 blog starter with SEO, search, filter, reading progress, mobile menu fab tags: @@ -1088,7 +1088,7 @@ - Stateless components using Recompose - Font changes depending on the chosen language - SEO (meta tags, openGraph, structured data, Twitter and more...) -- url: https://gatsby-starter-mate.netlify.com +- url: https://gatsby-starter-mate.netlify.app repo: https://github.com/EmaSuriano/gatsby-starter-mate description: A portfolio starter for Gatsby integrated with Contentful CMS. tags: @@ -1109,7 +1109,7 @@ - Netlify Deployment Friendly - Medium integration - Social sharing (Twitter, Facebook, Google, LinkedIn) -- url: https://gatsby-starter-typescript-sass.netlify.com +- url: https://gatsby-starter-typescript-sass.netlify.app repo: https://github.com/thetrevorharmon/gatsby-starter-typescript-sass description: A basic starter with TypeScript and Sass built in tags: @@ -1119,7 +1119,7 @@ features: - TypeScript and Sass support - TS linter with basic react rules -- url: https://gatsby-simple-contentful-starter.netlify.com/ +- url: https://gatsby-simple-contentful-starter.netlify.app/ repo: https://github.com/cwlsn/gatsby-simple-contentful-starter description: A simple starter to display Contentful data in Gatsby, ready to deploy on Netlify. Comes with a detailed article detailing the process. tags: @@ -1134,7 +1134,7 @@ - Simple format, easy to create your own site quickly - React Helmet for Header Modification - Remark for loading Markdown into React -- url: https://gatsby-blog-cosmicjs.netlify.com/ +- url: https://gatsby-blog-cosmicjs.netlify.app/ repo: https://github.com/cosmicjs/gatsby-blog-cosmicjs description: Blog that utilizes the power of the Cosmic headless CMS for easy content management tags: @@ -1143,7 +1143,7 @@ - Blog features: - Uses the Cosmic Gatsby source plugin -- url: https://cosmicjs-gatsby-starter.netlify.com/ +- url: https://cosmicjs-gatsby-starter.netlify.app/ repo: https://github.com/cosmicjs/gatsby-starter description: Simple Gatsby starter connected to the Cosmic headless CMS for easy content management tags: @@ -1170,7 +1170,7 @@ features: - Minimal starter based on the official default - Includes redux and a simple counter example -- url: https://gatsby-casper.netlify.com/ +- url: https://gatsby-casper.netlify.app/ repo: https://github.com/scttcper/gatsby-casper description: This is a starter blog that looks like the Ghost.io default theme, casper. tags: @@ -1182,7 +1182,7 @@ - TypeScript - Author and tag pages - RSS -- url: https://gatsby-universal.netlify.com +- url: https://gatsby-universal.netlify.app repo: https://github.com/fabe/gatsby-universal description: An opinionated Gatsby v2 starter for state-of-the-art marketing sites tags: @@ -1226,7 +1226,7 @@ - Responsive images with gatsby-image - Extensive SEO - ESLint & Prettier -- url: https://gatsby-starter-v2-casper.netlify.com/ +- url: https://gatsby-starter-v2-casper.netlify.app/ repo: https://github.com/GatsbyCentral/gatsby-v2-starter-casper description: A blog starter based on the Casper (v1.4) theme. tags: @@ -1240,7 +1240,7 @@ - Offline support - Web App Manifest - SEO -- url: https://lumen-v2.netlify.com/ +- url: https://lumen-v2.netlify.app/ repo: https://github.com/GatsbyCentral/gatsby-v2-starter-lumen description: A Gatsby v2 fork of the lumen starter. tags: @@ -1260,7 +1260,7 @@ - Offline support. - Google Analytics support. - Disqus Comments support. -- url: https://gatsby-starter-firebase.netlify.com/ +- url: https://gatsby-starter-firebase.netlify.app/ repo: https://github.com/muhajirdev/gatsby-starter-firebase description: A Gatsby + Firebase Starter. With Authentication tags: @@ -1281,7 +1281,7 @@ - Features a custom, accessible lightbox with gatsby-image - Styled with styled-components using CSS Grid - React Helmet for SEO -- url: http://jackbravo.github.io/gatsby-starter-i18n-blog/ +- url: https://jackbravo.github.io/gatsby-starter-i18n-blog/ repo: https://github.com/jackbravo/gatsby-starter-i18n-blog description: Same as official gatsby-starter-blog but with i18n support tags: @@ -1334,7 +1334,7 @@ - Ready to deploy to GitHub Pages or Netlify - Automatic RSS generation - Automatic Sitemap generation -- url: https://gatsby-starter-kontent.netlify.com +- url: https://gatsby-starter-kontent.netlify.app repo: https://github.com/Kentico/gatsby-starter-kontent description: Gatsby starter site with Kentico Kontent based on default Gatsby starter tags: @@ -1345,7 +1345,7 @@ - Comes with React Helmet for adding site meta tags - Includes plugins for offline support out of the box - Kentico Kontent integration -- url: https://gatsby-starter-storybook.netlify.com/ +- url: https://gatsby-starter-storybook.netlify.app/ repo: https://github.com/markoradak/gatsby-starter-storybook description: Gatsby starter site with Storybook tags: @@ -1357,7 +1357,7 @@ - Storybook v4 support - Styled Components v4 support - Styled Reset, ESLint, Netlify Conf -- url: https://jamstack-hackathon-starter.netlify.com/ +- url: https://jamstack-hackathon-starter.netlify.app/ repo: https://github.com/sw-yx/jamstack-hackathon-starter description: A JAMstack app with authenticated routes, static marketing pages, etc. with Gatsby, Netlify Identity, and Netlify Functions tags: @@ -1381,7 +1381,7 @@ - Progressive Web App features - Optimized for performance - Minimal UI and Styling -- url: https://gatsby-tutorial-starter.netlify.com/ +- url: https://gatsby-tutorial-starter.netlify.app/ repo: https://github.com/justinformentin/gatsby-v2-tutorial-starter description: Simple, modern designed blog with post lists, tags, and easily customizable code. tags: @@ -1428,7 +1428,7 @@ - Bootstrap v4 support - Css Modules support - ESLint, Prettier -- url: https://gatsby-typescript-boilerplate.netlify.com/ +- url: https://gatsby-typescript-boilerplate.netlify.app/ repo: https://github.com/leachjustin18/gatsby-typescript-boilerplate description: Opinionated Gatsby v2 starter with TypeScript. tags: @@ -1463,7 +1463,7 @@ - Manipulate csv data - draw with graph mermaid - display charts with chartjs -- url: https://gatsby-tailwind-styled-components.netlify.com/ +- url: https://gatsby-tailwind-styled-components.netlify.app/ repo: https://github.com/muhajirdev/gatsby-tailwind-styled-components-starter description: A Gatsby Starter with Tailwind CSS + Styled Components tags: @@ -1472,7 +1472,7 @@ - Eslint Airbnb without semicolon and without .jsx extension - Offline support - Web App Manifest -- url: https://gatsby-starter-mobx.netlify.com +- url: https://gatsby-starter-mobx.netlify.app repo: https://github.com/borekb/gatsby-starter-mobx description: MobX + TypeScript + TSLint + Prettier tags: @@ -1486,7 +1486,7 @@ - .editorconfig & Prettier - TSLint - Jest -- url: https://tender-raman-99e09b.netlify.com/ +- url: https://tender-raman-99e09b.netlify.app/ repo: https://github.com/amandeepmittal/gatsby-bulma-quickstart description: A Bulma CSS + Gatsby Starter Kit tags: @@ -1499,7 +1499,7 @@ - Google Analytics Integration - Uses Gatsby v2 - SEO -- url: https://gatsby-starter-notes.netlify.com/ +- url: https://gatsby-starter-notes.netlify.app/ repo: https://github.com/patricoferris/gatsby-starter-notes description: Gatsby starter for creating notes organised by subject and topic tags: @@ -1510,14 +1510,14 @@ - Support for code syntax highlighting - Support for mathematical expressions - Support for images -- url: https://gatsby-starter-ttag.netlify.com/ +- url: https://gatsby-starter-ttag.netlify.app/ repo: https://github.com/ttag-org/gatsby-starter-ttag description: Gatsby starter with the minimum required to demonstrate using ttag for precompiled internationalization of strings. tags: - i18n features: - Support for precompiled string internationalization using ttag and it's babel plugin -- url: https://gatsby-starter-typescript.netlify.com/ +- url: https://gatsby-starter-typescript.netlify.app/ repo: https://github.com/goblindegook/gatsby-starter-typescript description: Gatsby starter using TypeScript. tags: @@ -1533,7 +1533,7 @@ - Images - Styling with Emotion - Testing with Jest and react-testing-library -- url: https://gatsby-netlify-cms-example.netlify.com/ +- url: https://gatsby-netlify-cms-example.netlify.app/ repo: https://github.com/robertcoopercode/gatsby-netlify-cms description: Gatsby starter using Netlify CMS tags: @@ -1545,7 +1545,7 @@ - Mobile-friendly design - Styling done with Sass - Gatsby version 2 -- url: https://gatsby-typescript-starter-blog.netlify.com/ +- url: https://gatsby-typescript-starter-blog.netlify.app/ repo: https://github.com/frnki/gatsby-typescript-starter-blog description: A starter blog for TypeScript-based Gatsby projects with minimal settings. tags: @@ -1555,7 +1555,7 @@ - TypeScript & TSLint - No Styling (No Typography.js) - Minimal settings based on official starter blog -- url: https://gatsby-serif.netlify.com/ +- url: https://gatsby-serif.netlify.app/ repo: https://github.com/jugglerx/gatsby-serif-theme description: Multi page/content-type starter using Markdown and SCSS. Serif is a beautiful small business theme for Gatsby. The theme is fully responsive, blazing fast and artfully illustrated. tags: @@ -1572,7 +1572,7 @@ - Royalty free illustrations included - SEO titles & meta using `gatsby-plugin-react-helmet` - Eslint & Prettier -- url: https://awesome-gatsby-starter.netlify.com/ +- url: https://awesome-gatsby-starter.netlify.app/ repo: https://github.com/South-Paw/awesome-gatsby-starter description: Starter with a preconfigured MDX, Storybook and ESLint environment for component first development of your next Gatsby site. tags: @@ -1603,7 +1603,7 @@ - SEO - Styling with styled-components - Responsive Design, optimized for Mobile devices -- url: https://vigilant-leakey-a4f8cd.netlify.com/ +- url: https://vigilant-leakey-a4f8cd.netlify.app/ repo: https://github.com/agneym/gatsby-blog-starter description: Minimal Blog Starter Template with Styled Components. tags: @@ -1619,7 +1619,7 @@ - Image Optimisation - Code Styling and Formatting in markdown - Responsive Design -- url: https://inspiring-me-lwz7512.netlify.com/ +- url: https://inspiring-me-lwz7512.netlify.app/ repo: https://github.com/lwz7512/gatsby-netlify-identity-starter description: Gatsby Netlify Identity Starter with NIW auth support, and content gating, as well as responsive layout. tags: @@ -1631,7 +1631,7 @@ - User authentication by Netlify Identity Widget/Service - Pagination for posts - Navigation menu with active status -- url: https://gatsby-starter-event-calendar.netlify.com/ +- url: https://gatsby-starter-event-calendar.netlify.app/ repo: https://github.com/EmaSuriano/gatsby-starter-event-calendar description: Gatsby Starter to display information about events from Google Spreadsheets with Calendars tags: @@ -1650,7 +1650,7 @@ - Netlify Deployment Friendly - ESLint with Airbnb's config - Prettier integrated into ESLint -- url: https://gatsby-starter-tech-blog.netlify.com/ +- url: https://gatsby-starter-tech-blog.netlify.app/ repo: https://github.com/email2vimalraj/gatsby-starter-tech-blog description: A simple tech blog starter kit for Gatsby tags: @@ -1666,7 +1666,7 @@ - SEO support - PWA support - Offline support -- url: https://infallible-brown-28846b.netlify.com/ +- url: https://infallible-brown-28846b.netlify.app/ repo: https://github.com/tylergreulich/gatsby-typescript-mdx-prismjs-starter description: Gatsby starter using TypeScript, MDX, Prismjs, and styled-components tags: @@ -1682,7 +1682,7 @@ - Jest - react-testing-library - styled-components -- url: https://hardcore-darwin-d7328f.netlify.com/ +- url: https://hardcore-darwin-d7328f.netlify.app/ repo: https://github.com/agneym/gatsby-careers-page description: A Careers Page for startups using Gatsby tags: @@ -1725,7 +1725,7 @@ - Comes with React Helmet for adding site meta tags - Includes plugins for offline support out of the box - PurgeCSS to shave off unused styles -- url: https://tyra-starter.netlify.com/ +- url: https://tyra-starter.netlify.app/ repo: https://github.com/madelyneriksen/gatsby-starter-tyra description: A feminine Gatsby Starter Optimized for SEO tags: @@ -1737,7 +1737,7 @@ - Styled with Tachyons. - Rich structured data on blog posts for SEO. - Pagination and category pages. -- url: https://gatsby-starter-styled.netlify.com/ +- url: https://gatsby-starter-styled.netlify.app/ repo: https://github.com/gregoralbrecht/gatsby-starter-styled description: Yet another simple starter with Styled-System, Typography.js, SEO and Google Analytics. tags: @@ -1774,7 +1774,7 @@ - Offline Support - RSS Feed - Netlify integration ready to deploy -- url: https://traveler-blog.netlify.com/ +- url: https://traveler-blog.netlify.app/ repo: https://github.com/QingpingMeng/gatsby-starter-traveler-blog description: A fork of the Official Gatsby Starter Blog to build a travler blog with images support tags: @@ -1788,7 +1788,7 @@ - Material UI - styled-components - GitHub markdown css support -- url: https://create-ueno-app.netlify.com +- url: https://create-ueno-app.netlify.app repo: https://github.com/ueno-llc/ueno-gatsby-starter description: Opinionated Gatsby starter by Ueno. tags: @@ -1806,7 +1806,7 @@ - SVG to React component - Ueno's TSlint - Decorators -- url: https://gatsby-snyung-starter.netlify.com/ +- url: https://gatsby-snyung-starter.netlify.app/ repo: https://github.com/SeonHyungJo/gatsby-snyung-starter description: Basic starter template for You tags: @@ -1824,7 +1824,7 @@ - Nice Pagination - Comes with React Helmet for adding site meta tags - Create Yout Name Card for writing meta data -- url: https://gatsby-contentstack-starter.netlify.com/ +- url: https://gatsby-contentstack-starter.netlify.app/ repo: https://github.com/contentstack/gatsby-starter-contentstack description: A Gatsby starter powered by Headless CMS Contentstack. tags: @@ -1833,7 +1833,7 @@ features: - Includes Contentstack Delivery API for any environment - Dynamic content from Contentstack CMS -- url: https://gatsby-craftcms-barebones.netlify.com +- url: https://gatsby-craftcms-barebones.netlify.app repo: https://github.com/frankievalentine/gatsby-craftcms-barebones description: Barebones setup for using Craft CMS and Gatsby locally. tags: @@ -1842,7 +1842,7 @@ - Full setup instructions included - Documented to get you set up with Craft CMS quickly - Code referenced in repo -- url: https://gatsby-starter-buttercms.netlify.com/ +- url: https://gatsby-starter-buttercms.netlify.app/ repo: https://github.com/ButterCMS/gatsby-starter-buttercms description: A starter template for spinning up a Gatsby+ ButterCMS site tags: @@ -1876,7 +1876,7 @@ - React Bootstrap with Material Design css framework. - Free for personal and commercial use - Fully responsive -- url: https://frosty-ride-4ff3b9.netlify.com/ +- url: https://frosty-ride-4ff3b9.netlify.app/ repo: https://github.com/damassi/gatsby-starter-typescript-rebass-netlifycms description: A Gatsby starter built on top of MDX (React + Markdown), NetlifyCMS (with @@ -1910,7 +1910,7 @@ - Simple setup without opinionated setup - Fully instrumented for successful PROD deployments - Stylus for simple CSS -- url: https://example-company-website-gatsby-sanity-combo.netlify.com/ +- url: https://example-company-website-gatsby-sanity-combo.netlify.app/ repo: https://github.com/sanity-io/example-company-website-gatsby-sanity-combo description: This examples combines Gatsby site generation with Sanity.io content management in a neat company website. tags: @@ -1925,7 +1925,7 @@ - Full Render Control with Portable Text - gatsby-image support - Content types for company info, pages, projects, people, and blog posts -- url: https://gatsby-starter-oss.netlify.com/ +- url: https://gatsby-starter-oss.netlify.app/ repo: https://github.com/robinmetral/gatsby-starter-oss description: A Gatsby starter to showcase your open-source projects. tags: @@ -1943,7 +1943,7 @@ - ✨ Themeable with Theme UI - 🚀 Powered by gatsby-theme-oss - 💯 100/100 Lighthouse scores -- url: https://gatsby-starter-docz.netlify.com/ +- url: https://gatsby-starter-docz.netlify.app/ repo: https://github.com/RobinCsl/gatsby-starter-docz description: Simple starter where building your own documentation with Docz is possible tags: @@ -1951,7 +1951,7 @@ features: - Generate nice documentation with Docz, in addition to generating your normal Gatsby site - Document your React components in .mdx files -- url: https://gatsby-starter-santa-fe.netlify.com/ +- url: https://gatsby-starter-santa-fe.netlify.app/ repo: https://github.com/osogrizz/gatsby-starter-santa-fe description: A place for artist or designers to display their creations tags: @@ -2023,7 +2023,7 @@ - Material Design theme and icons - Simple setup without opinionated setup - Fully instrumented for successful PROD deployments -- url: https://gatsby-shopify-starter.netlify.com/ +- url: https://gatsby-shopify-starter.netlify.app/ repo: https://github.com/AlexanderProd/gatsby-shopify-starter description: Kick off your next, e-commerce experience with this Gatsby starter. It is based on the default Gatsby starter to be easily modifiable. tags: @@ -2048,7 +2048,7 @@ - Shopify Integration - Product Grid - Shopify Store Credentials included -- url: https://gatejs.netlify.com +- url: https://gatejs.netlify.app repo: https://github.com/sarasate/gate description: API Doc generator inspired by Stripe's API docs tags: @@ -2060,7 +2060,7 @@ - Code samples separated by language - Syntax highlighting - Everything in a single page -- url: https://hopeful-keller-943d65.netlify.com +- url: https://hopeful-keller-943d65.netlify.app repo: https://github.com/iwilsonq/gatsby-starter-reasonml description: Gatsby starter to create static sites using type-safe ReasonML tags: @@ -2071,7 +2071,7 @@ - Gatsby v2 support - bs-platform v4 support - Similar to gatsby-starter-blog -- url: https://gatsby-starter-blog-amp-to-pwa.netlify.com/ +- url: https://gatsby-starter-blog-amp-to-pwa.netlify.app/ repo: https://github.com/tomoyukikashiro/gatsby-starter-blog-amp-to-pwa description: Gatsby starter blog with AMP to PWA Strategy tags: @@ -2092,7 +2092,7 @@ - Responsive Web Design - Auto generated Sidebar - Auto generated Anchor -- url: https://gatsby-starter-wordpress-community.netlify.com/ +- url: https://gatsby-starter-wordpress-community.netlify.app/ repo: https://github.com/pablovila/gatsby-starter-wordpress-community description: Starter using gatsby-source-wordpress to display posts and pages from a WordPress site tags: @@ -2106,7 +2106,7 @@ - WordPress support - Bulma and Sass Support for styling - Pagination logic -- url: https://gatsby-blogger.netlify.com/ +- url: https://gatsby-blogger.netlify.app/ repo: https://github.com/aslammultidots/blogger description: A Simple, clean and modern designed blog with firebase authentication feature and easily customizable code. tags: @@ -2124,7 +2124,7 @@ - Firebase for Authentication. - Protected Routes with Authorization. - Contact form integration. -- url: https://gatsby-starter-styled-components.netlify.com/ +- url: https://gatsby-starter-styled-components.netlify.app/ repo: https://github.com/blakenoll/gatsby-starter-styled-components description: The Gatsby default starter modified to use styled-components tags: @@ -2155,7 +2155,7 @@ - uses react-intl - based on Gatsby Default Starter - unit tests with Jest -- url: https://cape.netlify.com/ +- url: https://cape.netlify.app/ repo: https://github.com/juhi-trivedi/cape description: A Gatsby - CMS:Contentful demo with Netlify. tags: @@ -2201,7 +2201,7 @@ - Uses styled-components + styled-system - SEO with Sitemap, Schema.org JSONLD, Tags - Responsive images with gatsby-image -- url: https://amazing-jones-e61bda.netlify.com/ +- url: https://amazing-jones-e61bda.netlify.app/ repo: https://github.com/WebCu/gatsby-material-kit-react description: Adaptation of Material Kit React to Gatsby tags: @@ -2210,7 +2210,7 @@ - 60 Handcrafted Components - 4 Customized Plugins - 3 Example Pages -- url: https://relaxed-bhaskara-5abd0a.netlify.com/ +- url: https://relaxed-bhaskara-5abd0a.netlify.app/ repo: https://github.com/LekovicMilos/gatsby-starter-portfolio description: Gatsby portfolio starter for creating quick portfolio tags: @@ -2218,7 +2218,7 @@ features: - Showcase of portfolio items - About me page -- url: https://gatsby-typescript-scss-docker-starter.netlify.com/ +- url: https://gatsby-typescript-scss-docker-starter.netlify.app/ repo: https://github.com/OFranke/gatsby-typescript-scss-docker description: Gatsby starter TypeScript, SCSS, Docker tags: @@ -2253,7 +2253,7 @@ - Responsive images with gatsby-image - Extensive SEO - ESLint & Prettier -- url: https://gatsby-starter-landing-page.netlify.com/ +- url: https://gatsby-starter-landing-page.netlify.app/ repo: https://github.com/gillkyle/gatsby-starter-landing-page description: Single page starter for minimal landing pages tags: @@ -2272,7 +2272,7 @@ - layout config either stacked or sidebar - theme dark/light mode - post support -- url: https://gatsby-starter-default-intl.netlify.com +- url: https://gatsby-starter-default-intl.netlify.app repo: https://github.com/wiziple/gatsby-starter-default-intl description: The default Gatsby starter with features of multi-language url routes and browser language detection. tags: @@ -2282,7 +2282,7 @@ - Support automatic redirection based on user's preferred language in browser provided by browser-lang. - Support multi-language url routes within a single page component. That means you don't have to create separate pages such as pages/en/index.js or pages/ko/index.js. - Based on gatsby-starter-default with least modification. -- url: https://gatsby-starter-julia.netlify.com/ +- url: https://gatsby-starter-julia.netlify.app/ repo: https://github.com/niklasmtj/gatsby-starter-julia description: A minimal blog starter template built with Gatsby tags: @@ -2329,7 +2329,7 @@ - 📡 Webhook Validation & Creation - 🔑 GDPR Ready (Including GDPR Webhooks) - 🏗 CircleCI Config for easy continuous deployments to Firebase -- url: https://gatsby-starter-paperbase.netlify.com/ +- url: https://gatsby-starter-paperbase.netlify.app/ repo: https://github.com/willcode4food/gatsby-starter-paperbase description: A Gatsby starter that implements the Paperbase Premium Theme from MaterialUI tags: @@ -2341,7 +2341,7 @@ - Responsive Design - MaterialUI Paper Components - MaterialUI Tab Components -- url: https://gatsby-starter-devto.netlify.com/ +- url: https://gatsby-starter-devto.netlify.app/ repo: https://github.com/geocine/gatsby-starter-devto description: A Gatsby starter template that leverages the Dev.to API tags: @@ -2349,7 +2349,7 @@ - Styling:CSS-in-JS features: - Blog post listing with previews (image + summary) for each blog post -- url: https://gatsby-starter-framer-x.netlify.com/ +- url: https://gatsby-starter-framer-x.netlify.app/ repo: https://github.com/simulieren/gatsby-starter-framer-x description: A Gatsby starter template that is connected to a Framer X project tags: @@ -2371,7 +2371,7 @@ - Configuration for Firebase hosting - Configuration for Cloud Build deployment - Clear documentation to have your site deployed on Firebase behind SSL in no time! -- url: https://lewis-gatsby-starter-blog.netlify.com/ +- url: https://lewis-gatsby-starter-blog.netlify.app/ repo: https://github.com/lewislbr/lewis-gatsby-starter-blog description: A simple custom Gatsby starter template to start a new blog or personal website. tags: @@ -2387,7 +2387,7 @@ - Optimized images. - Offline capabilities. - Auto-generated sitemap and robots.txt. -- url: https://gatsby-starter-stripe.netlify.com/ +- url: https://gatsby-starter-stripe.netlify.app/ repo: https://github.com/brxck/gatsby-starter-stripe description: A minimal starter to create a storefront with Gatsby, Stripe, & Netlify Functions. tags: @@ -2440,7 +2440,7 @@ - PWA (Progressive Web App) support - MobX - Customizable -- url: https://gatsby-starter-fine.netlify.com/ +- url: https://gatsby-starter-fine.netlify.app/ repo: https://github.com/toboko/gatsby-starter-fine description: A mutli-response and light, mobile first blog starter with columns layout and Seo optimization. tags: @@ -2478,7 +2478,7 @@ - custom project cards - easily extendable to include blog page - Responsive design -- url: https://gatsby-documentation-starter.netlify.com/ +- url: https://gatsby-documentation-starter.netlify.app/ repo: https://github.com/whoisryosuke/gatsby-documentation-starter description: Automatically generate docs for React components using MDX, react-docgen, and Gatsby tags: @@ -2504,7 +2504,7 @@ - Landing page structure split into sections - Basic UX/UX elements ready. navbar, smooth scrolling, faqs, theming - Convenient image handling and data separation -- url: https://gatsby-starter-quiz.netlify.com/ +- url: https://gatsby-starter-quiz.netlify.app/ repo: https://github.com/raphadeluca/gatsby-starter-quiz description: Create rich quizzes with Gatsby & Mdx. No need of database or headless CMS. Manage your data directly in your Mdx file's frontmatter and write your content in the body. Customize your HTML tags, use react components from a library or write your owns. Navigation will be automatically created between each question. tags: @@ -2514,7 +2514,7 @@ - Rich customizable content with MDX - Green / Red alert footer on user's answer - Navigation generated based on the index of each question -- url: https://gatsby-starter-accessibility.netlify.com/ +- url: https://gatsby-starter-accessibility.netlify.app/ repo: https://github.com/benrobertsonio/gatsby-starter-accessibility description: The default Gatsby starter with powerful accessibility tools built-in. tags: @@ -2525,7 +2525,7 @@ - ✅ lint:staged for adding a pre-commit hook to catch accessibility linting errors - 📣 react-axe for console reporting of accessibility errors in the DOM during development - 📖 storybook setup for accessibility reporting on individual components -- url: https://gatsby-theme-ggt-material-ui-blog.netlify.com/ +- url: https://gatsby-theme-ggt-material-ui-blog.netlify.app/ repo: https://github.com/avatar-kaleb/gatsby-starter-ggt-material-ui-blog description: Starter material-ui blog utilizing a Gatsby theme! tags: @@ -2535,7 +2535,7 @@ - Uses MDX with Gatsby theme for quick and easy set up - Material-ui design with optional config passed into the theme options - Gradient background with sitemap, rss feed, and offline capabilities -- url: https://gatsby-starter-blog-typescript.netlify.com/ +- url: https://gatsby-starter-blog-typescript.netlify.app/ repo: https://github.com/gperl27/Gatsby-Starter-Blog-Typescript description: Gatsby starter blog with TypeScript tags: @@ -2548,7 +2548,7 @@ - Styled components in favor of inline styles - Transition Link for nice page transitions - Type definitions from GraphQL schema (with code generation) -- url: https://gatsby-starter-sass.netlify.com/ +- url: https://gatsby-starter-sass.netlify.app/ repo: https://github.com/colbyfayock/gatsby-starter-sass description: A Gatsby starter with Sass and no assumptions! tags: @@ -2567,7 +2567,7 @@ - SASS stylesheets to make styling components easy - Sample navbar that sticks to the top of the page on scroll - Includes react-icons to make adding icons to your app super simple -- url: https://gatsbystartermdb.netlify.com +- url: https://gatsbystartermdb.netlify.app repo: https://github.com/jjcav84/mdbreact-gatsby-starter description: Gatsby starter built with MDBootstrap React free version tags: @@ -2577,7 +2577,7 @@ - Contact form and Google Map components - Animation - documentation and component library can be found at mdboostrap's website -- url: https://gatsby-starter-primer.netlify.com/ +- url: https://gatsby-starter-primer.netlify.app/ repo: https://github.com/thomaswangio/gatsby-starter-primer description: A Gatsby starter featuring GitHub Primer Design System and React components tags: @@ -2635,7 +2635,7 @@ - Styling with SCSS - Offline support - Web App Manifest -- url: https://hopeful-ptolemy-cd840b.netlify.com/ +- url: https://hopeful-ptolemy-cd840b.netlify.app/ repo: https://github.com/tonydiaz/gatsby-landing-page-starter description: A simple landing page starter for idea validation using material-ui. Includes email signup form and pricing section. tags: @@ -2681,7 +2681,7 @@ - Styling with SCSS - Offline support - Web App Manifest -- url: https://jovial-jones-806326.netlify.com/ +- url: https://jovial-jones-806326.netlify.app/ repo: https://github.com/GabeAtWork/gatsby-elm-starter description: An Elm-in-Gatsby integration, based on gatsby-plugin-elm tags: @@ -2718,7 +2718,7 @@ - Styling with SCSS - Offline support - Web App Manifest -- url: https://gatsby-london.netlify.com +- url: https://gatsby-london.netlify.app repo: https://github.com/ImedAdel/gatsby-london description: A custom, image-centric theme for Gatsby. tags: @@ -2793,7 +2793,7 @@ features: - Uses Google Sheets for data - Easily configurable -- url: https://the-plain-gatsby.netlify.com/ +- url: https://the-plain-gatsby.netlify.app/ repo: https://github.com/wangonya/the-plain-gatsby description: A simple minimalist starter for your personal blog. tags: @@ -2844,7 +2844,7 @@ - Styling with SCSS - Offline support - Web App Manifest -- url: https://gatsby-starter-material-business-markdown.netlify.com/ +- url: https://gatsby-starter-material-business-markdown.netlify.app/ repo: https://github.com/ANOUN/gatsby-starter-material-business-markdown description: A clean, modern starter for businesses using Material Design Components tags: @@ -2867,7 +2867,7 @@ - Fully Responsive - Markdown - PWA -- url: https://gatsby-starter-default-typescript.netlify.com/ +- url: https://gatsby-starter-default-typescript.netlify.app/ repo: https://github.com/andykenward/gatsby-starter-default-typescript description: Starter Default TypeScript tags: @@ -2891,7 +2891,7 @@ - Developer environment variables - Accessibility support - Based on Gatsby Starter Default -- url: https://material-ui-starter.netlify.com/ +- url: https://material-ui-starter.netlify.app/ repo: https://github.com/dominicabela/gatsby-starter-material-ui description: This starter includes Material UI boilerplate and configuration files along with the standard Gatsby configuration files. It provides a starting point for developing Gatsby apps with the Material UI framework. tags: @@ -2903,7 +2903,7 @@ - SEO - Offline Support - Based on Gatsby Default Starter -- url: https://developer-diary.netlify.com/ +- url: https://developer-diary.netlify.app/ repo: https://github.com/willjw3/gatsby-starter-developer-diary description: A blog template created with web developers in mind. Totally usable right out of the box, but minimalist enough to be easily modifiable. tags: @@ -2938,7 +2938,7 @@ - Styling with SCSS - Offline support - Web App Manifest -- url: https://dazzling-heyrovsky-62d4f9.netlify.com/ +- url: https://dazzling-heyrovsky-62d4f9.netlify.app/ repo: https://github.com/s-kris/gatsby-starter-medium description: A Gatsby starter blog as close as possible to medium. tags: @@ -2947,7 +2947,7 @@ features: - Careers Listing - Mobile Responsive -- url: https://gatsby-personal-starter-blog.netlify.com +- url: https://gatsby-personal-starter-blog.netlify.app repo: https://github.com/thomaswangio/gatsby-personal-starter-blog description: Gatsby starter for personal blogs! Blog configured to run at /blog and with Netlify CMS and gatsby-remark-vscode. tags: @@ -2984,7 +2984,7 @@ - lightweight - includes only internationalization code - LocalizedLink - built-in link component handling route generation - LanguageSwitcher - built-in language switcher component -- url: https://gatsby-starter-bee.netlify.com/ +- url: https://gatsby-starter-bee.netlify.app/ repo: https://github.com/JaeYeopHan/gatsby-starter-bee description: A simple starter for blog with fresh UI. tags: @@ -3017,7 +3017,7 @@ - Edit on GitHub button - Fully Customisable with rich embeds using React in MDX. - Search integration with Algolia -- url: https://gatsby-starter-blog-with-lunr.netlify.com/ +- url: https://gatsby-starter-blog-with-lunr.netlify.app/ repo: https://github.com/lukewhitehouse/gatsby-starter-blog-with-lunr description: Building upon Gatsby's blog starter with a Lunr.js powered Site Search. tags: @@ -3026,7 +3026,7 @@ features: - Same as the official starter blog - Integration with Lunr.js -- url: https://rg-portfolio.netlify.com/ +- url: https://rg-portfolio.netlify.app/ repo: https://github.com/rohitguptab/rg-portfolio description: Kick-off your Portfolio website with RG-Portfolio gatsby starter. We have used Gatsby + Contentful. tags: @@ -3049,7 +3049,7 @@ - All settings manage from contentful for example Header Menu, Homepage sections, blogs, and photos, etc. - Social share in blog details pages with comment ( Disqus ). - PWA -- url: https://oneshopper.netlify.com +- url: https://oneshopper.netlify.app repo: https://github.com/rohitguptab/OneShopper description: This Starter is created for e-commerce site with Gatsby + Contentful and snipcart tags: @@ -3105,7 +3105,7 @@ - Styling with SCSS - Very similar to gatsby-starter-netlify-cms, slightly more configurable (e.g. set site-title in gatsby-config) with Bootstrap/Bootswatch instead of bulma - LocalizedLink - built-in link component handling route generation -- url: https://gatsby-kea-starter.netlify.com/ +- url: https://gatsby-kea-starter.netlify.app/ repo: https://github.com/benjamin-glitsos/gatsby-kea-starter description: Gatsby starter with redux and sagas made simpler by the Kea library tags: @@ -3127,7 +3127,7 @@ - Styling with SCSS - Offline support - Web App Manifest -- url: https://yellowcake.netlify.com/ +- url: https://yellowcake.netlify.app/ repo: https://github.com/thriveweb/yellowcake description: A starter project for creating lightning-fast websites with Gatsby v2 and Netlify-CMS v2 + Uploadcare integration. tags: @@ -3157,7 +3157,7 @@ - Styling with SCSS - Offline support - Web App Manifest -- url: https://minimal-gatsby-ts-starter.netlify.com/ +- url: https://minimal-gatsby-ts-starter.netlify.app/ repo: https://github.com/TheoBr/minimal-gatsby-typescript-starter description: Minimal TypeScript Starter tags: @@ -3168,7 +3168,7 @@ - Prettier - Netlify ready - Minimal -- url: https://gatsby-typescript-starter-default.netlify.com/ +- url: https://gatsby-typescript-starter-default.netlify.app/ repo: https://github.com/RobertoMSousa/gatsby-typescript-starter-default description: Simple Gatsby starter using TypeScript and eslint instead of outdated tslint. tags: @@ -3180,7 +3180,7 @@ - Includes plugins for offline support out of the box - TypeScript - Prettier & eslint to format & check the code -- url: https://gatsby-starter-carraway.netlify.com/ +- url: https://gatsby-starter-carraway.netlify.app/ repo: https://github.com/endymion1818/gatsby-starter-carraway description: a Gatsby starter theme with Accessibility features, TypeScript, Jest, some basic UI elements, and a CircleCI pipeline tags: @@ -3217,7 +3217,7 @@ - Switch the dark mode according to the system theme - Scss - Pagination -- url: https://compassionate-morse-5204bf.netlify.com/ +- url: https://compassionate-morse-5204bf.netlify.app/ repo: https://github.com/deamme/gatsby-starter-prismic-resume description: Gatsby Resume/CV page with Prismic integration tags: @@ -3245,7 +3245,7 @@ - Styling with SCSS - Offline support - Web App Manifest -- url: https://gatsby-starter-typescript-jest.netlify.com/ +- url: https://gatsby-starter-typescript-jest.netlify.app/ repo: https://github.com/denningk/gatsby-starter-typescript-jest description: Barebones Gatsby starter with TypeScript, Jest, GitLab-CI, and other useful configurations tags: @@ -3353,7 +3353,7 @@ - Markdown and MDX for pages; - A customized webpack and babel configuration, for complex profecianal web apps with node.js, Jest tests, etc; - Progressively build more and more complex pages using gatsby-plugin-combine. -- url: https://gatsby-ghub.netlify.com/resume-book/ +- url: https://gatsby-ghub.netlify.app/resume-book/ repo: https://github.com/dwyfrequency/gatsby-ghub description: A resume builder app with authenticated routes, static marketing pages, and dynamic resume creation tags: @@ -3365,7 +3365,7 @@ - Static Marketing pages and Dynamic Client-side Authenticated App pages - SEO component - Apollo GraphQL (client-side) -- url: https://lewis-gatsby-starter-i18n.netlify.com +- url: https://lewis-gatsby-starter-i18n.netlify.app repo: https://github.com/lewislbr/lewis-gatsby-starter-i18n description: A simple custom Gatsby starter template to start a new multilanguage website. tags: @@ -3379,7 +3379,7 @@ - Optimized images. - Offline capabilities. - Auto-generated sitemap and robots.txt. -- url: https://gatsby-snipcart-starter.netlify.com/ +- url: https://gatsby-snipcart-starter.netlify.app/ repo: https://github.com/issydennis/gatsby-snipcart description: A simple e-commerce shop built using Gatsby and Snipcart. tags: @@ -3407,7 +3407,7 @@ - Styling with SCSS - Offline support - Web App Manifest -- url: https://lewis-gatsby-starter-basic.netlify.com +- url: https://lewis-gatsby-starter-basic.netlify.app repo: https://github.com/lewislbr/lewis-gatsby-starter-basic description: A simple custom basic Gatsby starter template to start a new website. tags: @@ -3419,7 +3419,7 @@ - Optimized images. - Offline capabilities. - Auto-generated sitemap and robots.txt. -- url: https://myclicks.netlify.com/ +- url: https://myclicks.netlify.app/ repo: https://github.com/himali-patel/MyClicks description: A simple Gatsby starter template to create portfolio website with contentful and Netlify. tags: @@ -3435,7 +3435,7 @@ - Contact form integration with Netlify. - Portfolio Result Filteration according to Category. - Index pages design with Recent Blogs and Intagram Feed. -- url: https://gatsby-starter-typescript-graphql.netlify.com +- url: https://gatsby-starter-typescript-graphql.netlify.app repo: https://github.com/spawnia/gatsby-starter-typescript-graphql description: A Gatsby starter with typesafe GraphQL using TypeScript tags: @@ -3448,7 +3448,7 @@ - Typesafe GraphQL with graphql-code-generator - ESLint with TypeScript support - Styling with styled-components -- url: https://gatsby-tailwind-serif.netlify.com/ +- url: https://gatsby-tailwind-serif.netlify.app/ repo: https://github.com/windedge/gatsby-tailwind-serif description: A Gatsby theme based on gatsby-serif-theme, rewrite with Tailwind CSS. tags: @@ -3460,7 +3460,7 @@ - Removes unused CSS with Purgecss - Responsive design - Suitable for small business website -- url: https://mystifying-mclean-5c7fce.netlify.com +- url: https://mystifying-mclean-5c7fce.netlify.app repo: https://github.com/renvrant/gatsby-mdx-netlify-cms-starter description: An extension of the default starter with Netlify CMS and MDX support. tags: @@ -3493,7 +3493,7 @@ - Offline support - Web App Manifest - SEO -- url: https://contentful-starter.netlify.com/ +- url: https://contentful-starter.netlify.app/ repo: https://github.com/algokun/gatsby_contentful_starter description: An Awesome Starter Kit to help you get going with Contentful and Gatsby tags: @@ -3539,7 +3539,7 @@ - Styling with SCSS - Offline support - Web App Manifest -- url: https://gatsby-all-in.netlify.com +- url: https://gatsby-all-in.netlify.app repo: https://github.com/Gherciu/gatsby-all-in description: A starter that includes the most popular js libraries, already pre-configured and ready for use. tags: @@ -3583,7 +3583,7 @@ - Styling with SCSS - Offline support - Web App Manifest -- url: https://gatsby-starter-krisp.netlify.com/ +- url: https://gatsby-starter-krisp.netlify.app/ repo: https://github.com/algokun/gatsby-starter-krisp description: A minimal, clean and responsive starter built with gatsby tags: @@ -3596,7 +3596,7 @@ - Styled-Components. - Mobile-First CSS. - Responsive Design, optimized for Mobile devices -- url: https://gatsby-datocms-starter.netlify.com/ +- url: https://gatsby-datocms-starter.netlify.app/ repo: https://github.com/brohlson/gatsby-datocms-starter description: An SEO-friendly DatoCMS starter with styled-components, page transitions, and out-of-the-box blog post support. tags: @@ -3609,7 +3609,7 @@ - Page Transitions - Blog Post Template - Sitemap & Robots.txt generation -- url: https://elemental.netlify.com/ +- url: https://elemental.netlify.app/ repo: https://github.com/akzhy/gatsby-starter-elemental description: A highly customizable portfolio starter with grid support. tags: @@ -3621,7 +3621,7 @@ - Portfolio Template - Blog Post Template - SEO Friendly -- url: https://gatsby-starter-apollo.netlify.com/ +- url: https://gatsby-starter-apollo.netlify.app/ repo: https://github.com/piducancore/gatsby-starter-apollo-netlify description: This project is an easy way to start developing fullstack apps with Gatsby and Apollo Server (using Netlify Lambda functions). For developing we use Netlify Dev to bring all of this magic to our local machine. tags: @@ -3630,7 +3630,7 @@ - Apollo Client - Apollo Server running on Netlify functions - Netlify Dev for local development -- url: https://gatsby-starter-blog-and-portfolio.netlify.com/ +- url: https://gatsby-starter-blog-and-portfolio.netlify.app/ repo: https://github.com/alisalahio/gatsby-starter-blog-and-portfolio description: Just gatsby-starter-blog, with portfolio section added tags: @@ -3683,7 +3683,7 @@ - Read Time and Progress - MDX support and inline code - Accessibility in Mind -- url: https://gatsby-starter-fashion-portfolio.netlify.com/ +- url: https://gatsby-starter-fashion-portfolio.netlify.app/ repo: https://github.com/shobhitchittora/gatsby-starter-fashion-portfolio description: A Gatsby starter for a professional and minimal fashion portfolio. tags: @@ -3698,7 +3698,7 @@ - Separate components for different pages and grid - Uses gatsby-image to load images - Built using the old school CSS. -- url: https://gatsby-theme-profile-builder.netlify.com/ +- url: https://gatsby-theme-profile-builder.netlify.app/ repo: https://github.com/ashr81/gatsby-theme-profile-builder description: Simple theme to build your personal portfolio and publish your articles using Contentful CMS. tags: @@ -3747,7 +3747,7 @@ - CSS based Modals - Content is fetched from JSON Files - Only one extra plugin from default Gatsby starter -- url: https://gatsby-starter-profile-site.netlify.com/ +- url: https://gatsby-starter-profile-site.netlify.app/ repo: https://github.com/Mr404Found/gatsby-starter-profile-site description: A minimal and clean starter build with gatsby. tags: @@ -3759,7 +3759,7 @@ features: - Simple Design - Made by Sumanth -- url: https://the404blog.netlify.com +- url: https://the404blog.netlify.app repo: https://github.com/algokun/the404blog description: An Awesome Starter Blog to help you get going with Gatsby and Markdown tags: @@ -3775,7 +3775,7 @@ - Includes Search Feature. - Syntax Highlight in Code. - Styling in Bootstrap -- url: https://gatsby-starter-unicorn.netlify.com/ +- url: https://gatsby-starter-unicorn.netlify.app/ repo: https://github.com/algokun/gatsby_starter_unicorn description: An Awesome Starter Blog to help you get going with Gatsby and Markdown tags: @@ -3788,7 +3788,7 @@ - Ready made Components - Responsive Design - Syntax Highlight in Code. -- url: https://gatsby-starter-organization.netlify.com/ +- url: https://gatsby-starter-organization.netlify.app/ repo: https://github.com/geocine/gatsby-starter-organization description: A Gatsby starter template for organization pages. Using the Gatsby theme "@geocine/gatsby-theme-organization" tags: @@ -3801,7 +3801,7 @@ - Theme UI and EmotionJS CSS-in-JS - A landing page with all your organization projects, configurable through a YML file. - Configurable logo, favicon, organization name and title -- url: https://gatsby-starter-interviews.netlify.com/ +- url: https://gatsby-starter-interviews.netlify.app/ repo: https://github.com/rmagon/gatsby-starter-interviews description: A Gatsby starter template for structured Q&A or Interview sessions tags: @@ -3814,7 +3814,7 @@ - Option to read all answers to a specific question - Share interview on social channels - All content in simple json files -- url: https://gatsby-starter-photo-book.netlify.com/ +- url: https://gatsby-starter-photo-book.netlify.app/ repo: https://github.com/baobabKoodaa/gatsby-starter-photo-book description: A Gatsby starter for sharing photosets. tags: @@ -3827,7 +3827,7 @@ - Beautiful "postcard" view for photos with fullscreen toggle. - Both views are responsive with minimal whitespace and polished UX. - Many performance optimizations for image delivery (both by Gatsby & way beyond what Gatsby can do). -- url: https://gatsby-typescript-scss-starter.netlify.com/ +- url: https://gatsby-typescript-scss-starter.netlify.app/ repo: https://github.com/GrantBartlett/gatsby-typescript-starter description: A simple starter project using TypeScript and SCSS tags: @@ -3837,7 +3837,7 @@ features: - Pages and components are classes. - A skeleton SCSS project added with prefixing -- url: https://portfolio-by-mohan.netlify.com/ +- url: https://portfolio-by-mohan.netlify.app/ repo: https://github.com/algokun/gatsby_starter_portfolio description: An Official Starter for Gatsby Tech Blog Theme tags: @@ -3848,7 +3848,7 @@ - Search using ElasticLunr - Theme by gatsby-tech-blog-theme - Deployed in Netlify -- url: https://brevifolia-gatsby-forestry.netlify.com/ +- url: https://brevifolia-gatsby-forestry.netlify.app/ repo: https://github.com/kendallstrautman/brevifolia-gatsby-forestry description: A minimal starter blog built with Gatsby & Forestry CMS tags: @@ -3863,7 +3863,7 @@ - Configured to work automatically with Forestry CMS - Customizable 'info' page - Simple layout & scss architecture, easily extensible -- url: https://gatsby-firebase-starter.netlify.com/ +- url: https://gatsby-firebase-starter.netlify.app/ repo: https://github.com/ovidiumihaibelciug/gatsby-firebase-starter description: Starter / Project Boilerplate for Authentication and creating Dynamic pages from collections with Firebase and Gatsby.js tags: @@ -3879,7 +3879,7 @@ - Email verification - Includes React Helmet to allow editing site meta tags - Includes plugins for offline support out of the box -- url: https://gatsby-typescript-minimal.netlify.com/ +- url: https://gatsby-typescript-minimal.netlify.app/ repo: https://github.com/benbarber/gatsby-typescript-minimal description: A minimal, bare-bones TypeScript starter for Gatsby tags: @@ -3894,7 +3894,7 @@ - Styled Components - Sitemap Generation - Google Analytics -- url: https://agility-gatsby-starter-gatsbycloud.netlify.com +- url: https://agility-gatsby-starter-gatsbycloud.netlify.app repo: https://github.com/agility/agility-gatsby-starter description: Get started with Gatsby and Agility CMS using a minimal blog. tags: @@ -3903,7 +3903,7 @@ - SEO features: - A bare-bones starter Blog to get you off and running with Agility CMS and Gatsby. -- url: https://gatsby-starter-dot.netlify.com/ +- url: https://gatsby-starter-dot.netlify.app/ repo: https://github.com/chronisp/gatsby-starter description: Gatsby Starter for creating portfolio & blog. tags: @@ -3935,7 +3935,7 @@ - React Scrollspy used to track page position - React Bootstrap used to create modal portfolio carousel - GitHub Actions deployment to GitHub Pages demonstrated -- url: https://bonneville.netlify.com/ +- url: https://bonneville.netlify.app/ repo: https://github.com/bagseye/bonneville description: A starter blog template for Gatsby tags: @@ -3945,7 +3945,7 @@ - Extensible & responsive design - Blog integration - SEO -- url: https://gatsby-starter-i18next-sanity.netlify.com/en +- url: https://gatsby-starter-i18next-sanity.netlify.app/en repo: https://github.com/johannesspohr/gatsby-starter-i18next-sanity description: A basic starter which integrates translations with i18next and localized sanity input. tags: @@ -3960,7 +3960,7 @@ - Alternate links to other languages - Sitemap with language information - Localized 404 pages -- url: https://gatsby-skeleton.netlify.com/ +- url: https://gatsby-skeleton.netlify.app/ repo: https://github.com/msallent/gatsby-skeleton description: Gatsby starter with TypeScript and all sort of linting tags: @@ -3974,7 +3974,7 @@ - Prettier - Stylelint - SEO -- url: https://nehalem.netlify.com/ +- url: https://nehalem.netlify.app/ repo: https://github.com/nehalist/gatsby-starter-nehalem description: A starter for the Gatsby Nehalem Theme tags: @@ -3995,7 +3995,7 @@ - Tagging - Theming - Customizable -- url: https://gatsby-starter-headless-wp.netlify.com +- url: https://gatsby-starter-headless-wp.netlify.app repo: https://github.com/crock/gatsby-starter-headless-wordpress description: A starter Gatsby site to quickly implement a site for headless WordPress tags: @@ -4006,7 +4006,7 @@ - New Header - Responsive - Sidebar that displays recent blog posts -- url: https://gatsby-advanced-blog-starter.netlify.com +- url: https://gatsby-advanced-blog-starter.netlify.app repo: https://github.com/aman29271/gatsby-advanced-blog-starter description: A pre-built Gatsby Starter Tech-blog tags: @@ -4032,7 +4032,7 @@ - Styling with SCSS - Offline support - Web App Manifest -- url: https://gatsby-starter-ts-hello-world.netlify.com +- url: https://gatsby-starter-ts-hello-world.netlify.app repo: https://github.com/hdorgeval/gatsby-starter-ts-hello-world description: TypeScript version of official hello world tags: @@ -4044,7 +4044,7 @@ - no boilerplate - Great for advanced users - VSCode ready -- url: https://grommet-file.netlify.com/ +- url: https://grommet-file.netlify.app/ repo: https://github.com/metinsenturk/gatsby-starter-grommet-file description: Grommet-File is made with Grommet V2 and a blog starter tags: @@ -4065,7 +4065,7 @@ - Mobile and responsive - Sitemap & Robots.txt generation - Optimized images with gatsby-image -- url: https://gatsby-wordpress-typescript-scss-blog.netlify.com/ +- url: https://gatsby-wordpress-typescript-scss-blog.netlify.app/ repo: https://github.com/sagar7993/gatsby-wordpress-typescript-scss-blog description: A Gatsby starter template for a WordPress blog, built using TypeScript, SCSS and Ant Design tags: @@ -4105,7 +4105,7 @@ - Git pre-commit and pre-push hooks using Husky - TSLint formatting - Highly optimized with excellent lighthouse audit score -- url: https://gatsby-starter-typescript-deluxe.netlify.com/ +- url: https://gatsby-starter-typescript-deluxe.netlify.app/ repo: https://github.com/gojutin/gatsby-starter-typescript-deluxe description: A Gatsby starter with TypeScript, Storybook, Styled Components, Framer Motion, Jest, and more. tags: @@ -4125,7 +4125,7 @@ - Jest and React Testing library for snapshots and unit tests. - ESLint (with TSLint and Prettier) to make your code look its best. - React Axe and React A11y for accessibility so that your site is awesome for everyone. -- url: https://gatsby-markdown-blog-starter.netlify.com/ +- url: https://gatsby-markdown-blog-starter.netlify.app/ repo: https://github.com/ammarjabakji/gatsby-markdown-blog-starter description: Gatsby v2 starter for creating a markdown blog. Based on Gatsby Advanced Starter. tags: @@ -4149,7 +4149,7 @@ - htaccess support - Typography.js - Integration with Social Media -- url: https://gatsby-starter-bloomer-db0aaf.netlify.com +- url: https://gatsby-starter-bloomer-db0aaf.netlify.app repo: https://github.com/zlutfi/gatsby-starter-bloomer description: Barebones starter website with Bloomer React components for Bulma. tags: @@ -4162,7 +4162,7 @@ - Uses SCSS for styling - Font Awesome Support - Progressive Web App -- url: https://gatsby-starter-mdbreact.netlify.com +- url: https://gatsby-starter-mdbreact.netlify.app repo: https://github.com/zlutfi/gatsby-starter-mdbreact description: Barebones starter website with Material Design Bootstrap React components. tags: @@ -4176,7 +4176,7 @@ - Uses SCSS for styling - Font Awesome Support - Progressive Web App -- url: https://gatsby-starter-ts-pwa.netlify.com/ +- url: https://gatsby-starter-ts-pwa.netlify.app/ repo: https://github.com/markselby9/gatsby-starter-typescript-pwa description: The default Gatsby starter fork with TypeScript and PWA support added tags: @@ -4186,7 +4186,7 @@ - Minimum changes based on default starter template for TypeScript and PWA - Added TypeScript support with eslint and tsc check - Support GitHub Actions CI/CD workflow (beta) -- url: https://iceberg-gatsby-multilang.netlify.com/ +- url: https://iceberg-gatsby-multilang.netlify.app/ repo: https://github.com/diogorodrigues/iceberg-gatsby-multilang description: Gatsby multi-language starter. Internationalization / i18n without third party plugins or packages for Posts and Pages. Different URLs dependending on the language. Focused on SEO, PWA, Image Optimization, Styled Components and more. This starter is also integrate with Netlify CMS to manage all pages, posts and images. tags: @@ -4211,7 +4211,7 @@ - Blog Posts list with pagination - Focus on SEO - PWA -- url: https://flexible-gatsby.netlify.com/ +- url: https://flexible-gatsby.netlify.app/ repo: https://github.com/wangonya/flexible-gatsby description: A simple and clean theme for Gatsby tags: @@ -4221,7 +4221,7 @@ - Google Analytics - Simple design - Markdown support -- url: https://gatsby-starter-leaflet.netlify.com/ +- url: https://gatsby-starter-leaflet.netlify.app/ repo: https://github.com/colbyfayock/gatsby-starter-leaflet description: A Gatsby starter with Leafet! tags: @@ -4234,7 +4234,7 @@ - Includes Leaflet and React Leaflet - Starts with some basic Sass stylesheets for styling - Linting and testing preconfigured -- url: https://gatsby-starter-luke.netlify.com/ +- url: https://gatsby-starter-luke.netlify.app/ repo: https://github.com/lukethacoder/luke-gatsby-starter description: An opinionated starter using TypeScript, styled-components (emotion flavoured), React Hooks & react-spring. Built as a BYOS (bring your own source) so you can get up and running with whatever data you choose. tags: @@ -4249,7 +4249,7 @@ - Emotion for styling components - Minimal Design - React Hooks (IntersectionObserver, KeyUp, LocalStorage) -- url: https://friendly-cray-96d631.netlify.com/ +- url: https://friendly-cray-96d631.netlify.app/ repo: https://github.com/PABlond/Gatsby-TypeScript-Starter-Blog description: Project boilerplate of a blog app. The starter was built using Gatsby and TypeScript. tags: @@ -4263,7 +4263,7 @@ - Easy editable posts in Markdown files - SEO component - Optimized with Google Lighthouse -- url: https://gatsby-starter-material-album.netlify.com +- url: https://gatsby-starter-material-album.netlify.app repo: https://github.com/JoeTrubenstein/gatsby-starter-material-album description: A simple portfolio starter based on the Material UI Album Layout tags: @@ -4274,7 +4274,7 @@ - Pagination - Material UI - Exif Data Parsing -- url: https://peaceful-ptolemy-d7beb4.netlify.com +- url: https://peaceful-ptolemy-d7beb4.netlify.app repo: https://github.com/TRamos5/gatsby-contentful-starter description: A starter template for an awesome static blog utilizing Contentful as a CMS and deployed to Netlify. tags: @@ -4299,11 +4299,11 @@ - Styling:PostCSS features: - Tailwind CSS for rapid development - - Emotion with `tailwind.macro` for flexible styled components - - PostCSS configured out-of-the-box for when you need to write your own CSS + - Emotion with `twin.macro` for flexible styled components + - PostCSS configured out-of-the-box to write your own custom CSS - postcss-preset-env to write tomorrow's CSS today - Bare bones starter to help you hit the ground running -- url: https://gatsby-starter-grayscale-promo.netlify.com/ +- url: https://gatsby-starter-grayscale-promo.netlify.app/ repo: https://github.com/gannochenko/gatsby-starter-grayscale-promo description: one-page promo site tags: @@ -4319,7 +4319,7 @@ - NetlifyCMS - TypeScript - Basic design -- url: https://gatsby-starter-mdx-website-blog.netlify.com/ +- url: https://gatsby-starter-mdx-website-blog.netlify.app/ repo: https://github.com/doakheggeness/gatsby-starter-mdx-website-blog description: Gatsby website and blog starter utilizing MDX for adding components to mdx pages and posts. Incorportates Emotion. tags: @@ -4330,7 +4330,7 @@ - Create pages and posts using MDX - Incorporates the CSS-in-JS library Emotion - Visual effects -- url: https://gatsby-starter-zurgbot.netlify.com/ +- url: https://gatsby-starter-zurgbot.netlify.app/ repo: https://github.com/zurgbot/gatsby-starter-zurgbot description: The ultimate force of starter awesomeness in the galaxy of Gatsby tags: @@ -4367,7 +4367,7 @@ - Graphql queries - Sass - Markdown -- url: https://wataruoguchi-gatsby-starter-typescript-contentful.netlify.com/ +- url: https://wataruoguchi-gatsby-starter-typescript-contentful.netlify.app/ repo: https://github.com/wataruoguchi/gatsby-starter-typescript-contentful description: Simple TypeScript starter with Contentful Integration tags: @@ -4382,7 +4382,7 @@ - Supports Contentful Rich Text - Prettier & ESlint & StyleLint to format & check the code - Husky & lint-staged to automate checking -- url: https://gatsby-starter-point.netlify.com/ +- url: https://gatsby-starter-point.netlify.app/ repo: https://github.com/teaware/gatsby-starter-point description: A humble Gatsby starter for blog tags: @@ -4394,7 +4394,7 @@ - SEO - Dark Mode - Google Analytics -- url: https://gatsby-typescript-storybook-starter.netlify.com/ +- url: https://gatsby-typescript-storybook-starter.netlify.app/ repo: https://github.com/RobertoMSousa/gatsby-typescript-storybook-starter description: A Gatsby starter with storybook, tags and eslint tags: @@ -4412,7 +4412,7 @@ - Storybook - Jest and React Testing library for snapshots and unit tests. - Styled-Components for all your styles. -- url: https://semantic-ui-docs-gatsby.netlify.com/ +- url: https://semantic-ui-docs-gatsby.netlify.app/ repo: https://github.com/whoisryosuke/semantic-ui-docs-gatsby description: Documentation starter using Semantic UI and MDX tags: @@ -4432,7 +4432,7 @@ - Responsive design - Nodemon for restarting dev server on changes - webpack aliasing for components, assets, etc -- url: https://gatsby-starter-saas-marketing.netlify.com/ +- url: https://gatsby-starter-saas-marketing.netlify.app/ repo: https://github.com/keegn/gatsby-starter-saas-marketing description: A simple one page marketing site starter for SaaS companies and products tags: @@ -4445,7 +4445,7 @@ - Styled-Components - Minimal design and easy to customize - Great for software or product related marketing sites -- url: https://react-landnig-page.netlify.com/ +- url: https://react-landnig-page.netlify.app/ repo: https://github.com/zilahir/react-landing-page description: Landing page with GraphCMS tags: @@ -4462,7 +4462,7 @@ - Good for app showcase for startups - Prettier & ESlint & StyleLint to format & check the code - Husky & lint-staged to automate checking -- url: https://gatsby-strapi-starter.netlify.com/ +- url: https://gatsby-strapi-starter.netlify.app/ repo: https://github.com/jeremylynch/gatsby-strapi-starter description: Get started with Strapi, Bootstrap (reactstrap) and Gatsby FAST! tags: @@ -4472,7 +4472,7 @@ - Strapi - Bootstrap - Reactstrap -- url: https://kontent-template-gatsby-landing-page-photon.netlify.com +- url: https://kontent-template-gatsby-landing-page-photon.netlify.app repo: https://github.com/Simply007/kontent-template-gatsby-landing-page-photon description: Kentico Kontent based starter based on Photon starter by HTML5 UP tags: @@ -4492,7 +4492,7 @@ - Font awesome - Material Icons - CSS Grid -- url: https://gatsby-starter-typescript-blog-forms.netlify.com/ +- url: https://gatsby-starter-typescript-blog-forms.netlify.app/ repo: https://github.com/joerneu/gatsby-starter-typescript-blog-forms description: Gatsby starter for a website in TypeScript with a homepage, blog and forms tags: @@ -4516,7 +4516,7 @@ - Accessible UI components implemented with Reakit and styling based on mini.css - Netlify CMS to create and edit blog posts - Small bundle size -- url: https://gatsby-tailwind-styled-components-storybook-starter.netlify.com/ +- url: https://gatsby-tailwind-styled-components-storybook-starter.netlify.app/ repo: https://github.com/denvash/gatsby-tailwind-styled-components-storybook-starter description: Tailwind CSS + Styled-Components + Storybook starter for Gatsby tags: @@ -4532,7 +4532,7 @@ - PostCSS - Deploy Storybook - Documentation -- url: https://gatsby-tfs-starter.netlify.com/ +- url: https://gatsby-tfs-starter.netlify.app/ repo: https://github.com/tiagofsanchez/gatsby-tfs-starter description: a gatsby-advanced-starter with Theme UI styling tags: @@ -4562,7 +4562,7 @@ - Built with PostCSS - Made for image-centric portfolios - Based on London for Gatsby -- url: https://alipiry-gatsby-starter-typescript.netlify.com/ +- url: https://alipiry-gatsby-starter-typescript.netlify.app/ repo: https://github.com/alipiry/gatsby-starter-typescript description: The default Gatsby starter with TypeScript tags: @@ -4572,7 +4572,7 @@ features: - Type Checking With TypeScript - Powerful Linting With ESLint -- url: https://gatsby-typescript-tailwind.netlify.com/ +- url: https://gatsby-typescript-tailwind.netlify.app/ repo: https://github.com/impulse/gatsby-typescript-tailwind description: Gatsby starter with TypeScript and Tailwind CSS tags: @@ -4598,7 +4598,7 @@ - Based on the official Gatsby starter blog - Uses Tailwind CSS - Uses PostCSS -- url: https://gatsby-minimalist-starter.netlify.com/ +- url: https://gatsby-minimalist-starter.netlify.app/ repo: https://github.com/dylanesque/Gatsby-Minimalist-Starter description: A minimalist, general-purpose Gatsby starter tags: @@ -4610,7 +4610,7 @@ - Layout.css includes checklist of initial design system decisions to make - Uses Emotion - Uses CSS-In-JS -- url: https://gastby-starter-zeevo.netlify.com/ +- url: https://gastby-starter-zeevo.netlify.app/ repo: https://github.com/zeevosec/gatsby-starter-zeevo description: Yet another Blog starter with a different style tags: @@ -4638,7 +4638,7 @@ - Customizable with Tailwind CSS - Code highlighting with Prism - RSS feed -- url: https://gatsby-starter-landed.netlify.com/ +- url: https://gatsby-starter-landed.netlify.app/ repo: https://github.com/vasrush/gatsby-starter-landed description: A Gatsby theme based on Landed template by HTML5UP tags: @@ -4660,7 +4660,7 @@ - Left, Right and no sidebar templates - Font awesome icons - HTML5UP Design -- url: https://tina-starter-grande.netlify.com/ +- url: https://tina-starter-grande.netlify.app/ repo: https://github.com/tinacms/tina-starter-grande description: Feature rich Gatsby starter with full TinaCMS integration tags: @@ -4677,7 +4677,7 @@ - Styled Components - Code syntax highlighting - Light/Dark mode -- url: https://amelie-blog.netlify.com/ +- url: https://amelie-blog.netlify.app/ repo: https://github.com/tobyau/gatsby-starter-amelie description: A minimal and mobile friendly blog template tags: @@ -4701,7 +4701,7 @@ - Linting features: - Starter for Chronoblog Gatsby Theme -- url: https://gatsby-eth-dapp-starter.netlify.com +- url: https://gatsby-eth-dapp-starter.netlify.app repo: https://github.com/robsecord/gatsby-eth-dapp-starter description: Gatsby Starter for Ethereum Dapps using Web3 with Multiple Account Management Integrations tags: @@ -4731,7 +4731,7 @@ - 🏗 Unified Theme and Layout - 🆙 Easy customized header nav - 🧩 Built-in home page components -- url: https://gatsby-starter-cafe.netlify.com +- url: https://gatsby-starter-cafe.netlify.app repo: https://github.com/crolla97/gatsby-starter-cafe description: Gatsby starter for creating a single page cafe website using Contentful and Leaflet tags: @@ -4744,7 +4744,7 @@ - Instagram Feed - Contentful for menu item storage - Responsive design -- url: https://gatsby-firebase-simple-auth.netlify.com/ +- url: https://gatsby-firebase-simple-auth.netlify.app/ repo: https://github.com/marcomelilli/gatsby-firebase-simple-auth description: A simple Firebase Authentication Starter with protected routes tags: @@ -4773,7 +4773,7 @@ - Optimized images with gatsby-image. - SEO - A11y -- url: https://keturah.netlify.com/ +- url: https://keturah.netlify.app/ repo: https://github.com/giocare/gatsby-starter-keturah description: A portfolio starter for developers tags: @@ -4800,7 +4800,7 @@ - Landing Page Design - Fully Responsive - Styling with Tailwind -- url: https://gatsby-starter-papan01.netlify.com/ +- url: https://gatsby-starter-papan01.netlify.app/ repo: https://github.com/papan01/gatsby-starter-papan01 description: A Gatsby starter for creating a markdown blog. tags: @@ -4916,7 +4916,7 @@ - MDX for pages and content - Code syntax highlighting - SEO (OpenGraph and Twitter) out of the box with default settings that make sense (thanks to React Helmet) -- url: https://gatsby-starter-tailwind2-emotion-styled-components.netlify.com/ +- url: https://gatsby-starter-tailwind2-emotion-styled-components.netlify.app/ repo: https://github.com/chrish-d/gatsby-starter-tailwind2-emotion-styled-components description: A (reasonably) unopinionated Gatsby starter, including; Tailwind 2 and Emotion. Use Tailwind utilities with Emotion powered CSS-in-JS to produce component scoped CSS (no need for utilities like Purge CSS, etc). tags: @@ -4928,7 +4928,7 @@ - Only compiles the CSS you use (no need to use PurgeCSS/similar). - Automatically gives you Critical CSS with inline stlyes. - Hybrid of PostCSS and CSS-in-JS to give you Tailwind base styles. -- url: https://5e0a570d6afb0ef0fb162f0f--wizardly-bassi-e4658f.netlify.com/ +- url: https://5e0a570d6afb0ef0fb162f0f--wizardly-bassi-e4658f.netlify.app/ repo: https://github.com/adamistheanswer/gatsby-starter-baysik-blog description: A basic and themeable starter for creating blogs in Gatsby. tags: @@ -4951,7 +4951,7 @@ - MDX for pages and content - Code syntax highlighting - SEO (OpenGraph and Twitter) out of the box with default settings that make sense (thanks to React Helmet) -- url: https://gatsby-starter-robin.netlify.com/ +- url: https://gatsby-starter-robin.netlify.app/ repo: https://github.com/robinmetral/gatsby-starter-robin description: Gatsby Default Starter with state-of-the-art tooling tags: @@ -5002,7 +5002,7 @@ - 📓 Steps for deploying to Gh-pages - ✔️ CI with TravisCI - ⚡ Steps for deploying to GitHub Pages, AWS S3, or Netlify. -- url: https://gatsby-resume-starter.netlify.com/ +- url: https://gatsby-resume-starter.netlify.app/ repo: https://github.com/barancezayirli/gatsby-starter-resume-cms description: Resume starter styled using Tailwind with Netlify CMS as headless CMS. tags: @@ -5020,7 +5020,7 @@ - Basic SEO, site metadata - Prettier - Social media links -- url: https://gatsby-starter-default-nostyles.netlify.com/ +- url: https://gatsby-starter-default-nostyles.netlify.app/ repo: https://github.com/JuanJavier1979/gatsby-starter-default-nostyles description: The default Gatsby starter with no styles. tags: @@ -5040,7 +5040,7 @@ - includes Storybook - Full TypeScript support - Uses styled-components Global Styles API for consistency in styling across application and Storybook -- url: https://gatsby-simplefolio.netlify.com/ +- url: https://gatsby-simplefolio.netlify.app/ repo: https://github.com/cobidev/gatsby-simplefolio description: A clean, beautiful and responsive portfolio template for Developers ⚡️ tags: @@ -5056,7 +5056,7 @@ - Configurable color scheme - OnePage portfolio site - Fast image optimization -- url: https://gatsby-starter-hpp.netlify.com/ +- url: https://gatsby-starter-hpp.netlify.app/ repo: https://github.com/hppRC/gatsby-starter-hpp description: All in one Gatsby skeleton based TypeScript, emotion, and unstated-next. tags: @@ -5076,7 +5076,7 @@ - Advanced SEO components(ex. default twitter ogp image, sitemaps, robot.txt) - Prettier, ESLint - unstated-next(useful easy state library) -- url: https://gatsby-typescript-emotion-storybook.netlify.com/ +- url: https://gatsby-typescript-emotion-storybook.netlify.app/ repo: https://github.com/duncanleung/gatsby-typescript-emotion-storybook description: Config for TypeScript + Emotion + Storybook + React Intl + SVGR + Jest. tags: @@ -5095,7 +5095,7 @@ - 🖼️ SVG support with SVGR - 📝 Unit and integration testing with Jest and react-testing-library - ⚡ CD with Netlify -- url: https://felco-gsap.netlify.com +- url: https://felco-gsap.netlify.app repo: https://github.com/AshfaqKabir/Felco-Gsap-Gatsby-Starter description: Minimal Multipurpose Gsap Gatsby Landing Page. Helps Getting Started With Gsap and Netlify Forms. tags: @@ -5109,7 +5109,7 @@ - Styled Components for responsive component based styling with theming - Basic SEO, site metadata - Prettier -- url: https://gatsby-starter-fusion-blog.netlify.com/ +- url: https://gatsby-starter-fusion-blog.netlify.app/ repo: https://github.com/robertistok/gatsby-starter-fusion-blog description: Easy to configure blog starter with modern, minimal theme tags: @@ -5141,7 +5141,7 @@ - Complete header - Homepage and service templates pages ready to use - Meta tags for improved SEO with React Helmet -- url: https://gatsby-starter-webcomic.netlify.com +- url: https://gatsby-starter-webcomic.netlify.app repo: https://github.com/JLDevOps/gatsby-starter-webcomic description: Gatsby blog starter that focuses on webcomics and art with a minimalistic UI. tags: @@ -5161,7 +5161,7 @@ - Pagination between blog posts - Has a "archive" page that categorizes and displays all the blog posts by date - Mobile friendly -- url: https://gatsby-starter-material-emotion.netlify.com +- url: https://gatsby-starter-material-emotion.netlify.app repo: https://github.com/liketurbo/gatsby-starter-material-emotion description: Gatsby starter of Material-UI with Emotion 👩‍🎤 tags: @@ -5190,7 +5190,7 @@ - SEO and Open graphs support - Color modes - Code Highlighting -- url: https://london-night-day.netlify.com/ +- url: https://london-night-day.netlify.app/ repo: https://github.com/jooplaan/gatsby-london-night-and-day description: A custom, image-centric dark and light mode aware theme for Gatsby. Advanced from the Gatsby starter London After Midnight. tags: @@ -5210,7 +5210,7 @@ - Using the London After Midnight is now “Dark mode” (the default), and the original London as “Light mode”. - Removed Google Fonts, using system fonts in stead (for speed and privacy :) - Use SASS -- url: https://the-gatsby-bootcamp-blog.netlify.com +- url: https://the-gatsby-bootcamp-blog.netlify.app repo: https://github.com/SafdarJamal/gatsby-bootcamp-blog description: A minimal blogging site built with Gatsby using Contentful and hosted on Netlify. tags: @@ -5243,7 +5243,7 @@ - SEO optimized to include social media images and Twitter handles - Tight integration with SANITY.io including a predefined content studio. - A full tutorial is available in the docs. -- url: https://rocketdocs.netlify.com/ +- url: https://rocketdocs.netlify.app/ repo: https://github.com/Rocketseat/gatsby-starter-rocket-docs description: Out of the box Gatsby Starter for creating documentation websites easily and quickly. tags: @@ -5263,7 +5263,7 @@ - Custom docs schema; - Offline Support & WebApp Manifest; - Yaml-based sidebar navigation; -- url: https://gatsby-starter-typescript-default.netlify.com/ +- url: https://gatsby-starter-typescript-default.netlify.app/ repo: https://github.com/lianghx-319/gatsby-starter-typescript-default description: Only TypeScript Gatsby starter base on Default starter tags: @@ -5289,7 +5289,7 @@ - SEO optimized to include social media images and Twitter handles. - React Scroll for one page, anchor based navigation is available. - Code highlighting via Prism. -- url: https://gatsby-starter-default-dark-mode.netlify.com/ +- url: https://gatsby-starter-default-dark-mode.netlify.app/ repo: https://github.com/alexandreramosdev/gatsby-starter-default-dark-mode description: A simple starter to get developing quickly with Gatsby, dark mode, and styled-components. tags: @@ -5301,7 +5301,7 @@ - Styled Components - Comes with React Helmet for adding site meta tags - Includes plugins for offline support out of the box -- url: https://eager-memento.netlify.com/ +- url: https://eager-memento.netlify.app/ repo: https://github.com/Mr404Found/gatsby-memento-blogpost description: A responsive gatsby portfolio starter to show off or to flex your skills in a single page tags: @@ -5313,7 +5313,7 @@ - React Bootstrap - Responsive webpage - TypeWriter Effect -- url: https://gatsby-starter-wilde-creations.netlify.com/ +- url: https://gatsby-starter-wilde-creations.netlify.app/ repo: https://github.com/georgewilde/gatsby-starter-wilde-creations description: Barebones starter with a minimal number of components to kick off a TypeScript and Styled Components project. tags: @@ -5340,7 +5340,7 @@ - ✔️ Responsive design - ✔️ Netlify Deployment Friendly - ✔️ Highly optimized (Lighthouse score 4 x 100) -- url: https://gatsby-starter-typescript-deploy.netlify.com/ +- url: https://gatsby-starter-typescript-deploy.netlify.app/ repo: https://github.com/jongwooo/gatsby-starter-typescript description: TypeScript version of the default Gatsby starter🔮 tags: @@ -5354,7 +5354,7 @@ - Prettier code formatting - Jest for testing - Deploy to Netlify through GitHub Actions -- url: https://answer.netlify.com/ +- url: https://answer.netlify.app/ repo: https://github.com/passwd10/gatsby-starter-answer description: A simple Gatsby blog to show your Future Action on top of the page tags: @@ -5369,7 +5369,7 @@ - Disqus - Resume - Place plan on the top -- url: https://gatsby-portfolio-starter.netlify.com/ +- url: https://gatsby-portfolio-starter.netlify.app/ repo: https://github.com/Judionit/gatsby-portfolio-starter description: A simple Gatsby portfolio starter tags: @@ -5381,7 +5381,7 @@ - Styled components - Responsive webpage - Portfolio -- url: https://wp-graphql-gatsby-starter.netlify.com/ +- url: https://wp-graphql-gatsby-starter.netlify.app/ repo: https://github.com/n8finch/wp-graphql-gatsby-starter description: A super simple, bare-bone starter based on the Gatsby Starter for the front end and the WP GraphQL plugin on your WordPress install. This is a basic "headless CMS" setup. This starter will pull posts, pages, categories, tags, and a menu from your WordPress site. You should use either the TwentyNineteen or TwentyTwenty WordPress themes on your WordPress install. See the starter repo for more detailed instructions on getting set up. The example here uses the WordPress Theme Unit Test Data for post and page dummy content. Find something wrong? Issues are welcome on the starter reository. tags: @@ -5396,7 +5396,7 @@ - Integrated navigation - Verbose (i.e., not D.R.Y.) GraphQL queries to get data from - Includes plugins for offline support out of the box -- url: https://gatsby-starter-docz-netlifycms.netlify.com/ +- url: https://gatsby-starter-docz-netlifycms.netlify.app/ repo: https://github.com/colbyfayock/gatsby-starter-docz-netlifycms description: Quickly deploy Docz documentation powered by Netlify CMS! tags: @@ -5406,7 +5406,7 @@ features: - Docz documentation powered by Gatsby - Netlify CMS to manage content -- url: https://keanu-pattern.netlify.com/ +- url: https://keanu-pattern.netlify.app/ repo: https://github.com/Mr404Found/gatsby-keanu-blog description: A responsive and super simple gatsby portfolio starter and extendable for blog also used yaml parsing tags: @@ -5422,7 +5422,7 @@ - Gatsby - yaml parsing - Automatic page Generation by adding content -- url: https://gatsby-contentful-portfolio-blog.netlify.com/ +- url: https://gatsby-contentful-portfolio-blog.netlify.app/ repo: https://github.com/escapemanuele/gatsby-contentful-blog-portfolio description: Simple gatsby starter for integration with Contentful. The result is a clean and nice website for businesses or freelancers with a blog and a portfolio. tags: @@ -5439,7 +5439,7 @@ - Blog - Testing - PWA -- url: https://example-site-for-square-starter.netlify.com/ +- url: https://example-site-for-square-starter.netlify.app/ repo: https://github.com/jonniebigodes/example-site-for-square-starter description: A barebones starter to help you kickstart your next Gatsby project with Square payments tags: @@ -5451,7 +5451,7 @@ - Serverless - Gatsby - Square -- url: https://gatsby-animate.netlify.com/ +- url: https://gatsby-animate.netlify.app/ repo: https://github.com/Mr404Found/gatsby-animate-starter description: A responsive and super simple gatsby starter with awesome animations to components and to build your online solutions website. stay tuned more features coming soon tags: @@ -5468,7 +5468,7 @@ - yaml parsing - Component Animations - ReactReveal Library -- url: https://gatsby-starter-instagram-baseweb.netlify.com/ +- url: https://gatsby-starter-instagram-baseweb.netlify.app/ repo: https://github.com/timrodz/gatsby-starter-instagram-baseweb description: 🎢 A portfolio based on your latest Instagram posts, implemented with the Base Web Design System by Uber. It features out-of-the-box responsive layouts, easy-to-implement components and CSS-in-JS styling. tags: @@ -5487,7 +5487,7 @@ - Simple React functional components (FC). - Google Analytics ready. - Continuous deployment via Netlify or Vercel. -- url: https://gatsby-starter-mountain.netlify.com/ +- url: https://gatsby-starter-mountain.netlify.app/ repo: https://github.com/artezan/gatsby-starter-mountain description: Blog theme that combine the new powerful MDX with the old WordPress. Built with WP/MDX and Theme UI tags: @@ -5509,7 +5509,7 @@ - Light/Dark mode - CSS Animations - Mountain style -- url: https://gatsby-starter-redux-storybook.netlify.com/ +- url: https://gatsby-starter-redux-storybook.netlify.app/ repo: https://github.com/fabianunger/gatsby-starter-redux-storybook description: Gatsby Starter that has Redux (persist) and Storybook implemented. tags: @@ -5541,7 +5541,7 @@ - Offline support - Google Analytics support - Disqus Comments support -- url: https://gatsby-starter-typescript-themes.netlify.com/ +- url: https://gatsby-starter-typescript-themes.netlify.app/ repo: https://github.com/room-js/gatsby-starter-typescript-themes description: Gatsby TypeScript starter with light/dark themes based on CSS variables tags: @@ -5564,7 +5564,7 @@ - Utilizing Notion as a CMS - Fully Responsive - Styling with SCSS -- url: https://sumanth.netlify.com/ +- url: https://sumanth.netlify.app/ repo: https://github.com/Mr404Found/gatsby-sidedrawer description: A responsive and super simple gatsby site with awesome navbar and stay tuned more features coming soon tags: @@ -5623,7 +5623,7 @@ - Disqus - Breadcrumbs - ESLint -- url: https://barcadia.netlify.com/ +- url: https://barcadia.netlify.app/ repo: https://github.com/bagseye/barcadia description: A super-fast site using Gatsby tags: @@ -5636,7 +5636,7 @@ - Responsive webpage - Portfolio - Blog -- url: https://gatsby-starter-clean-resume.netlify.com/ +- url: https://gatsby-starter-clean-resume.netlify.app/ repo: https://github.com/masoudkarimif/gatsby-starter-clean-resume description: A Gatsby Starter Template for Putting Your Resume Online Super Quick! tags: @@ -5654,7 +5654,7 @@ - Five different themes (great-gatsby, master-yoda, wonder-woman, darth-vader, luke-lightsaber) - Includes React Helmet for title and description tags - Includes Google Analytics plugin -- url: https://gatsby-starter-i18n-bulma.netlify.com +- url: https://gatsby-starter-i18n-bulma.netlify.app repo: https://github.com/kalwalt/gatsby-starter-i18n-bulma description: A gatsby starter with Bulma and optimized slug for better SEO. tags: @@ -5679,8 +5679,8 @@ - Robots.txt - Sitemap - PWA -- url: https://gatsby-attila.netlify.com/ - repo: https://github.com/armada-inc/gatsby-attila-theme-starter +- url: https://ghost-attila-preview.draftbox.co/ + repo: https://github.com/draftbox-co/gatsby-attila-theme-starter description: A Gatsby starter for creating blogs from headless Ghost CMS. tags: - Blog @@ -5701,7 +5701,7 @@ - Offline Support - RSS Feed - Composable and extensible -- url: https://gatsby-contentful-portfolio.netlify.com/ +- url: https://gatsby-contentful-portfolio.netlify.app/ repo: https://github.com/wkocjan/gatsby-contentful-portfolio description: Gatsby portfolio theme integrated with Contentful tags: @@ -5721,7 +5721,7 @@ - SEO optimized - OpenGraph structured data - Integration with Mailchimp -- url: https://gatsby-graphcms-ecommerce-starter.netlify.com +- url: https://gatsby-graphcms-ecommerce-starter.netlify.app repo: https://github.com/GraphCMS/gatsby-graphcms-ecommerce-starter description: Swag store built with GraphCMS, Stripe, Gatsby, Postmark and Printful. tags: @@ -5737,7 +5737,7 @@ - Custom GraphQL API for handling checkout and payment - Postmark for order notifications - Strong Customer Authentication -- url: https://koop-blog.netlify.com/ +- url: https://koop-blog.netlify.app/ repo: https://github.com/bagseye/koop-blog description: A simple blog platform using Gatsby and MDX tags: @@ -5770,7 +5770,7 @@ - SEO + Sitemap + RSS - Googly Analytics Support - Easy & Highly Customizable -- url: https://gatsby-airtable-listing.netlify.com/ +- url: https://gatsby-airtable-listing.netlify.app/ repo: https://github.com/wkocjan/gatsby-airtable-listing description: Airtable theme for Gatsby tags: @@ -5787,7 +5787,7 @@ - SEO optimized - Robots.txt - OpenGraph structured data -- url: https://gatsby-starter-personality.netlify.com/ +- url: https://gatsby-starter-personality.netlify.app/ repo: https://github.com/matheusquintaes/gatsby-starter-personality description: A free responsive Gatsby Starter tags: @@ -5812,7 +5812,7 @@ - includes an Airtable form to collect local submissions and add them to Airtable for approval - can be personalized to a city or region without touching a line of code - one-click deployment via Netlify -- url: https://shards-gatsby-starter.netlify.com/ +- url: https://shards-gatsby-starter.netlify.app/ repo: https://github.com/wcisco17/gatsby-typescript-shards-starter description: Portfolio with TypeScript and Shards UI tags: @@ -5846,7 +5846,7 @@ - TypeScript for easier debugging and development, strict types, etc - Netlify for hosting - SEO Capabilities -- url: https://serene-ramanujan-285722.netlify.com/ +- url: https://serene-ramanujan-285722.netlify.app/ repo: https://github.com/kunalJa/gatsby-starter-math-blog description: A responsive math focused blog with MDX and Latex built in tags: @@ -5864,7 +5864,7 @@ - Storybook with tested components included - Uses Tachyons for styling - Easy to create new posts -- url: https://gatsby-starter-canada-pandemic.netlify.com/ +- url: https://gatsby-starter-canada-pandemic.netlify.app/ repo: https://github.com/masoudkarimif/gatsby-starter-canada-pandemic description: A Gatsby starter template for covering pandemics in Canada tags: @@ -5891,7 +5891,7 @@ - Lots of built-in templates, widgets, or bring in your own custom components. - Uses @builder.io/gatsby plugin to dynamically create pages published on the editor. - SEO -- url: https://gatsby-starter-reason-blog.netlify.com/ +- url: https://gatsby-starter-reason-blog.netlify.app/ repo: https://github.com/mukul-rathi/gatsby-starter-reason-blog description: The Gatsby Starter Blog using ReasonML! tags: @@ -5921,7 +5921,7 @@ - Automatic Linting on Commit using husky and pretty-quick - Custom server to test Production Builds on your local network via Vercel/serve - Extensive Readme in the repo -- url: https://gatsby-redux-toolkit-typescript.netlify.com/ +- url: https://gatsby-redux-toolkit-typescript.netlify.app/ repo: https://github.com/saimirkapaj/gatsby-redux-toolkit-typescript-starter description: Gatsby Starter using Redux-Toolkit, TypeScript, Styled Components and Tailwind CSS. tags: @@ -5940,7 +5940,7 @@ - SEO - React Helmet - Offline Support -- url: https://gatsby-ts-tw-styled-eslint.netlify.com +- url: https://gatsby-ts-tw-styled-eslint.netlify.app repo: https://github.com/Miloshinjo/gatsby-ts-tw-styled-eslint-starter description: Gatsby starter with TypeScript, Tailwind CSS, @emotion/styled and eslint. tags: @@ -5963,7 +5963,7 @@ - Uses react-bootstrap, sass, and little else - Skeleton starter, based on gatsby-starter-default - Optional easy integration of themes from Bootswatch.com -- url: https://gatsby-starter-songc.netlify.com/ +- url: https://gatsby-starter-songc.netlify.app/ repo: https://github.com/FFM-TEAM/gatsby-starter-song description: A Gatsby starter for blog style with fresh UI. tags: @@ -5980,7 +5980,7 @@ - Post side PostTOC - Simple fresh design like Medium - Readability -- url: https://gatsby-starter-kontent-lumen.netlify.com/ +- url: https://gatsby-starter-kontent-lumen.netlify.app/ repo: https://github.com/Kentico/gatsby-starter-kontent-lumen description: A minimal, lightweight, and mobile-first starter for creating blogs uses Gatsby and Kentico Kontent CMS. Inspired by Lumen. tags: @@ -6000,7 +6000,7 @@ - Stylesheet built using Sass and BEM-Style naming. - Syntax highlighting in code blocks. - Google Analytics support. -- url: https://dindim-production.netlify.com/ +- url: https://dindim-production.netlify.app/ repo: https://github.com/lorenzogm/gatsby-ecommerce-starter description: Gatsby starter to create an ecommerce website with netlify and stripe. Setup and release your shop in a few minutes. tags: @@ -6293,7 +6293,7 @@ - PurgeCSS support to remove unused styles - PostCSS including Autoprefixer - React Helmet for better SEO -- url: https://wordpress-balsa.draftbox.co/ +- url: https://wp-balsa-preview.draftbox.co/ repo: https://github.com/draftbox-co/gatsby-wordpress-balsa-starter description: A Gatsby starter for creating blogs from headless WordPress CMS. tags: @@ -6648,3 +6648,15 @@ - The default Gatsby formatting tool Prettier, has been removed in order to avoid conflicts with the ESLint + AirBnB TypeScript tools described above. - Firebase Hosting is supported and configured for Gatsby from the start. - Dynamic pages for blog posts in markdown is implemented. +- url: https://gatsby-starter-woo.surge.sh/ + repo: https://github.com/desmukh/gatsby-starter-woo + description: Simple, clean and responsive landing page for your product or service. This is a GatsbyJS port of StyleShout's Woo template. + tags: + - Landing Page + - Onepage + - Portfolio + features: + - Ported from StyleShout Woo theme + - Fully responsive + - Includes React Helmet to allow editing site meta tags + - All landing page content can be customised through YAML files stored in content folder and in gatsby-config.js diff --git a/docs/tutorial/blog-netlify-cms-tutorial/index.md b/docs/tutorial/blog-netlify-cms-tutorial/index.md index 818019263fe57..af97b321007a7 100644 --- a/docs/tutorial/blog-netlify-cms-tutorial/index.md +++ b/docs/tutorial/blog-netlify-cms-tutorial/index.md @@ -64,7 +64,7 @@ git remote add origin https://github.com/[your-username]/[your-repo-name].git git push -u origin master ``` -Then, open [app.netlify.com](http://app.netlify.com) and add a "New site from Git". Choose your newly created repo and click on "Deploy site" with the default deployment settings. +Then, open [app.netlify.com](https://app.netlify.com) and add a "New site from Git". Choose your newly created repo and click on "Deploy site" with the default deployment settings. > _Note: if you don't see the correct repo listed, you may need to install or reconfigure the Netlify app on GitHub._ diff --git a/docs/tutorial/e-commerce-with-datocms-and-snipcart/index.md b/docs/tutorial/e-commerce-with-datocms-and-snipcart/index.md index 1abffc22d87c8..44ccda1632f48 100644 --- a/docs/tutorial/e-commerce-with-datocms-and-snipcart/index.md +++ b/docs/tutorial/e-commerce-with-datocms-and-snipcart/index.md @@ -339,7 +339,7 @@ render={data => ( data-item-price={product.price} data-item-image={product.image.url} data-item-name={product.name} - data-item-url={`https://determined-easley-e806d0.netlify.com/`} + data-item-url={`https://determined-easley-e806d0.netlify.app/`} > Add to cart diff --git a/docs/tutorial/ecommerce-tutorial/index.md b/docs/tutorial/ecommerce-tutorial/index.md index bfe52560dc465..00fa5dd27341a 100644 --- a/docs/tutorial/ecommerce-tutorial/index.md +++ b/docs/tutorial/ecommerce-tutorial/index.md @@ -4,7 +4,7 @@ title: "Gatsby E-commerce Tutorial" In this advanced tutorial, you’ll learn how to use Gatsby to build the UI for a basic e-commerce site that can accept payments, with [Stripe](https://stripe.com) as the backend for processing payments. -- Demo running [on Netlify](https://gatsby-ecommerce-stripe.netlify.com/) +- Demo running [on Netlify](https://gatsby-ecommerce-stripe.netlify.app/) - Code hosted [on GitHub](https://github.com/gatsbyjs/gatsby/tree/master/examples/ecommerce-tutorial-with-stripe) ## Why use Gatsby for an E-commerce site? diff --git a/docs/tutorial/part-one/index.md b/docs/tutorial/part-one/index.md index c2d7124fe72b4..bb7f402f56256 100644 --- a/docs/tutorial/part-one/index.md +++ b/docs/tutorial/part-one/index.md @@ -4,11 +4,11 @@ typora-copy-images-to: ./ disableTableOfContents: true --- -In the [**previous section**](/tutorial/part-zero/), you prepared your local development environment by installing the necessary software and creating your first Gatsby site using the [**“hello world” starter**](https://github.com/gatsbyjs/gatsby-starter-hello-world). Now, take a deeper dive into the code generated by that starter. +In the [**previous section**](/tutorial/part-zero/), you prepared your local development environment by installing the necessary software and creating your first Gatsby site using the [**"hello world" starter**](https://github.com/gatsbyjs/gatsby-starter-hello-world). Now, take a deeper dive into the code generated by that starter. ## Using Gatsby starters -In [**tutorial part zero**](/tutorial/part-zero/), you created a new site based on the “hello world” starter using the following command: +In [**tutorial part zero**](/tutorial/part-zero/), you created a new site based on the "hello world" starter using the following command: ```shell gatsby new hello-world https://github.com/gatsbyjs/gatsby-starter-hello-world @@ -20,17 +20,17 @@ When creating a new Gatsby site, you can use the following command structure to gatsby new [SITE_DIRECTORY_NAME] [URL_OF_STARTER_GITHUB_REPO] ``` -If you omit a URL from the end, Gatsby will automatically generate a site for you based on the [**default starter**](https://github.com/gatsbyjs/gatsby-starter-default). For this section of the tutorial, stick with the “Hello World” site you already created in tutorial part zero. You can learn more about [modifying starters](/docs/modifying-a-starter) in the docs. +If you omit a URL from the end, Gatsby will automatically generate a site for you based on the [**default starter**](https://github.com/gatsbyjs/gatsby-starter-default). For this section of the tutorial, stick with the "Hello World" site you already created in tutorial part zero. You can learn more about [modifying starters](/docs/modifying-a-starter) in the docs. ### ✋ Open up the code -In your code editor, open up the code generated for your “Hello World” site and take a look at the different directories and files contained in the ‘hello-world’ directory. It should look something like this: +In your code editor, open up the code generated for your "Hello World" site and take a look at the different directories and files contained in the 'hello-world' directory. It should look something like this: ![Hello World project in VS Code](01-hello-world-vscode.png) -_Note: Again, the editor shown here is Visual Studio Code. If you’re using a different editor, it will look a little different._ +_Note: Again, the editor shown here is Visual Studio Code. If you're using a different editor, it will look a little different._ -Let’s take a look at the code that powers the homepage. +Let's take a look at the code that powers the homepage. > 💡 If you stopped your development server after running `gatsby develop` in the previous section, start it up again now — time to make some changes to the hello-world site! @@ -38,20 +38,20 @@ Let’s take a look at the code that powers the homepage. Open up the `/src` directory in your code editor. Inside is a single directory: `/pages`. -Open the file at `src/pages/index.js`. The code in this file creates a component that contains a single div and some text — appropriately, “Hello world!” +Open the file at `src/pages/index.js`. The code in this file creates a component that contains a single div and some text — appropriately, "Hello world!" -### ✋ Make changes to the “Hello World” homepage +### ✋ Make changes to the "Hello World" homepage -1. Change the “Hello World!” text to “Hello Gatsby!” and save the file. If your windows are side-by-side, you can see that your code and content changes are reflected almost instantly in the browser after you save the file. +1. Change the "Hello World!" text to "Hello Gatsby!" and save the file. If your windows are side-by-side, you can see that your code and content changes are reflected almost instantly in the browser after you save the file. -> 💡 Gatsby uses **hot reloading** to speed up your development process. Essentially, when you’re running a Gatsby development server, the Gatsby site files are being “watched” in the background — any time you save a file, your changes will be immediately reflected in the browser. You don’t need to hard refresh the page or restart the development server — your changes just appear. +> 💡 Gatsby uses **hot reloading** to speed up your development process. Essentially, when you're running a Gatsby development server, the Gatsby site files are being "watched" in the background — any time you save a file, your changes will be immediately reflected in the browser. You don't need to hard refresh the page or restart the development server — your changes just appear. -2. Now you can make your changes a little more visible. Try replacing the code in `src/pages/index.js` with the code below and save again. You’ll see changes to the text — the text color will be purple and the font size will be larger. +2. Now you can make your changes a little more visible. Try replacing the code in `src/pages/index.js` with the code below and save again. You'll see changes to the text — the text color will be purple and the font size will be larger. ```jsx:title=src/pages/index.js import React from "react" @@ -61,9 +61,9 @@ export default function Home() { } ``` -> 💡 We’ll be covering more about styling in Gatsby in [**part two**](/tutorial/part-two/) of the tutorial. +> 💡 We'll be covering more about styling in Gatsby in [**part two**](/tutorial/part-two/) of the tutorial. -3. Remove the font size styling, change the “Hello Gatsby!” text to a level-one header, and add a paragraph beneath the header. +3. Remove the font size styling, change the "Hello Gatsby!" text to a level-one header, and add a paragraph beneath the header. ```jsx:title=src/pages/index.js import React from "react" @@ -103,7 +103,7 @@ export default function Home() { ### Wait… HTML in our JavaScript? -_If you’re familiar with React and JSX, feel free to skip this section._ If you haven’t worked with the React framework before, you may be wondering what HTML is doing in a JavaScript function. Or why we’re importing `react` on the first line but seemingly not using it anywhere. This hybrid “HTML-in-JS” is actually a syntax extension of JavaScript, for React, called JSX. You can follow along with this tutorial without prior experience with React, but if you’re curious, here’s a brief primer… +_If you're familiar with React and JSX, feel free to skip this section._ If you haven't worked with the React framework before, you may be wondering what HTML is doing in a JavaScript function. Or why we're importing `react` on the first line but seemingly not using it anywhere. This hybrid "HTML-in-JS" is actually a syntax extension of JavaScript, for React, called JSX. You can follow along with this tutorial without prior experience with React, but if you're curious, here's a brief primer… Consider the original contents of the `src/pages/index.js` file: @@ -125,11 +125,11 @@ export default function Home() { } ``` -Now you can spot the use of the `'react'` import! But wait. You’re writing JSX, not pure HTML and JavaScript. How does the browser read that? The short answer: It doesn’t. Gatsby sites come with tooling already set up to convert your source code into something that browsers can interpret. +Now you can spot the use of the `'react'` import! But wait. You're writing JSX, not pure HTML and JavaScript. How does the browser read that? The short answer: It doesn't. Gatsby sites come with tooling already set up to convert your source code into something that browsers can interpret. ## Building with components -The homepage you were just making edits to was created by defining a page component. What exactly is a “component”? +The homepage you were just making edits to was created by defining a page component. What exactly is a "component"? Broadly defined, a component is a building block for your site; It is a self-contained piece of code that describes a section of UI (user interface). @@ -156,9 +156,9 @@ Components become the base building blocks of your site. Instead of being limite ### ✋ Using page components -Any React component defined in `src/pages/*.js` will automatically become a page. Let’s see this in action. +Any React component defined in `src/pages/*.js` will automatically become a page. Let's see this in action. -You already have a `src/pages/index.js` file that came with the “Hello World” starter. Let’s create an about page. +You already have a `src/pages/index.js` file that came with the "Hello World" starter. Let's create an about page. 1. Create a new file at `src/pages/about.js`, copy the following code into the new file, and save. @@ -183,7 +183,7 @@ Just by putting a React component in the `src/pages/about.js` file, you now have ### ✋ Using sub-components -Let’s say the homepage and the about page both got quite large and you were rewriting a lot of things. You can use sub-components to break the UI into reusable pieces. Both of your pages have `

` headers — create a component that will describe a `Header`. +Let's say the homepage and the about page both got quite large and you were rewriting a lot of things. You can use sub-components to break the UI into reusable pieces. Both of your pages have `

` headers — create a component that will describe a `Header`. 1. Create a new directory at `src/components` and a file within that directory called `header.js`. 2. Add the following code to the new `src/components/header.js` file. @@ -214,7 +214,7 @@ export default function About() { ![Adding Header component](06-header-component.png) -In the browser, the “About Gatsby” header text should now be replaced with “This is a header.” But you don’t want the “About” page to say “This is a header.” You want it to say, “About Gatsby”. +In the browser, the "About Gatsby" header text should now be replaced with "This is a header." But you don't want the "About" page to say "This is a header." You want it to say, "About Gatsby". 4. Head back to `src/components/header.js` and make the following change: @@ -246,9 +246,9 @@ export default function About() { ![Passing data to header](07-pass-data-header.png) -You should now see your “About Gatsby” header text again! +You should now see your "About Gatsby" header text again! -### What are “props”? +### What are "props"? Earlier, you defined React components as reusable pieces of code describing a UI. To make these reusable pieces dynamic you need to be able to supply them with different data. You do that with input called "props". Props are (appropriately enough) properties supplied to React components. @@ -258,13 +258,13 @@ In `about.js` you passed a `headerText` prop with the value of `"About Gatsby"`
``` -Over in `header.js`, the header component expects to receive the `headerText` prop (because you’ve written it to expect that). So you can access it like so: +Over in `header.js`, the header component expects to receive the `headerText` prop (because you've written it to expect that). So you can access it like so: ```jsx:title=src/components/header.js

{props.headerText}

``` -> 💡 In JSX, you can embed any JavaScript expression by wrapping it with `{}`. This is how you can access the `headerText` property (or “prop!”) from the “props” object. +> 💡 In JSX, you can embed any JavaScript expression by wrapping it with `{}`. This is how you can access the `headerText` property (or "prop!") from the "props" object. If you had passed another prop to your `
` component, like so... @@ -299,7 +299,7 @@ And there you have it; A second header — without rewriting any code — by pas Layout components are for sections of a site that you want to share across multiple pages. For example, Gatsby sites will commonly have a layout component with a shared header and footer. Other common things to add to layouts include a sidebar and/or a navigation menu. -You’ll explore layout components in [**part three**](/tutorial/part-three/). +You'll explore layout components in [**part three**](/tutorial/part-three/). ## Linking between pages @@ -361,10 +361,12 @@ The Gatsby `` component is for linking between pages within your site. F ## Deploying a Gatsby site -Gatsby.js is a _modern site generator_, which means there are no servers to set up or complicated databases to deploy. Instead, the Gatsby `build` command produces a directory of static HTML and JavaScript files which you can deploy to a static site hosting service. +Gatsby is a _modern site generator_, which means there are no servers to set up or complicated databases to deploy. Instead, the Gatsby `build` command produces a directory of static HTML and JavaScript files which you can deploy to a static site hosting service. Try using [Surge](http://surge.sh/) for deploying your first Gatsby website. Surge is one of many "static site hosts" which makes it possible to deploy Gatsby sites. +> Gatsby Cloud is another deployment option, built by the team behind Gatsby. In the next section, you'll find instructions for [deploying to Gatsby Cloud](/tutorial/part-one/#alternative-deploying-to-gatsby-cloud). + If you haven't previously installed & set up Surge, open a new terminal window and install their command-line tool: ```shell @@ -403,7 +405,29 @@ Once this finishes running, you should see in your terminal something like: Open the web address listed on the bottom line (`lowly-pain.surge.sh` in this case) and you'll see your newly published site! Great work! -## ➡️ What’s Next? +### Alternative: Deploying to Gatsby Cloud + +[Gatsby Cloud](https://gatsbyjs.com) is a platform built specifically for Gatsby sites, with features like real-time previews, fast builds, and integrations with dozens of other tools. It's the best place to build and deploy sites built with Gatsby, and you can use Gatsby Cloud free for personal projects. + +To deploy your site to Gatsby Cloud, create an account on [GitHub](https://github.com) if you don't have one. GitHub allows you to host and collaborate on code projects using Git for version control. + +Create a new repository on GitHub. Since you're importing your existing project, you'll want a completely empty one, so don't initialize it with `README` or `.gitignore` files. + +You can tell Git where the remote (i.e. not on your computer) repository is like this: + +```shell +git remote add origin [GITHUB_REPOSITORY_URL] +``` + +When you created a new Gatsby project with a starter, it automatically made an initial `git commit`, or a set of changes. Now, you can push your changes to the new remote location: + +```shell +git push -u origin master +``` + +Now you're ready to link this GitHub repository right to Gatsby Cloud! Check out the reference guide on [Deploying to Gatsby Cloud](/docs/deploying-to-gatsby-cloud/#set-up-an-existing-gatsby-site). + +## ➡️ What's Next? In this section you: @@ -411,6 +435,6 @@ In this section you: - Learned about JSX syntax - Learned about components - Learned about Gatsby page components and sub-components -- Learned about React “props” and reusing React components +- Learned about React "props" and reusing React components Now, move on to [**adding styles to your site**](/tutorial/part-two/)! diff --git a/docs/tutorial/source-plugin-tutorial.md b/docs/tutorial/source-plugin-tutorial.md index 04a57358ca760..57527d0ed0705 100644 --- a/docs/tutorial/source-plugin-tutorial.md +++ b/docs/tutorial/source-plugin-tutorial.md @@ -110,7 +110,7 @@ _You can include the plugin by using its name if you are using [npm link or yarn You can now navigate into the `example-site` folder and run `gatsby develop`. You should see a line in the output in the terminal that shows your plugin loaded: -```shell +```shell:title=example-site $ gatsby develop success open and validate gatsby-configs - 0.033s success load plugins - 0.074s @@ -200,7 +200,7 @@ You can query data from any location to source at build time using functions and You'll use several modules from npm to making fetching data with GraphQL easier. Install them in the `source-plugin` project with: -```shell +```shell:title=source-plugin npm install apollo-cache-inmemory apollo-client apollo-link apollo-link-http apollo-link-ws apollo-utilities graphql graphql-tag node-fetch ws subscriptions-transport-ws ``` @@ -642,7 +642,7 @@ Add a file at `example-site/src/pages/index.js` and copy the following code into Ensure you have `gatsby-image` installed in the site by running `npm install gatsby-image`. It provides a component that can take the optimized image data and render it. -```javascript:title=example-site/src/pages/index.js +```jsx:title=example-site/src/pages/index.js import React from "react" import { graphql } from "gatsby" import Img from "gatsby-image" diff --git a/docs/tutorial/using-multiple-themes-together.md b/docs/tutorial/using-multiple-themes-together.md index 29d3d103850e0..9a31c87a93aa9 100644 --- a/docs/tutorial/using-multiple-themes-together.md +++ b/docs/tutorial/using-multiple-themes-together.md @@ -208,7 +208,7 @@ export default merge(defaultTheme, { ## Add another theme -Themes can be big, like `gatsby-theme-blog`, but they can also be a small discrete set of components or functions. A great example of this is [gatsby-mdx-embed](https://gatsby-mdx-embed.netlify.com/) which adds the ability to embed social media content and videos directly into your MDX files. +Themes can be big, like `gatsby-theme-blog`, but they can also be a small discrete set of components or functions. A great example of this is [gatsby-mdx-embed](https://gatsby-mdx-embed.netlify.app/) which adds the ability to embed social media content and videos directly into your MDX files. 1. Install the theme: diff --git a/examples/styleguide/src/templates/ComponentPage/components/ComponentPreview/prism-theme.css b/examples/styleguide/src/templates/ComponentPage/components/ComponentPreview/prism-theme.css index dbd7780ae8866..844e6de56c131 100644 --- a/examples/styleguide/src/templates/ComponentPage/components/ComponentPreview/prism-theme.css +++ b/examples/styleguide/src/templates/ComponentPage/components/ComponentPreview/prism-theme.css @@ -1,9 +1,9 @@ /* Name: Base16 Atelier Sulphurpool Light -Author: Bram de Haan (http://atelierbram.github.io/syntax-highlighting/atelier-schemes/sulphurpool) +Author: Bram de Haan (https://atelierbram.github.io/syntax-highlighting/atelier-schemes/sulphurpool) -Prism template by Bram de Haan (http://atelierbram.github.io/syntax-highlighting/prism/) +Prism template by Bram de Haan (https://atelierbram.github.io/syntax-highlighting/prism/) Original Base16 color scheme by Chris Kempson (https://github.com/chriskempson/base16) */ diff --git a/examples/using-contentful/README.md b/examples/using-contentful/README.md index 9963177405464..7e7d51c6bec48 100644 --- a/examples/using-contentful/README.md +++ b/examples/using-contentful/README.md @@ -1,6 +1,6 @@ # Using Contentful -https://using-contentful.netlify.com +https://using-contentful.netlify.app Example site that demonstrates how to build Gatsby sites that pull data from the [Contentful CMS API](https://www.contentful.com/). diff --git a/examples/using-gatsby-source-graphql/README.md b/examples/using-gatsby-source-graphql/README.md index bbc4a55e65455..f9dfa50cae561 100644 --- a/examples/using-gatsby-source-graphql/README.md +++ b/examples/using-gatsby-source-graphql/README.md @@ -4,7 +4,7 @@ Simple gatsby site that displays blog with data inside GraphCMS. Built using [gatsby-source-graphql](https://www.gatsbyjs.org/packages/gatsby-source-graphql/). - + ## How it works diff --git a/examples/using-gatsby-with-json-yaml/README.md b/examples/using-gatsby-with-json-yaml/README.md index ce5262d66ebb7..4893ea0f30d18 100644 --- a/examples/using-gatsby-with-json-yaml/README.md +++ b/examples/using-gatsby-with-json-yaml/README.md @@ -4,7 +4,7 @@ Gatsby example that uses JSON files and YAML files as a means of sourcing data. ## Live Version -[Live version here](https://relaxed-stallman-db9f95.netlify.com/) +[Live version here](https://relaxed-stallman-db9f95.netlify.app/) ## Routes diff --git a/examples/using-i18n/README.md b/examples/using-i18n/README.md index bfe02f1200d03..37daa6d759121 100644 --- a/examples/using-i18n/README.md +++ b/examples/using-i18n/README.md @@ -1,6 +1,6 @@ # Using i18n -https://using-i18n.netlify.com/ +https://using-i18n.netlify.app/ Example site that demonstrates how to build Gatsby sites with multiple languages (Internationalization / i18n) without any third-party plugins or packages. Per language a dedicated page is built (so no client-side translations) which is among other things important for SEO. diff --git a/examples/using-javascript-transforms/README.md b/examples/using-javascript-transforms/README.md index c13e0cacb3ac0..87a19ccdea78c 100644 --- a/examples/using-javascript-transforms/README.md +++ b/examples/using-javascript-transforms/README.md @@ -2,7 +2,7 @@ ### An exploration of the JavaScript ecosystem in Gatsby -#### Demo at [https://using-javascript-transforms.netlify.com](https://using-javascript-transforms.netlify.com) +#### Demo at [https://using-javascript-transforms.netlify.app](https://using-javascript-transforms.netlify.app) The example mixes JavaScript and remark, uses scss and bulma.io, has use case examples for graphql in layouts, and some "manual" page creation with the help diff --git a/examples/using-js-search/README.md b/examples/using-js-search/README.md index 020b7214cc212..ecabe6b3ad574 100644 --- a/examples/using-js-search/README.md +++ b/examples/using-js-search/README.md @@ -2,5 +2,5 @@ The code in this folder is the full implementation for the documentation on how to add client search with [js-search](https://github.com/bvaughn/js-search). -A live version of this example is located [here](https://pedantic-clarke-873963.netlify.com/) -The endpoint that uses Gatsby API is located [here](https://pedantic-clarke-873963.netlify.com/search) +A live version of this example is located [here](https://pedantic-clarke-873963.netlify.app/) +The endpoint that uses Gatsby API is located [here](https://pedantic-clarke-873963.netlify.app/search) diff --git a/examples/using-mobx/readme.md b/examples/using-mobx/readme.md index 5a420c83be1d1..cd1c8d7fc3da5 100644 --- a/examples/using-mobx/readme.md +++ b/examples/using-mobx/readme.md @@ -1,6 +1,6 @@ # MOBX -[Using mobx with gatsby](https://dazzling-meninsky-6f4ac3.netlify.com/) +[Using mobx with gatsby](https://dazzling-meninsky-6f4ac3.netlify.app/) Gatsby example site that shows use of mobx. diff --git a/examples/using-page-transitions/README.md b/examples/using-page-transitions/README.md index 95023f62e2525..c90352df50787 100644 --- a/examples/using-page-transitions/README.md +++ b/examples/using-page-transitions/README.md @@ -4,4 +4,4 @@ Gatsby example site using page transitions. This example uses `react-transition-group` in conjunction with `gatsby-plugin-layout`. For more complex page transitions and no `gatsby-plugin-layout` dependency, you can make use of [`react-pose`](https://github.com/Popmotion/popmotion/tree/master/packages/react-pose). -[View the live demo](https://using-page-transitions.netlify.com/) +[View the live demo](https://using-page-transitions.netlify.app/) diff --git a/examples/using-reach-skip-nav/README.md b/examples/using-reach-skip-nav/README.md index 441847a13723b..9d4c85741ce07 100644 --- a/examples/using-reach-skip-nav/README.md +++ b/examples/using-reach-skip-nav/README.md @@ -8,9 +8,11 @@ This example will show you how to leverage the [@reach/skip-nav](https://reacttr ## Using @reach/skip-nav -### Add SkipNavLink and SkipNavContent to your Layout +### Add `SkipNavLink` and `SkipNavContent` to your Layout + +```javascript:title=src/components/layout.js +// src/components/layout.js -```javascript:layout.js import { SkipNavLink, SkipNavContent } from "@reach/skip-nav" import "@reach/skip-nav/styles.css" //this will show/hide the link on focus @@ -29,9 +31,11 @@ export default Layout ### Focus your link on page navigation -Hooking into Gatsby's onRouteUpdate API method will allow you to focus automatically on a skip link on page change, putting a user in a more appropriate spot to take action. More information about this method can be found the [browser API docs](https://www.gatsbyjs.org/docs/browser-apis/#onRouteUpdate). +Hooking into Gatsby's `onRouteUpdate` API method will allow you to focus automatically on a skip link on page change, putting a user in a more appropriate spot to take action. More information about this method can be found the [browser API docs](https://www.gatsbyjs.org/docs/browser-apis/#onRouteUpdate). + +```javascript:title=gatsby-browser.js +// gatsby-browser.js -```javascript:gatsby-browser.js export const onRouteUpdate = ({ location, prevLocation }) => { if (prevLocation !== null) { const skipLink = document.querySelector("[data-reach-skip-link]") //this is the query selector that comes with the component @@ -48,6 +52,7 @@ export const onRouteUpdate = ({ location, prevLocation }) => { A quick look at the relevant files and directories you'll see in this example: +```text . ├── cypress/ │ ├── integration/ @@ -60,6 +65,7 @@ A quick look at the relevant files and directories you'll see in this example: │ │ └── seo.js │ └── pages/ ├── gatsby-browser.js +``` 1. **`/src`**: This directory will contain all of the code related to what you will see on the front-end of your site. It has pages and components to be used in those pages. 1. **`/components`**: This directory will contain all of the code related to what you will see on the front-end of your site. It has pages and components to be used in those pages. @@ -71,7 +77,7 @@ A quick look at the relevant files and directories you'll see in this example: 1. **`/pages`**: This directory contains pages that will be automatically built and served by Gatsby. This example includes three pages to demonstrate navigation between them and how your skip nav link behaves. All of these pages use the `Layout` component. 1. **`gatsby-browser.js`**: This file is where you tell the Gatsby to focus the skip navigation when users navigate to a new page. -1. **`/cypress**: This directory is where tests and [Cypress](https://www.cypress.io/) configuration live. You're going to focus on the test. If you want to learn more about using Cypress, check out the [example](https://github.com/gatsbyjs/gatsby/tree/master/examples/using-cypress). +1. **`/cypress`**: This directory is where tests and [Cypress](https://www.cypress.io/) configuration live. You're going to focus on the test. If you want to learn more about using Cypress, check out the [example](https://github.com/gatsbyjs/gatsby/tree/master/examples/using-cypress). 1. **`/integrations/skip-nav.test.js`**: runs two tests to ensure that you have a skip link and that the skip link is focused on page navigation. ### Running the example @@ -88,7 +94,7 @@ A quick look at the relevant files and directories you'll see in this example: ### Running tests -1. Use the CLI to run cypress tests +1. Use the CLI to run Cypress tests ```shell npm run test:e2e ``` diff --git a/examples/using-styled-jsx/README.md b/examples/using-styled-jsx/README.md index c4fce08a9e46f..ab0a12cf635c8 100644 --- a/examples/using-styled-jsx/README.md +++ b/examples/using-styled-jsx/README.md @@ -2,7 +2,7 @@ https://using-styled-jsx.gatsbyjs.org -Demonstrates using [styled-jsx](https://github.com/zeit/styled-jsx) with the +Demonstrates using [styled-jsx](https://github.com/vercel/styled-jsx) with the Gatsby plugin [gatsby-plugin-styled-jsx](https://www.gatsbyjs.org/packages/gatsby-plugin-styled-jsx/) which automatically provides SSR support. diff --git a/integration-tests/gatsby-cli/__tests__/recipes.js b/integration-tests/gatsby-cli/__tests__/recipes.js new file mode 100644 index 0000000000000..b12a9542234a8 --- /dev/null +++ b/integration-tests/gatsby-cli/__tests__/recipes.js @@ -0,0 +1,28 @@ +import { GatsbyCLI } from "../test-helpers" + +const MAX_TIMEOUT = 2147483647 +jest.setTimeout(MAX_TIMEOUT) + +describe(`gatsby recipes`, () => { + const cwd = `gatsby-sites/gatsby-develop` + + beforeAll(() => GatsbyCLI.from(cwd).invoke(`clean`)) + afterAll(() => GatsbyCLI.from(cwd).invoke(`clean`)) + + it(`begins running the jest recipe`, async () => { + // 1. Start the `gatsby recipes` command + const [childProcess, getLogs] = GatsbyCLI.from(cwd).invokeAsync( + [`recipes`, `jest`], + log => log.includes("Add recipe") + ) + + // 2. Wait for the process to finish + await childProcess + + const logs = getLogs() + + // This checks that the recipe command is being properly required + // and is attempting to fetch the jest recipe + logs.should.contain(`Loading recipe`) + }) +}) diff --git a/packages/babel-plugin-remove-graphql-queries/CHANGELOG.md b/packages/babel-plugin-remove-graphql-queries/CHANGELOG.md index ccd4ae613475d..868fc4c341f36 100644 --- a/packages/babel-plugin-remove-graphql-queries/CHANGELOG.md +++ b/packages/babel-plugin-remove-graphql-queries/CHANGELOG.md @@ -3,6 +3,16 @@ All notable changes to this project will be documented in this file. See [Conventional Commits](https://conventionalcommits.org) for commit guidelines. +## [2.9.5](https://github.com/gatsbyjs/gatsby/compare/babel-plugin-remove-graphql-queries@2.9.4...babel-plugin-remove-graphql-queries@2.9.5) (2020-06-09) + +**Note:** Version bump only for package babel-plugin-remove-graphql-queries + +## [2.9.4](https://github.com/gatsbyjs/gatsby/compare/babel-plugin-remove-graphql-queries@2.9.3...babel-plugin-remove-graphql-queries@2.9.4) (2020-06-09) + +### Bug Fixes + +- **babel-plugin-remove-graphql-queries:** Strip ignored characters from query text for better caching and deduping ([#24807](https://github.com/gatsbyjs/gatsby/issues/24807)) ([752f5ff](https://github.com/gatsbyjs/gatsby/commit/752f5ff)) + ## [2.9.3](https://github.com/gatsbyjs/gatsby/compare/babel-plugin-remove-graphql-queries@2.9.2...babel-plugin-remove-graphql-queries@2.9.3) (2020-06-02) **Note:** Version bump only for package babel-plugin-remove-graphql-queries diff --git a/packages/babel-plugin-remove-graphql-queries/package.json b/packages/babel-plugin-remove-graphql-queries/package.json index 21ee6166639f3..65d19bd0131b8 100644 --- a/packages/babel-plugin-remove-graphql-queries/package.json +++ b/packages/babel-plugin-remove-graphql-queries/package.json @@ -1,6 +1,6 @@ { "name": "babel-plugin-remove-graphql-queries", - "version": "2.9.3", + "version": "2.9.5", "author": "Jason Quense ", "repository": { "type": "git", @@ -11,7 +11,7 @@ "devDependencies": { "@babel/cli": "^7.10.1", "@babel/core": "^7.10.2", - "babel-preset-gatsby-package": "^0.4.3", + "babel-preset-gatsby-package": "^0.4.4", "cross-env": "^5.2.1" }, "peerDependencies": { diff --git a/packages/babel-plugin-remove-graphql-queries/src/__tests__/__snapshots__/index.js.snap b/packages/babel-plugin-remove-graphql-queries/src/__tests__/__snapshots__/index.js.snap index c748dc25c9d01..546576e117356 100644 --- a/packages/babel-plugin-remove-graphql-queries/src/__tests__/__snapshots__/index.js.snap +++ b/packages/babel-plugin-remove-graphql-queries/src/__tests__/__snapshots__/index.js.snap @@ -1,37 +1,37 @@ // Jest Snapshot v1, https://goo.gl/fbAQLP exports[`Allow alternative import of useStaticQuery 1`] = ` -"import staticQueryData from \\"public/static/d/2626356014.json\\"; +"import staticQueryData from \\"public/static/d/426988268.json\\"; import * as React from 'react'; import * as Gatsby from 'gatsby'; export default (() => { - const query = \\"2626356014\\"; + const query = \\"426988268\\"; const siteTitle = staticQueryData.data; return /*#__PURE__*/React.createElement(\\"h1\\", null, siteTitle.site.siteMetadata.title); });" `; exports[`Doesn't add data import for non static queries 1`] = ` -"import staticQueryData from \\"public/static/d/4279313589.json\\"; +"import staticQueryData from \\"public/static/d/426988268.json\\"; import * as React from 'react'; import { StaticQuery } from \\"gatsby\\"; const Test = () => /*#__PURE__*/React.createElement(StaticQuery, { - query: \\"4279313589\\", + query: \\"426988268\\", render: data => /*#__PURE__*/React.createElement(\\"div\\", null, data.site.siteMetadata.title), data: staticQueryData }); export default Test; -export const fragment = \\"2962815581\\";" +export const fragment = \\"4176178832\\";" `; exports[`Handles closing StaticQuery tag 1`] = ` -"import staticQueryData from \\"public/static/d/2626356014.json\\"; +"import staticQueryData from \\"public/static/d/426988268.json\\"; import * as React from 'react'; import { StaticQuery } from 'gatsby'; export default (() => /*#__PURE__*/React.createElement(StaticQuery, { - query: \\"2626356014\\", + query: \\"426988268\\", data: staticQueryData }, data => /*#__PURE__*/React.createElement(\\"div\\", null, data.site.siteMetadata.title)));" `; @@ -50,7 +50,7 @@ export const query = graphql\` exports[`Only runs transforms if useStaticQuery is imported from gatsby 1`] = ` "import * as React from 'react'; export default (() => { - const query = \\"2626356014\\"; + const query = \\"426988268\\"; const siteTitle = useStaticQuery(query); return /*#__PURE__*/React.createElement(\\"h1\\", null, siteTitle.site.siteMetadata.title); });" @@ -58,12 +58,12 @@ export default (() => { exports[`Removes all gatsby queries 1`] = ` "export default (() => /*#__PURE__*/React.createElement(\\"div\\", null, data.site.siteMetadata.title)); -export const siteMetaQuery = \\"2673797374\\"; -export const query = \\"2589775908\\";" +export const siteMetaQuery = \\"504726680\\"; +export const query = \\"3211238532\\";" `; exports[`Transformation does not break custom hooks 1`] = ` -"import staticQueryData from \\"public/static/d/2626356014.json\\"; +"import staticQueryData from \\"public/static/d/426988268.json\\"; import React from \\"react\\"; const useSiteMetadata = () => { @@ -78,17 +78,17 @@ export default (() => { `; exports[`Transforms exported queries in useStaticQuery 1`] = ` -"import staticQueryData from \\"public/static/d/2626356014.json\\"; +"import staticQueryData from \\"public/static/d/426988268.json\\"; import * as React from 'react'; export default (() => { const data = staticQueryData.data; return /*#__PURE__*/React.createElement(React.Fragment, null, /*#__PURE__*/React.createElement(\\"h1\\", null, data.site.siteMetadata.title), /*#__PURE__*/React.createElement(\\"p\\", null, data.site.siteMetadata.description)); }); -export const query = \\"2626356014\\";" +export const query = \\"426988268\\";" `; exports[`Transforms only the call expression in useStaticQuery 1`] = ` -"import staticQueryData from \\"public/static/d/2626356014.json\\"; +"import staticQueryData from \\"public/static/d/426988268.json\\"; import React from \\"react\\"; const useSiteMetadata = () => { @@ -102,10 +102,10 @@ export default (() => { `; exports[`Transforms queries and preserves destructuring in useStaticQuery 1`] = ` -"import staticQueryData from \\"public/static/d/2626356014.json\\"; +"import staticQueryData from \\"public/static/d/426988268.json\\"; import * as React from 'react'; export default (() => { - const query = \\"2626356014\\"; + const query = \\"426988268\\"; const { site } = staticQueryData.data; @@ -114,10 +114,10 @@ export default (() => { `; exports[`Transforms queries and preserves variable type in useStaticQuery 1`] = ` -"import staticQueryData from \\"public/static/d/2626356014.json\\"; +"import staticQueryData from \\"public/static/d/426988268.json\\"; import * as React from 'react'; export default (() => { - const query = \\"2626356014\\"; + const query = \\"426988268\\"; let { site } = staticQueryData.data; @@ -126,10 +126,10 @@ export default (() => { `; exports[`Transforms queries defined in own variable in 1`] = ` -"import staticQueryData from \\"public/static/d/2626356014.json\\"; +"import staticQueryData from \\"public/static/d/426988268.json\\"; import * as React from 'react'; import { StaticQuery } from 'gatsby'; -const query = \\"2626356014\\"; +const query = \\"426988268\\"; export default (() => /*#__PURE__*/React.createElement(StaticQuery, { query: query, render: data => /*#__PURE__*/React.createElement(\\"div\\", null, data.site.siteMetadata.title), @@ -138,30 +138,30 @@ export default (() => /*#__PURE__*/React.createElement(StaticQuery, { `; exports[`Transforms queries defined in own variable in useStaticQuery 1`] = ` -"import staticQueryData from \\"public/static/d/2626356014.json\\"; +"import staticQueryData from \\"public/static/d/426988268.json\\"; import * as React from 'react'; export default (() => { - const query = \\"2626356014\\"; + const query = \\"426988268\\"; const siteTitle = staticQueryData.data; return /*#__PURE__*/React.createElement(\\"h1\\", null, siteTitle.site.siteMetadata.title); });" `; exports[`Transforms queries in 1`] = ` -"import staticQueryData from \\"public/static/d/2626356014.json\\"; +"import staticQueryData from \\"public/static/d/426988268.json\\"; import * as React from 'react'; import { StaticQuery } from 'gatsby'; export default (() => /*#__PURE__*/React.createElement(StaticQuery, { - query: \\"2626356014\\", + query: \\"426988268\\", render: data => /*#__PURE__*/React.createElement(\\"div\\", null, data.site.siteMetadata.title), data: staticQueryData }));" `; -exports[`Transforms queries in page components 1`] = `"export const query = \\"3687030656\\";"`; +exports[`Transforms queries in page components 1`] = `"export const query = \\"426988268\\";"`; exports[`Transforms queries in useStaticQuery 1`] = ` -"import staticQueryData from \\"public/static/d/2626356014.json\\"; +"import staticQueryData from \\"public/static/d/426988268.json\\"; import * as React from 'react'; export default (() => { const siteTitle = staticQueryData.data; @@ -169,7 +169,7 @@ export default (() => { });" `; -exports[`allows the global tag 1`] = `"export const query = \\"3687030656\\";"`; +exports[`allows the global tag 1`] = `"export const query = \\"426988268\\";"`; exports[`distinguishes between the right tags 1`] = ` "const foo = styled('div')\` @@ -195,22 +195,22 @@ const pulse = keyframes\` animation-timing-function: ease-out; } \`; -export const query = \\"3687030656\\";" +export const query = \\"426988268\\";" `; -exports[`handles import aliasing 1`] = `"export const query = \\"3687030656\\";"`; +exports[`handles import aliasing 1`] = `"export const query = \\"426988268\\";"`; -exports[`handles require 1`] = `"export const query = \\"3687030656\\";"`; +exports[`handles require 1`] = `"export const query = \\"426988268\\";"`; -exports[`handles require alias 1`] = `"export const query = \\"3687030656\\";"`; +exports[`handles require alias 1`] = `"export const query = \\"426988268\\";"`; -exports[`handles require namespace 1`] = `"export const query = \\"3687030656\\";"`; +exports[`handles require namespace 1`] = `"export const query = \\"426988268\\";"`; exports[`transforms exported variable queries in 1`] = ` -"import staticQueryData from \\"public/static/d/2626356014.json\\"; +"import staticQueryData from \\"public/static/d/426988268.json\\"; import * as React from 'react'; import { StaticQuery } from 'gatsby'; -export const query = \\"2626356014\\"; +export const query = \\"426988268\\"; export default (() => /*#__PURE__*/React.createElement(StaticQuery, { query: query, render: data => /*#__PURE__*/React.createElement(\\"div\\", null, data.site.siteMetadata.title), diff --git a/packages/babel-plugin-remove-graphql-queries/src/index.js b/packages/babel-plugin-remove-graphql-queries/src/index.js index cd01e70e09e9f..fdb3e3b860b95 100644 --- a/packages/babel-plugin-remove-graphql-queries/src/index.js +++ b/packages/babel-plugin-remove-graphql-queries/src/index.js @@ -155,7 +155,9 @@ function getGraphQLTag(path) { } const text = quasis[0].value.raw - const hash = murmurhash(text, `abc`) + const normalizedText = graphql.stripIgnoredCharacters(text) + + const hash = murmurhash(normalizedText, `abc`) try { const ast = graphql.parse(text) @@ -163,7 +165,7 @@ function getGraphQLTag(path) { if (ast.definitions.length === 0) { throw new EmptyGraphQLTagError(quasis[0].loc) } - return { ast, text, hash, isGlobal } + return { ast, text: normalizedText, hash, isGlobal } } catch (err) { throw new GraphQLSyntaxError(text, err, quasis[0].loc) } diff --git a/packages/babel-preset-gatsby-package/CHANGELOG.md b/packages/babel-preset-gatsby-package/CHANGELOG.md index 01dafbce253f1..274f52f3f661c 100644 --- a/packages/babel-preset-gatsby-package/CHANGELOG.md +++ b/packages/babel-preset-gatsby-package/CHANGELOG.md @@ -3,6 +3,12 @@ All notable changes to this project will be documented in this file. See [Conventional Commits](https://conventionalcommits.org) for commit guidelines. +## [0.4.4](https://github.com/gatsbyjs/gatsby/compare/babel-preset-gatsby-package@0.4.3...babel-preset-gatsby-package@0.4.4) (2020-06-09) + +### Bug Fixes + +- **babel-preset-gatsby-package:** remove explicit `@babel/plugin-proposal-class-properties` and let `@babel/preset-env` add it ([#24640](https://github.com/gatsbyjs/gatsby/issues/24640)) ([272ba4f](https://github.com/gatsbyjs/gatsby/commit/272ba4f)) + ## [0.4.3](https://github.com/gatsbyjs/gatsby/compare/babel-preset-gatsby-package@0.4.2...babel-preset-gatsby-package@0.4.3) (2020-06-02) **Note:** Version bump only for package babel-preset-gatsby-package diff --git a/packages/babel-preset-gatsby-package/__tests__/__snapshots__/index.js.snap b/packages/babel-preset-gatsby-package/__tests__/__snapshots__/index.js.snap index e1b4da70e6b80..8caa0e21d0dab 100644 --- a/packages/babel-preset-gatsby-package/__tests__/__snapshots__/index.js.snap +++ b/packages/babel-preset-gatsby-package/__tests__/__snapshots__/index.js.snap @@ -54,7 +54,6 @@ Array [ exports[`babel-preset-gatsby-package in browser mode specifies the proper plugins 1`] = ` Array [ - "@babel/plugin-proposal-class-properties", "@babel/plugin-proposal-nullish-coalescing-operator", "@babel/plugin-proposal-optional-chaining", "@babel/plugin-transform-runtime", @@ -111,7 +110,6 @@ Array [ exports[`babel-preset-gatsby-package in node mode specifies the proper plugins 1`] = ` Array [ - "@babel/plugin-proposal-class-properties", "@babel/plugin-proposal-nullish-coalescing-operator", "@babel/plugin-proposal-optional-chaining", "@babel/plugin-transform-runtime", diff --git a/packages/babel-preset-gatsby-package/index.js b/packages/babel-preset-gatsby-package/index.js index cc390c7235487..9d034c7d5fa39 100644 --- a/packages/babel-preset-gatsby-package/index.js +++ b/packages/babel-preset-gatsby-package/index.js @@ -4,7 +4,7 @@ function preset(context, options = {}) { const { browser = false, debug = false, nodeVersion = `10.13.0` } = options const { NODE_ENV, BABEL_ENV } = process.env - const IS_TEST = (BABEL_ENV || NODE_ENV) === `test` + const IS_TEST = (BABEL_ENV || NODE_ENV) === `test` const browserConfig = { useBuiltIns: false, @@ -39,12 +39,11 @@ function preset(context, options = {}) { r(`@babel/preset-flow`), ], plugins: [ - r(`@babel/plugin-proposal-class-properties`), r(`@babel/plugin-proposal-nullish-coalescing-operator`), r(`@babel/plugin-proposal-optional-chaining`), r(`@babel/plugin-transform-runtime`), r(`@babel/plugin-syntax-dynamic-import`), - IS_TEST && r(`babel-plugin-dynamic-import-node`) + IS_TEST && r(`babel-plugin-dynamic-import-node`), ].filter(Boolean), overrides: [ { diff --git a/packages/babel-preset-gatsby-package/package.json b/packages/babel-preset-gatsby-package/package.json index 1c33f4b425843..c7651bbea26bc 100644 --- a/packages/babel-preset-gatsby-package/package.json +++ b/packages/babel-preset-gatsby-package/package.json @@ -1,6 +1,6 @@ { "name": "babel-preset-gatsby-package", - "version": "0.4.3", + "version": "0.4.4", "author": "Philipp Spiess ", "repository": { "type": "git", @@ -9,7 +9,6 @@ }, "homepage": "https://github.com/gatsbyjs/gatsby/tree/master/packages/babel-preset-gatsby-package#readme", "dependencies": { - "@babel/plugin-proposal-class-properties": "^7.10.1", "@babel/plugin-proposal-nullish-coalescing-operator": "^7.10.1", "@babel/plugin-proposal-optional-chaining": "^7.10.1", "@babel/plugin-syntax-dynamic-import": "^7.8.3", diff --git a/packages/babel-preset-gatsby/CHANGELOG.md b/packages/babel-preset-gatsby/CHANGELOG.md index c3c63f55f8aea..956e8ca5a3aa9 100644 --- a/packages/babel-preset-gatsby/CHANGELOG.md +++ b/packages/babel-preset-gatsby/CHANGELOG.md @@ -3,6 +3,10 @@ All notable changes to this project will be documented in this file. See [Conventional Commits](https://conventionalcommits.org) for commit guidelines. +## [0.4.9](https://github.com/gatsbyjs/gatsby/compare/babel-preset-gatsby@0.4.8...babel-preset-gatsby@0.4.9) (2020-06-09) + +**Note:** Version bump only for package babel-preset-gatsby + ## [0.4.8](https://github.com/gatsbyjs/gatsby/compare/babel-preset-gatsby@0.4.7...babel-preset-gatsby@0.4.8) (2020-06-02) **Note:** Version bump only for package babel-preset-gatsby diff --git a/packages/babel-preset-gatsby/package.json b/packages/babel-preset-gatsby/package.json index 09e6fdb3412ef..3d30cc8f847f7 100644 --- a/packages/babel-preset-gatsby/package.json +++ b/packages/babel-preset-gatsby/package.json @@ -1,6 +1,6 @@ { "name": "babel-preset-gatsby", - "version": "0.4.8", + "version": "0.4.9", "author": "Philipp Spiess ", "repository": { "type": "git", @@ -21,7 +21,7 @@ "babel-plugin-dynamic-import-node": "^2.3.3", "babel-plugin-macros": "^2.8.0", "babel-plugin-transform-react-remove-prop-types": "^0.4.24", - "gatsby-core-utils": "^1.3.4" + "gatsby-core-utils": "^1.3.5" }, "peerDependencies": { "@babel/core": "^7.0.0" @@ -35,7 +35,7 @@ }, "devDependencies": { "@babel/cli": "^7.10.1", - "babel-preset-gatsby-package": "^0.4.3", + "babel-preset-gatsby-package": "^0.4.4", "cross-env": "^5.2.1", "slash": "^3.0.0" }, diff --git a/packages/gatsby-admin/CHANGELOG.md b/packages/gatsby-admin/CHANGELOG.md index 3eecbcb7c1a79..a8dd7a3049b98 100644 --- a/packages/gatsby-admin/CHANGELOG.md +++ b/packages/gatsby-admin/CHANGELOG.md @@ -3,6 +3,18 @@ All notable changes to this project will be documented in this file. See [Conventional Commits](https://conventionalcommits.org) for commit guidelines. +## [0.1.67](https://github.com/gatsbyjs/gatsby/compare/gatsby-admin@0.1.66...gatsby-admin@0.1.67) (2020-06-09) + +**Note:** Version bump only for package gatsby-admin + +## [0.1.66](https://github.com/gatsbyjs/gatsby/compare/gatsby-admin@0.1.65...gatsby-admin@0.1.66) (2020-06-09) + +**Note:** Version bump only for package gatsby-admin + +## [0.1.65](https://github.com/gatsbyjs/gatsby/compare/gatsby-admin@0.1.64...gatsby-admin@0.1.65) (2020-06-05) + +**Note:** Version bump only for package gatsby-admin + ## [0.1.64](https://github.com/gatsbyjs/gatsby/compare/gatsby-admin@0.1.63...gatsby-admin@0.1.64) (2020-06-04) **Note:** Version bump only for package gatsby-admin diff --git a/packages/gatsby-admin/gatsby-config.js b/packages/gatsby-admin/gatsby-config.js index ce8d411660037..464f83eebd0aa 100644 --- a/packages/gatsby-admin/gatsby-config.js +++ b/packages/gatsby-admin/gatsby-config.js @@ -1,4 +1,4 @@ module.exports = { - plugins: [], + plugins: [`gatsby-plugin-react-helmet`], pathPrefix: `/___admin` -} \ No newline at end of file +}; \ No newline at end of file diff --git a/packages/gatsby-admin/package.json b/packages/gatsby-admin/package.json index 88b011fac6110..ef3127f89d9d2 100644 --- a/packages/gatsby-admin/package.json +++ b/packages/gatsby-admin/package.json @@ -1,6 +1,6 @@ { "name": "gatsby-admin", - "version": "0.1.64", + "version": "0.1.67", "main": "index.js", "author": "Max Stoiber", "license": "MIT", @@ -17,12 +17,13 @@ "@typescript-eslint/parser": "^2.28.0", "csstype": "^2.6.10", "formik": "^2.1.4", - "gatsby": "^2.23.0", + "gatsby": "^2.23.3", "gatsby-interface": "0.0.167", - "gatsby-plugin-typescript": "^2.4.4", - "gatsby-source-graphql": "^2.5.3", + "gatsby-plugin-typescript": "^2.4.6", + "gatsby-source-graphql": "^2.5.4", "react": "^16.12.0", "react-dom": "^16.12.0", + "react-helmet": "^6.0.0", "react-icons": "^3.10.0", "strict-ui": "^0.1.3", "subscriptions-transport-ws": "^0.9.16", diff --git a/packages/gatsby-admin/src/components/layout.tsx b/packages/gatsby-admin/src/components/layout.tsx index 02eafbfb8f7ab..3ee059b972c03 100644 --- a/packages/gatsby-admin/src/components/layout.tsx +++ b/packages/gatsby-admin/src/components/layout.tsx @@ -2,12 +2,17 @@ import { jsx, Flex } from "strict-ui" import Providers from "./providers" import Navbar from "./navbar" +import { Helmet } from "react-helmet" const Layout: React.FC<{}> = ({ children }) => ( + + Gatsby Admin + + - {children} +
{children}
 ) diff --git a/packages/gatsby-admin/src/components/navbar.tsx b/packages/gatsby-admin/src/components/navbar.tsx index 9da44794f5d08..99873d41f07f0 100644 --- a/packages/gatsby-admin/src/components/navbar.tsx +++ b/packages/gatsby-admin/src/components/navbar.tsx @@ -16,6 +16,7 @@ const Navbar: React.FC<{}> = () => { return ( = () => { +const SecondaryButton: React.FC = props => ( + +) + +const InstallInput: React.FC<{ for: string }> = props => { + const inputId = `install-${props.for}` const [value, setValue] = React.useState(``) - const [, installGatbyPlugin] = useMutation(` + const [{ fetching }, installGatbyPlugin] = useMutation(` mutation installGatsbyPlugin($name: String!) { createNpmPackage(npmPackage: { name: $name, @@ -36,28 +56,45 @@ const InstallInput: React.FC<{}> = () => { { evt.preventDefault() + if (value.indexOf(`gatsby-`) !== 0) return + installGatbyPlugin({ name: value, }) }} > - - setValue(e.target.value)} - sx={{ - backgroundColor: `background`, - borderColor: `grey.60`, - color: `white`, - width: `initial`, - "&:focus": { - borderColor: `grey.40`, - // TODO(@mxstbr): Fix this focus outline - boxShadow: `none`, - }, - }} - /> + + + + + + + setValue(e.target.value)} + sx={{ + backgroundColor: `background`, + borderColor: `grey.60`, + color: `white`, + width: `initial`, + "&:focus": { + borderColor: `grey.40`, + // TODO(@mxstbr): Fix this focus outline + boxShadow: `none`, + }, + }} + /> + + Install + + + ) @@ -85,44 +122,43 @@ const DestroyButton: React.FC<{ name: string }> = ({ name }) => { `) return ( - + ) } const SectionHeading: React.FC = props => ( - + ) -const PluginCard: React.FC<{ name: string }> = ({ name }) => ( +const PluginCard: React.FC<{ + plugin: { name: string; description?: string } +}> = ({ plugin }) => ( - - {name} - + + {plugin.name} + - Start setting up your sites styles with one of our curated recipes to - write styling the way you love. Choose from libraries like theme-UI, - emotion, and styled-components. + {plugin.description || No description.} - + ) @@ -134,6 +170,7 @@ const Index: React.FC<{}> = () => { allGatsbyPlugin { nodes { name + description id shadowedFiles shadowableFiles @@ -150,25 +187,25 @@ const Index: React.FC<{}> = () => { return ( Plugins - + {data.allGatsbyPlugin.nodes .filter(plugin => plugin.name.indexOf(`gatsby-plugin`) === 0) .map(plugin => ( - + ))} - + Themes - + {data.allGatsbyPlugin.nodes .filter(plugin => plugin.name.indexOf(`gatsby-theme`) === 0) .map(plugin => ( - + ))} - + ) } diff --git a/packages/gatsby-cli/CHANGELOG.md b/packages/gatsby-cli/CHANGELOG.md index 36704e68dd68d..ba32ba2b54623 100644 --- a/packages/gatsby-cli/CHANGELOG.md +++ b/packages/gatsby-cli/CHANGELOG.md @@ -3,6 +3,14 @@ All notable changes to this project will be documented in this file. See [Conventional Commits](https://conventionalcommits.org) for commit guidelines. +## [2.12.45](https://github.com/gatsbyjs/gatsby/compare/gatsby-cli@2.12.44...gatsby-cli@2.12.45) (2020-06-09) + +**Note:** Version bump only for package gatsby-cli + +## [2.12.44](https://github.com/gatsbyjs/gatsby/compare/gatsby-cli@2.12.43...gatsby-cli@2.12.44) (2020-06-05) + +**Note:** Version bump only for package gatsby-cli + ## [2.12.43](https://github.com/gatsbyjs/gatsby/compare/gatsby-cli@2.12.42...gatsby-cli@2.12.43) (2020-06-03) **Note:** Version bump only for package gatsby-cli diff --git a/packages/gatsby-cli/package.json b/packages/gatsby-cli/package.json index 5e6f2873bec93..2fd9002e901da 100644 --- a/packages/gatsby-cli/package.json +++ b/packages/gatsby-cli/package.json @@ -1,7 +1,7 @@ { "name": "gatsby-cli", "description": "Gatsby command-line interface for creating new sites and running Gatsby commands", - "version": "2.12.43", + "version": "2.12.45", "author": "Kyle Mathews ", "bin": { "gatsby": "lib/index.js" @@ -25,9 +25,9 @@ "execa": "^3.4.0", "fs-exists-cached": "^1.0.0", "fs-extra": "^8.1.0", - "gatsby-core-utils": "^1.3.4", - "gatsby-recipes": "^0.1.37", - "gatsby-telemetry": "^1.3.10", + "gatsby-core-utils": "^1.3.5", + "gatsby-recipes": "^0.1.39", + "gatsby-telemetry": "^1.3.11", "hosted-git-info": "^3.0.4", "ink": "^2.7.1", "ink-spinner": "^3.0.1", @@ -58,7 +58,7 @@ "@babel/core": "^7.10.2", "@types/hosted-git-info": "^3.0.0", "@types/yargs": "^15.0.4", - "babel-preset-gatsby-package": "^0.4.3", + "babel-preset-gatsby-package": "^0.4.4", "cross-env": "^5.2.1", "typescript": "^3.9.3" }, diff --git a/packages/gatsby-codemods/CHANGELOG.md b/packages/gatsby-codemods/CHANGELOG.md index b53a22fbe4b38..f98ab71bf514d 100644 --- a/packages/gatsby-codemods/CHANGELOG.md +++ b/packages/gatsby-codemods/CHANGELOG.md @@ -3,6 +3,10 @@ All notable changes to this project will be documented in this file. See [Conventional Commits](https://conventionalcommits.org) for commit guidelines. +## [1.3.4](https://github.com/gatsbyjs/gatsby/compare/gatsby-codemods@1.3.3...gatsby-codemods@1.3.4) (2020-06-09) + +**Note:** Version bump only for package gatsby-codemods + ## [1.3.3](https://github.com/gatsbyjs/gatsby/compare/gatsby-codemods@1.3.2...gatsby-codemods@1.3.3) (2020-06-02) **Note:** Version bump only for package gatsby-codemods diff --git a/packages/gatsby-codemods/package.json b/packages/gatsby-codemods/package.json index f114cae788b27..8e81e14c7d130 100644 --- a/packages/gatsby-codemods/package.json +++ b/packages/gatsby-codemods/package.json @@ -1,6 +1,6 @@ { "name": "gatsby-codemods", - "version": "1.3.3", + "version": "1.3.4", "description": "A collection of codemod scripts for use with JSCodeshift that help migrate to newer versions of Gatsby.", "main": "index.js", "scripts": { @@ -29,7 +29,7 @@ "devDependencies": { "@babel/cli": "^7.10.1", "@babel/core": "^7.10.2", - "babel-preset-gatsby-package": "^0.4.3", + "babel-preset-gatsby-package": "^0.4.4", "cross-env": "^5.2.1", "jscodeshift": "^0.7.0" }, diff --git a/packages/gatsby-core-utils/CHANGELOG.md b/packages/gatsby-core-utils/CHANGELOG.md index 403fd1d1d74c4..840b3fea9b3ff 100644 --- a/packages/gatsby-core-utils/CHANGELOG.md +++ b/packages/gatsby-core-utils/CHANGELOG.md @@ -3,6 +3,10 @@ All notable changes to this project will be documented in this file. See [Conventional Commits](https://conventionalcommits.org) for commit guidelines. +## [1.3.5](https://github.com/gatsbyjs/gatsby/compare/gatsby-core-utils@1.3.4...gatsby-core-utils@1.3.5) (2020-06-09) + +**Note:** Version bump only for package gatsby-core-utils + ## [1.3.4](https://github.com/gatsbyjs/gatsby/compare/gatsby-core-utils@1.3.3...gatsby-core-utils@1.3.4) (2020-06-02) **Note:** Version bump only for package gatsby-core-utils diff --git a/packages/gatsby-core-utils/package.json b/packages/gatsby-core-utils/package.json index e0aeada26be44..0f14261376d91 100644 --- a/packages/gatsby-core-utils/package.json +++ b/packages/gatsby-core-utils/package.json @@ -1,6 +1,6 @@ { "name": "gatsby-core-utils", - "version": "1.3.4", + "version": "1.3.5", "description": "A collection of gatsby utils used in different gatsby packages", "keywords": [ "gatsby", @@ -40,7 +40,7 @@ "@babel/cli": "^7.10.1", "@babel/core": "^7.10.2", "@types/ci-info": "2.0.0", - "babel-preset-gatsby-package": "^0.4.3", + "babel-preset-gatsby-package": "^0.4.4", "cross-env": "^5.2.1", "typescript": "^3.9.3" }, diff --git a/packages/gatsby-cypress/CHANGELOG.md b/packages/gatsby-cypress/CHANGELOG.md index 7e37fc5506780..8de50a3ce48e9 100644 --- a/packages/gatsby-cypress/CHANGELOG.md +++ b/packages/gatsby-cypress/CHANGELOG.md @@ -3,6 +3,10 @@ All notable changes to this project will be documented in this file. See [Conventional Commits](https://conventionalcommits.org) for commit guidelines. +## [0.4.4](https://github.com/gatsbyjs/gatsby/compare/gatsby-cypress@0.4.3...gatsby-cypress@0.4.4) (2020-06-09) + +**Note:** Version bump only for package gatsby-cypress + ## [0.4.3](https://github.com/gatsbyjs/gatsby/compare/gatsby-cypress@0.4.2...gatsby-cypress@0.4.3) (2020-06-02) **Note:** Version bump only for package gatsby-cypress diff --git a/packages/gatsby-cypress/package.json b/packages/gatsby-cypress/package.json index 5c38669a9fe9f..025e44643de8b 100644 --- a/packages/gatsby-cypress/package.json +++ b/packages/gatsby-cypress/package.json @@ -1,6 +1,6 @@ { "name": "gatsby-cypress", - "version": "0.4.3", + "version": "0.4.4", "description": "Cypress tools for Gatsby projects", "main": "index.js", "repository": { @@ -20,7 +20,7 @@ "devDependencies": { "@babel/cli": "^7.10.1", "@babel/core": "^7.10.2", - "babel-preset-gatsby-package": "^0.4.3", + "babel-preset-gatsby-package": "^0.4.4", "cross-env": "^5.2.1" }, "keywords": [ diff --git a/packages/gatsby-dev-cli/CHANGELOG.md b/packages/gatsby-dev-cli/CHANGELOG.md index c112eed21de5a..b4ff429845c95 100644 --- a/packages/gatsby-dev-cli/CHANGELOG.md +++ b/packages/gatsby-dev-cli/CHANGELOG.md @@ -3,6 +3,10 @@ All notable changes to this project will be documented in this file. See [Conventional Commits](https://conventionalcommits.org) for commit guidelines. +## [2.7.9](https://github.com/gatsbyjs/gatsby/compare/gatsby-dev-cli@2.7.8...gatsby-dev-cli@2.7.9) (2020-06-09) + +**Note:** Version bump only for package gatsby-dev-cli + ## [2.7.8](https://github.com/gatsbyjs/gatsby/compare/gatsby-dev-cli@2.7.7...gatsby-dev-cli@2.7.8) (2020-06-02) ### Bug Fixes diff --git a/packages/gatsby-dev-cli/package.json b/packages/gatsby-dev-cli/package.json index f9d8fc5045e21..c91683db5c839 100644 --- a/packages/gatsby-dev-cli/package.json +++ b/packages/gatsby-dev-cli/package.json @@ -1,7 +1,7 @@ { "name": "gatsby-dev-cli", "description": "CLI helpers for contributors working on Gatsby", - "version": "2.7.8", + "version": "2.7.9", "author": "Kyle Mathews ", "bin": { "gatsby-dev": "./dist/index.js" @@ -27,7 +27,7 @@ "devDependencies": { "@babel/cli": "^7.10.1", "@babel/core": "^7.10.2", - "babel-preset-gatsby-package": "^0.4.3", + "babel-preset-gatsby-package": "^0.4.4", "cross-env": "^5.2.1" }, "homepage": "https://github.com/gatsbyjs/gatsby/tree/master/packages/gatsby-dev-cli#readme", diff --git a/packages/gatsby-graphiql-explorer/CHANGELOG.md b/packages/gatsby-graphiql-explorer/CHANGELOG.md index eea934e563f1c..4bdf7b5e92037 100644 --- a/packages/gatsby-graphiql-explorer/CHANGELOG.md +++ b/packages/gatsby-graphiql-explorer/CHANGELOG.md @@ -3,6 +3,10 @@ All notable changes to this project will be documented in this file. See [Conventional Commits](https://conventionalcommits.org) for commit guidelines. +## [0.4.5](https://github.com/gatsbyjs/gatsby/compare/gatsby-graphiql-explorer@0.4.4...gatsby-graphiql-explorer@0.4.5) (2020-06-09) + +**Note:** Version bump only for package gatsby-graphiql-explorer + ## [0.4.4](https://github.com/gatsbyjs/gatsby/compare/gatsby-graphiql-explorer@0.4.3...gatsby-graphiql-explorer@0.4.4) (2020-06-02) **Note:** Version bump only for package gatsby-graphiql-explorer diff --git a/packages/gatsby-graphiql-explorer/package.json b/packages/gatsby-graphiql-explorer/package.json index 4d4a1bb06f38b..5e63d539c4cd1 100644 --- a/packages/gatsby-graphiql-explorer/package.json +++ b/packages/gatsby-graphiql-explorer/package.json @@ -1,6 +1,6 @@ { "name": "gatsby-graphiql-explorer", - "version": "0.4.4", + "version": "0.4.5", "description": "GraphiQL IDE with custom features for Gatsby users", "main": "index.js", "scripts": { @@ -38,7 +38,7 @@ "@babel/preset-env": "^7.10.2", "@babel/preset-react": "^7.10.1", "babel-loader": "^8.1.0", - "babel-preset-gatsby-package": "^0.4.3", + "babel-preset-gatsby-package": "^0.4.4", "core-js": "^2.6.11", "cross-env": "^5.2.1", "css-loader": "^1.0.1", diff --git a/packages/gatsby-image/CHANGELOG.md b/packages/gatsby-image/CHANGELOG.md index 226cdf7f258bb..4f9dcf8c828b1 100644 --- a/packages/gatsby-image/CHANGELOG.md +++ b/packages/gatsby-image/CHANGELOG.md @@ -3,6 +3,10 @@ All notable changes to this project will be documented in this file. See [Conventional Commits](https://conventionalcommits.org) for commit guidelines. +## [2.4.7](https://github.com/gatsbyjs/gatsby/compare/gatsby-image@2.4.6...gatsby-image@2.4.7) (2020-06-09) + +**Note:** Version bump only for package gatsby-image + ## [2.4.6](https://github.com/gatsbyjs/gatsby/compare/gatsby-image@2.4.5...gatsby-image@2.4.6) (2020-06-02) **Note:** Version bump only for package gatsby-image diff --git a/packages/gatsby-image/package.json b/packages/gatsby-image/package.json index 6ebcae327a21f..53182bb0836de 100644 --- a/packages/gatsby-image/package.json +++ b/packages/gatsby-image/package.json @@ -1,7 +1,7 @@ { "name": "gatsby-image", "description": "Lazy-loading React image component with optional support for the blur-up effect.", - "version": "2.4.6", + "version": "2.4.7", "author": "Kyle Mathews ", "bugs": { "url": "https://github.com/gatsbyjs/gatsby/issues" @@ -15,7 +15,7 @@ "@babel/cli": "^7.10.1", "@babel/core": "^7.10.2", "@testing-library/react": "^9.5.0", - "babel-preset-gatsby-package": "^0.4.3", + "babel-preset-gatsby-package": "^0.4.4", "cross-env": "^5.2.1" }, "homepage": "https://github.com/gatsbyjs/gatsby/tree/master/packages/gatsby-image#readme", diff --git a/packages/gatsby-link/CHANGELOG.md b/packages/gatsby-link/CHANGELOG.md index 528cb4d63f5d7..a76d11694afd0 100644 --- a/packages/gatsby-link/CHANGELOG.md +++ b/packages/gatsby-link/CHANGELOG.md @@ -3,6 +3,10 @@ All notable changes to this project will be documented in this file. See [Conventional Commits](https://conventionalcommits.org) for commit guidelines. +## [2.4.6](https://github.com/gatsbyjs/gatsby/compare/gatsby-link@2.4.5...gatsby-link@2.4.6) (2020-06-09) + +**Note:** Version bump only for package gatsby-link + ## [2.4.5](https://github.com/gatsbyjs/gatsby/compare/gatsby-link@2.4.4...gatsby-link@2.4.5) (2020-06-03) ### Bug Fixes diff --git a/packages/gatsby-link/package.json b/packages/gatsby-link/package.json index 810c06c625719..9c71f1ad61be0 100644 --- a/packages/gatsby-link/package.json +++ b/packages/gatsby-link/package.json @@ -1,7 +1,7 @@ { "name": "gatsby-link", "description": "An enhanced Link component for Gatsby sites with support for resource prefetching", - "version": "2.4.5", + "version": "2.4.6", "author": "Kyle Mathews ", "bugs": { "url": "https://github.com/gatsbyjs/gatsby/issues" @@ -15,7 +15,7 @@ "@babel/cli": "^7.10.1", "@babel/core": "^7.10.2", "@testing-library/react": "^9.5.0", - "babel-preset-gatsby-package": "^0.4.3", + "babel-preset-gatsby-package": "^0.4.4", "cross-env": "^5.2.1" }, "peerDependencies": { diff --git a/packages/gatsby-page-utils/CHANGELOG.md b/packages/gatsby-page-utils/CHANGELOG.md index 810ac7f93da9c..fe1c7ab4be7a1 100644 --- a/packages/gatsby-page-utils/CHANGELOG.md +++ b/packages/gatsby-page-utils/CHANGELOG.md @@ -3,6 +3,10 @@ All notable changes to this project will be documented in this file. See [Conventional Commits](https://conventionalcommits.org) for commit guidelines. +## [0.2.9](https://github.com/gatsbyjs/gatsby/compare/gatsby-page-utils@0.2.8...gatsby-page-utils@0.2.9) (2020-06-09) + +**Note:** Version bump only for package gatsby-page-utils + ## [0.2.8](https://github.com/gatsbyjs/gatsby/compare/gatsby-page-utils@0.2.7...gatsby-page-utils@0.2.8) (2020-06-02) **Note:** Version bump only for package gatsby-page-utils diff --git a/packages/gatsby-page-utils/package.json b/packages/gatsby-page-utils/package.json index 42dd4f3b77e89..8456a0f42e071 100644 --- a/packages/gatsby-page-utils/package.json +++ b/packages/gatsby-page-utils/package.json @@ -1,6 +1,6 @@ { "name": "gatsby-page-utils", - "version": "0.2.8", + "version": "0.2.9", "description": "Gatsby library that helps creating pages", "main": "dist/index.js", "scripts": { @@ -24,7 +24,7 @@ "bluebird": "^3.7.2", "chokidar": "3.4.0", "fs-exists-cached": "^1.0.0", - "gatsby-core-utils": "^1.3.4", + "gatsby-core-utils": "^1.3.5", "glob": "^7.1.6", "lodash": "^4.17.15", "micromatch": "^3.1.10" @@ -32,7 +32,7 @@ "devDependencies": { "@babel/cli": "^7.10.1", "@babel/core": "^7.10.2", - "babel-preset-gatsby-package": "^0.4.3", + "babel-preset-gatsby-package": "^0.4.4", "cross-env": "^5.2.1" }, "files": [ diff --git a/packages/gatsby-plugin-benchmark-reporting/CHANGELOG.md b/packages/gatsby-plugin-benchmark-reporting/CHANGELOG.md index 6378fd76a9f6f..ae4b8a8a2725f 100644 --- a/packages/gatsby-plugin-benchmark-reporting/CHANGELOG.md +++ b/packages/gatsby-plugin-benchmark-reporting/CHANGELOG.md @@ -3,6 +3,10 @@ All notable changes to this project will be documented in this file. See [Conventional Commits](https://conventionalcommits.org) for commit guidelines. +## [0.2.7](https://github.com/gatsbyjs/gatsby/compare/gatsby-plugin-benchmark-reporting@0.2.6...gatsby-plugin-benchmark-reporting@0.2.7) (2020-06-09) + +**Note:** Version bump only for package gatsby-plugin-benchmark-reporting + ## [0.2.6](https://github.com/gatsbyjs/gatsby/compare/gatsby-plugin-benchmark-reporting@0.2.5...gatsby-plugin-benchmark-reporting@0.2.6) (2020-06-02) **Note:** Version bump only for package gatsby-plugin-benchmark-reporting diff --git a/packages/gatsby-plugin-benchmark-reporting/package.json b/packages/gatsby-plugin-benchmark-reporting/package.json index 8c237042ad754..18763c4267345 100644 --- a/packages/gatsby-plugin-benchmark-reporting/package.json +++ b/packages/gatsby-plugin-benchmark-reporting/package.json @@ -1,7 +1,7 @@ { "name": "gatsby-plugin-benchmark-reporting", "description": "Gatsby Benchmark Reporting", - "version": "0.2.6", + "version": "0.2.7", "author": "Peter van der Zee ", "bugs": { "url": "https://github.com/gatsbyjs/gatsby/issues" @@ -16,7 +16,7 @@ "devDependencies": { "@babel/cli": "^7.10.1", "@babel/core": "^7.10.2", - "babel-preset-gatsby-package": "^0.4.3" + "babel-preset-gatsby-package": "^0.4.4" }, "dependencies": { "fast-glob": "^3.2.2", diff --git a/packages/gatsby-plugin-canonical-urls/CHANGELOG.md b/packages/gatsby-plugin-canonical-urls/CHANGELOG.md index aa7e6a1dac1f7..274b9a82ea51e 100644 --- a/packages/gatsby-plugin-canonical-urls/CHANGELOG.md +++ b/packages/gatsby-plugin-canonical-urls/CHANGELOG.md @@ -3,6 +3,10 @@ All notable changes to this project will be documented in this file. See [Conventional Commits](https://conventionalcommits.org) for commit guidelines. +## [2.3.4](https://github.com/gatsbyjs/gatsby/compare/gatsby-plugin-canonical-urls@2.3.3...gatsby-plugin-canonical-urls@2.3.4) (2020-06-09) + +**Note:** Version bump only for package gatsby-plugin-canonical-urls + ## [2.3.3](https://github.com/gatsbyjs/gatsby/compare/gatsby-plugin-canonical-urls@2.3.2...gatsby-plugin-canonical-urls@2.3.3) (2020-06-02) **Note:** Version bump only for package gatsby-plugin-canonical-urls diff --git a/packages/gatsby-plugin-canonical-urls/package.json b/packages/gatsby-plugin-canonical-urls/package.json index 3de5c220774bc..6fd1f180c9751 100644 --- a/packages/gatsby-plugin-canonical-urls/package.json +++ b/packages/gatsby-plugin-canonical-urls/package.json @@ -1,7 +1,7 @@ { "name": "gatsby-plugin-canonical-urls", "description": "Add canonical links to HTML pages Gatsby generates.", - "version": "2.3.3", + "version": "2.3.4", "author": "Kyle Mathews ", "bugs": { "url": "https://github.com/gatsbyjs/gatsby/issues" @@ -12,7 +12,7 @@ "devDependencies": { "@babel/cli": "^7.10.1", "@babel/core": "^7.10.2", - "babel-preset-gatsby-package": "^0.4.3", + "babel-preset-gatsby-package": "^0.4.4", "cross-env": "^5.2.1" }, "homepage": "https://github.com/gatsbyjs/gatsby/tree/master/packages/gatsby-plugin-canonical-urls#readme", diff --git a/packages/gatsby-plugin-catch-links/CHANGELOG.md b/packages/gatsby-plugin-catch-links/CHANGELOG.md index 25fdba27b7943..bd0168cc52e9d 100644 --- a/packages/gatsby-plugin-catch-links/CHANGELOG.md +++ b/packages/gatsby-plugin-catch-links/CHANGELOG.md @@ -3,6 +3,10 @@ All notable changes to this project will be documented in this file. See [Conventional Commits](https://conventionalcommits.org) for commit guidelines. +## [2.3.5](https://github.com/gatsbyjs/gatsby/compare/gatsby-plugin-catch-links@2.3.4...gatsby-plugin-catch-links@2.3.5) (2020-06-09) + +**Note:** Version bump only for package gatsby-plugin-catch-links + ## [2.3.4](https://github.com/gatsbyjs/gatsby/compare/gatsby-plugin-catch-links@2.3.3...gatsby-plugin-catch-links@2.3.4) (2020-06-02) **Note:** Version bump only for package gatsby-plugin-catch-links diff --git a/packages/gatsby-plugin-catch-links/package.json b/packages/gatsby-plugin-catch-links/package.json index b4e3997881bfd..c14636d91af02 100644 --- a/packages/gatsby-plugin-catch-links/package.json +++ b/packages/gatsby-plugin-catch-links/package.json @@ -1,7 +1,7 @@ { "name": "gatsby-plugin-catch-links", "description": "Intercepts local links from markdown and other non-react pages and does a client-side pushState to avoid the browser having to refresh the page.", - "version": "2.3.4", + "version": "2.3.5", "author": "Kyle Mathews ", "bugs": { "url": "https://github.com/gatsbyjs/gatsby/issues" @@ -13,7 +13,7 @@ "devDependencies": { "@babel/cli": "^7.10.1", "@babel/core": "^7.10.2", - "babel-preset-gatsby-package": "^0.4.3", + "babel-preset-gatsby-package": "^0.4.4", "cross-env": "^5.2.1" }, "homepage": "https://github.com/gatsbyjs/gatsby/tree/master/packages/gatsby-plugin-catch-links#readme", diff --git a/packages/gatsby-plugin-coffeescript/CHANGELOG.md b/packages/gatsby-plugin-coffeescript/CHANGELOG.md index d4e44170add0a..d7563e10d53a2 100644 --- a/packages/gatsby-plugin-coffeescript/CHANGELOG.md +++ b/packages/gatsby-plugin-coffeescript/CHANGELOG.md @@ -3,6 +3,10 @@ All notable changes to this project will be documented in this file. See [Conventional Commits](https://conventionalcommits.org) for commit guidelines. +## [2.3.4](https://github.com/gatsbyjs/gatsby/compare/gatsby-plugin-coffeescript@2.3.3...gatsby-plugin-coffeescript@2.3.4) (2020-06-09) + +**Note:** Version bump only for package gatsby-plugin-coffeescript + ## [2.3.3](https://github.com/gatsbyjs/gatsby/compare/gatsby-plugin-coffeescript@2.3.2...gatsby-plugin-coffeescript@2.3.3) (2020-06-02) **Note:** Version bump only for package gatsby-plugin-coffeescript diff --git a/packages/gatsby-plugin-coffeescript/package.json b/packages/gatsby-plugin-coffeescript/package.json index 73d17e2791bab..3b45770172f0e 100644 --- a/packages/gatsby-plugin-coffeescript/package.json +++ b/packages/gatsby-plugin-coffeescript/package.json @@ -1,7 +1,7 @@ { "name": "gatsby-plugin-coffeescript", "description": "Adds CoffeeScript support for Gatsby", - "version": "2.3.3", + "version": "2.3.4", "author": "Kyle Mathews ", "bugs": { "url": "https://github.com/gatsbyjs/gatsby/issues" @@ -18,7 +18,7 @@ "devDependencies": { "@babel/cli": "^7.10.1", "@babel/core": "^7.10.2", - "babel-preset-gatsby-package": "^0.4.3", + "babel-preset-gatsby-package": "^0.4.4", "cross-env": "^5.2.1" }, "homepage": "https://github.com/gatsbyjs/gatsby/tree/master/packages/gatsby-plugin-coffeescript#readme", diff --git a/packages/gatsby-plugin-create-client-paths/CHANGELOG.md b/packages/gatsby-plugin-create-client-paths/CHANGELOG.md index 36cbbd11fd886..e000e7280870a 100644 --- a/packages/gatsby-plugin-create-client-paths/CHANGELOG.md +++ b/packages/gatsby-plugin-create-client-paths/CHANGELOG.md @@ -3,6 +3,10 @@ All notable changes to this project will be documented in this file. See [Conventional Commits](https://conventionalcommits.org) for commit guidelines. +## [2.3.4](https://github.com/gatsbyjs/gatsby/compare/gatsby-plugin-create-client-paths@2.3.3...gatsby-plugin-create-client-paths@2.3.4) (2020-06-09) + +**Note:** Version bump only for package gatsby-plugin-create-client-paths + ## [2.3.3](https://github.com/gatsbyjs/gatsby/compare/gatsby-plugin-create-client-paths@2.3.2...gatsby-plugin-create-client-paths@2.3.3) (2020-06-02) **Note:** Version bump only for package gatsby-plugin-create-client-paths diff --git a/packages/gatsby-plugin-create-client-paths/package.json b/packages/gatsby-plugin-create-client-paths/package.json index a0031efb65b0b..4360ceb9994ad 100644 --- a/packages/gatsby-plugin-create-client-paths/package.json +++ b/packages/gatsby-plugin-create-client-paths/package.json @@ -1,7 +1,7 @@ { "name": "gatsby-plugin-create-client-paths", "description": "Gatsby-plugin for creating paths that exist only on the client", - "version": "2.3.3", + "version": "2.3.4", "author": "scott.eckenthal@gmail.com", "bugs": { "url": "https://github.com/gatsbyjs/gatsby/issues" @@ -12,7 +12,7 @@ "devDependencies": { "@babel/cli": "^7.10.1", "@babel/core": "^7.10.2", - "babel-preset-gatsby-package": "^0.4.3", + "babel-preset-gatsby-package": "^0.4.4", "cross-env": "^5.2.1" }, "homepage": "https://github.com/gatsbyjs/gatsby/tree/master/packages/gatsby-plugin-create-client-paths#readme", diff --git a/packages/gatsby-plugin-cxs/CHANGELOG.md b/packages/gatsby-plugin-cxs/CHANGELOG.md index 260df69d4ce93..a1f3b96fdef5a 100644 --- a/packages/gatsby-plugin-cxs/CHANGELOG.md +++ b/packages/gatsby-plugin-cxs/CHANGELOG.md @@ -3,6 +3,10 @@ All notable changes to this project will be documented in this file. See [Conventional Commits](https://conventionalcommits.org) for commit guidelines. +## [2.3.4](https://github.com/gatsbyjs/gatsby/compare/gatsby-plugin-cxs@2.3.3...gatsby-plugin-cxs@2.3.4) (2020-06-09) + +**Note:** Version bump only for package gatsby-plugin-cxs + ## [2.3.3](https://github.com/gatsbyjs/gatsby/compare/gatsby-plugin-cxs@2.3.2...gatsby-plugin-cxs@2.3.3) (2020-06-02) **Note:** Version bump only for package gatsby-plugin-cxs diff --git a/packages/gatsby-plugin-cxs/package.json b/packages/gatsby-plugin-cxs/package.json index 71e604bb5a798..6b450e1e2843d 100644 --- a/packages/gatsby-plugin-cxs/package.json +++ b/packages/gatsby-plugin-cxs/package.json @@ -1,7 +1,7 @@ { "name": "gatsby-plugin-cxs", "description": "Gatsby plugin to add SSR support for ctx", - "version": "2.3.3", + "version": "2.3.4", "author": "Chen-Tai Hou ", "bugs": { "url": "https://github.com/gatsbyjs/gatsby/issues" @@ -12,7 +12,7 @@ "devDependencies": { "@babel/cli": "^7.10.1", "@babel/core": "^7.10.2", - "babel-preset-gatsby-package": "^0.4.3", + "babel-preset-gatsby-package": "^0.4.4", "cross-env": "^5.2.1", "cxs": "^6.2.0" }, diff --git a/packages/gatsby-plugin-emotion/CHANGELOG.md b/packages/gatsby-plugin-emotion/CHANGELOG.md index 24e92f162c01c..792073427d63c 100644 --- a/packages/gatsby-plugin-emotion/CHANGELOG.md +++ b/packages/gatsby-plugin-emotion/CHANGELOG.md @@ -3,6 +3,10 @@ All notable changes to this project will be documented in this file. See [Conventional Commits](https://conventionalcommits.org) for commit guidelines. +## [4.3.4](https://github.com/gatsbyjs/gatsby/compare/gatsby-plugin-emotion@4.3.3...gatsby-plugin-emotion@4.3.4) (2020-06-09) + +**Note:** Version bump only for package gatsby-plugin-emotion + ## [4.3.3](https://github.com/gatsbyjs/gatsby/compare/gatsby-plugin-emotion@4.3.2...gatsby-plugin-emotion@4.3.3) (2020-06-02) **Note:** Version bump only for package gatsby-plugin-emotion diff --git a/packages/gatsby-plugin-emotion/package.json b/packages/gatsby-plugin-emotion/package.json index 1f76b393f6a7b..b6f86ae5fa123 100644 --- a/packages/gatsby-plugin-emotion/package.json +++ b/packages/gatsby-plugin-emotion/package.json @@ -1,7 +1,7 @@ { "name": "gatsby-plugin-emotion", "description": "Gatsby plugin to add support for Emotion", - "version": "4.3.3", + "version": "4.3.4", "author": "Tegan Churchill ", "bugs": { "url": "https://github.com/gatsbyjs/gatsby/issues" @@ -13,7 +13,7 @@ "devDependencies": { "@babel/cli": "^7.10.1", "@babel/core": "^7.10.2", - "babel-preset-gatsby-package": "^0.4.3", + "babel-preset-gatsby-package": "^0.4.4", "cross-env": "^5.2.1" }, "peerDependencies": { diff --git a/packages/gatsby-plugin-facebook-analytics/CHANGELOG.md b/packages/gatsby-plugin-facebook-analytics/CHANGELOG.md index e81b5a165d4d9..097575d74865f 100644 --- a/packages/gatsby-plugin-facebook-analytics/CHANGELOG.md +++ b/packages/gatsby-plugin-facebook-analytics/CHANGELOG.md @@ -3,6 +3,10 @@ All notable changes to this project will be documented in this file. See [Conventional Commits](https://conventionalcommits.org) for commit guidelines. +## [2.4.4](https://github.com/gatsbyjs/gatsby/compare/gatsby-plugin-facebook-analytics@2.4.3...gatsby-plugin-facebook-analytics@2.4.4) (2020-06-09) + +**Note:** Version bump only for package gatsby-plugin-facebook-analytics + ## [2.4.3](https://github.com/gatsbyjs/gatsby/compare/gatsby-plugin-facebook-analytics@2.4.2...gatsby-plugin-facebook-analytics@2.4.3) (2020-06-02) **Note:** Version bump only for package gatsby-plugin-facebook-analytics diff --git a/packages/gatsby-plugin-facebook-analytics/package.json b/packages/gatsby-plugin-facebook-analytics/package.json index f98212b89a50a..986b6c6f49d75 100644 --- a/packages/gatsby-plugin-facebook-analytics/package.json +++ b/packages/gatsby-plugin-facebook-analytics/package.json @@ -1,7 +1,7 @@ { "name": "gatsby-plugin-facebook-analytics", "description": "Gatsby plugin to add facebook analytics onto a site", - "version": "2.4.3", + "version": "2.4.4", "author": "Yeison Daza ", "bugs": { "url": "https://github.com/gatsbyjs/gatsby/issues" @@ -12,7 +12,7 @@ "devDependencies": { "@babel/cli": "^7.10.1", "@babel/core": "^7.10.2", - "babel-preset-gatsby-package": "^0.4.3", + "babel-preset-gatsby-package": "^0.4.4", "cross-env": "^5.2.1" }, "homepage": "https://github.com/gatsbyjs/gatsby/tree/master/packages/gatsby-plugin-facebook-analytics#readme", diff --git a/packages/gatsby-plugin-feed/CHANGELOG.md b/packages/gatsby-plugin-feed/CHANGELOG.md index 4e68b0f7ab114..d38ee95ad911f 100644 --- a/packages/gatsby-plugin-feed/CHANGELOG.md +++ b/packages/gatsby-plugin-feed/CHANGELOG.md @@ -3,6 +3,10 @@ All notable changes to this project will be documented in this file. See [Conventional Commits](https://conventionalcommits.org) for commit guidelines. +## [2.5.5](https://github.com/gatsbyjs/gatsby/compare/gatsby-plugin-feed@2.5.4...gatsby-plugin-feed@2.5.5) (2020-06-09) + +**Note:** Version bump only for package gatsby-plugin-feed + ## [2.5.4](https://github.com/gatsbyjs/gatsby/compare/gatsby-plugin-feed@2.5.3...gatsby-plugin-feed@2.5.4) (2020-06-02) **Note:** Version bump only for package gatsby-plugin-feed diff --git a/packages/gatsby-plugin-feed/package.json b/packages/gatsby-plugin-feed/package.json index 2f0c2ec386aaf..b8ffa4c7d683f 100644 --- a/packages/gatsby-plugin-feed/package.json +++ b/packages/gatsby-plugin-feed/package.json @@ -1,7 +1,7 @@ { "name": "gatsby-plugin-feed", "description": "Creates an RSS feed for your Gatsby site.", - "version": "2.5.4", + "version": "2.5.5", "author": "Nicholas Young ", "bugs": { "url": "https://github.com/gatsbyjs/gatsby/issues" @@ -16,7 +16,7 @@ "devDependencies": { "@babel/cli": "^7.10.1", "@babel/core": "^7.10.2", - "babel-preset-gatsby-package": "^0.4.3", + "babel-preset-gatsby-package": "^0.4.4", "cross-env": "^5.2.1" }, "homepage": "https://github.com/gatsbyjs/gatsby/tree/master/packages/gatsby-plugin-feed#readme", diff --git a/packages/gatsby-plugin-flow/CHANGELOG.md b/packages/gatsby-plugin-flow/CHANGELOG.md index c123afc69976e..3813991c29565 100644 --- a/packages/gatsby-plugin-flow/CHANGELOG.md +++ b/packages/gatsby-plugin-flow/CHANGELOG.md @@ -3,6 +3,10 @@ All notable changes to this project will be documented in this file. See [Conventional Commits](https://conventionalcommits.org) for commit guidelines. +## [1.3.5](https://github.com/gatsbyjs/gatsby/compare/gatsby-plugin-flow@1.3.4...gatsby-plugin-flow@1.3.5) (2020-06-09) + +**Note:** Version bump only for package gatsby-plugin-flow + ## [1.3.4](https://github.com/gatsbyjs/gatsby/compare/gatsby-plugin-flow@1.3.3...gatsby-plugin-flow@1.3.4) (2020-06-02) **Note:** Version bump only for package gatsby-plugin-flow diff --git a/packages/gatsby-plugin-flow/package.json b/packages/gatsby-plugin-flow/package.json index 3d3db0e5940c2..f850c0c5a05e3 100644 --- a/packages/gatsby-plugin-flow/package.json +++ b/packages/gatsby-plugin-flow/package.json @@ -1,6 +1,6 @@ { "name": "gatsby-plugin-flow", - "version": "1.3.4", + "version": "1.3.5", "description": "Provides drop-in support for Flow by adding @babel/preset-flow.", "main": "index.js", "scripts": { @@ -30,7 +30,7 @@ "devDependencies": { "@babel/cli": "^7.10.1", "@babel/core": "^7.10.2", - "babel-preset-gatsby-package": "^0.4.3", + "babel-preset-gatsby-package": "^0.4.4", "cross-env": "^5.2.1" }, "engines": { diff --git a/packages/gatsby-plugin-fullstory/CHANGELOG.md b/packages/gatsby-plugin-fullstory/CHANGELOG.md index ec290d81e42b2..4a0a41e924647 100644 --- a/packages/gatsby-plugin-fullstory/CHANGELOG.md +++ b/packages/gatsby-plugin-fullstory/CHANGELOG.md @@ -3,6 +3,10 @@ All notable changes to this project will be documented in this file. See [Conventional Commits](https://conventionalcommits.org) for commit guidelines. +## [2.3.5](https://github.com/gatsbyjs/gatsby/compare/gatsby-plugin-fullstory@2.3.4...gatsby-plugin-fullstory@2.3.5) (2020-06-09) + +**Note:** Version bump only for package gatsby-plugin-fullstory + ## [2.3.4](https://github.com/gatsbyjs/gatsby/compare/gatsby-plugin-fullstory@2.3.3...gatsby-plugin-fullstory@2.3.4) (2020-06-02) **Note:** Version bump only for package gatsby-plugin-fullstory diff --git a/packages/gatsby-plugin-fullstory/package.json b/packages/gatsby-plugin-fullstory/package.json index 78e4f115c6319..7c4aaca8384cd 100644 --- a/packages/gatsby-plugin-fullstory/package.json +++ b/packages/gatsby-plugin-fullstory/package.json @@ -1,6 +1,6 @@ { "name": "gatsby-plugin-fullstory", - "version": "2.3.4", + "version": "2.3.5", "description": "Plugin to add the tracking code for Fullstory.com", "main": "index.js", "scripts": { @@ -29,7 +29,7 @@ "devDependencies": { "@babel/cli": "^7.10.1", "@babel/core": "^7.10.2", - "babel-preset-gatsby-package": "^0.4.3", + "babel-preset-gatsby-package": "^0.4.4", "cross-env": "^5.2.1" }, "peerDependencies": { diff --git a/packages/gatsby-plugin-glamor/CHANGELOG.md b/packages/gatsby-plugin-glamor/CHANGELOG.md index 272bf6bc78118..d305d266d371a 100644 --- a/packages/gatsby-plugin-glamor/CHANGELOG.md +++ b/packages/gatsby-plugin-glamor/CHANGELOG.md @@ -3,6 +3,10 @@ All notable changes to this project will be documented in this file. See [Conventional Commits](https://conventionalcommits.org) for commit guidelines. +## [2.3.4](https://github.com/gatsbyjs/gatsby/compare/gatsby-plugin-glamor@2.3.3...gatsby-plugin-glamor@2.3.4) (2020-06-09) + +**Note:** Version bump only for package gatsby-plugin-glamor + ## [2.3.3](https://github.com/gatsbyjs/gatsby/compare/gatsby-plugin-glamor@2.3.2...gatsby-plugin-glamor@2.3.3) (2020-06-02) **Note:** Version bump only for package gatsby-plugin-glamor diff --git a/packages/gatsby-plugin-glamor/package.json b/packages/gatsby-plugin-glamor/package.json index cbfde21833d83..69724c2f5b561 100644 --- a/packages/gatsby-plugin-glamor/package.json +++ b/packages/gatsby-plugin-glamor/package.json @@ -1,7 +1,7 @@ { "name": "gatsby-plugin-glamor", "description": "Gatsby plugin to add support for Glamor", - "version": "2.3.3", + "version": "2.3.4", "author": "Kyle Mathews ", "bugs": { "url": "https://github.com/gatsbyjs/gatsby/issues" @@ -12,7 +12,7 @@ "devDependencies": { "@babel/cli": "^7.10.1", "@babel/core": "^7.10.2", - "babel-preset-gatsby-package": "^0.4.3", + "babel-preset-gatsby-package": "^0.4.4", "cross-env": "^5.2.1" }, "homepage": "https://github.com/gatsbyjs/gatsby/tree/master/packages/gatsby-plugin-glamor#readme", diff --git a/packages/gatsby-plugin-google-analytics/CHANGELOG.md b/packages/gatsby-plugin-google-analytics/CHANGELOG.md index 9251f666c21ba..d1355f7d2676c 100644 --- a/packages/gatsby-plugin-google-analytics/CHANGELOG.md +++ b/packages/gatsby-plugin-google-analytics/CHANGELOG.md @@ -3,6 +3,10 @@ All notable changes to this project will be documented in this file. See [Conventional Commits](https://conventionalcommits.org) for commit guidelines. +## [2.3.4](https://github.com/gatsbyjs/gatsby/compare/gatsby-plugin-google-analytics@2.3.3...gatsby-plugin-google-analytics@2.3.4) (2020-06-09) + +**Note:** Version bump only for package gatsby-plugin-google-analytics + ## [2.3.3](https://github.com/gatsbyjs/gatsby/compare/gatsby-plugin-google-analytics@2.3.2...gatsby-plugin-google-analytics@2.3.3) (2020-06-02) **Note:** Version bump only for package gatsby-plugin-google-analytics diff --git a/packages/gatsby-plugin-google-analytics/package.json b/packages/gatsby-plugin-google-analytics/package.json index 3f52115040edf..8ace3fa441856 100644 --- a/packages/gatsby-plugin-google-analytics/package.json +++ b/packages/gatsby-plugin-google-analytics/package.json @@ -1,7 +1,7 @@ { "name": "gatsby-plugin-google-analytics", "description": "Gatsby plugin to add google analytics onto a site", - "version": "2.3.3", + "version": "2.3.4", "author": "Kyle Mathews ", "bugs": { "url": "https://github.com/gatsbyjs/gatsby/issues" @@ -14,7 +14,7 @@ "@babel/cli": "^7.10.1", "@babel/core": "^7.10.2", "@testing-library/react": "^9.5.0", - "babel-preset-gatsby-package": "^0.4.3", + "babel-preset-gatsby-package": "^0.4.4", "cross-env": "^5.2.1" }, "homepage": "https://github.com/gatsbyjs/gatsby/tree/master/packages/gatsby-plugin-google-analytics#readme", diff --git a/packages/gatsby-plugin-google-gtag/CHANGELOG.md b/packages/gatsby-plugin-google-gtag/CHANGELOG.md index 8736385944209..e39f7d7e13b83 100644 --- a/packages/gatsby-plugin-google-gtag/CHANGELOG.md +++ b/packages/gatsby-plugin-google-gtag/CHANGELOG.md @@ -3,6 +3,10 @@ All notable changes to this project will be documented in this file. See [Conventional Commits](https://conventionalcommits.org) for commit guidelines. +## [2.1.4](https://github.com/gatsbyjs/gatsby/compare/gatsby-plugin-google-gtag@2.1.3...gatsby-plugin-google-gtag@2.1.4) (2020-06-09) + +**Note:** Version bump only for package gatsby-plugin-google-gtag + ## [2.1.3](https://github.com/gatsbyjs/gatsby/compare/gatsby-plugin-google-gtag@2.1.2...gatsby-plugin-google-gtag@2.1.3) (2020-06-02) **Note:** Version bump only for package gatsby-plugin-google-gtag diff --git a/packages/gatsby-plugin-google-gtag/package.json b/packages/gatsby-plugin-google-gtag/package.json index aade5d7388766..aedb8e6a42a38 100644 --- a/packages/gatsby-plugin-google-gtag/package.json +++ b/packages/gatsby-plugin-google-gtag/package.json @@ -1,7 +1,7 @@ { "name": "gatsby-plugin-google-gtag", "description": "Gatsby plugin to add google gtag onto a site", - "version": "2.1.3", + "version": "2.1.4", "author": "Tyler Buchea ", "bugs": { "url": "https://github.com/gatsbyjs/gatsby/issues" @@ -13,7 +13,7 @@ "devDependencies": { "@babel/cli": "^7.10.1", "@babel/core": "^7.10.2", - "babel-preset-gatsby-package": "^0.4.3", + "babel-preset-gatsby-package": "^0.4.4", "cross-env": "^5.2.1" }, "homepage": "https://github.com/gatsbyjs/gatsby/tree/master/packages/gatsby-plugin-google-gtag#readme", diff --git a/packages/gatsby-plugin-google-tagmanager/CHANGELOG.md b/packages/gatsby-plugin-google-tagmanager/CHANGELOG.md index 361a94ad3d0e6..8cab748923faf 100644 --- a/packages/gatsby-plugin-google-tagmanager/CHANGELOG.md +++ b/packages/gatsby-plugin-google-tagmanager/CHANGELOG.md @@ -3,6 +3,10 @@ All notable changes to this project will be documented in this file. See [Conventional Commits](https://conventionalcommits.org) for commit guidelines. +## [2.3.5](https://github.com/gatsbyjs/gatsby/compare/gatsby-plugin-google-tagmanager@2.3.4...gatsby-plugin-google-tagmanager@2.3.5) (2020-06-09) + +**Note:** Version bump only for package gatsby-plugin-google-tagmanager + ## [2.3.4](https://github.com/gatsbyjs/gatsby/compare/gatsby-plugin-google-tagmanager@2.3.3...gatsby-plugin-google-tagmanager@2.3.4) (2020-06-02) **Note:** Version bump only for package gatsby-plugin-google-tagmanager diff --git a/packages/gatsby-plugin-google-tagmanager/package.json b/packages/gatsby-plugin-google-tagmanager/package.json index 21f71ee3a520c..d29b690bff786 100644 --- a/packages/gatsby-plugin-google-tagmanager/package.json +++ b/packages/gatsby-plugin-google-tagmanager/package.json @@ -1,7 +1,7 @@ { "name": "gatsby-plugin-google-tagmanager", "description": "Gatsby plugin to add google tagmanager onto a site", - "version": "2.3.4", + "version": "2.3.5", "author": "Thijs Koerselman ", "bugs": { "url": "https://github.com/gatsbyjs/gatsby/issues" @@ -12,7 +12,7 @@ "devDependencies": { "@babel/cli": "^7.10.1", "@babel/core": "^7.10.2", - "babel-preset-gatsby-package": "^0.4.3", + "babel-preset-gatsby-package": "^0.4.4", "cross-env": "^5.2.1" }, "homepage": "https://github.com/gatsbyjs/gatsby/tree/master/packages/gatsby-plugin-google-tagmanager#readme", diff --git a/packages/gatsby-plugin-guess-js/CHANGELOG.md b/packages/gatsby-plugin-guess-js/CHANGELOG.md index 29d3df2c423ef..223bda4effaae 100644 --- a/packages/gatsby-plugin-guess-js/CHANGELOG.md +++ b/packages/gatsby-plugin-guess-js/CHANGELOG.md @@ -3,6 +3,10 @@ All notable changes to this project will be documented in this file. See [Conventional Commits](https://conventionalcommits.org) for commit guidelines. +## [1.3.5](https://github.com/gatsbyjs/gatsby/compare/gatsby-plugin-guess-js@1.3.4...gatsby-plugin-guess-js@1.3.5) (2020-06-09) + +**Note:** Version bump only for package gatsby-plugin-guess-js + ## [1.3.4](https://github.com/gatsbyjs/gatsby/compare/gatsby-plugin-guess-js@1.3.3...gatsby-plugin-guess-js@1.3.4) (2020-06-02) **Note:** Version bump only for package gatsby-plugin-guess-js diff --git a/packages/gatsby-plugin-guess-js/package.json b/packages/gatsby-plugin-guess-js/package.json index 75e77091ac9de..2373116f36e78 100644 --- a/packages/gatsby-plugin-guess-js/package.json +++ b/packages/gatsby-plugin-guess-js/package.json @@ -1,6 +1,6 @@ { "name": "gatsby-plugin-guess-js", - "version": "1.3.4", + "version": "1.3.5", "description": "Gatsby plugin providing drop-in integration with Guess.js to enabling using machine learning and analytics data to power prefetching", "main": "index.js", "scripts": { @@ -34,7 +34,7 @@ "devDependencies": { "@babel/cli": "^7.10.1", "@babel/core": "^7.10.2", - "babel-preset-gatsby-package": "^0.4.3", + "babel-preset-gatsby-package": "^0.4.4", "cross-env": "^5.2.1" }, "peerDependencies": { diff --git a/packages/gatsby-plugin-jss/CHANGELOG.md b/packages/gatsby-plugin-jss/CHANGELOG.md index 737f448592fa9..ca4bcd4de61ff 100644 --- a/packages/gatsby-plugin-jss/CHANGELOG.md +++ b/packages/gatsby-plugin-jss/CHANGELOG.md @@ -3,6 +3,10 @@ All notable changes to this project will be documented in this file. See [Conventional Commits](https://conventionalcommits.org) for commit guidelines. +## [2.3.4](https://github.com/gatsbyjs/gatsby/compare/gatsby-plugin-jss@2.3.3...gatsby-plugin-jss@2.3.4) (2020-06-09) + +**Note:** Version bump only for package gatsby-plugin-jss + ## [2.3.3](https://github.com/gatsbyjs/gatsby/compare/gatsby-plugin-jss@2.3.2...gatsby-plugin-jss@2.3.3) (2020-06-02) **Note:** Version bump only for package gatsby-plugin-jss diff --git a/packages/gatsby-plugin-jss/package.json b/packages/gatsby-plugin-jss/package.json index 7042fc40be3fb..9e81cdac95e7d 100644 --- a/packages/gatsby-plugin-jss/package.json +++ b/packages/gatsby-plugin-jss/package.json @@ -1,7 +1,7 @@ { "name": "gatsby-plugin-jss", "description": "Gatsby plugin that adds SSR support for JSS", - "version": "2.3.3", + "version": "2.3.4", "author": "Vladimir Guguiev ", "bugs": { "url": "https://github.com/gatsbyjs/gatsby/issues" @@ -12,7 +12,7 @@ "devDependencies": { "@babel/cli": "^7.10.1", "@babel/core": "^7.10.2", - "babel-preset-gatsby-package": "^0.4.3", + "babel-preset-gatsby-package": "^0.4.4", "cross-env": "^5.2.1" }, "homepage": "https://github.com/gatsbyjs/gatsby/tree/master/packages/gatsby-plugin-jss#readme", diff --git a/packages/gatsby-plugin-layout/CHANGELOG.md b/packages/gatsby-plugin-layout/CHANGELOG.md index 18ee9883fdb1e..0166c5a33a633 100644 --- a/packages/gatsby-plugin-layout/CHANGELOG.md +++ b/packages/gatsby-plugin-layout/CHANGELOG.md @@ -3,6 +3,10 @@ All notable changes to this project will be documented in this file. See [Conventional Commits](https://conventionalcommits.org) for commit guidelines. +## [1.3.4](https://github.com/gatsbyjs/gatsby/compare/gatsby-plugin-layout@1.3.3...gatsby-plugin-layout@1.3.4) (2020-06-09) + +**Note:** Version bump only for package gatsby-plugin-layout + ## [1.3.3](https://github.com/gatsbyjs/gatsby/compare/gatsby-plugin-layout@1.3.2...gatsby-plugin-layout@1.3.3) (2020-06-02) **Note:** Version bump only for package gatsby-plugin-layout diff --git a/packages/gatsby-plugin-layout/package.json b/packages/gatsby-plugin-layout/package.json index 0bcf419e36bfd..7920f2c838b6d 100644 --- a/packages/gatsby-plugin-layout/package.json +++ b/packages/gatsby-plugin-layout/package.json @@ -1,6 +1,6 @@ { "name": "gatsby-plugin-layout", - "version": "1.3.3", + "version": "1.3.4", "description": "Reimplements the behavior of layout components in gatsby@1, which was removed in version 2.", "main": "index.js", "scripts": { @@ -29,7 +29,7 @@ "devDependencies": { "@babel/cli": "^7.10.1", "@babel/core": "^7.10.2", - "babel-preset-gatsby-package": "^0.4.3", + "babel-preset-gatsby-package": "^0.4.4", "cross-env": "^5.2.1" }, "engines": { diff --git a/packages/gatsby-plugin-less/CHANGELOG.md b/packages/gatsby-plugin-less/CHANGELOG.md index 1aa861cfa8a32..f8ca35f100b6c 100644 --- a/packages/gatsby-plugin-less/CHANGELOG.md +++ b/packages/gatsby-plugin-less/CHANGELOG.md @@ -3,6 +3,10 @@ All notable changes to this project will be documented in this file. See [Conventional Commits](https://conventionalcommits.org) for commit guidelines. +## [3.2.4](https://github.com/gatsbyjs/gatsby/compare/gatsby-plugin-less@3.2.3...gatsby-plugin-less@3.2.4) (2020-06-09) + +**Note:** Version bump only for package gatsby-plugin-less + ## [3.2.3](https://github.com/gatsbyjs/gatsby/compare/gatsby-plugin-less@3.2.2...gatsby-plugin-less@3.2.3) (2020-06-02) **Note:** Version bump only for package gatsby-plugin-less diff --git a/packages/gatsby-plugin-less/package.json b/packages/gatsby-plugin-less/package.json index 8f028de247f85..76755c5b50359 100644 --- a/packages/gatsby-plugin-less/package.json +++ b/packages/gatsby-plugin-less/package.json @@ -1,7 +1,7 @@ { "name": "gatsby-plugin-less", "description": "Gatsby plugin to add support for using Less", - "version": "3.2.3", + "version": "3.2.4", "author": "monastic.panic@gmail.com", "bugs": { "url": "https://github.com/gatsbyjs/gatsby/issues" @@ -13,7 +13,7 @@ "devDependencies": { "@babel/cli": "^7.10.1", "@babel/core": "^7.10.2", - "babel-preset-gatsby-package": "^0.4.3", + "babel-preset-gatsby-package": "^0.4.4", "cross-env": "^5.2.1" }, "homepage": "https://github.com/gatsbyjs/gatsby/tree/master/packages/gatsby-plugin-less#readme", diff --git a/packages/gatsby-plugin-lodash/CHANGELOG.md b/packages/gatsby-plugin-lodash/CHANGELOG.md index 27f081c8eda49..ea1720484a932 100644 --- a/packages/gatsby-plugin-lodash/CHANGELOG.md +++ b/packages/gatsby-plugin-lodash/CHANGELOG.md @@ -3,6 +3,10 @@ All notable changes to this project will be documented in this file. See [Conventional Commits](https://conventionalcommits.org) for commit guidelines. +## [3.3.4](https://github.com/gatsbyjs/gatsby/compare/gatsby-plugin-lodash@3.3.3...gatsby-plugin-lodash@3.3.4) (2020-06-09) + +**Note:** Version bump only for package gatsby-plugin-lodash + ## [3.3.3](https://github.com/gatsbyjs/gatsby/compare/gatsby-plugin-lodash@3.3.2...gatsby-plugin-lodash@3.3.3) (2020-06-02) **Note:** Version bump only for package gatsby-plugin-lodash diff --git a/packages/gatsby-plugin-lodash/package.json b/packages/gatsby-plugin-lodash/package.json index 2ce808f857576..3e68dd895a85d 100644 --- a/packages/gatsby-plugin-lodash/package.json +++ b/packages/gatsby-plugin-lodash/package.json @@ -1,7 +1,7 @@ { "name": "gatsby-plugin-lodash", "description": "Easy modular Lodash builds. Adds the Lodash webpack & Babel plugins to your Gatsby build", - "version": "3.3.3", + "version": "3.3.4", "author": "Kyle Mathews ", "bugs": { "url": "https://github.com/gatsbyjs/gatsby/issues" @@ -14,7 +14,7 @@ "devDependencies": { "@babel/cli": "^7.10.1", "@babel/core": "^7.10.2", - "babel-preset-gatsby-package": "^0.4.3", + "babel-preset-gatsby-package": "^0.4.4", "cross-env": "^5.2.1" }, "homepage": "https://github.com/gatsbyjs/gatsby/tree/master/packages/gatsby-plugin-lodash#readme", diff --git a/packages/gatsby-plugin-manifest/CHANGELOG.md b/packages/gatsby-plugin-manifest/CHANGELOG.md index 9a69887ce6e4f..42833a88f0d56 100644 --- a/packages/gatsby-plugin-manifest/CHANGELOG.md +++ b/packages/gatsby-plugin-manifest/CHANGELOG.md @@ -3,6 +3,10 @@ All notable changes to this project will be documented in this file. See [Conventional Commits](https://conventionalcommits.org) for commit guidelines. +## [2.4.11](https://github.com/gatsbyjs/gatsby/compare/gatsby-plugin-manifest@2.4.10...gatsby-plugin-manifest@2.4.11) (2020-06-09) + +**Note:** Version bump only for package gatsby-plugin-manifest + ## [2.4.10](https://github.com/gatsbyjs/gatsby/compare/gatsby-plugin-manifest@2.4.9...gatsby-plugin-manifest@2.4.10) (2020-06-02) **Note:** Version bump only for package gatsby-plugin-manifest diff --git a/packages/gatsby-plugin-manifest/package.json b/packages/gatsby-plugin-manifest/package.json index 64288acbececc..6889d338e651b 100644 --- a/packages/gatsby-plugin-manifest/package.json +++ b/packages/gatsby-plugin-manifest/package.json @@ -1,21 +1,21 @@ { "name": "gatsby-plugin-manifest", "description": "Gatsby plugin which adds a manifest.webmanifest to make sites progressive web apps", - "version": "2.4.10", + "version": "2.4.11", "author": "Kyle Mathews ", "bugs": { "url": "https://github.com/gatsbyjs/gatsby/issues" }, "dependencies": { "@babel/runtime": "^7.10.2", - "gatsby-core-utils": "^1.3.4", + "gatsby-core-utils": "^1.3.5", "semver": "^5.7.1", "sharp": "^0.25.1" }, "devDependencies": { "@babel/cli": "^7.10.1", "@babel/core": "^7.10.2", - "babel-preset-gatsby-package": "^0.4.3", + "babel-preset-gatsby-package": "^0.4.4", "cross-env": "^5.2.1" }, "homepage": "https://github.com/gatsbyjs/gatsby/tree/master/packages/gatsby-plugin-manifest#readme", diff --git a/packages/gatsby-plugin-mdx/CHANGELOG.md b/packages/gatsby-plugin-mdx/CHANGELOG.md index d3a388239aac2..e784aa3c2b944 100644 --- a/packages/gatsby-plugin-mdx/CHANGELOG.md +++ b/packages/gatsby-plugin-mdx/CHANGELOG.md @@ -3,6 +3,10 @@ All notable changes to this project will be documented in this file. See [Conventional Commits](https://conventionalcommits.org) for commit guidelines. +## [1.2.15](https://github.com/gatsbyjs/gatsby/compare/gatsby-plugin-mdx@1.2.14...gatsby-plugin-mdx@1.2.15) (2020-06-09) + +**Note:** Version bump only for package gatsby-plugin-mdx + ## [1.2.14](https://github.com/gatsbyjs/gatsby/compare/gatsby-plugin-mdx@1.2.13...gatsby-plugin-mdx@1.2.14) (2020-06-02) **Note:** Version bump only for package gatsby-plugin-mdx diff --git a/packages/gatsby-plugin-mdx/package.json b/packages/gatsby-plugin-mdx/package.json index 82d4356998bab..703006213c719 100644 --- a/packages/gatsby-plugin-mdx/package.json +++ b/packages/gatsby-plugin-mdx/package.json @@ -1,6 +1,6 @@ { "name": "gatsby-plugin-mdx", - "version": "1.2.14", + "version": "1.2.15", "description": "MDX integration for Gatsby", "main": "index.js", "license": "MIT", @@ -33,7 +33,7 @@ "escape-string-regexp": "^1.0.5", "eval": "^0.1.4", "fs-extra": "^8.1.0", - "gatsby-core-utils": "^1.3.4", + "gatsby-core-utils": "^1.3.5", "gray-matter": "^4.0.2", "json5": "^2.1.3", "loader-utils": "^1.4.0", diff --git a/packages/gatsby-plugin-netlify-cms/CHANGELOG.md b/packages/gatsby-plugin-netlify-cms/CHANGELOG.md index d4b8c3f410b8d..168ce3ce92ef9 100644 --- a/packages/gatsby-plugin-netlify-cms/CHANGELOG.md +++ b/packages/gatsby-plugin-netlify-cms/CHANGELOG.md @@ -3,6 +3,10 @@ All notable changes to this project will be documented in this file. See [Conventional Commits](https://conventionalcommits.org) for commit guidelines. +## [4.3.5](https://github.com/gatsbyjs/gatsby/compare/gatsby-plugin-netlify-cms@4.3.4...gatsby-plugin-netlify-cms@4.3.5) (2020-06-09) + +**Note:** Version bump only for package gatsby-plugin-netlify-cms + ## [4.3.4](https://github.com/gatsbyjs/gatsby/compare/gatsby-plugin-netlify-cms@4.3.3...gatsby-plugin-netlify-cms@4.3.4) (2020-06-02) **Note:** Version bump only for package gatsby-plugin-netlify-cms diff --git a/packages/gatsby-plugin-netlify-cms/package.json b/packages/gatsby-plugin-netlify-cms/package.json index 88243c3b687c0..bd1c2048704c4 100644 --- a/packages/gatsby-plugin-netlify-cms/package.json +++ b/packages/gatsby-plugin-netlify-cms/package.json @@ -1,7 +1,7 @@ { "name": "gatsby-plugin-netlify-cms", "description": "A Gatsby plugin which generates the Netlify CMS single page app", - "version": "4.3.4", + "version": "4.3.5", "author": "Shawn Erquhart ", "bugs": { "url": "https://github.com/gatsbyjs/gatsby/issues" @@ -20,7 +20,7 @@ "devDependencies": { "@babel/cli": "^7.10.1", "@babel/core": "^7.10.2", - "babel-preset-gatsby-package": "^0.4.3", + "babel-preset-gatsby-package": "^0.4.4", "cross-env": "^5.2.1", "react": "^16.12.0", "react-dom": "^16.12.0" diff --git a/packages/gatsby-plugin-netlify/CHANGELOG.md b/packages/gatsby-plugin-netlify/CHANGELOG.md index 8dec706b93ca2..490fe01f2f72d 100644 --- a/packages/gatsby-plugin-netlify/CHANGELOG.md +++ b/packages/gatsby-plugin-netlify/CHANGELOG.md @@ -3,6 +3,10 @@ All notable changes to this project will be documented in this file. See [Conventional Commits](https://conventionalcommits.org) for commit guidelines. +## [2.3.5](https://github.com/gatsbyjs/gatsby/compare/gatsby-plugin-netlify@2.3.4...gatsby-plugin-netlify@2.3.5) (2020-06-09) + +**Note:** Version bump only for package gatsby-plugin-netlify + ## [2.3.4](https://github.com/gatsbyjs/gatsby/compare/gatsby-plugin-netlify@2.3.3...gatsby-plugin-netlify@2.3.4) (2020-06-02) **Note:** Version bump only for package gatsby-plugin-netlify diff --git a/packages/gatsby-plugin-netlify/package.json b/packages/gatsby-plugin-netlify/package.json index 862e74046bdae..370a3b3e59e13 100644 --- a/packages/gatsby-plugin-netlify/package.json +++ b/packages/gatsby-plugin-netlify/package.json @@ -1,7 +1,7 @@ { "name": "gatsby-plugin-netlify", "description": "A Gatsby plugin which generates a _headers file for netlify", - "version": "2.3.4", + "version": "2.3.5", "author": "Kyle Mathews ", "bugs": { "url": "https://github.com/gatsbyjs/gatsby/issues" @@ -22,7 +22,7 @@ "devDependencies": { "@babel/cli": "^7.10.1", "@babel/core": "^7.10.2", - "babel-preset-gatsby-package": "^0.4.3", + "babel-preset-gatsby-package": "^0.4.4", "cross-env": "^5.2.1" }, "homepage": "https://github.com/gatsbyjs/gatsby/tree/master/packages/gatsby-plugin-netlify#readme", diff --git a/packages/gatsby-plugin-nprogress/CHANGELOG.md b/packages/gatsby-plugin-nprogress/CHANGELOG.md index 27efdcc2ebdb0..57db8f35160fc 100644 --- a/packages/gatsby-plugin-nprogress/CHANGELOG.md +++ b/packages/gatsby-plugin-nprogress/CHANGELOG.md @@ -3,6 +3,10 @@ All notable changes to this project will be documented in this file. See [Conventional Commits](https://conventionalcommits.org) for commit guidelines. +## [2.3.4](https://github.com/gatsbyjs/gatsby/compare/gatsby-plugin-nprogress@2.3.3...gatsby-plugin-nprogress@2.3.4) (2020-06-09) + +**Note:** Version bump only for package gatsby-plugin-nprogress + ## [2.3.3](https://github.com/gatsbyjs/gatsby/compare/gatsby-plugin-nprogress@2.3.2...gatsby-plugin-nprogress@2.3.3) (2020-06-02) **Note:** Version bump only for package gatsby-plugin-nprogress diff --git a/packages/gatsby-plugin-nprogress/package.json b/packages/gatsby-plugin-nprogress/package.json index 5f6c0f39fcf0e..6b394c41f3d24 100644 --- a/packages/gatsby-plugin-nprogress/package.json +++ b/packages/gatsby-plugin-nprogress/package.json @@ -1,7 +1,7 @@ { "name": "gatsby-plugin-nprogress", "description": "Shows page loading indicator when loading page resources is delayed", - "version": "2.3.3", + "version": "2.3.4", "author": "Kyle Mathews", "bugs": { "url": "https://github.com/gatsbyjs/gatsby/issues" @@ -13,7 +13,7 @@ "devDependencies": { "@babel/cli": "^7.10.1", "@babel/core": "^7.10.2", - "babel-preset-gatsby-package": "^0.4.3", + "babel-preset-gatsby-package": "^0.4.4", "cross-env": "^5.2.1" }, "homepage": "https://github.com/gatsbyjs/gatsby/tree/master/packages/gatsby-plugin-nprogress#readme", diff --git a/packages/gatsby-plugin-offline/CHANGELOG.md b/packages/gatsby-plugin-offline/CHANGELOG.md index 454085f8ecc1f..0023e627b6ed5 100644 --- a/packages/gatsby-plugin-offline/CHANGELOG.md +++ b/packages/gatsby-plugin-offline/CHANGELOG.md @@ -3,6 +3,10 @@ All notable changes to this project will be documented in this file. See [Conventional Commits](https://conventionalcommits.org) for commit guidelines. +## [3.2.9](https://github.com/gatsbyjs/gatsby/compare/gatsby-plugin-offline@3.2.8...gatsby-plugin-offline@3.2.9) (2020-06-09) + +**Note:** Version bump only for package gatsby-plugin-offline + ## [3.2.8](https://github.com/gatsbyjs/gatsby/compare/gatsby-plugin-offline@3.2.7...gatsby-plugin-offline@3.2.8) (2020-06-02) **Note:** Version bump only for package gatsby-plugin-offline diff --git a/packages/gatsby-plugin-offline/package.json b/packages/gatsby-plugin-offline/package.json index 479d20f047c84..12adffe3babe9 100644 --- a/packages/gatsby-plugin-offline/package.json +++ b/packages/gatsby-plugin-offline/package.json @@ -1,7 +1,7 @@ { "name": "gatsby-plugin-offline", "description": "Gatsby plugin which sets up a site to be able to run offline", - "version": "3.2.8", + "version": "3.2.9", "author": "Kyle Mathews ", "bugs": { "url": "https://github.com/gatsbyjs/gatsby/issues" @@ -9,7 +9,7 @@ "dependencies": { "@babel/runtime": "^7.10.2", "cheerio": "^1.0.0-rc.3", - "gatsby-core-utils": "^1.3.4", + "gatsby-core-utils": "^1.3.5", "glob": "^7.1.6", "idb-keyval": "^3.2.0", "lodash": "^4.17.15", @@ -18,7 +18,7 @@ "devDependencies": { "@babel/cli": "^7.10.1", "@babel/core": "^7.10.2", - "babel-preset-gatsby-package": "^0.4.3", + "babel-preset-gatsby-package": "^0.4.4", "cpx": "^1.5.0", "cross-env": "^5.2.1", "rewire": "^4.0.1" diff --git a/packages/gatsby-plugin-page-creator/CHANGELOG.md b/packages/gatsby-plugin-page-creator/CHANGELOG.md index d6560aeb194e0..830df0196cafd 100644 --- a/packages/gatsby-plugin-page-creator/CHANGELOG.md +++ b/packages/gatsby-plugin-page-creator/CHANGELOG.md @@ -3,6 +3,10 @@ All notable changes to this project will be documented in this file. See [Conventional Commits](https://conventionalcommits.org) for commit guidelines. +## [2.3.9](https://github.com/gatsbyjs/gatsby/compare/gatsby-plugin-page-creator@2.3.8...gatsby-plugin-page-creator@2.3.9) (2020-06-09) + +**Note:** Version bump only for package gatsby-plugin-page-creator + ## [2.3.8](https://github.com/gatsbyjs/gatsby/compare/gatsby-plugin-page-creator@2.3.7...gatsby-plugin-page-creator@2.3.8) (2020-06-02) **Note:** Version bump only for package gatsby-plugin-page-creator diff --git a/packages/gatsby-plugin-page-creator/package.json b/packages/gatsby-plugin-page-creator/package.json index 04f5091064647..7e49781b73e55 100644 --- a/packages/gatsby-plugin-page-creator/package.json +++ b/packages/gatsby-plugin-page-creator/package.json @@ -1,6 +1,6 @@ { "name": "gatsby-plugin-page-creator", - "version": "2.3.8", + "version": "2.3.9", "description": "Gatsby plugin that automatically creates pages from React components in specified directories", "main": "index.js", "scripts": { @@ -27,7 +27,7 @@ "@babel/runtime": "^7.10.2", "bluebird": "^3.7.2", "fs-exists-cached": "^1.0.0", - "gatsby-page-utils": "^0.2.8", + "gatsby-page-utils": "^0.2.9", "glob": "^7.1.6", "lodash": "^4.17.15", "micromatch": "^3.1.10" @@ -35,7 +35,7 @@ "devDependencies": { "@babel/cli": "^7.10.1", "@babel/core": "^7.10.2", - "babel-preset-gatsby-package": "^0.4.3", + "babel-preset-gatsby-package": "^0.4.4", "cross-env": "^5.2.1" }, "peerDependencies": { diff --git a/packages/gatsby-plugin-postcss/CHANGELOG.md b/packages/gatsby-plugin-postcss/CHANGELOG.md index 867c918bc2ad8..1d788c5a41479 100644 --- a/packages/gatsby-plugin-postcss/CHANGELOG.md +++ b/packages/gatsby-plugin-postcss/CHANGELOG.md @@ -3,6 +3,10 @@ All notable changes to this project will be documented in this file. See [Conventional Commits](https://conventionalcommits.org) for commit guidelines. +## [2.3.4](https://github.com/gatsbyjs/gatsby/compare/gatsby-plugin-postcss@2.3.3...gatsby-plugin-postcss@2.3.4) (2020-06-09) + +**Note:** Version bump only for package gatsby-plugin-postcss + ## [2.3.3](https://github.com/gatsbyjs/gatsby/compare/gatsby-plugin-postcss@2.3.2...gatsby-plugin-postcss@2.3.3) (2020-06-02) **Note:** Version bump only for package gatsby-plugin-postcss diff --git a/packages/gatsby-plugin-postcss/package.json b/packages/gatsby-plugin-postcss/package.json index c61c16b4006b6..252ad409f184b 100644 --- a/packages/gatsby-plugin-postcss/package.json +++ b/packages/gatsby-plugin-postcss/package.json @@ -1,7 +1,7 @@ { "name": "gatsby-plugin-postcss", "description": "Gatsby plugin to handle PostCSS", - "version": "2.3.3", + "version": "2.3.4", "author": "Marat Dreizin ", "bugs": { "url": "https://github.com/gatsbyjs/gatsby/issues" @@ -13,7 +13,7 @@ "devDependencies": { "@babel/cli": "^7.10.1", "@babel/core": "^7.10.2", - "babel-preset-gatsby-package": "^0.4.3", + "babel-preset-gatsby-package": "^0.4.4", "cross-env": "^5.2.1" }, "homepage": "https://github.com/gatsbyjs/gatsby/tree/master/packages/gatsby-plugin-postcss#readme", diff --git a/packages/gatsby-plugin-preact/CHANGELOG.md b/packages/gatsby-plugin-preact/CHANGELOG.md index 095825c4ebe85..0f0218727cc91 100644 --- a/packages/gatsby-plugin-preact/CHANGELOG.md +++ b/packages/gatsby-plugin-preact/CHANGELOG.md @@ -3,6 +3,10 @@ All notable changes to this project will be documented in this file. See [Conventional Commits](https://conventionalcommits.org) for commit guidelines. +## [4.0.3](https://github.com/gatsbyjs/gatsby/compare/gatsby-plugin-preact@4.0.2...gatsby-plugin-preact@4.0.3) (2020-06-09) + +**Note:** Version bump only for package gatsby-plugin-preact + ## [4.0.2](https://github.com/gatsbyjs/gatsby/compare/gatsby-plugin-preact@4.0.1...gatsby-plugin-preact@4.0.2) (2020-06-02) **Note:** Version bump only for package gatsby-plugin-preact diff --git a/packages/gatsby-plugin-preact/package.json b/packages/gatsby-plugin-preact/package.json index a1abaacfc4be0..f03db200939a7 100644 --- a/packages/gatsby-plugin-preact/package.json +++ b/packages/gatsby-plugin-preact/package.json @@ -1,7 +1,7 @@ { "name": "gatsby-plugin-preact", "description": "A Gatsby plugin which replaces React with Preact", - "version": "4.0.2", + "version": "4.0.3", "author": "Kyle Mathews ", "bugs": { "url": "https://github.com/gatsbyjs/gatsby/issues" @@ -14,7 +14,7 @@ "@babel/cli": "^7.10.1", "@babel/core": "^7.10.2", "@pmmmwh/react-refresh-webpack-plugin": "^0.3.3", - "babel-preset-gatsby-package": "^0.4.3", + "babel-preset-gatsby-package": "^0.4.4", "cross-env": "^5.2.1" }, "homepage": "https://github.com/gatsbyjs/gatsby/tree/master/packages/gatsby-plugin-preact#readme", diff --git a/packages/gatsby-plugin-preload-fonts/CHANGELOG.md b/packages/gatsby-plugin-preload-fonts/CHANGELOG.md index cb5bf1d9e80b4..61a6ab494fa26 100644 --- a/packages/gatsby-plugin-preload-fonts/CHANGELOG.md +++ b/packages/gatsby-plugin-preload-fonts/CHANGELOG.md @@ -3,6 +3,10 @@ All notable changes to this project will be documented in this file. See [Conventional Commits](https://conventionalcommits.org) for commit guidelines. +## [1.2.10](https://github.com/gatsbyjs/gatsby/compare/gatsby-plugin-preload-fonts@1.2.9...gatsby-plugin-preload-fonts@1.2.10) (2020-06-09) + +**Note:** Version bump only for package gatsby-plugin-preload-fonts + ## [1.2.9](https://github.com/gatsbyjs/gatsby/compare/gatsby-plugin-preload-fonts@1.2.8...gatsby-plugin-preload-fonts@1.2.9) (2020-06-02) **Note:** Version bump only for package gatsby-plugin-preload-fonts diff --git a/packages/gatsby-plugin-preload-fonts/package.json b/packages/gatsby-plugin-preload-fonts/package.json index 63f476944b381..908366d17874c 100644 --- a/packages/gatsby-plugin-preload-fonts/package.json +++ b/packages/gatsby-plugin-preload-fonts/package.json @@ -1,7 +1,7 @@ { "name": "gatsby-plugin-preload-fonts", "description": "Gatsby plugin for preloading fonts per page", - "version": "1.2.9", + "version": "1.2.10", "author": "Aaron Ross ", "main": "index.js", "bin": { @@ -14,7 +14,7 @@ "chalk": "^2.4.2", "date-fns": "^2.14.0", "fs-extra": "^8.1.0", - "gatsby-core-utils": "^1.3.4", + "gatsby-core-utils": "^1.3.5", "graphql-request": "^1.8.2", "progress": "^2.0.3", "puppeteer": "^1.20.0" @@ -22,7 +22,7 @@ "devDependencies": { "@babel/cli": "^7.10.1", "@babel/core": "^7.10.2", - "babel-preset-gatsby-package": "^0.4.3", + "babel-preset-gatsby-package": "^0.4.4", "cross-env": "^5.2.1" }, "homepage": "https://github.com/gatsbyjs/gatsby/tree/master/packages/gatsby-plugin-preload-fonts#readme", diff --git a/packages/gatsby-plugin-react-css-modules/CHANGELOG.md b/packages/gatsby-plugin-react-css-modules/CHANGELOG.md index acc85b82e10af..35e0dcaad0115 100644 --- a/packages/gatsby-plugin-react-css-modules/CHANGELOG.md +++ b/packages/gatsby-plugin-react-css-modules/CHANGELOG.md @@ -3,6 +3,10 @@ All notable changes to this project will be documented in this file. See [Conventional Commits](https://conventionalcommits.org) for commit guidelines. +## [2.3.4](https://github.com/gatsbyjs/gatsby/compare/gatsby-plugin-react-css-modules@2.3.3...gatsby-plugin-react-css-modules@2.3.4) (2020-06-09) + +**Note:** Version bump only for package gatsby-plugin-react-css-modules + ## [2.3.3](https://github.com/gatsbyjs/gatsby/compare/gatsby-plugin-react-css-modules@2.3.2...gatsby-plugin-react-css-modules@2.3.3) (2020-06-02) **Note:** Version bump only for package gatsby-plugin-react-css-modules diff --git a/packages/gatsby-plugin-react-css-modules/package.json b/packages/gatsby-plugin-react-css-modules/package.json index 088a9b1c1e00c..cd61d572e4a09 100644 --- a/packages/gatsby-plugin-react-css-modules/package.json +++ b/packages/gatsby-plugin-react-css-modules/package.json @@ -1,7 +1,7 @@ { "name": "gatsby-plugin-react-css-modules", "description": "Gatsby plugin that transforms styleName to className using compile time CSS module resolution", - "version": "2.3.3", + "version": "2.3.4", "author": "Ming Aldrich-Gan ", "bugs": { "url": "https://github.com/gatsbyjs/gatsby/issues" @@ -13,7 +13,7 @@ "devDependencies": { "@babel/cli": "^7.10.1", "@babel/core": "^7.10.2", - "babel-preset-gatsby-package": "^0.4.3", + "babel-preset-gatsby-package": "^0.4.4", "cross-env": "^5.2.1" }, "homepage": "https://github.com/gatsbyjs/gatsby/tree/master/packages/gatsby-plugin-react-css-modules#readme", diff --git a/packages/gatsby-plugin-react-helmet/CHANGELOG.md b/packages/gatsby-plugin-react-helmet/CHANGELOG.md index 1239a7d857d60..dc0a222f392d6 100644 --- a/packages/gatsby-plugin-react-helmet/CHANGELOG.md +++ b/packages/gatsby-plugin-react-helmet/CHANGELOG.md @@ -3,6 +3,10 @@ All notable changes to this project will be documented in this file. See [Conventional Commits](https://conventionalcommits.org) for commit guidelines. +## [3.3.4](https://github.com/gatsbyjs/gatsby/compare/gatsby-plugin-react-helmet@3.3.3...gatsby-plugin-react-helmet@3.3.4) (2020-06-09) + +**Note:** Version bump only for package gatsby-plugin-react-helmet + ## [3.3.3](https://github.com/gatsbyjs/gatsby/compare/gatsby-plugin-react-helmet@3.3.2...gatsby-plugin-react-helmet@3.3.3) (2020-06-02) **Note:** Version bump only for package gatsby-plugin-react-helmet diff --git a/packages/gatsby-plugin-react-helmet/package.json b/packages/gatsby-plugin-react-helmet/package.json index 779dbde09cafd..75259f09ea593 100644 --- a/packages/gatsby-plugin-react-helmet/package.json +++ b/packages/gatsby-plugin-react-helmet/package.json @@ -1,7 +1,7 @@ { "name": "gatsby-plugin-react-helmet", "description": "Manage document head data with react-helmet. Provides drop-in server rendering support for Gatsby.", - "version": "3.3.3", + "version": "3.3.4", "author": "Kyle Mathews ", "bugs": { "url": "https://github.com/gatsbyjs/gatsby/issues" @@ -12,7 +12,7 @@ "devDependencies": { "@babel/cli": "^7.10.1", "@babel/core": "^7.10.2", - "babel-preset-gatsby-package": "^0.4.3", + "babel-preset-gatsby-package": "^0.4.4", "cross-env": "^5.2.1" }, "homepage": "https://github.com/gatsbyjs/gatsby/tree/master/packages/gatsby-plugin-react-helmet#readme", diff --git a/packages/gatsby-plugin-remove-trailing-slashes/CHANGELOG.md b/packages/gatsby-plugin-remove-trailing-slashes/CHANGELOG.md index 1209a16a6a34f..6912bd9824f08 100644 --- a/packages/gatsby-plugin-remove-trailing-slashes/CHANGELOG.md +++ b/packages/gatsby-plugin-remove-trailing-slashes/CHANGELOG.md @@ -3,6 +3,10 @@ All notable changes to this project will be documented in this file. See [Conventional Commits](https://conventionalcommits.org) for commit guidelines. +## [2.3.5](https://github.com/gatsbyjs/gatsby/compare/gatsby-plugin-remove-trailing-slashes@2.3.4...gatsby-plugin-remove-trailing-slashes@2.3.5) (2020-06-09) + +**Note:** Version bump only for package gatsby-plugin-remove-trailing-slashes + ## [2.3.4](https://github.com/gatsbyjs/gatsby/compare/gatsby-plugin-remove-trailing-slashes@2.3.3...gatsby-plugin-remove-trailing-slashes@2.3.4) (2020-06-02) **Note:** Version bump only for package gatsby-plugin-remove-trailing-slashes diff --git a/packages/gatsby-plugin-remove-trailing-slashes/package.json b/packages/gatsby-plugin-remove-trailing-slashes/package.json index 424226eb4a165..4843b5853e09e 100644 --- a/packages/gatsby-plugin-remove-trailing-slashes/package.json +++ b/packages/gatsby-plugin-remove-trailing-slashes/package.json @@ -1,7 +1,7 @@ { "name": "gatsby-plugin-remove-trailing-slashes", "description": "Removes trailing slashes from your project's paths. For example, yoursite.com/about/ becomes yoursite.com/about", - "version": "2.3.4", + "version": "2.3.5", "author": "scott.eckenthal@gmail.com", "bugs": { "url": "https://github.com/gatsbyjs/gatsby/issues" @@ -12,7 +12,7 @@ "devDependencies": { "@babel/cli": "^7.10.1", "@babel/core": "^7.10.2", - "babel-preset-gatsby-package": "^0.4.3", + "babel-preset-gatsby-package": "^0.4.4", "cross-env": "^5.2.1" }, "homepage": "https://github.com/gatsbyjs/gatsby/tree/master/packages/gatsby-plugin-remove-trailing-slashes#readme", diff --git a/packages/gatsby-plugin-sass/CHANGELOG.md b/packages/gatsby-plugin-sass/CHANGELOG.md index 7396244f816db..93278ad98fd48 100644 --- a/packages/gatsby-plugin-sass/CHANGELOG.md +++ b/packages/gatsby-plugin-sass/CHANGELOG.md @@ -3,6 +3,10 @@ All notable changes to this project will be documented in this file. See [Conventional Commits](https://conventionalcommits.org) for commit guidelines. +## [2.3.4](https://github.com/gatsbyjs/gatsby/compare/gatsby-plugin-sass@2.3.3...gatsby-plugin-sass@2.3.4) (2020-06-09) + +**Note:** Version bump only for package gatsby-plugin-sass + ## [2.3.3](https://github.com/gatsbyjs/gatsby/compare/gatsby-plugin-sass@2.3.2...gatsby-plugin-sass@2.3.3) (2020-06-02) **Note:** Version bump only for package gatsby-plugin-sass diff --git a/packages/gatsby-plugin-sass/package.json b/packages/gatsby-plugin-sass/package.json index 6ff68c5320c1f..73168cccf527c 100644 --- a/packages/gatsby-plugin-sass/package.json +++ b/packages/gatsby-plugin-sass/package.json @@ -1,7 +1,7 @@ { "name": "gatsby-plugin-sass", "description": "Gatsby plugin to handle scss/sass files", - "version": "2.3.3", + "version": "2.3.4", "author": "Daniel Farrell ", "bugs": { "url": "https://github.com/gatsbyjs/gatsby/issues" @@ -13,7 +13,7 @@ "devDependencies": { "@babel/cli": "^7.10.1", "@babel/core": "^7.10.2", - "babel-preset-gatsby-package": "^0.4.3", + "babel-preset-gatsby-package": "^0.4.4", "cross-env": "^5.2.1" }, "homepage": "https://github.com/gatsbyjs/gatsby/tree/master/packages/gatsby-plugin-sass#readme", diff --git a/packages/gatsby-plugin-sharp/CHANGELOG.md b/packages/gatsby-plugin-sharp/CHANGELOG.md index 8d3b36d84ab6b..4b00d471a1cb2 100644 --- a/packages/gatsby-plugin-sharp/CHANGELOG.md +++ b/packages/gatsby-plugin-sharp/CHANGELOG.md @@ -3,6 +3,10 @@ All notable changes to this project will be documented in this file. See [Conventional Commits](https://conventionalcommits.org) for commit guidelines. +## [2.6.11](https://github.com/gatsbyjs/gatsby/compare/gatsby-plugin-sharp@2.6.10...gatsby-plugin-sharp@2.6.11) (2020-06-09) + +**Note:** Version bump only for package gatsby-plugin-sharp + ## [2.6.10](https://github.com/gatsbyjs/gatsby/compare/gatsby-plugin-sharp@2.6.9...gatsby-plugin-sharp@2.6.10) (2020-06-02) **Note:** Version bump only for package gatsby-plugin-sharp diff --git a/packages/gatsby-plugin-sharp/package.json b/packages/gatsby-plugin-sharp/package.json index a9171090365b2..2bebbb07cd8f9 100644 --- a/packages/gatsby-plugin-sharp/package.json +++ b/packages/gatsby-plugin-sharp/package.json @@ -1,7 +1,7 @@ { "name": "gatsby-plugin-sharp", "description": "Wrapper of the Sharp image manipulation library for Gatsby plugins", - "version": "2.6.10", + "version": "2.6.11", "author": "Kyle Mathews ", "bugs": { "url": "https://github.com/gatsbyjs/gatsby/issues" @@ -11,7 +11,7 @@ "async": "^2.6.3", "bluebird": "^3.7.2", "fs-extra": "^8.1.0", - "gatsby-core-utils": "^1.3.4", + "gatsby-core-utils": "^1.3.5", "got": "^8.3.2", "imagemin": "^6.1.0", "imagemin-mozjpeg": "^8.0.0", @@ -30,7 +30,7 @@ "devDependencies": { "@babel/cli": "^7.10.1", "@babel/core": "^7.10.2", - "babel-preset-gatsby-package": "^0.4.3", + "babel-preset-gatsby-package": "^0.4.4", "cross-env": "^5.2.1" }, "homepage": "https://github.com/gatsbyjs/gatsby/tree/master/packages/gatsby-plugin-sharp#readme", diff --git a/packages/gatsby-plugin-sitemap/CHANGELOG.md b/packages/gatsby-plugin-sitemap/CHANGELOG.md index 1ad18a9886b52..74750e019b605 100644 --- a/packages/gatsby-plugin-sitemap/CHANGELOG.md +++ b/packages/gatsby-plugin-sitemap/CHANGELOG.md @@ -3,6 +3,10 @@ All notable changes to this project will be documented in this file. See [Conventional Commits](https://conventionalcommits.org) for commit guidelines. +## [2.4.5](https://github.com/gatsbyjs/gatsby/compare/gatsby-plugin-sitemap@2.4.4...gatsby-plugin-sitemap@2.4.5) (2020-06-09) + +**Note:** Version bump only for package gatsby-plugin-sitemap + ## [2.4.4](https://github.com/gatsbyjs/gatsby/compare/gatsby-plugin-sitemap@2.4.3...gatsby-plugin-sitemap@2.4.4) (2020-06-02) **Note:** Version bump only for package gatsby-plugin-sitemap diff --git a/packages/gatsby-plugin-sitemap/package.json b/packages/gatsby-plugin-sitemap/package.json index 2b7166bd8dabb..b7a63b4dfc41d 100644 --- a/packages/gatsby-plugin-sitemap/package.json +++ b/packages/gatsby-plugin-sitemap/package.json @@ -1,7 +1,7 @@ { "name": "gatsby-plugin-sitemap", "description": "Gatsby plugin that automatically creates a sitemap for your site", - "version": "2.4.4", + "version": "2.4.5", "author": "Nicholas Young <nicholas@nicholaswyoung.com>", "bugs": { "url": "https://github.com/gatsbyjs/gatsby/issues" @@ -15,7 +15,7 @@ "devDependencies": { "@babel/cli": "^7.10.1", "@babel/core": "^7.10.2", - "babel-preset-gatsby-package": "^0.4.3", + "babel-preset-gatsby-package": "^0.4.4", "cross-env": "^5.2.1" }, "homepage": "https://github.com/gatsbyjs/gatsby/tree/master/packages/gatsby-plugin-sitemap#readme", diff --git a/packages/gatsby-plugin-styled-components/CHANGELOG.md b/packages/gatsby-plugin-styled-components/CHANGELOG.md index 555497f69c6a8..9077843caaeb3 100644 --- a/packages/gatsby-plugin-styled-components/CHANGELOG.md +++ b/packages/gatsby-plugin-styled-components/CHANGELOG.md @@ -3,6 +3,10 @@ All notable changes to this project will be documented in this file. See [Conventional Commits](https://conventionalcommits.org) for commit guidelines. +## [3.3.4](https://github.com/gatsbyjs/gatsby/compare/gatsby-plugin-styled-components@3.3.3...gatsby-plugin-styled-components@3.3.4) (2020-06-09) + +**Note:** Version bump only for package gatsby-plugin-styled-components + ## [3.3.3](https://github.com/gatsbyjs/gatsby/compare/gatsby-plugin-styled-components@3.3.2...gatsby-plugin-styled-components@3.3.3) (2020-06-02) **Note:** Version bump only for package gatsby-plugin-styled-components diff --git a/packages/gatsby-plugin-styled-components/package.json b/packages/gatsby-plugin-styled-components/package.json index 60254d46eaac1..ddb1d8b667e1f 100644 --- a/packages/gatsby-plugin-styled-components/package.json +++ b/packages/gatsby-plugin-styled-components/package.json @@ -1,7 +1,7 @@ { "name": "gatsby-plugin-styled-components", "description": "Gatsby plugin to add support for styled components", - "version": "3.3.3", + "version": "3.3.4", "author": "Guten Ye ", "bugs": { "url": "https://github.com/gatsbyjs/gatsby/issues" @@ -12,7 +12,7 @@ "devDependencies": { "@babel/cli": "^7.10.1", "@babel/core": "^7.10.2", - "babel-preset-gatsby-package": "^0.4.3", + "babel-preset-gatsby-package": "^0.4.4", "cross-env": "^5.2.1" }, "homepage": "https://github.com/gatsbyjs/gatsby/tree/master/packages/gatsby-plugin-styled-components#readme", diff --git a/packages/gatsby-plugin-styled-jsx/CHANGELOG.md b/packages/gatsby-plugin-styled-jsx/CHANGELOG.md index c38723a9dcc73..5f95d38fc5b88 100644 --- a/packages/gatsby-plugin-styled-jsx/CHANGELOG.md +++ b/packages/gatsby-plugin-styled-jsx/CHANGELOG.md @@ -3,6 +3,10 @@ All notable changes to this project will be documented in this file. See [Conventional Commits](https://conventionalcommits.org) for commit guidelines. +## [3.3.4](https://github.com/gatsbyjs/gatsby/compare/gatsby-plugin-styled-jsx@3.3.3...gatsby-plugin-styled-jsx@3.3.4) (2020-06-09) + +**Note:** Version bump only for package gatsby-plugin-styled-jsx + ## [3.3.3](https://github.com/gatsbyjs/gatsby/compare/gatsby-plugin-styled-jsx@3.3.2...gatsby-plugin-styled-jsx@3.3.3) (2020-06-02) **Note:** Version bump only for package gatsby-plugin-styled-jsx diff --git a/packages/gatsby-plugin-styled-jsx/README.md b/packages/gatsby-plugin-styled-jsx/README.md index 2dec7e7024dd6..af81cff0c914a 100644 --- a/packages/gatsby-plugin-styled-jsx/README.md +++ b/packages/gatsby-plugin-styled-jsx/README.md @@ -1,6 +1,6 @@ # gatsby-plugin-styled-jsx -Provides drop-in support for [styled-jsx](https://github.com/zeit/styled-jsx). +Provides drop-in support for [styled-jsx](https://github.com/vercel/styled-jsx). ## Install @@ -14,7 +14,7 @@ Add the plugin to the plugins array in your `gatsby-config.js` and use `