From c20466a3dae07daaaef4c39556920222d45775cf Mon Sep 17 00:00:00 2001 From: Alex Reed Date: Thu, 10 Mar 2022 10:48:20 -0500 Subject: [PATCH 1/7] replace all references to gatsbyjs.org with gatsbyjs.com --- .../gatsby-site-showcase-validator/README.md | 2 +- .../src/__tests__/fixtures/data.json | 2 +- .../gabe-csv-markdown/src/components/bio.js | 2 +- .../src/components/layout.js | 2 +- .../gabe-csv-text/src/components/bio.js | 2 +- .../gabe-csv-text/src/components/layout.js | 2 +- .../src/components/bio.js | 2 +- .../src/components/layout.js | 2 +- .../src/components/bio.js | 2 +- .../src/components/layout.js | 2 +- .../gabe-fs-markdown/src/components/bio.js | 2 +- .../gabe-fs-markdown/src/components/layout.js | 2 +- .../gabe-fs-mdx/src/components/layout.js | 2 +- benchmarks/gabe-fs-text/src/components/bio.js | 2 +- .../gabe-fs-text/src/components/layout.js | 2 +- .../gabe-json-text/src/components/bio.js | 2 +- .../gabe-json-text/src/components/layout.js | 2 +- .../gabe-yaml-text/src/components/bio.js | 2 +- .../gabe-yaml-text/src/components/layout.js | 2 +- benchmarks/image-processing/gatsby-browser.js | 2 +- benchmarks/image-processing/gatsby-ssr.js | 2 +- .../image-processing/src/components/image.js | 2 +- .../image-processing/src/components/layout.js | 4 +- .../image-processing/src/components/seo.js | 2 +- benchmarks/markdown_id/src/components/bio.js | 2 +- .../markdown_id/src/components/layout.js | 2 +- benchmarks/markdown_id/src/components/seo.js | 2 +- .../markdown_slug/src/components/bio.js | 2 +- .../markdown_slug/src/components/layout.js | 2 +- .../markdown_slug/src/components/seo.js | 2 +- benchmarks/source-agilitycms/gatsby-config.js | 2 +- benchmarks/source-strapi/gatsby-browser.js | 2 +- deprecated-packages/gatsby-image/README.md | 6 +- deprecated-packages/gatsby-image/src/index.js | 2 +- .../gatsby-recipes/CONTRIBUTING.md | 4 +- deprecated-packages/gatsby-recipes/README.md | 6 +- .../gatsby-recipes/recipes/README.md | 2 +- .../gatsby-recipes/recipes/gatsby-image.mdx | 2 +- .../recipes/gatsby-plugin-layout.mdx | 4 +- .../recipes/gatsby-plugin-react-helmet.mdx | 6 +- .../recipes/gatsby-theme-blog-core.mdx | 2 +- .../recipes/gatsby-theme-blog.mdx | 2 +- .../recipes/gatsby-theme-notes.mdx | 2 +- .../gatsby-recipes/recipes/mdx-images.mdx | 2 +- .../gatsby-recipes/recipes/pwa.mdx | 4 +- .../gatsby/__snapshots__/plugin.test.js.snap | 8 +- .../gatsby-config.js | 2 +- .../src/providers/gatsby/site-metadata.js | 2 +- docs/contributing/contributor-swag.md | 6 +- docs/docs/conceptual/data-fetching.md | 2 +- .../building-a-site-with-authentication.md | 4 +- .../images-and-media/using-gatsby-image.md | 4 +- ...ent-only-routes-and-user-authentication.md | 2 +- ...porting-from-create-react-app-to-gatsby.md | 2 +- .../built-in-components/gatsby-image.md | 10 +-- .../release-notes/migrating-from-v1-to-v2.md | 6 +- .../release-notes/v1-release-notes.md | 2 +- docs/docs/themes.md | 2 +- docs/tutorial/authentication-tutorial.md | 2 +- docs/tutorial/wordpress-image-tutorial.md | 4 +- e2e-tests/contentful/README.md | 2 +- e2e-tests/development-runtime/README.md | 18 ++-- e2e-tests/development-runtime/gatsby-ssr.js | 2 +- e2e-tests/gatsby-image/README.md | 2 +- e2e-tests/gatsby-image/gatsby-browser.js | 2 +- e2e-tests/gatsby-image/gatsby-node.js | 2 +- e2e-tests/gatsby-image/gatsby-ssr.js | 2 +- e2e-tests/gatsby-static-image/README.md | 2 +- e2e-tests/path-prefix/README.md | 2 +- e2e-tests/path-prefix/gatsby-browser.js | 2 +- e2e-tests/path-prefix/gatsby-node.js | 2 +- e2e-tests/path-prefix/gatsby-ssr.js | 2 +- e2e-tests/production-runtime/README.md | 2 +- examples/gatsbygram/README.md | 2 +- examples/image-processing/README.md | 2 +- examples/no-trailing-slashes/README.md | 2 +- examples/using-asciidoc/README.md | 2 +- examples/using-css-modules/README.md | 2 +- examples/using-drupal/README.md | 2 +- examples/using-emotion/README.md | 2 +- examples/using-gatsby-image/README.md | 2 +- examples/using-glamor/README.md | 2 +- examples/using-hjson/README.md | 2 +- examples/using-jss/README.md | 2 +- examples/using-medium/README.md | 2 +- examples/using-mongodb/README.md | 2 +- examples/using-redux/README.md | 2 +- examples/using-remark/README.md | 2 +- .../index.md | 2 +- examples/using-sass/README.md | 2 +- examples/using-styled-components/README.md | 2 +- examples/using-styled-jsx/README.md | 2 +- examples/using-stylus/README.md | 2 +- examples/using-wordpress-with-acf/README.md | 2 +- .../gatsby-pipeline/src/components/layout.js | 2 +- .../structured-plugin-errors/gatsby-node.js | 2 +- packages/babel-preset-gatsby/README.md | 4 +- packages/gatsby-cli/README.md | 16 ++-- packages/gatsby-cli/scripts/postinstall.js | 2 +- .../__tests__/__snapshots__/index.ts.snap | 4 +- .../src/reporter/__tests__/index.ts | 6 +- .../__tests__/construct-error.ts | 6 +- packages/gatsby-codemods/README.md | 8 +- packages/gatsby-design-tokens/CHANGELOG.md | 10 +-- packages/gatsby-design-tokens/README.md | 12 +-- .../src/theme-gatsbyjs-org.js | 2 +- packages/gatsby-dev-cli/README.md | 2 +- packages/gatsby-link/README.md | 2 +- packages/gatsby-plugin-catch-links/README.md | 4 +- .../README.md | 2 +- packages/gatsby-plugin-feed/README.md | 2 +- packages/gatsby-plugin-gatsby-cloud/README.md | 6 +- .../gatsby-plugin-google-analytics/README.md | 2 +- packages/gatsby-plugin-google-gtag/README.md | 4 +- packages/gatsby-plugin-jss/README.md | 2 +- packages/gatsby-plugin-layout/README.md | 4 +- packages/gatsby-plugin-mdx/README.md | 8 +- packages/gatsby-plugin-netlify-cms/README.md | 4 +- .../src/__tests__/fixtures/public/index.html | 4 +- .../src/__tests__/gatsby-browser.test.js | 6 +- .../src/gatsby-node.ts | 2 +- .../gatsby-plugin-react-css-modules/README.md | 2 +- packages/gatsby-plugin-typography/README.md | 2 +- .../gatsby-remark-copy-linked-files/README.md | 2 +- .../gatsby-remark-custom-blocks/README.md | 2 +- .../gatsby-remark-embed-snippet/README.md | 4 +- packages/gatsby-remark-images/README.md | 2 +- packages/gatsby-remark-katex/README.md | 4 +- packages/gatsby-remark-prismjs/README.md | 6 +- packages/gatsby-source-contentful/README.md | 10 +-- .../src/__tests__/normalize.js | 2 +- .../src/source-nodes.js | 2 +- packages/gatsby-source-drupal/README.md | 4 +- packages/gatsby-source-filesystem/README.md | 2 +- packages/gatsby-source-filesystem/index.d.ts | 8 +- .../src/gatsby-node.js | 2 +- packages/gatsby-source-lever/src/normalize.js | 2 +- .../README.md | 4 +- packages/gatsby-transformer-remark/README.md | 2 +- .../gatsby-transformer-screenshot/README.md | 2 +- packages/gatsby-transformer-sharp/README.md | 4 +- packages/gatsby/CHANGELOG.md | 26 +++--- .../gatsby/cache-dir/__tests__/dev-loader.js | 2 +- .../cache-dir/__tests__/static-entry.js | 6 +- packages/gatsby/cache-dir/dev-loader.js | 2 +- packages/gatsby/index.d.ts | 82 +++++++++---------- .../src/bootstrap/load-plugins/validate.ts | 4 +- packages/gatsby/src/commands/build.ts | 2 +- .../prod-404-500/gatsby-node.js | 2 +- packages/gatsby/src/query/query-watcher.ts | 2 +- .../__snapshots__/rebuild-schema.js.snap | 2 +- .../schema/infer/type-conflict-reporter.ts | 2 +- .../src/utils/__tests__/api-runner-node.js | 4 +- .../gatsby/src/utils/api-node-helpers-docs.js | 2 +- .../validate-yaml-creators.test.ts | 2 +- scripts/i18n/PROGRESS.template.md | 2 +- scripts/i18n/create.js | 4 +- scripts/i18n/sync.js | 2 +- scripts/site-up-checker/index.js | 6 +- 159 files changed, 301 insertions(+), 301 deletions(-) diff --git a/.github/actions/gatsby-site-showcase-validator/README.md b/.github/actions/gatsby-site-showcase-validator/README.md index 2751dcfe61983..61b7960a3fd9d 100644 --- a/.github/actions/gatsby-site-showcase-validator/README.md +++ b/.github/actions/gatsby-site-showcase-validator/README.md @@ -1,5 +1,5 @@ # Gatsby Site Showcase Validator -A simple node script that visits and checks all of the sites in the [Site Showcase](https://www.gatsbyjs.org/showcase/) for Gatsby. +A simple node script that visits and checks all of the sites in the [Site Showcase](https://www.gatsbyjs.com/showcase/) for Gatsby. Run locally [using act](https://github.com/nektos/act): `act -a "gatsby-site-showcase-validator"` diff --git a/.github/actions/high-priority-prs/src/__tests__/fixtures/data.json b/.github/actions/high-priority-prs/src/__tests__/fixtures/data.json index f42c7fd2b544c..b1553f20c2718 100644 --- a/.github/actions/high-priority-prs/src/__tests__/fixtures/data.json +++ b/.github/actions/high-priority-prs/src/__tests__/fixtures/data.json @@ -7356,7 +7356,7 @@ { "commit": { "authoredDate": "2019-06-03T02:42:32Z", - "message": "Made the doc easier to read\n\n- Moved a lot of sentences into active voice\r\n- Removed unnecessary words and sentences\r\n- Fixed some grammatical errors\r\n- Removed potentially confusing emojis as a literary device\r\n- Split up some long sentences into shorter ones\r\n- Added a link to https://www.gatsbyjs.org/blog/2018-06-08-life-after-layouts/ in the layouts section to help people move from Gatsby's layout behavior in v1\r\n- Capitalized instances of \"Babel\" that were lowercase" + "message": "Made the doc easier to read\n\n- Moved a lot of sentences into active voice\r\n- Removed unnecessary words and sentences\r\n- Fixed some grammatical errors\r\n- Removed potentially confusing emojis as a literary device\r\n- Split up some long sentences into shorter ones\r\n- Added a link to https://www.gatsbyjs.com/blog/2018-06-08-life-after-layouts/ in the layouts section to help people move from Gatsby's layout behavior in v1\r\n- Capitalized instances of \"Babel\" that were lowercase" } }, { diff --git a/benchmarks/gabe-csv-markdown/src/components/bio.js b/benchmarks/gabe-csv-markdown/src/components/bio.js index 867acfe818a21..7da2de84df3fa 100644 --- a/benchmarks/gabe-csv-markdown/src/components/bio.js +++ b/benchmarks/gabe-csv-markdown/src/components/bio.js @@ -2,7 +2,7 @@ * Bio component that queries for data * with Gatsby's useStaticQuery component * - * See: https://www.gatsbyjs.org/docs/use-static-query/ + * See: https://www.gatsbyjs.com/docs/use-static-query/ */ import React from "react" diff --git a/benchmarks/gabe-csv-markdown/src/components/layout.js b/benchmarks/gabe-csv-markdown/src/components/layout.js index 0fb3df2756467..0110e61d165d9 100644 --- a/benchmarks/gabe-csv-markdown/src/components/layout.js +++ b/benchmarks/gabe-csv-markdown/src/components/layout.js @@ -62,7 +62,7 @@ class Layout extends React.Component { ) diff --git a/benchmarks/gabe-csv-text/src/components/bio.js b/benchmarks/gabe-csv-text/src/components/bio.js index 867acfe818a21..7da2de84df3fa 100644 --- a/benchmarks/gabe-csv-text/src/components/bio.js +++ b/benchmarks/gabe-csv-text/src/components/bio.js @@ -2,7 +2,7 @@ * Bio component that queries for data * with Gatsby's useStaticQuery component * - * See: https://www.gatsbyjs.org/docs/use-static-query/ + * See: https://www.gatsbyjs.com/docs/use-static-query/ */ import React from "react" diff --git a/benchmarks/gabe-csv-text/src/components/layout.js b/benchmarks/gabe-csv-text/src/components/layout.js index 0fb3df2756467..0110e61d165d9 100644 --- a/benchmarks/gabe-csv-text/src/components/layout.js +++ b/benchmarks/gabe-csv-text/src/components/layout.js @@ -62,7 +62,7 @@ class Layout extends React.Component { ) diff --git a/benchmarks/gabe-fs-markdown-images/src/components/bio.js b/benchmarks/gabe-fs-markdown-images/src/components/bio.js index 867acfe818a21..7da2de84df3fa 100644 --- a/benchmarks/gabe-fs-markdown-images/src/components/bio.js +++ b/benchmarks/gabe-fs-markdown-images/src/components/bio.js @@ -2,7 +2,7 @@ * Bio component that queries for data * with Gatsby's useStaticQuery component * - * See: https://www.gatsbyjs.org/docs/use-static-query/ + * See: https://www.gatsbyjs.com/docs/use-static-query/ */ import React from "react" diff --git a/benchmarks/gabe-fs-markdown-images/src/components/layout.js b/benchmarks/gabe-fs-markdown-images/src/components/layout.js index 0fb3df2756467..0110e61d165d9 100644 --- a/benchmarks/gabe-fs-markdown-images/src/components/layout.js +++ b/benchmarks/gabe-fs-markdown-images/src/components/layout.js @@ -62,7 +62,7 @@ class Layout extends React.Component { ) diff --git a/benchmarks/gabe-fs-markdown-route-api/src/components/bio.js b/benchmarks/gabe-fs-markdown-route-api/src/components/bio.js index 867acfe818a21..7da2de84df3fa 100644 --- a/benchmarks/gabe-fs-markdown-route-api/src/components/bio.js +++ b/benchmarks/gabe-fs-markdown-route-api/src/components/bio.js @@ -2,7 +2,7 @@ * Bio component that queries for data * with Gatsby's useStaticQuery component * - * See: https://www.gatsbyjs.org/docs/use-static-query/ + * See: https://www.gatsbyjs.com/docs/use-static-query/ */ import React from "react" diff --git a/benchmarks/gabe-fs-markdown-route-api/src/components/layout.js b/benchmarks/gabe-fs-markdown-route-api/src/components/layout.js index 0fb3df2756467..0110e61d165d9 100644 --- a/benchmarks/gabe-fs-markdown-route-api/src/components/layout.js +++ b/benchmarks/gabe-fs-markdown-route-api/src/components/layout.js @@ -62,7 +62,7 @@ class Layout extends React.Component { ) diff --git a/benchmarks/gabe-fs-markdown/src/components/bio.js b/benchmarks/gabe-fs-markdown/src/components/bio.js index 867acfe818a21..7da2de84df3fa 100644 --- a/benchmarks/gabe-fs-markdown/src/components/bio.js +++ b/benchmarks/gabe-fs-markdown/src/components/bio.js @@ -2,7 +2,7 @@ * Bio component that queries for data * with Gatsby's useStaticQuery component * - * See: https://www.gatsbyjs.org/docs/use-static-query/ + * See: https://www.gatsbyjs.com/docs/use-static-query/ */ import React from "react" diff --git a/benchmarks/gabe-fs-markdown/src/components/layout.js b/benchmarks/gabe-fs-markdown/src/components/layout.js index 0fb3df2756467..0110e61d165d9 100644 --- a/benchmarks/gabe-fs-markdown/src/components/layout.js +++ b/benchmarks/gabe-fs-markdown/src/components/layout.js @@ -62,7 +62,7 @@ class Layout extends React.Component { ) diff --git a/benchmarks/gabe-fs-mdx/src/components/layout.js b/benchmarks/gabe-fs-mdx/src/components/layout.js index 0fb3df2756467..0110e61d165d9 100644 --- a/benchmarks/gabe-fs-mdx/src/components/layout.js +++ b/benchmarks/gabe-fs-mdx/src/components/layout.js @@ -62,7 +62,7 @@ class Layout extends React.Component { ) diff --git a/benchmarks/gabe-fs-text/src/components/bio.js b/benchmarks/gabe-fs-text/src/components/bio.js index 867acfe818a21..7da2de84df3fa 100644 --- a/benchmarks/gabe-fs-text/src/components/bio.js +++ b/benchmarks/gabe-fs-text/src/components/bio.js @@ -2,7 +2,7 @@ * Bio component that queries for data * with Gatsby's useStaticQuery component * - * See: https://www.gatsbyjs.org/docs/use-static-query/ + * See: https://www.gatsbyjs.com/docs/use-static-query/ */ import React from "react" diff --git a/benchmarks/gabe-fs-text/src/components/layout.js b/benchmarks/gabe-fs-text/src/components/layout.js index 0fb3df2756467..0110e61d165d9 100644 --- a/benchmarks/gabe-fs-text/src/components/layout.js +++ b/benchmarks/gabe-fs-text/src/components/layout.js @@ -62,7 +62,7 @@ class Layout extends React.Component { ) diff --git a/benchmarks/gabe-json-text/src/components/bio.js b/benchmarks/gabe-json-text/src/components/bio.js index 867acfe818a21..7da2de84df3fa 100644 --- a/benchmarks/gabe-json-text/src/components/bio.js +++ b/benchmarks/gabe-json-text/src/components/bio.js @@ -2,7 +2,7 @@ * Bio component that queries for data * with Gatsby's useStaticQuery component * - * See: https://www.gatsbyjs.org/docs/use-static-query/ + * See: https://www.gatsbyjs.com/docs/use-static-query/ */ import React from "react" diff --git a/benchmarks/gabe-json-text/src/components/layout.js b/benchmarks/gabe-json-text/src/components/layout.js index 0fb3df2756467..0110e61d165d9 100644 --- a/benchmarks/gabe-json-text/src/components/layout.js +++ b/benchmarks/gabe-json-text/src/components/layout.js @@ -62,7 +62,7 @@ class Layout extends React.Component { ) diff --git a/benchmarks/gabe-yaml-text/src/components/bio.js b/benchmarks/gabe-yaml-text/src/components/bio.js index 867acfe818a21..7da2de84df3fa 100644 --- a/benchmarks/gabe-yaml-text/src/components/bio.js +++ b/benchmarks/gabe-yaml-text/src/components/bio.js @@ -2,7 +2,7 @@ * Bio component that queries for data * with Gatsby's useStaticQuery component * - * See: https://www.gatsbyjs.org/docs/use-static-query/ + * See: https://www.gatsbyjs.com/docs/use-static-query/ */ import React from "react" diff --git a/benchmarks/gabe-yaml-text/src/components/layout.js b/benchmarks/gabe-yaml-text/src/components/layout.js index 0fb3df2756467..0110e61d165d9 100644 --- a/benchmarks/gabe-yaml-text/src/components/layout.js +++ b/benchmarks/gabe-yaml-text/src/components/layout.js @@ -62,7 +62,7 @@ class Layout extends React.Component { ) diff --git a/benchmarks/image-processing/gatsby-browser.js b/benchmarks/image-processing/gatsby-browser.js index b1e5c316b7f94..ff807f19ef7cc 100644 --- a/benchmarks/image-processing/gatsby-browser.js +++ b/benchmarks/image-processing/gatsby-browser.js @@ -1,7 +1,7 @@ /** * Implement Gatsby's Browser APIs in this file. * - * See: https://www.gatsbyjs.org/docs/browser-apis/ + * See: https://www.gatsbyjs.com/docs/browser-apis/ */ // You can delete this file if you're not using it diff --git a/benchmarks/image-processing/gatsby-ssr.js b/benchmarks/image-processing/gatsby-ssr.js index b17b8fc19d659..01d83255f4f2c 100644 --- a/benchmarks/image-processing/gatsby-ssr.js +++ b/benchmarks/image-processing/gatsby-ssr.js @@ -1,7 +1,7 @@ /** * Implement Gatsby's SSR (Server Side Rendering) APIs in this file. * - * See: https://www.gatsbyjs.org/docs/ssr-apis/ + * See: https://www.gatsbyjs.com/docs/ssr-apis/ */ // You can delete this file if you're not using it diff --git a/benchmarks/image-processing/src/components/image.js b/benchmarks/image-processing/src/components/image.js index e61edb684de4e..b134a7b80be74 100644 --- a/benchmarks/image-processing/src/components/image.js +++ b/benchmarks/image-processing/src/components/image.js @@ -10,7 +10,7 @@ import Img from "gatsby-image" * * For more information, see the docs: * - `gatsby-image`: https://gatsby.dev/gatsby-image - * - `useStaticQuery`: https://www.gatsbyjs.org/docs/use-static-query/ + * - `useStaticQuery`: https://www.gatsbyjs.com/docs/use-static-query/ */ const Image = () => { diff --git a/benchmarks/image-processing/src/components/layout.js b/benchmarks/image-processing/src/components/layout.js index 8d559875eb270..5cded509ac498 100644 --- a/benchmarks/image-processing/src/components/layout.js +++ b/benchmarks/image-processing/src/components/layout.js @@ -2,7 +2,7 @@ * Layout component that queries for data * with Gatsby's useStaticQuery component * - * See: https://www.gatsbyjs.org/docs/use-static-query/ + * See: https://www.gatsbyjs.com/docs/use-static-query/ */ import React from "react" @@ -38,7 +38,7 @@ const Layout = ({ children }) => { diff --git a/benchmarks/image-processing/src/components/seo.js b/benchmarks/image-processing/src/components/seo.js index e15f59958a3c0..b40a909ae8c8b 100644 --- a/benchmarks/image-processing/src/components/seo.js +++ b/benchmarks/image-processing/src/components/seo.js @@ -2,7 +2,7 @@ * SEO component that queries for data with * Gatsby's useStaticQuery React hook * - * See: https://www.gatsbyjs.org/docs/use-static-query/ + * See: https://www.gatsbyjs.com/docs/use-static-query/ */ import React from "react" diff --git a/benchmarks/markdown_id/src/components/bio.js b/benchmarks/markdown_id/src/components/bio.js index f74b2e8318dc5..62b09465ec8c3 100644 --- a/benchmarks/markdown_id/src/components/bio.js +++ b/benchmarks/markdown_id/src/components/bio.js @@ -2,7 +2,7 @@ * Bio component that queries for data * with Gatsby's useStaticQuery component * - * See: https://www.gatsbyjs.org/docs/use-static-query/ + * See: https://www.gatsbyjs.com/docs/use-static-query/ */ import React from "react" diff --git a/benchmarks/markdown_id/src/components/layout.js b/benchmarks/markdown_id/src/components/layout.js index 5a44c9cacfed2..fa512ff708b40 100644 --- a/benchmarks/markdown_id/src/components/layout.js +++ b/benchmarks/markdown_id/src/components/layout.js @@ -65,7 +65,7 @@ class Layout extends React.Component { ) diff --git a/benchmarks/markdown_id/src/components/seo.js b/benchmarks/markdown_id/src/components/seo.js index e15f59958a3c0..b40a909ae8c8b 100644 --- a/benchmarks/markdown_id/src/components/seo.js +++ b/benchmarks/markdown_id/src/components/seo.js @@ -2,7 +2,7 @@ * SEO component that queries for data with * Gatsby's useStaticQuery React hook * - * See: https://www.gatsbyjs.org/docs/use-static-query/ + * See: https://www.gatsbyjs.com/docs/use-static-query/ */ import React from "react" diff --git a/benchmarks/markdown_slug/src/components/bio.js b/benchmarks/markdown_slug/src/components/bio.js index f74b2e8318dc5..62b09465ec8c3 100644 --- a/benchmarks/markdown_slug/src/components/bio.js +++ b/benchmarks/markdown_slug/src/components/bio.js @@ -2,7 +2,7 @@ * Bio component that queries for data * with Gatsby's useStaticQuery component * - * See: https://www.gatsbyjs.org/docs/use-static-query/ + * See: https://www.gatsbyjs.com/docs/use-static-query/ */ import React from "react" diff --git a/benchmarks/markdown_slug/src/components/layout.js b/benchmarks/markdown_slug/src/components/layout.js index 5a44c9cacfed2..fa512ff708b40 100644 --- a/benchmarks/markdown_slug/src/components/layout.js +++ b/benchmarks/markdown_slug/src/components/layout.js @@ -65,7 +65,7 @@ class Layout extends React.Component { ) diff --git a/benchmarks/markdown_slug/src/components/seo.js b/benchmarks/markdown_slug/src/components/seo.js index e15f59958a3c0..b40a909ae8c8b 100644 --- a/benchmarks/markdown_slug/src/components/seo.js +++ b/benchmarks/markdown_slug/src/components/seo.js @@ -2,7 +2,7 @@ * SEO component that queries for data with * Gatsby's useStaticQuery React hook * - * See: https://www.gatsbyjs.org/docs/use-static-query/ + * See: https://www.gatsbyjs.com/docs/use-static-query/ */ import React from "react" diff --git a/benchmarks/source-agilitycms/gatsby-config.js b/benchmarks/source-agilitycms/gatsby-config.js index 65a00a262366a..c10190d3d7b4e 100644 --- a/benchmarks/source-agilitycms/gatsby-config.js +++ b/benchmarks/source-agilitycms/gatsby-config.js @@ -13,7 +13,7 @@ const agilityConfig = { /** * Configure your Gatsby site with this file. * - * See: https://www.gatsbyjs.org/docs/gatsby-config/ + * See: https://www.gatsbyjs.com/docs/gatsby-config/ */ module.exports = { diff --git a/benchmarks/source-strapi/gatsby-browser.js b/benchmarks/source-strapi/gatsby-browser.js index b1e5c316b7f94..ff807f19ef7cc 100644 --- a/benchmarks/source-strapi/gatsby-browser.js +++ b/benchmarks/source-strapi/gatsby-browser.js @@ -1,7 +1,7 @@ /** * Implement Gatsby's Browser APIs in this file. * - * See: https://www.gatsbyjs.org/docs/browser-apis/ + * See: https://www.gatsbyjs.com/docs/browser-apis/ */ // You can delete this file if you're not using it diff --git a/deprecated-packages/gatsby-image/README.md b/deprecated-packages/gatsby-image/README.md index cd9471bf0e511..c9424b474604f 100644 --- a/deprecated-packages/gatsby-image/README.md +++ b/deprecated-packages/gatsby-image/README.md @@ -8,7 +8,7 @@ Speedy, optimized images without the work. `gatsby-image` is a React component specially designed to work seamlessly with Gatsby's GraphQL queries. It combines -[Gatsby's native image processing](https://image-processing.gatsbyjs.org/) +[Gatsby's native image processing](https://image-processing.gatsbyjs.com/) capabilities with advanced image loading techniques to easily and completely optimize image loading for your sites. `gatsby-image` uses [gatsby-plugin-sharp](/plugins/gatsby-plugin-sharp/) @@ -18,7 +18,7 @@ _Note: gatsby-image is **not** a drop-in replacement for ``. It's optimized for fixed width/height images and images that stretch the full-width of a container. Some ways you can use `` won't work with gatsby-image._ -**[Demo](https://using-gatsby-image.gatsbyjs.org)** +**[Demo](https://using-gatsby-image.gatsbyjs.com)** ## Table of Contents @@ -269,7 +269,7 @@ format, use the `withWebp` fragments. If the browser doesn't support WebP, `gatsby-image` will fall back to the default image format. For more information about these options, please see the -[Gatsby Image API](https://www.gatsbyjs.org/docs/gatsby-image/#image-query-fragments). +[Gatsby Image API](https://www.gatsbyjs.com/docs/gatsby-image/#image-query-fragments). _Please see the [gatsby-plugin-sharp](/plugins/gatsby-plugin-sharp/#tracedsvg) diff --git a/deprecated-packages/gatsby-image/src/index.js b/deprecated-packages/gatsby-image/src/index.js index cd4b732d410e1..37533e35a8093 100644 --- a/deprecated-packages/gatsby-image/src/index.js +++ b/deprecated-packages/gatsby-image/src/index.js @@ -192,7 +192,7 @@ function groupByMedia(imageVariants) { if (without.length > 1 && process.env.NODE_ENV !== `production`) { console.warn( - `We've found ${without.length} sources without a media property. They might be ignored by the browser, see: https://www.gatsbyjs.org/packages/gatsby-image/#art-directing-multiple-images` + `We've found ${without.length} sources without a media property. They might be ignored by the browser, see: https://www.gatsbyjs.com/packages/gatsby-image/#art-directing-multiple-images` ) } diff --git a/deprecated-packages/gatsby-recipes/CONTRIBUTING.md b/deprecated-packages/gatsby-recipes/CONTRIBUTING.md index 59c5363b9ac9c..82fe96be51df9 100644 --- a/deprecated-packages/gatsby-recipes/CONTRIBUTING.md +++ b/deprecated-packages/gatsby-recipes/CONTRIBUTING.md @@ -88,7 +88,7 @@ This example will be used throughout this document as an illustration tool. ## Setting up a development environment -First [follow the instructions on setting up a local Gatsby dev environment](https://www.gatsbyjs.org/contributing/setting-up-your-local-dev-environment/). +First [follow the instructions on setting up a local Gatsby dev environment](https://www.gatsbyjs.com/contributing/setting-up-your-local-dev-environment/). ### Running the unit tests @@ -108,7 +108,7 @@ yarn jest packages/gatsby-recipes --testPathPattern "providers" --watch ### Using gatsby-dev-cli -You can create test recipes that you run in a test site. You’ll need to [use `gatsby-dev-cli` for this.](https://www.gatsbyjs.org/contributing/setting-up-your-local-dev-environment/#gatsby-functional-changes). +You can create test recipes that you run in a test site. You’ll need to [use `gatsby-dev-cli` for this.](https://www.gatsbyjs.com/contributing/setting-up-your-local-dev-environment/#gatsby-functional-changes). One note, as you’ll be testing changes to the Gatsby CLI — instead of running the global gatsby-cli package (i.e. what you’d run by typing `gatsby`, you’ll want to run the version copied over by `gatsby-dev-cli` by running `./node_modules/.bin/gatsby`. diff --git a/deprecated-packages/gatsby-recipes/README.md b/deprecated-packages/gatsby-recipes/README.md index 087cf15bc0cc4..488f49d6675c0 100644 --- a/deprecated-packages/gatsby-recipes/README.md +++ b/deprecated-packages/gatsby-recipes/README.md @@ -13,10 +13,10 @@ Recipes to automate more things. We chose [MDX](https://mdxjs.com/) to allow for a literate programming style of writing recipes which enables us to port our dozens of recipes from -https://www.gatsbyjs.org/docs/recipes/ as well as in the future, entire +https://www.gatsbyjs.com/docs/recipes/ as well as in the future, entire tutorials. -[Read more about Recipes on the launch blog post](https://www.gatsbyjs.org/blog/2020-04-15-announcing-gatsby-recipes/) +[Read more about Recipes on the launch blog post](https://www.gatsbyjs.com/blog/2020-04-15-announcing-gatsby-recipes/) There's an umbrella issue for testing / using Recipes during its incubation stage. Follow the issue for updates! https://github.com/gatsbyjs/gatsby/issues/22991 @@ -285,5 +285,5 @@ a step If you’d like to write a recipe, there are a few great places to get an idea: - Think of a task that took you more time than other tasks in the last Gatsby site you built. Is there a way to automate any part of that task? -- Look at this list of recipes in the Gatsby docs. Many of these can be partially or fully automated through creating a recipe `mdx` file. https://www.gatsbyjs.org/docs/recipes/ +- Look at this list of recipes in the Gatsby docs. Many of these can be partially or fully automated through creating a recipe `mdx` file. https://www.gatsbyjs.com/docs/recipes/ - community members have posted a number of recipes in the [recipes umbrella issue](https://github.com/gatsbyjs/gatsby/issues/22991). You can browse their ideas to find inspiration for new recipes to write. diff --git a/deprecated-packages/gatsby-recipes/recipes/README.md b/deprecated-packages/gatsby-recipes/recipes/README.md index 67792bfed4970..7a026df69355f 100644 --- a/deprecated-packages/gatsby-recipes/recipes/README.md +++ b/deprecated-packages/gatsby-recipes/recipes/README.md @@ -1,6 +1,6 @@ # Gatsby Recipes MDX Source -These are the MDX files for the official Recipes. [Please contribute!](https://www.gatsbyjs.org/contributing/how-to-contribute/) We welcome PRs for new recipes and fixes/improvements to existing recipes. +These are the MDX files for the official Recipes. [Please contribute!](https://www.gatsbyjs.com/contributing/how-to-contribute/) We welcome PRs for new recipes and fixes/improvements to existing recipes. When you add a new recipe, please also add it to the recipes list at https://github.com/gatsbyjs/gatsby/blob/05151c006974b7636b00f0cd608fac89ddaa1c08/packages/gatsby-recipes/src/cli.js#L60 diff --git a/deprecated-packages/gatsby-recipes/recipes/gatsby-image.mdx b/deprecated-packages/gatsby-recipes/recipes/gatsby-image.mdx index fe5e3d136f422..fd9cc1ab5b70e 100644 --- a/deprecated-packages/gatsby-recipes/recipes/gatsby-image.mdx +++ b/deprecated-packages/gatsby-recipes/recipes/gatsby-image.mdx @@ -5,7 +5,7 @@ the necessary NPM packages & Gatsby plugins to enable speedy, optimized images with Gatsby Image in your React code. -Based on https://www.gatsbyjs.org/docs/working-with-images-in-markdown/ +Based on https://www.gatsbyjs.com/docs/working-with-images-in-markdown/ This recipe: diff --git a/deprecated-packages/gatsby-recipes/recipes/gatsby-plugin-layout.mdx b/deprecated-packages/gatsby-recipes/recipes/gatsby-plugin-layout.mdx index 01b570ca33838..6f3d01b81fa33 100644 --- a/deprecated-packages/gatsby-recipes/recipes/gatsby-plugin-layout.mdx +++ b/deprecated-packages/gatsby-recipes/recipes/gatsby-plugin-layout.mdx @@ -1,6 +1,6 @@ # Setup gatsby-plugin-layout -This plugin sets up [gatsby-plugin-layout](https://www.gatsbyjs.org/packages/gatsby-plugin-layout/?=gatsby%20layout), which enables adding components that live above the page components and persist across page changes. +This plugin sets up [gatsby-plugin-layout](https://www.gatsbyjs.com/packages/gatsby-plugin-layout/?=gatsby%20layout), which enables adding components that live above the page components and persist across page changes. This can be helpful for: @@ -35,4 +35,4 @@ Writes out a sample layout component to get started with. --- Read more about the documentation for Gatsby Layout Component here: -https://www.gatsbyjs.org/packages/gatsby-plugin-layout/ +https://www.gatsbyjs.com/packages/gatsby-plugin-layout/ diff --git a/deprecated-packages/gatsby-recipes/recipes/gatsby-plugin-react-helmet.mdx b/deprecated-packages/gatsby-recipes/recipes/gatsby-plugin-react-helmet.mdx index 37cdaad375a57..37866a98e2c0d 100644 --- a/deprecated-packages/gatsby-recipes/recipes/gatsby-plugin-react-helmet.mdx +++ b/deprecated-packages/gatsby-recipes/recipes/gatsby-plugin-react-helmet.mdx @@ -4,7 +4,7 @@ React Helmet is a reusable React component that manages all of your changes to t Helmet takes plain HTML tags and outputs plain HTML tags. -[gatsby-plugin-helmet](https://www.gatsbyjs.org/packages/gatsby-plugin-react-helmet/?=react%20helmet) makes it easy to use React Helmet inside Gatsby projects as it automatically adds title and meta tags to the HTML during SSR. +[gatsby-plugin-helmet](https://www.gatsbyjs.com/packages/gatsby-plugin-react-helmet/?=react%20helmet) makes it easy to use React Helmet inside Gatsby projects as it automatically adds title and meta tags to the HTML during SSR. This recipe: @@ -33,7 +33,7 @@ Writes out an `` component which helps ensure pages have the necessary titl --- Read more about Gatsby React Helmet here: -https://www.gatsbyjs.org/packages/gatsby-plugin-react-helmet +https://www.gatsbyjs.com/packages/gatsby-plugin-react-helmet You can also read about the "SEO" component here: -https://www.gatsbyjs.org/docs/add-seo-component/ +https://www.gatsbyjs.com/docs/add-seo-component/ diff --git a/deprecated-packages/gatsby-recipes/recipes/gatsby-theme-blog-core.mdx b/deprecated-packages/gatsby-recipes/recipes/gatsby-theme-blog-core.mdx index f300d07202c20..60816bb94a0db 100644 --- a/deprecated-packages/gatsby-recipes/recipes/gatsby-theme-blog-core.mdx +++ b/deprecated-packages/gatsby-recipes/recipes/gatsby-theme-blog-core.mdx @@ -1,6 +1,6 @@ # Gatsby Theme Blog Core Starter Recipe -[Gatsby theme blog core](https://www.gatsbyjs.org/packages/gatsby-theme-blog-core/) is a great theme for adding blog functionality to your site. It's designed to handle sourcing your blog data for you so you can style it however you like. +[Gatsby theme blog core](https://www.gatsbyjs.com/packages/gatsby-theme-blog-core/) is a great theme for adding blog functionality to your site. It's designed to handle sourcing your blog data for you so you can style it however you like. This recipe: diff --git a/deprecated-packages/gatsby-recipes/recipes/gatsby-theme-blog.mdx b/deprecated-packages/gatsby-recipes/recipes/gatsby-theme-blog.mdx index e8bd0233e5167..35b32ded45266 100644 --- a/deprecated-packages/gatsby-recipes/recipes/gatsby-theme-blog.mdx +++ b/deprecated-packages/gatsby-recipes/recipes/gatsby-theme-blog.mdx @@ -1,6 +1,6 @@ # Setup Gatsby Theme Blog -[Gatsby theme blog](https://www.gatsbyjs.org/packages/gatsby-theme-blog/) is a great theme for adding blog functionality to your site. +[Gatsby theme blog](https://www.gatsbyjs.com/packages/gatsby-theme-blog/) is a great theme for adding blog functionality to your site. This recipe: diff --git a/deprecated-packages/gatsby-recipes/recipes/gatsby-theme-notes.mdx b/deprecated-packages/gatsby-recipes/recipes/gatsby-theme-notes.mdx index c1e77d942c250..2a92d09e5884d 100644 --- a/deprecated-packages/gatsby-recipes/recipes/gatsby-theme-notes.mdx +++ b/deprecated-packages/gatsby-recipes/recipes/gatsby-theme-notes.mdx @@ -1,6 +1,6 @@ # Gatsby Theme Notes Starter Recipe -[Gatsby theme notes](https://www.gatsbyjs.org/packages/gatsby-theme-notes) is a great theme for adding learning notes to your site. +[Gatsby theme notes](https://www.gatsbyjs.com/packages/gatsby-theme-notes) is a great theme for adding learning notes to your site. This recipe: diff --git a/deprecated-packages/gatsby-recipes/recipes/mdx-images.mdx b/deprecated-packages/gatsby-recipes/recipes/mdx-images.mdx index b631cc6ef69b5..66a6ebea3bd71 100644 --- a/deprecated-packages/gatsby-recipes/recipes/mdx-images.mdx +++ b/deprecated-packages/gatsby-recipes/recipes/mdx-images.mdx @@ -4,7 +4,7 @@ This recipe installs and configures all the necessary NPM packages & Gatsby plugins to enable inline-images in MDX and MD files. -Based on https://www.gatsbyjs.org/docs/working-with-images-in-markdown/ +Based on https://www.gatsbyjs.com/docs/working-with-images-in-markdown/ This recipe: diff --git a/deprecated-packages/gatsby-recipes/recipes/pwa.mdx b/deprecated-packages/gatsby-recipes/recipes/pwa.mdx index f834e879ab6d2..232939ade4d8b 100644 --- a/deprecated-packages/gatsby-recipes/recipes/pwa.mdx +++ b/deprecated-packages/gatsby-recipes/recipes/pwa.mdx @@ -50,5 +50,5 @@ After running this recipe, your site will be a PWA. Refer to the documentation for the manifest & offline plugins if there are any other edits you'd like to make. -- https://www.gatsbyjs.org/packages/gatsby-plugin-manifest -- https://www.gatsbyjs.org/packages/gatsby-plugin-offline +- https://www.gatsbyjs.com/packages/gatsby-plugin-manifest +- https://www.gatsbyjs.com/packages/gatsby-plugin-offline diff --git a/deprecated-packages/gatsby-recipes/src/providers/gatsby/__snapshots__/plugin.test.js.snap b/deprecated-packages/gatsby-recipes/src/providers/gatsby/__snapshots__/plugin.test.js.snap index ec89f1dc620c0..c15fa3faf45a0 100644 --- a/deprecated-packages/gatsby-recipes/src/providers/gatsby/__snapshots__/plugin.test.js.snap +++ b/deprecated-packages/gatsby-recipes/src/providers/gatsby/__snapshots__/plugin.test.js.snap @@ -521,7 +521,7 @@ Object { "currentState": "/** * Configure your Gatsby site with this file. * - * See: https://www.gatsbyjs.org/docs/gatsby-config/ + * See: https://www.gatsbyjs.com/docs/gatsby-config/ */ module.exports = { /* Your site config here */ @@ -557,7 +557,7 @@ module.exports = { "newState": "/** * Configure your Gatsby site with this file. * - * See: https://www.gatsbyjs.org/docs/gatsby-config/ + * See: https://www.gatsbyjs.com/docs/gatsby-config/ */ module.exports = { /* Your site config here */ @@ -593,7 +593,7 @@ Object { "currentState": "/** * Configure your Gatsby site with this file. * - * See: https://www.gatsbyjs.org/docs/gatsby-config/ + * See: https://www.gatsbyjs.com/docs/gatsby-config/ */ module.exports = { /* Your site config here */ @@ -630,7 +630,7 @@ module.exports = { "newState": "/** * Configure your Gatsby site with this file. * - * See: https://www.gatsbyjs.org/docs/gatsby-config/ + * See: https://www.gatsbyjs.com/docs/gatsby-config/ */ module.exports = { /* Your site config here */ diff --git a/deprecated-packages/gatsby-recipes/src/providers/gatsby/fixtures/gatsby-starter-hello-world/gatsby-config.js b/deprecated-packages/gatsby-recipes/src/providers/gatsby/fixtures/gatsby-starter-hello-world/gatsby-config.js index ccf4e9671b419..8975d05ac7798 100644 --- a/deprecated-packages/gatsby-recipes/src/providers/gatsby/fixtures/gatsby-starter-hello-world/gatsby-config.js +++ b/deprecated-packages/gatsby-recipes/src/providers/gatsby/fixtures/gatsby-starter-hello-world/gatsby-config.js @@ -1,7 +1,7 @@ /** * Configure your Gatsby site with this file. * - * See: https://www.gatsbyjs.org/docs/gatsby-config/ + * See: https://www.gatsbyjs.com/docs/gatsby-config/ */ module.exports = { /* Your site config here */ diff --git a/deprecated-packages/gatsby-recipes/src/providers/gatsby/site-metadata.js b/deprecated-packages/gatsby-recipes/src/providers/gatsby/site-metadata.js index 51c72b3fbfa67..a14da88ff6050 100644 --- a/deprecated-packages/gatsby-recipes/src/providers/gatsby/site-metadata.js +++ b/deprecated-packages/gatsby-recipes/src/providers/gatsby/site-metadata.js @@ -65,7 +65,7 @@ const readConfigFile = async root => { src = `/** * Configure your Gatsby site with this file. * - * See: https://www.gatsbyjs.org/docs/gatsby-config/ + * See: https://www.gatsbyjs.com/docs/gatsby-config/ */ module.exports = { diff --git a/docs/contributing/contributor-swag.md b/docs/contributing/contributor-swag.md index 92d76c701509b..e8929f993db8a 100644 --- a/docs/contributing/contributor-swag.md +++ b/docs/contributing/contributor-swag.md @@ -10,18 +10,18 @@ To show our appreciation, _**everyone who contributes to Gatsby is eligible to r ## How to claim your free swag -If you contribute to the Gatsby organization on GitHub, you can claim your swag by [logging into the Gatsby Store](https://store.gatsbyjs.org/) and requesting a discount code. With five or more contributions, you can claim your _**Level 2**_ swag. +If you contribute to the Gatsby organization on GitHub, you can claim your swag by [logging into the Gatsby Store](https://store.gatsbyjs.com/) and requesting a discount code. With five or more contributions, you can claim your _**Level 2**_ swag. If you’ve contributed in other ways, such as giving talks about Gatsby, teaching others to use it, writing Gatsby articles/tutorials, participating in a Gatsby research project, or any other way, please fill out [this short form](https://forms.gle/zBnybrZNjsdpXvDx8) to let us know! ## Details about free swag -- We will send one item from our [swag store](https://store.gatsbyjs.org/) per swag tier +- We will send one item from our [swag store](https://store.gatsbyjs.com/) per swag tier - Tier 1 swag includes most items valued 10 dollars or less - Tier 2 swag includes most items valued 31 dollars or less - Not all items are eligible due to high cost to create the swag. We’ll make it clear which items are not eligible - There’s a limit of one free swag item per swag tier - Shipping is free worldwide -- Additional details can be found in our [swag FAQs](https://github.com/gatsbyjs/store.gatsbyjs.org#frequently-asked-questions) +- Additional details can be found in our [swag FAQs](https://github.com/gatsbyjs/store.gatsbyjs.com#frequently-asked-questions) > **NOTE:** Worldwide free shipping is a pilot program. If shipping costs get out of control, we may need to adjust this policy in the future. diff --git a/docs/docs/conceptual/data-fetching.md b/docs/docs/conceptual/data-fetching.md index c5032eadf87d1..135924b68c70c 100644 --- a/docs/docs/conceptual/data-fetching.md +++ b/docs/docs/conceptual/data-fetching.md @@ -214,7 +214,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][example site] 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 store](https://github.com/gatsbyjs/store.gatsbyjs.com): 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/how-to/adding-common-features/building-a-site-with-authentication.md b/docs/docs/how-to/adding-common-features/building-a-site-with-authentication.md index 74db050f95f94..501f115c9da9f 100644 --- a/docs/docs/how-to/adding-common-features/building-a-site-with-authentication.md +++ b/docs/docs/how-to/adding-common-features/building-a-site-with-authentication.md @@ -75,9 +75,9 @@ More information on build related errors is available in the guide on [debugging ## Real-world example: Gatsby store -The [Gatsby store](https://github.com/gatsbyjs/store.gatsbyjs.org) is a live application built with Gatsby that implements authentication using Auth0. +The [Gatsby store](https://github.com/gatsbyjs/store.gatsbyjs.com) is a live application built with Gatsby that implements authentication using Auth0. -[Util functions](https://github.com/gatsbyjs/store.gatsbyjs.org/blob/master/src/utils/auth.js) in the Gatsby Store repo make use of Auth0's APIs to authenticate users with GitHub, and wrap Auth0's APIs to check that [some of the Auth0 code runs only in the browser](https://github.com/gatsbyjs/store.gatsbyjs.org/blob/master/src/utils/auth.js#L3). +[Util functions](https://github.com/gatsbyjs/store.gatsbyjs.com/blob/master/src/utils/auth.js) in the Gatsby Store repo make use of Auth0's APIs to authenticate users with GitHub, and wrap Auth0's APIs to check that [some of the Auth0 code runs only in the browser](https://github.com/gatsbyjs/store.gatsbyjs.com/blob/master/src/utils/auth.js#L3). In order to protect authenticated content with a private route, a `` is implemented in the `` component that checks whether a user is authenticated or reroutes them to `/login`. diff --git a/docs/docs/how-to/images-and-media/using-gatsby-image.md b/docs/docs/how-to/images-and-media/using-gatsby-image.md index 689018f7df921..65a472eae3af8 100644 --- a/docs/docs/how-to/images-and-media/using-gatsby-image.md +++ b/docs/docs/how-to/images-and-media/using-gatsby-image.md @@ -10,11 +10,11 @@ Using images in Gatsby components and pages requires four steps to take advantag -`gatsby-image` is a React component designed to work seamlessly with Gatsby’s GraphQL queries ([`gatsby-image` plugin README](/plugins/gatsby-image/)). It combines [Gatsby’s native image processing](https://image-processing.gatsbyjs.org/) capabilities with advanced image loading techniques to easily and completely optimize image loading for your sites. `gatsby-image` uses [gatsby-plugin-sharp](/plugins/gatsby-plugin-sharp/) to power its image transformations. +`gatsby-image` is a React component designed to work seamlessly with Gatsby’s GraphQL queries ([`gatsby-image` plugin README](/plugins/gatsby-image/)). It combines [Gatsby’s native image processing](https://image-processing.gatsbyjs.com/) capabilities with advanced image loading techniques to easily and completely optimize image loading for your sites. `gatsby-image` uses [gatsby-plugin-sharp](/plugins/gatsby-plugin-sharp/) to power its image transformations. > _Warning: gatsby-image is **not** a drop-in replacement for ``. It’s optimized for fixed width/height images and images that stretch the full width of a container. Some ways you can use `` won’t work with gatsby-image._ -Here's a [demo site that uses the gatsby-image plugin](https://using-gatsby-image.gatsbyjs.org/) +Here's a [demo site that uses the gatsby-image plugin](https://using-gatsby-image.gatsbyjs.com/) `gatsby-image` includes the tricks you’d expect from a modern image component. It: diff --git a/docs/docs/how-to/routing/client-only-routes-and-user-authentication.md b/docs/docs/how-to/routing/client-only-routes-and-user-authentication.md index 61b47d34695ee..75a93d85d0c21 100644 --- a/docs/docs/how-to/routing/client-only-routes-and-user-authentication.md +++ b/docs/docs/how-to/routing/client-only-routes-and-user-authentication.md @@ -127,4 +127,4 @@ Your server configuration should handle `GET` requests to `/app/*` e.g. `/app/wh - [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.app/) -- [The Gatsby store](https://github.com/gatsbyjs/store.gatsbyjs.org) which also implements an authenticated flow +- [The Gatsby store](https://github.com/gatsbyjs/store.gatsbyjs.com) which also implements an authenticated flow diff --git a/docs/docs/porting-from-create-react-app-to-gatsby.md b/docs/docs/porting-from-create-react-app-to-gatsby.md index b3bf33a4e1cf7..0551aefb6edf7 100644 --- a/docs/docs/porting-from-create-react-app-to-gatsby.md +++ b/docs/docs/porting-from-create-react-app-to-gatsby.md @@ -19,7 +19,7 @@ _Both_ Create React App and Gatsby use React and allow users to build apps more Gatsby enables some useful performance optimizations for you, by default. Route-based code splitting and pre-loading of the _next_ resources make your application lightning fast, without any additional effort! Further still, the following optimizations and techniques are also available to you: - `gatsby-link` uses an [intersection observer to preload linked pages](/blog/2019-04-02-behind-the-scenes-what-makes-gatsby-great/#intersectionobserver) when they appear in the viewport, making them feel like they load _instantly_ -- `gatsby-plugin-image` will create optimized versions of your images in different sizes, loading a smaller, optimized version of an image and replacing it with a higher resolution version when loading has finished. It also uses an intersection observer to cheaply lazy load images. Check out [the demo](https://using-gatsby-image.gatsbyjs.org/) to see for yourself +- `gatsby-plugin-image` will create optimized versions of your images in different sizes, loading a smaller, optimized version of an image and replacing it with a higher resolution version when loading has finished. It also uses an intersection observer to cheaply lazy load images. Check out [the demo](https://using-gatsby-image.gatsbyjs.com/) to see for yourself These features and more work together to make your Gatsby site fast by default. If you'd like a deep dive on these and other performance optimizations, check out [this blog post](/blog/2019-04-02-behind-the-scenes-what-makes-gatsby-great/) diff --git a/docs/docs/reference/built-in-components/gatsby-image.md b/docs/docs/reference/built-in-components/gatsby-image.md index efc9c9f24ef1c..52233585acf84 100644 --- a/docs/docs/reference/built-in-components/gatsby-image.md +++ b/docs/docs/reference/built-in-components/gatsby-image.md @@ -4,11 +4,11 @@ title: Gatsby Image API _This document talks about the deprecated image plugin. Please check out how to work with the new [gatsby-plugin-image](/docs/how-to/images-and-media/using-gatsby-plugin-image)_ -Part of what makes Gatsby sites so fast is its recommended approach to handling images. `gatsby-image` is a React component designed to work seamlessly with Gatsby’s [native image processing](https://image-processing.gatsbyjs.org/) capabilities powered by GraphQL and [gatsby-plugin-sharp](/plugins/gatsby-plugin-sharp/) to easily and completely optimize image loading for your sites. +Part of what makes Gatsby sites so fast is its recommended approach to handling images. `gatsby-image` is a React component designed to work seamlessly with Gatsby’s [native image processing](https://image-processing.gatsbyjs.com/) capabilities powered by GraphQL and [gatsby-plugin-sharp](/plugins/gatsby-plugin-sharp/) to easily and completely optimize image loading for your sites. > _Note: gatsby-image is **not** a drop-in replacement for ``. It’s optimized for responsive fixed width/height images and images that stretch the full-width of a container. There are also other ways to [work with images](/docs/images-and-files/) in Gatsby that don't require GraphQL._ -Demo: https://using-gatsby-image.gatsbyjs.org/ +Demo: https://using-gatsby-image.gatsbyjs.com/ ## Setting up Gatsby Image @@ -310,11 +310,11 @@ GraphQL includes a concept called "query fragments", which are a part of a query #### About `noBase64` -If you don't want to use the [blur-up effect](https://using-gatsby-image.gatsbyjs.org/blur-up/), choose the fragment with `noBase64` at the end. +If you don't want to use the [blur-up effect](https://using-gatsby-image.gatsbyjs.com/blur-up/), choose the fragment with `noBase64` at the end. #### About `tracedSVG` -If you want to use the [traced placeholder SVGs](https://using-gatsby-image.gatsbyjs.org/traced-svg/), choose the fragment with `tracedSVG` at the end. +If you want to use the [traced placeholder SVGs](https://using-gatsby-image.gatsbyjs.com/traced-svg/), choose the fragment with `tracedSVG` at the end. #### About `withWebp` @@ -333,7 +333,7 @@ file(relativePath: { eq: "images/default.jpg" }) { } ``` -For more info on how these options work, check out the Gatsby Image demo: https://using-gatsby-image.gatsbyjs.org/ +For more info on how these options work, check out the Gatsby Image demo: https://using-gatsby-image.gatsbyjs.com/ #### Additional plugin fragments diff --git a/docs/docs/reference/release-notes/migrating-from-v1-to-v2.md b/docs/docs/reference/release-notes/migrating-from-v1-to-v2.md index eab564e6fc6f1..7536aefd25e9c 100644 --- a/docs/docs/reference/release-notes/migrating-from-v1-to-v2.md +++ b/docs/docs/reference/release-notes/migrating-from-v1-to-v2.md @@ -2,7 +2,7 @@ title: Migrating from v1 to v2 --- -Looking for the v1 docs? [Find them here](https://v1.gatsbyjs.org/). +Looking for the v1 docs? [Find them here](https://v1.gatsbyjs.com/). > This document is a work in progress. Have you run into something that's not covered here? [Add your changes on GitHub](https://github.com/gatsbyjs/gatsby/edit/master/docs/docs/reference/release-notes/migrating-from-v1-to-v2.md)! @@ -509,7 +509,7 @@ export default function Routes() { ``` Here's a more complex example of migrating a `` component (used -in store.gatsbyjs.org) from React Router to @reach/router. +in store.gatsbyjs.com) from React Router to @reach/router. ```diff import * as React from 'react'; @@ -549,7 +549,7 @@ in store.gatsbyjs.org) from React Router to @reach/router. Here are links to diffs for three sites with client routes upgraded to @reach/router: -- [store.gatsbyjs.org](https://github.com/gatsbyjs/store.gatsbyjs.org/pull/111) +- [store.gatsbyjs.com](https://github.com/gatsbyjs/store.gatsbyjs.com/pull/111) - [client-only-routes](https://github.com/gatsbyjs/gatsby/pull/6918/files#diff-69757e54875e28ef83eb8efe45a33fdf) - [simple-auth](https://github.com/gatsbyjs/gatsby/pull/6918/files#diff-53ac112a4b2ec760b26a86c953df2339) diff --git a/docs/docs/reference/release-notes/v1-release-notes.md b/docs/docs/reference/release-notes/v1-release-notes.md index b5cc085be62cb..4849b77810d6a 100644 --- a/docs/docs/reference/release-notes/v1-release-notes.md +++ b/docs/docs/reference/release-notes/v1-release-notes.md @@ -4,6 +4,6 @@ title: v1 Release Notes Check out the following useful links for Gatsby version 1: -- [v1 documentation](https://v1.gatsbyjs.org/) +- [v1 documentation](https://v1.gatsbyjs.com/) - [v1 changelog](https://github.com/gatsbyjs/gatsby/blob/master/packages/gatsby/CHANGELOG.md#100---2017-07-06) - [v1 release announcement](/blog/gatsby-v1/) diff --git a/docs/docs/themes.md b/docs/docs/themes.md index 9dad8de43f229..8df4b2414095e 100644 --- a/docs/docs/themes.md +++ b/docs/docs/themes.md @@ -12,7 +12,7 @@ This means that the configuration and functionality isn’t directly written int ## Browse themes - [Themes in Plugin Library](/plugins/?=gatsby-theme) -- [Theme Jam Showcase](https://themejam.gatsbyjs.org/showcase) +- [Theme Jam Showcase](https://themejam.gatsbyjs.com/showcase) ## Other resources diff --git a/docs/tutorial/authentication-tutorial.md b/docs/tutorial/authentication-tutorial.md index 40678bca892ff..1d629f1f1f47c 100644 --- a/docs/tutorial/authentication-tutorial.md +++ b/docs/tutorial/authentication-tutorial.md @@ -415,7 +415,7 @@ If you want to learn more about using production-ready auth solutions, these lin - [Gatsby repo simple auth example](https://github.com/gatsbyjs/gatsby/tree/master/examples/simple-auth) - [A Gatsby email _application_](https://github.com/DSchau/gatsby-mail), using React Context API to handle authentication -- [The Gatsby store for swag and other Gatsby goodies](https://github.com/gatsbyjs/store.gatsbyjs.org) +- [The Gatsby store for swag and other Gatsby goodies](https://github.com/gatsbyjs/store.gatsbyjs.com) - [Building a blog with Gatsby, React and Webtask.io!](https://auth0.com/blog/building-a-blog-with-gatsby-react-and-webtask/) - [JAMstack PWA — Let’s Build a Polling App. with Gatsby.js, Firebase, and Styled-components Pt. 2](https://medium.com/@UnicornAgency/jamstack-pwa-lets-build-a-polling-app-with-gatsby-js-firebase-and-styled-components-pt-2-9044534ea6bc) - [JAMstack Hackathon Starter - Authenticated Gatsby app starter with Netlify Identity](/starters/sw-yx/jamstack-hackathon-starter) diff --git a/docs/tutorial/wordpress-image-tutorial.md b/docs/tutorial/wordpress-image-tutorial.md index 08b393760db3d..6491cd0786884 100644 --- a/docs/tutorial/wordpress-image-tutorial.md +++ b/docs/tutorial/wordpress-image-tutorial.md @@ -10,13 +10,13 @@ Please follow the tutorial on [creating a new site with `gatsby-source-wordpress ## What this tutorial covers: -In this tutorial, you will install the several image plugins and components in order to pull image data from a WordPress account into your Gatsby site and render that data. This [Gatsby + WordPress demo site](https://using-wordpress.gatsbyjs.org/) shows you a sample of what you’re going to be building in this tutorial, although in this tutorial you’ll just focus on adding images. +In this tutorial, you will install the several image plugins and components in order to pull image data from a WordPress account into your Gatsby site and render that data. This [Gatsby + WordPress demo site](https://using-wordpress.gatsbyjs.com/) shows you a sample of what you’re going to be building in this tutorial, although in this tutorial you’ll just focus on adding images. ## Why go through this tutorial? Images are one of the most beautiful and striking ways to communicate to people, and are a key part of creating an effective and positive user experience; at the same time, high quality images can load slowly and cause text boxes to jump around, both of which make it difficult for people to be patient with visiting your website. -The Gatsby Way™ of creating images describes a set of best practices that help you optimize performance and responsiveness of images so that you can get the benefits of awesome images that don't slow down your site. This [Gatsbygram site](https://gatsbygram.gatsbyjs.org/) (an Instagram feed fed through Gatsby) shows off the SVG image tracing effect. Here’s an [image processing demo site](https://image-processing.gatsbyjs.org/) exploring how to have fun with images in your Gatsby site. +The Gatsby Way™ of creating images describes a set of best practices that help you optimize performance and responsiveness of images so that you can get the benefits of awesome images that don't slow down your site. This [Gatsbygram site](https://gatsbygram.gatsbyjs.com/) (an Instagram feed fed through Gatsby) shows off the SVG image tracing effect. Here’s an [image processing demo site](https://image-processing.gatsbyjs.com/) exploring how to have fun with images in your Gatsby site. ## Installing the `gatsby-source-wordpress` plugin diff --git a/e2e-tests/contentful/README.md b/e2e-tests/contentful/README.md index 3e8ac870edc7f..7c89bb0360b88 100644 --- a/e2e-tests/contentful/README.md +++ b/e2e-tests/contentful/README.md @@ -2,7 +2,7 @@ The default Gatsby starter. -For an overview of the project structure please refer to the [Gatsby documentation - Building with Components](https://www.gatsbyjs.org/docs/building-with-components/). +For an overview of the project structure please refer to the [Gatsby documentation - Building with Components](https://www.gatsbyjs.com/docs/building-with-components/). ## Install diff --git a/e2e-tests/development-runtime/README.md b/e2e-tests/development-runtime/README.md index 926aa1e1eb88c..b6515cbbdd326 100644 --- a/e2e-tests/development-runtime/README.md +++ b/e2e-tests/development-runtime/README.md @@ -9,7 +9,7 @@ Kick off your project with this default boilerplate ([live demo](https://gatsby-starter-default-demo.netlify.app/)). This barebones starter ships with the main Gatsby configuration files you might need. -_Have another more specific idea? You may want to check out our vibrant collection of [official and community-created starters](https://www.gatsbyjs.org/docs/gatsby-starters/)._ +_Have another more specific idea? You may want to check out our vibrant collection of [official and community-created starters](https://www.gatsbyjs.com/docs/gatsby-starters/)._ ## 🚀 Quick start @@ -35,7 +35,7 @@ _Have another more specific idea? You may want to check out our vibrant collecti Your site is now running at `http://localhost:8000`! - \_Note: You'll also see a second link: `http://localhost:8000/___graphql`. This is a tool you can use to experiment with querying your data. Learn more about using this tool in the [Gatsby tutorial](https://www.gatsbyjs.org/tutorial/part-5/#introducing-graphiql).\_ + \_Note: You'll also see a second link: `http://localhost:8000/___graphql`. This is a tool you can use to experiment with querying your data. Learn more about using this tool in the [Gatsby tutorial](https://www.gatsbyjs.com/tutorial/part-5/#introducing-graphiql).\_ Open the `my-default-starter` directory in your code editor of choice and edit `src/pages/index.js`. Save your changes and the browser will update in real time! @@ -66,13 +66,13 @@ A quick look at the top-level files and directories you'll see in a Gatsby proje 4. **`.prettierrc`**: This is a configuration file for [Prettier](https://prettier.io/). Prettier is a tool to help keep the formatting of your code consistent. -5. **`gatsby-browser.js`**: This file is where Gatsby expects to find any usage of the [Gatsby browser APIs](https://www.gatsbyjs.org/docs/browser-apis/) (if any). These allow customization/extension of default Gatsby settings affecting the browser. +5. **`gatsby-browser.js`**: This file is where Gatsby expects to find any usage of the [Gatsby browser APIs](https://www.gatsbyjs.com/docs/browser-apis/) (if any). These allow customization/extension of default Gatsby settings affecting the browser. -6. **`gatsby-config.js`**: This is the main configuration file for a Gatsby site. This is where you can specify information about your site (metadata) like the site title and description, which Gatsby plugins you’d like to include, etc. (Check out the [config docs](https://www.gatsbyjs.org/docs/gatsby-config/) for more detail). +6. **`gatsby-config.js`**: This is the main configuration file for a Gatsby site. This is where you can specify information about your site (metadata) like the site title and description, which Gatsby plugins you’d like to include, etc. (Check out the [config docs](https://www.gatsbyjs.com/docs/gatsby-config/) for more detail). -7. **`gatsby-node.js`**: This file is where Gatsby expects to find any usage of the [Gatsby Node APIs](https://www.gatsbyjs.org/docs/node-apis/) (if any). These allow customization/extension of default Gatsby settings affecting pieces of the site build process. +7. **`gatsby-node.js`**: This file is where Gatsby expects to find any usage of the [Gatsby Node APIs](https://www.gatsbyjs.com/docs/node-apis/) (if any). These allow customization/extension of default Gatsby settings affecting pieces of the site build process. -8. **`gatsby-ssr.js`**: This file is where Gatsby expects to find any usage of the [Gatsby server-side rendering APIs](https://www.gatsbyjs.org/docs/ssr-apis/) (if any). These allow customization of default Gatsby settings affecting server-side rendering. +8. **`gatsby-ssr.js`**: This file is where Gatsby expects to find any usage of the [Gatsby server-side rendering APIs](https://www.gatsbyjs.com/docs/ssr-apis/) (if any). These allow customization of default Gatsby settings affecting server-side rendering. 9. **`LICENSE`**: Gatsby is licensed under the MIT license. @@ -86,11 +86,11 @@ A quick look at the top-level files and directories you'll see in a Gatsby proje ## 🎓 Learning Gatsby -Looking for more guidance? Full documentation for Gatsby lives [on the website](https://www.gatsbyjs.org/). Here are some places to start: +Looking for more guidance? Full documentation for Gatsby lives [on the website](https://www.gatsbyjs.com/). Here are some places to start: -- **For most developers, we recommend starting with our [in-depth tutorial for creating a site with Gatsby](https://www.gatsbyjs.org/tutorial/).** It starts with zero assumptions about your level of ability and walks through every step of the process. +- **For most developers, we recommend starting with our [in-depth tutorial for creating a site with Gatsby](https://www.gatsbyjs.com/tutorial/).** It starts with zero assumptions about your level of ability and walks through every step of the process. -- **To dive straight into code samples, head [to our documentation](https://www.gatsbyjs.org/docs/).** In particular, check out the _Guides_, _API Reference_, and _Advanced Tutorials_ sections in the sidebar. +- **To dive straight into code samples, head [to our documentation](https://www.gatsbyjs.com/docs/).** In particular, check out the _Guides_, _API Reference_, and _Advanced Tutorials_ sections in the sidebar. ## 💫 Deploy diff --git a/e2e-tests/development-runtime/gatsby-ssr.js b/e2e-tests/development-runtime/gatsby-ssr.js index b17b8fc19d659..01d83255f4f2c 100644 --- a/e2e-tests/development-runtime/gatsby-ssr.js +++ b/e2e-tests/development-runtime/gatsby-ssr.js @@ -1,7 +1,7 @@ /** * Implement Gatsby's SSR (Server Side Rendering) APIs in this file. * - * See: https://www.gatsbyjs.org/docs/ssr-apis/ + * See: https://www.gatsbyjs.com/docs/ssr-apis/ */ // You can delete this file if you're not using it diff --git a/e2e-tests/gatsby-image/README.md b/e2e-tests/gatsby-image/README.md index 3e8ac870edc7f..7c89bb0360b88 100644 --- a/e2e-tests/gatsby-image/README.md +++ b/e2e-tests/gatsby-image/README.md @@ -2,7 +2,7 @@ The default Gatsby starter. -For an overview of the project structure please refer to the [Gatsby documentation - Building with Components](https://www.gatsbyjs.org/docs/building-with-components/). +For an overview of the project structure please refer to the [Gatsby documentation - Building with Components](https://www.gatsbyjs.com/docs/building-with-components/). ## Install diff --git a/e2e-tests/gatsby-image/gatsby-browser.js b/e2e-tests/gatsby-image/gatsby-browser.js index b1e5c316b7f94..ff807f19ef7cc 100644 --- a/e2e-tests/gatsby-image/gatsby-browser.js +++ b/e2e-tests/gatsby-image/gatsby-browser.js @@ -1,7 +1,7 @@ /** * Implement Gatsby's Browser APIs in this file. * - * See: https://www.gatsbyjs.org/docs/browser-apis/ + * See: https://www.gatsbyjs.com/docs/browser-apis/ */ // You can delete this file if you're not using it diff --git a/e2e-tests/gatsby-image/gatsby-node.js b/e2e-tests/gatsby-image/gatsby-node.js index 2f4266513eb66..6d4a90e7a0555 100644 --- a/e2e-tests/gatsby-image/gatsby-node.js +++ b/e2e-tests/gatsby-image/gatsby-node.js @@ -1,7 +1,7 @@ /** * Implement Gatsby's Node APIs in this file. * - * See: https://www.gatsbyjs.org/docs/node-apis/ + * See: https://www.gatsbyjs.com/docs/node-apis/ */ // You can delete this file if you're not using it diff --git a/e2e-tests/gatsby-image/gatsby-ssr.js b/e2e-tests/gatsby-image/gatsby-ssr.js index b17b8fc19d659..01d83255f4f2c 100644 --- a/e2e-tests/gatsby-image/gatsby-ssr.js +++ b/e2e-tests/gatsby-image/gatsby-ssr.js @@ -1,7 +1,7 @@ /** * Implement Gatsby's SSR (Server Side Rendering) APIs in this file. * - * See: https://www.gatsbyjs.org/docs/ssr-apis/ + * See: https://www.gatsbyjs.com/docs/ssr-apis/ */ // You can delete this file if you're not using it diff --git a/e2e-tests/gatsby-static-image/README.md b/e2e-tests/gatsby-static-image/README.md index 3e8ac870edc7f..7c89bb0360b88 100644 --- a/e2e-tests/gatsby-static-image/README.md +++ b/e2e-tests/gatsby-static-image/README.md @@ -2,7 +2,7 @@ The default Gatsby starter. -For an overview of the project structure please refer to the [Gatsby documentation - Building with Components](https://www.gatsbyjs.org/docs/building-with-components/). +For an overview of the project structure please refer to the [Gatsby documentation - Building with Components](https://www.gatsbyjs.com/docs/building-with-components/). ## Install diff --git a/e2e-tests/path-prefix/README.md b/e2e-tests/path-prefix/README.md index 3e8ac870edc7f..7c89bb0360b88 100644 --- a/e2e-tests/path-prefix/README.md +++ b/e2e-tests/path-prefix/README.md @@ -2,7 +2,7 @@ The default Gatsby starter. -For an overview of the project structure please refer to the [Gatsby documentation - Building with Components](https://www.gatsbyjs.org/docs/building-with-components/). +For an overview of the project structure please refer to the [Gatsby documentation - Building with Components](https://www.gatsbyjs.com/docs/building-with-components/). ## Install diff --git a/e2e-tests/path-prefix/gatsby-browser.js b/e2e-tests/path-prefix/gatsby-browser.js index b1e5c316b7f94..ff807f19ef7cc 100644 --- a/e2e-tests/path-prefix/gatsby-browser.js +++ b/e2e-tests/path-prefix/gatsby-browser.js @@ -1,7 +1,7 @@ /** * Implement Gatsby's Browser APIs in this file. * - * See: https://www.gatsbyjs.org/docs/browser-apis/ + * See: https://www.gatsbyjs.com/docs/browser-apis/ */ // You can delete this file if you're not using it diff --git a/e2e-tests/path-prefix/gatsby-node.js b/e2e-tests/path-prefix/gatsby-node.js index 2f4266513eb66..6d4a90e7a0555 100644 --- a/e2e-tests/path-prefix/gatsby-node.js +++ b/e2e-tests/path-prefix/gatsby-node.js @@ -1,7 +1,7 @@ /** * Implement Gatsby's Node APIs in this file. * - * See: https://www.gatsbyjs.org/docs/node-apis/ + * See: https://www.gatsbyjs.com/docs/node-apis/ */ // You can delete this file if you're not using it diff --git a/e2e-tests/path-prefix/gatsby-ssr.js b/e2e-tests/path-prefix/gatsby-ssr.js index b17b8fc19d659..01d83255f4f2c 100644 --- a/e2e-tests/path-prefix/gatsby-ssr.js +++ b/e2e-tests/path-prefix/gatsby-ssr.js @@ -1,7 +1,7 @@ /** * Implement Gatsby's SSR (Server Side Rendering) APIs in this file. * - * See: https://www.gatsbyjs.org/docs/ssr-apis/ + * See: https://www.gatsbyjs.com/docs/ssr-apis/ */ // You can delete this file if you're not using it diff --git a/e2e-tests/production-runtime/README.md b/e2e-tests/production-runtime/README.md index 3e8ac870edc7f..7c89bb0360b88 100644 --- a/e2e-tests/production-runtime/README.md +++ b/e2e-tests/production-runtime/README.md @@ -2,7 +2,7 @@ The default Gatsby starter. -For an overview of the project structure please refer to the [Gatsby documentation - Building with Components](https://www.gatsbyjs.org/docs/building-with-components/). +For an overview of the project structure please refer to the [Gatsby documentation - Building with Components](https://www.gatsbyjs.com/docs/building-with-components/). ## Install diff --git a/examples/gatsbygram/README.md b/examples/gatsbygram/README.md index f7a37997a9234..486d09571d56c 100644 --- a/examples/gatsbygram/README.md +++ b/examples/gatsbygram/README.md @@ -1,6 +1,6 @@ # Gatsbygram -https://gatsbygram.gatsbyjs.org/ +https://gatsbygram.gatsbyjs.com/ Built with Gatsby 2.0 as a demo of Gatsby's new built-in image processing capabilities. diff --git a/examples/image-processing/README.md b/examples/image-processing/README.md index a65b7f1c9f28e..36a84704cd93c 100644 --- a/examples/image-processing/README.md +++ b/examples/image-processing/README.md @@ -1,6 +1,6 @@ # Image Processing -https://image-processing.gatsbyjs.org +https://image-processing.gatsbyjs.com Example site that demonstrates how to use [gatsby-plugin-sharp][1]. diff --git a/examples/no-trailing-slashes/README.md b/examples/no-trailing-slashes/README.md index 0708bfbac5e1f..41a7d0879d4f9 100644 --- a/examples/no-trailing-slashes/README.md +++ b/examples/no-trailing-slashes/README.md @@ -1,5 +1,5 @@ # No trailing slashes -https://no-trailing-slashes.gatsbyjs.org +https://no-trailing-slashes.gatsbyjs.com Gatsby example site that shows how to remove trailing slashes from urls. diff --git a/examples/using-asciidoc/README.md b/examples/using-asciidoc/README.md index bc4e81a8f039d..8986d37ae6de1 100644 --- a/examples/using-asciidoc/README.md +++ b/examples/using-asciidoc/README.md @@ -1,6 +1,6 @@ # Using AsciiDoc -https://using-asciidoc.gatsbyjs.org +https://using-asciidoc.gatsbyjs.com Example site that demonstrates how to build a Gatsby site pulling in data from [asciidoc](http://asciidoc.org/)-files. diff --git a/examples/using-css-modules/README.md b/examples/using-css-modules/README.md index 92eac66c15f26..ee6bf817301b2 100644 --- a/examples/using-css-modules/README.md +++ b/examples/using-css-modules/README.md @@ -1,6 +1,6 @@ # using-css-modules -https://using-css-modules.gatsbyjs.org +https://using-css-modules.gatsbyjs.com Demonstrates using css modules in Gatsby with normal (Postcss) css and sass/scss. diff --git a/examples/using-drupal/README.md b/examples/using-drupal/README.md index adeecf6155630..079b3fa61d9ba 100644 --- a/examples/using-drupal/README.md +++ b/examples/using-drupal/README.md @@ -1,6 +1,6 @@ # Using Drupal -https://using-drupal.gatsbyjs.org +https://using-drupal.gatsbyjs.com Example site that demonstrates how to build Gatsby sites that pull data from the [Drupal CMS](https://www.drupal.org/). diff --git a/examples/using-emotion/README.md b/examples/using-emotion/README.md index b4d63386663f8..fe7f46475085b 100644 --- a/examples/using-emotion/README.md +++ b/examples/using-emotion/README.md @@ -1,6 +1,6 @@ # using-emotion -https://using-emotion.gatsbyjs.org +https://using-emotion.gatsbyjs.com Example site that demonstrates how to build Gatsby sites with [emotion](https://github.com/emotion-js/emotion). diff --git a/examples/using-gatsby-image/README.md b/examples/using-gatsby-image/README.md index ce03dc79e5e06..b922d7bb5af20 100644 --- a/examples/using-gatsby-image/README.md +++ b/examples/using-gatsby-image/README.md @@ -1,6 +1,6 @@ # Using Gatsby Image -https://using-gatsby-image.gatsbyjs.org +https://using-gatsby-image.gatsbyjs.com Gatsby example site that shows how to use [gatsby-plugin-image](https://github.com/gatsbyjs/gatsby/tree/master/packages/gatsby-image). diff --git a/examples/using-glamor/README.md b/examples/using-glamor/README.md index e0f2d00a39319..ff95982d008bd 100644 --- a/examples/using-glamor/README.md +++ b/examples/using-glamor/README.md @@ -1,6 +1,6 @@ # Using Glamor -https://using-glamor.gatsbyjs.org +https://using-glamor.gatsbyjs.com Example site that demonstrates how to build Gatsby sites using the [Glamor](https://github.com/threepointone/glamor) css-in-js library. diff --git a/examples/using-hjson/README.md b/examples/using-hjson/README.md index dca6b4958dab4..e2009467727eb 100644 --- a/examples/using-hjson/README.md +++ b/examples/using-hjson/README.md @@ -1,5 +1,5 @@ # using-hjson -https://using-hjson.gatsbyjs.org +https://using-hjson.gatsbyjs.com Gatsby example site demonstrating how to use [HJson](https://hjson.org) diff --git a/examples/using-jss/README.md b/examples/using-jss/README.md index 1609e738db31c..d0dfb9b95ea8a 100644 --- a/examples/using-jss/README.md +++ b/examples/using-jss/README.md @@ -1,6 +1,6 @@ # Using JSS -https://using-jss.gatsbyjs.org +https://using-jss.gatsbyjs.com Example site that demonstrates how to build Gatsby sites with [JSS](http://cssinjs.org/). diff --git a/examples/using-medium/README.md b/examples/using-medium/README.md index ea77384323866..e3c5984e20ee6 100644 --- a/examples/using-medium/README.md +++ b/examples/using-medium/README.md @@ -1,6 +1,6 @@ # Using Medium -https://using-medium.gatsbyjs.org +https://using-medium.gatsbyjs.com Gatsby example site that shows how to use the [gatsby-source-medium](https://github.com/gatsbyjs/gatsby/tree/master/packages/gatsby-source-medium) diff --git a/examples/using-mongodb/README.md b/examples/using-mongodb/README.md index 9f4a55771d315..3f8a41df7b2c2 100644 --- a/examples/using-mongodb/README.md +++ b/examples/using-mongodb/README.md @@ -1,5 +1,5 @@ # using-mongodb -https://using-mongodb.gatsbyjs.org +https://using-mongodb.gatsbyjs.com In this example site we will use the gatsby-source-mongodb plugin. diff --git a/examples/using-redux/README.md b/examples/using-redux/README.md index e0073f5d6570d..5b9c8103a49c5 100644 --- a/examples/using-redux/README.md +++ b/examples/using-redux/README.md @@ -1,6 +1,6 @@ # Redux -https://using-redux.gatsbyjs.org/ +https://using-redux.gatsbyjs.com/ Gatsby example site that shows use of redux. diff --git a/examples/using-remark/README.md b/examples/using-remark/README.md index 5f345f5a21dcb..dbf8739804881 100644 --- a/examples/using-remark/README.md +++ b/examples/using-remark/README.md @@ -1,6 +1,6 @@ # Using remark -https://using-remark.gatsbyjs.org +https://using-remark.gatsbyjs.com Example site that demonstrates how to use [gatsby-transformer-remark][1] and its various plugins. It uses [Typography.js][2] and self-hosted fonts via the diff --git a/examples/using-remark/src/pages/2017-03-21---copy-linked-files-intercepting-local-links/index.md b/examples/using-remark/src/pages/2017-03-21---copy-linked-files-intercepting-local-links/index.md index 9de0f74403d4d..548b1ee35fffa 100644 --- a/examples/using-remark/src/pages/2017-03-21---copy-linked-files-intercepting-local-links/index.md +++ b/examples/using-remark/src/pages/2017-03-21---copy-linked-files-intercepting-local-links/index.md @@ -32,7 +32,7 @@ Let's try linking to the "[Code and Syntax Highlighting with PrismJS](/code-and-syntax-highlighting/)" article using a relative path. -Also, let's link to "[Rendering math equations with KaTeX](https://using-remark.gatsbyjs.org/katex/)" article using an absolute path. +Also, let's link to "[Rendering math equations with KaTeX](https://using-remark.gatsbyjs.com/katex/)" article using an absolute path. And this [link will be excluded](/excluded-link). diff --git a/examples/using-sass/README.md b/examples/using-sass/README.md index e9f2c322c9a33..16c9789661677 100644 --- a/examples/using-sass/README.md +++ b/examples/using-sass/README.md @@ -1,6 +1,6 @@ # Using gatsby-plugin-sass -https://using-sass.gatsbyjs.org +https://using-sass.gatsbyjs.com Example site that demonstrates how to build Gatsby sites using the Gatsby plugin `gatsby-plugin-sass` which sets up webpack to run Sass/Scss code through the diff --git a/examples/using-styled-components/README.md b/examples/using-styled-components/README.md index b07601ebd5ad6..02288319851bb 100644 --- a/examples/using-styled-components/README.md +++ b/examples/using-styled-components/README.md @@ -1,6 +1,6 @@ # Using Styled Components -https://using-styled-components.gatsbyjs.org +https://using-styled-components.gatsbyjs.com Example site that demonstrates how to build Gatsby sites with [Styled Components](https://styled-components.com/). diff --git a/examples/using-styled-jsx/README.md b/examples/using-styled-jsx/README.md index bca3f4c64edfc..37d0ff7beeb3e 100644 --- a/examples/using-styled-jsx/README.md +++ b/examples/using-styled-jsx/README.md @@ -1,6 +1,6 @@ # using-styled-jsx -https://using-styled-jsx.gatsbyjs.org +https://using-styled-jsx.gatsbyjs.com Demonstrates using [styled-jsx](https://github.com/vercel/styled-jsx) with the Gatsby plugin diff --git a/examples/using-stylus/README.md b/examples/using-stylus/README.md index d22f44a64c3c3..98f45d5941bd7 100644 --- a/examples/using-stylus/README.md +++ b/examples/using-stylus/README.md @@ -1,6 +1,6 @@ # Using gatsby-plugin-stylus -https://using-stylus.gatsbyjs.org +https://using-stylus.gatsbyjs.com Example site that demonstrates how to build Gatsby sites using the Gatsby plugin `gatsby-plugin-stylus` which sets up webpack to run [Stylus][] code. diff --git a/examples/using-wordpress-with-acf/README.md b/examples/using-wordpress-with-acf/README.md index 5d45a88ca53af..22f0c4c231fe3 100644 --- a/examples/using-wordpress-with-acf/README.md +++ b/examples/using-wordpress-with-acf/README.md @@ -1,6 +1,6 @@ # Using WordPress With Advanced Custom Fields (ACF) -https://using-wordpress.gatsbyjs.org/ +https://using-wordpress.gatsbyjs.com/ Example site that extends the [using-wordpress](examples/using-wordpress/) example and demonstrates how to build Gatsby sites that pull data from the [WordPress CMS API](https://www.wordpress.com/) using Advanced Custom Fields. diff --git a/integration-tests/gatsby-pipeline/src/components/layout.js b/integration-tests/gatsby-pipeline/src/components/layout.js index b18838351684a..04c763861029b 100644 --- a/integration-tests/gatsby-pipeline/src/components/layout.js +++ b/integration-tests/gatsby-pipeline/src/components/layout.js @@ -31,7 +31,7 @@ const Layout = ({ children }) => (
© {new Date().getFullYear()}, Built with {` `} - Gatsby + Gatsby
diff --git a/integration-tests/structured-logging/plugins/structured-plugin-errors/gatsby-node.js b/integration-tests/structured-logging/plugins/structured-plugin-errors/gatsby-node.js index 8edb2b4d76438..a3cc2c3482759 100644 --- a/integration-tests/structured-logging/plugins/structured-plugin-errors/gatsby-node.js +++ b/integration-tests/structured-logging/plugins/structured-plugin-errors/gatsby-node.js @@ -4,7 +4,7 @@ exports.onPreInit = ({ reporter }) => { text: context => `Error text is ${context && context.someProp}`, level: "ERROR", category: "SYSTEM", - docsUrl: `https://www.gatsbyjs.org/docs/gatsby-cli/#new`, + docsUrl: `https://www.gatsbyjs.com/docs/gatsby-cli/#new`, }, "12345": { text: context => `Error text is ${context && context.someProp}`, diff --git a/packages/babel-preset-gatsby/README.md b/packages/babel-preset-gatsby/README.md index 093d9d10d6d93..67adc55ffb5a2 100644 --- a/packages/babel-preset-gatsby/README.md +++ b/packages/babel-preset-gatsby/README.md @@ -2,7 +2,7 @@ Gatsby uses the phenomenal project [Babel](https://babeljs.io/) to enable support for writing modern JavaScript — while still supporting older browsers. This package contains the default Babel setup for all Gatsby projects. -For more information on how to customize the Babel configuration of your Gatsby site, check out [our documentation](https://www.gatsbyjs.org/docs/babel/). +For more information on how to customize the Babel configuration of your Gatsby site, check out [our documentation](https://www.gatsbyjs.com/docs/babel/). ## Packages @@ -37,4 +37,4 @@ npm install --dev babel-preset-gatsby `{ [string]: number | string }`, defaults to `{ "browsers": ["last 4 versions", "safari >= 7", "ie >= 9"] }` in production and `{ "browsers": ["last 2 versions", "not ie <= 11", "not android 4.4.3"] }` in development when targeting the browser and `{ "node": 6 }` in production and `{ "node": "current" }` in development when targeting Node.js. -Use this option to configure [custom target browsers](https://www.gatsbyjs.org/docs/babel/). +Use this option to configure [custom target browsers](https://www.gatsbyjs.com/docs/babel/). diff --git a/packages/gatsby-cli/README.md b/packages/gatsby-cli/README.md index 0620689989386..e525787dbb2a7 100644 --- a/packages/gatsby-cli/README.md +++ b/packages/gatsby-cli/README.md @@ -3,11 +3,11 @@ The Gatsby command line interface (CLI). It is used to perform common functionality, such as creating a Gatsby application based on a starter, spinning up a hot-reloading local development server, and more! Lets you create new Gatsby apps using -[Gatsby starters](https://www.gatsbyjs.org/docs/gatsby-starters/). It also lets you run commands on sites. The tool runs code from the `gatsby` package installed locally. +[Gatsby starters](https://www.gatsbyjs.com/docs/gatsby-starters/). It also lets you run commands on sites. The tool runs code from the `gatsby` package installed locally. The Gatsby CLI (`gatsby-cli`) is packaged as an executable that can be used globally. The Gatsby CLI is available via [npm](https://www.npmjs.com/) and is installed globally by running `npm install -g gatsby-cli`. -You can also use the `package.json` script variant of these commands, typically exposed _for you_ with most [starters](https://www.gatsbyjs.org/docs/starters/). For example, if we want to make the [`gatsby develop`](#develop) command available in our application, we would open up `package.json` and add a script like so: +You can also use the `package.json` script variant of these commands, typically exposed _for you_ with most [starters](https://www.gatsbyjs.com/docs/starters/). For example, if we want to make the [`gatsby develop`](#develop) command available in our application, we would open up `package.json` and add a script like so: ```json:title=package.json { @@ -39,7 +39,7 @@ gatsby new [ []] | Argument | Description | | ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | site-name | Your Gatsby site name, which is also used to create the project directory. | -| starter-url | A Gatsby starter URL or local file path. Defaults to [gatsby-starter-default](https://github.com/gatsbyjs/gatsby-starter-default); see the [Gatsby starters](https://www.gatsbyjs.org/docs/gatsby-starters/) docs for more information. | +| starter-url | A Gatsby starter URL or local file path. Defaults to [gatsby-starter-default](https://github.com/gatsbyjs/gatsby-starter-default); see the [Gatsby starters](https://www.gatsbyjs.com/docs/gatsby-starters/) docs for more information. | > Note: The `site-name` should only consist of letters and numbers. If you specify a `.`, `./` or a `` in the name, `gatsby new` will throw an error. @@ -51,7 +51,7 @@ gatsby new [ []] gatsby new my-awesome-site ``` -- Create a Gatsby site named `my-awesome-blog-site`, using [gatsby-starter-blog](https://www.gatsbyjs.org/starters/gatsbyjs/gatsby-starter-blog/): +- Create a Gatsby site named `my-awesome-blog-site`, using [gatsby-starter-blog](https://www.gatsbyjs.com/starters/gatsbyjs/gatsby-starter-blog/): ```shell gatsby new my-awesome-blog-site https://github.com/gatsbyjs/gatsby-starter-blog @@ -69,7 +69,7 @@ gatsby new (Use a different starter) ``` -See the [Gatsby starters docs](https://www.gatsbyjs.org/docs/gatsby-starters/) for more details. +See the [Gatsby starters docs](https://www.gatsbyjs.com/docs/gatsby-starters/) for more details. ### `develop` @@ -85,7 +85,7 @@ development server. | `-o`, `--open` | Open the site in your (default) browser for you | | | `-S`, `--https` | Use HTTPS | | -Follow the [Local HTTPS guide](https://www.gatsbyjs.org/docs/local-https/) +Follow the [Local HTTPS guide](https://www.gatsbyjs.com/docs/local-https/) to find out how you can set up an HTTPS development server using Gatsby. ### `build` @@ -98,8 +98,8 @@ At the root of a Gatsby app run `gatsby build` to do a production build of a sit | :--------------------------: | ------------------------------------------------------------------------------------------------------------------ | :---------------------------: | | `--prefix-paths` | Build site with link paths prefixed (set pathPrefix in your config) | `env.PREFIX_PATHS` or `false` | | `--no-uglify` | Build site without uglifying JS bundles (for debugging) | `false` | -| `--profile` | Build site with react profiling. See https://www.gatsbyjs.org/docs/profiling-site-performance-with-react-profiler/ | `false` | -| `--open-tracing-config-file` | Tracer configuration file (OpenTracing compatible). See https://www.gatsbyjs.org/docs/performance-tracing/ | | +| `--profile` | Build site with react profiling. See https://www.gatsbyjs.com/docs/profiling-site-performance-with-react-profiler/ | `false` | +| `--open-tracing-config-file` | Tracer configuration file (OpenTracing compatible). See https://www.gatsbyjs.com/docs/performance-tracing/ | | | `--no-color`, `--no-colors` | Disables colored terminal output | `false` | For prefixing paths, most will want to use the CLI flag (`gatsby build --prefix-paths`). For environments where you can't pass the --prefix-paths flag (ie Gatsby Cloud), the environment variable `PREFIX_PATHS` can be set to `true` to provide another way to prefix paths. diff --git a/packages/gatsby-cli/scripts/postinstall.js b/packages/gatsby-cli/scripts/postinstall.js index f317707dc80c1..548418394d20b 100644 --- a/packages/gatsby-cli/scripts/postinstall.js +++ b/packages/gatsby-cli/scripts/postinstall.js @@ -3,7 +3,7 @@ const chalk = require(`chalk`); const showSuccessMessage = () => { console.log(chalk.green(`Success!\n`)); console.log(chalk.cyan(`Welcome to the Gatsby CLI! Please visit `) + - chalk.underline(`https://www.gatsbyjs.org/docs/gatsby-cli/`) + + chalk.underline(`https://www.gatsbyjs.com/docs/gatsby-cli/`) + chalk.cyan(` for more information.\n`)); } diff --git a/packages/gatsby-cli/src/reporter/__tests__/__snapshots__/index.ts.snap b/packages/gatsby-cli/src/reporter/__tests__/__snapshots__/index.ts.snap index 8859a8ef5cdb8..67e09c8571889 100644 --- a/packages/gatsby-cli/src/reporter/__tests__/__snapshots__/index.ts.snap +++ b/packages/gatsby-cli/src/reporter/__tests__/__snapshots__/index.ts.snap @@ -140,7 +140,7 @@ Object { "context": Object { "someProp": "test123", }, - "docsUrl": "https://www.gatsbyjs.org/docs/gatsby-cli/#new", + "docsUrl": "https://www.gatsbyjs.com/docs/gatsby-cli/#new", "level": "ERROR", "stack": Array [], "text": "Error text is test123", @@ -153,7 +153,7 @@ Object { "context": Object { "someProp": "test123", }, - "docsUrl": "https://www.gatsbyjs.org/docs/gatsby-cli/#new", + "docsUrl": "https://www.gatsbyjs.com/docs/gatsby-cli/#new", "level": "ERROR", "pluginName": "gatsby-plugin-foo-bar", "stack": Array [], diff --git a/packages/gatsby-cli/src/reporter/__tests__/index.ts b/packages/gatsby-cli/src/reporter/__tests__/index.ts index 85d51d6aac530..0d806d60c4e92 100644 --- a/packages/gatsby-cli/src/reporter/__tests__/index.ts +++ b/packages/gatsby-cli/src/reporter/__tests__/index.ts @@ -111,7 +111,7 @@ describe(`report.error`, () => { "1337": { text: (context): string => `Error text is ${context.someProp}`, level: Level.ERROR, - docsUrl: `https://www.gatsbyjs.org/docs/gatsby-cli/#new`, + docsUrl: `https://www.gatsbyjs.com/docs/gatsby-cli/#new`, }, }) @@ -123,7 +123,7 @@ describe(`report.error`, () => { "1337": { text: (context): string => `Error text is ${context.someProp}`, level: Level.ERROR, - docsUrl: `https://www.gatsbyjs.org/docs/gatsby-cli/#new`, + docsUrl: `https://www.gatsbyjs.com/docs/gatsby-cli/#new`, }, }) @@ -146,7 +146,7 @@ describe(`report.error`, () => { "gatsby-plugin-foo-bar_1337": { text: (context): string => `Error text is ${context.someProp}`, level: Level.ERROR, - docsUrl: `https://www.gatsbyjs.org/docs/gatsby-cli/#new`, + docsUrl: `https://www.gatsbyjs.com/docs/gatsby-cli/#new`, }, }) diff --git a/packages/gatsby-cli/src/structured-errors/__tests__/construct-error.ts b/packages/gatsby-cli/src/structured-errors/__tests__/construct-error.ts index 5285c7b8843ca..365493ba70947 100644 --- a/packages/gatsby-cli/src/structured-errors/__tests__/construct-error.ts +++ b/packages/gatsby-cli/src/structured-errors/__tests__/construct-error.ts @@ -47,13 +47,13 @@ test(`it constructs an error from the supplied errorMap`, () => { "1337": { text: (context): string => `Error text is ${context.someProp} `, level: Level.ERROR, - docsUrl: `https://www.gatsbyjs.org/docs/gatsby-cli/#new`, + docsUrl: `https://www.gatsbyjs.com/docs/gatsby-cli/#new`, }, } ) expect(error.code).toBe(`1337`) - expect(error.docsUrl).toBe(`https://www.gatsbyjs.org/docs/gatsby-cli/#new`) + expect(error.docsUrl).toBe(`https://www.gatsbyjs.com/docs/gatsby-cli/#new`) }) test(`it does not overwrite internal error map`, () => { @@ -63,7 +63,7 @@ test(`it does not overwrite internal error map`, () => { "95312": { text: (context): string => `Error text is ${context.someProp} `, level: Level.ERROR, - docsUrl: `https://www.gatsbyjs.org/docs/gatsby-cli/#new`, + docsUrl: `https://www.gatsbyjs.com/docs/gatsby-cli/#new`, }, } ) diff --git a/packages/gatsby-codemods/README.md b/packages/gatsby-codemods/README.md index 5a26ff44ba524..533b633265544 100644 --- a/packages/gatsby-codemods/README.md +++ b/packages/gatsby-codemods/README.md @@ -55,7 +55,7 @@ Structure of a jscodeshift call: Add a `graphql` import to modules that use the `graphql` tag function without an import. This was supported in Gatsby v1 and deprecated for Gatsby v2. -See the [Gatsby v2 migration guide for details on when to use this](https://gatsbyjs.org/docs/migrating-from-v1-to-v2/#import-graphql-from-gatsby). +See the [Gatsby v2 migration guide for details on when to use this](https://gatsbyjs.com/docs/migrating-from-v1-to-v2/#import-graphql-from-gatsby). ```shell jscodeshift -t node_modules/gatsby-codemods/dist/transforms/global-graphql-calls.js @@ -86,7 +86,7 @@ export const query = graphql` Import `Link` from `gatsby` instead of `gatsby-link` and remove the `gatsby-link` import. -See the [Gatsby v2 migration guide for details on when to use this](https://gatsbyjs.org/docs/migrating-from-v1-to-v2/#import-link-from-gatsby). +See the [Gatsby v2 migration guide for details on when to use this](https://gatsbyjs.com/docs/migrating-from-v1-to-v2/#import-link-from-gatsby). ```shell jscodeshift -t node_modules/gatsby-codemods/dist/transforms/import-link.js @@ -107,7 +107,7 @@ export default props => ( Change the deprecated `navigateTo` method from `gatsby-link` to `navigate` from the `gatsby` module. -See the [Gatsby v2 migration guide for details on when to use this](https://gatsbyjs.org/docs/migrating-from-v1-to-v2/#change-navigateto-to-navigate). +See the [Gatsby v2 migration guide for details on when to use this](https://gatsbyjs.com/docs/migrating-from-v1-to-v2/#change-navigateto-to-navigate). ```shell jscodeshift -t node_modules/gatsby-codemods/dist/transforms/navigate-calls.js @@ -134,7 +134,7 @@ Rename `boundActionCreators` to `actions`. `boundActionCreators` has been deprec Note: Run this codemod only against files that use `boundActionCreators` instead of running it against a whole directory. -See the [Gatsby v2 migration guide for details on when to use this](https://gatsbyjs.org/docs/migrating-from-v1-to-v2/#rename-boundactioncreators-to-actions). +See the [Gatsby v2 migration guide for details on when to use this](https://gatsbyjs.com/docs/migrating-from-v1-to-v2/#rename-boundactioncreators-to-actions). ```shell jscodeshift -t node_modules/gatsby-codemods/dist/transforms/rename-bound-action-creators.js diff --git a/packages/gatsby-design-tokens/CHANGELOG.md b/packages/gatsby-design-tokens/CHANGELOG.md index 8e0907bd0b704..2f85f3d48ec8d 100644 --- a/packages/gatsby-design-tokens/CHANGELOG.md +++ b/packages/gatsby-design-tokens/CHANGELOG.md @@ -343,8 +343,8 @@ Here's all changes listed by "token group": - add `colors.whiteFade[5]` - BREAKING CHANGE: fix `colors.blackFade[80]`, `colors.whiteFade[80]` - both were set to an opacity of `.85`, adjusted to `.8` - - TODO: Adjust a couple of values for gatsbyjs.org; no clue about where we currently might use this in `gatsby-interface` and related (.com/Cloud dashboard). -- feat: port `colors.code` from the gatsbyjs.org `theme-ui` theme to the `colors` tokens + - TODO: Adjust a couple of values for gatsbyjs.com; no clue about where we currently might use this in `gatsby-interface` and related (.com/Cloud dashboard). +- feat: port `colors.code` from the gatsbyjs.com `theme-ui` theme to the `colors` tokens - 💚 This improves compliance with WCAG 2.0 AA color contrasts. - feat: add `colors.code.copyButton` - feat: add `colors.code.lineHighlightBackground` @@ -384,7 +384,7 @@ Here's all changes listed by "token group": ##### `sizes` - BREAKING CHANGE: removed - - As discussed in https://github.com/gatsby-inc/gatsby-interface/issues/181, this moves the current gatsbyjs.org-centric `sizes` tokens to `theme-gatsbyjs-org` for clarity, until a clear pattern emerges. + - As discussed in https://github.com/gatsby-inc/gatsby-interface/issues/181, this moves the current gatsbyjs.com-centric `sizes` tokens to `theme-gatsbyjs-org` for clarity, until a clear pattern emerges. ##### `space` @@ -402,11 +402,11 @@ Here's all changes listed by "token group": ##### `zIndices` - BREAKING CHANGE: removed - - As discussed in https://github.com/gatsby-inc/gatsby-interface/issues/181, this moves the current gatsbyjs.org-centric `zIndices` tokens to `theme-gatsbyjs-org`for clarity, until a clear pattern emerges. + - As discussed in https://github.com/gatsby-inc/gatsby-interface/issues/181, this moves the current gatsbyjs.com-centric `zIndices` tokens to `theme-gatsbyjs-org`for clarity, until a clear pattern emerges. #### Themes -- feat: add base `theme-ui` Gatsby theme, gatsbyjs.org `theme-ui` theme +- feat: add base `theme-ui` Gatsby theme, gatsbyjs.com `theme-ui` theme - Both themes don't tree-shake yet, so no `agadoo` yet in the corresponding `gatsby-design-tokens/package.json` scripts. - Both export the `theme-ui` theme as `theme` and also provide individual token group exports (because we require them in `www` for usage outside of the `theme-ui` context). - Example usage: diff --git a/packages/gatsby-design-tokens/README.md b/packages/gatsby-design-tokens/README.md index 49dc8813fa5eb..c446c82c7d29b 100644 --- a/packages/gatsby-design-tokens/README.md +++ b/packages/gatsby-design-tokens/README.md @@ -100,7 +100,7 @@ import { - `rem` values are based on a `font-size` of `16px` for the root element. - All tokens work in the context of [Theme UI's Theme Scales](https://theme-ui.com/theme-spec/#theme-scales), with the exception of `breakpoints`: Use `breakpointsArray` for `theme-ui` and its [responsive styles](https://theme-ui.com/getting-started/#responsive-styles) feature. -Find a work-in-progress list of design tokens in the design tokens documentation at [gatsbyjs.org/guidelines/design-tokens](https://www.gatsbyjs.org/guidelines/design-tokens/). +Find a work-in-progress list of design tokens in the design tokens documentation at [gatsbyjs.com/guidelines/design-tokens](https://www.gatsbyjs.com/guidelines/design-tokens/). ## `theme-ui` themes 🎨 @@ -136,7 +136,7 @@ import { ### `theme-gatsbyjs-org` -The theme currently in use on gatsbyjs.org via `gatsby-plugin-theme-ui`: +The theme currently in use on gatsbyjs.com via `gatsby-plugin-theme-ui`: - Extends the base theme's `colors` with a couple .org-specific things, and provides a `dark` mode (ref. https://theme-ui.com/color-modes). - Adds .org-specific `sizes` and `zIndices`. @@ -171,11 +171,11 @@ import { ## Local development -The Gatsby monorepo, which hosts this package, also contains the source for gatsbyjs.org, aka `www` — where `theme-gatsbyjs-org` is in use. Using a little helper called `gatsby-dev` we can develop and test both of them locally. +The Gatsby monorepo, which hosts this package, also contains the source for gatsbyjs.com, aka `www` — where `theme-gatsbyjs-org` is in use. Using a little helper called `gatsby-dev` we can develop and test both of them locally. ### 1. Clone the `gatsby` monorepo and set it up for local dev -Follow the [official guide](https://www.gatsbyjs.org/contributing/setting-up-your-local-dev-environment/#fork-clone-and-branch-the-repository) to clone/fork and set up the Gatsby monorepo. This will roughly look like this: +Follow the [official guide](https://www.gatsbyjs.com/contributing/setting-up-your-local-dev-environment/#fork-clone-and-branch-the-repository) to clone/fork and set up the Gatsby monorepo. This will roughly look like this: ```shell # clone the repo/your fork @@ -194,7 +194,7 @@ git checkout -b topics/new-feature-name #### Install `gatsby-dev-cli` to ease testing your local changes to `packages` -Assuming `gatsby-cli` [is installed](https://www.gatsbyjs.org/contributing/setting-up-your-local-dev-environment/#gatsby-functional-changes), let's install [`gatsby-dev-cli`](<(https://www.npmjs.com/package/gatsby-dev-cli)>) with +Assuming `gatsby-cli` [is installed](https://www.gatsbyjs.com/contributing/setting-up-your-local-dev-environment/#gatsby-functional-changes), let's install [`gatsby-dev-cli`](<(https://www.npmjs.com/package/gatsby-dev-cli)>) with ```shell yarn global add gatsby-dev-cli @@ -218,7 +218,7 @@ Follow the [README instructions](https://github.com/gatsbyjs/gatsby/blob/master/ > […] skip downloading screenshots and generating responsive images for all screenshots and replace them with a placeholder image -Run `yarn develop`, which thanks to the previous step shouldn't take ~40 minutes but way less. Hopefully you should be able to browse a local version of gatsbyjs.org after this. Let's leave `yarn develop` running! +Run `yarn develop`, which thanks to the previous step shouldn't take ~40 minutes but way less. Hopefully you should be able to browse a local version of gatsbyjs.com after this. Let's leave `yarn develop` running! ### 3. Rebuild `gatsby-design-tokens` when it changes, and use `gatsby-dev` to copy the changed-and-compiled package over to `www/node_modules` diff --git a/packages/gatsby-design-tokens/src/theme-gatsbyjs-org.js b/packages/gatsby-design-tokens/src/theme-gatsbyjs-org.js index eabb203d926f5..61fda3bb20e42 100644 --- a/packages/gatsby-design-tokens/src/theme-gatsbyjs-org.js +++ b/packages/gatsby-design-tokens/src/theme-gatsbyjs-org.js @@ -18,7 +18,7 @@ const shadowDarkFlares = `0,0,0` // provides a "dark" mode along the initial color mode "light" const c = { ...colorsTokens, - // gatsbyjs.org specific stuff + // gatsbyjs.com specific stuff banner: colorsTokens.purple[70], // moved `text.placeholder` to `input.placeholder` // ref. e.g. https://github.com/system-ui/theme-ui/blob/702c43e804046a94389e7a12a8bba4c4f436b14e/packages/presets/src/tailwind.js#L6 diff --git a/packages/gatsby-dev-cli/README.md b/packages/gatsby-dev-cli/README.md index 375f077111e59..8626194e28139 100644 --- a/packages/gatsby-dev-cli/README.md +++ b/packages/gatsby-dev-cli/README.md @@ -48,7 +48,7 @@ git checkout package.json; npm install --force **[Demo Video](https://www.youtube.com/watch?v=D0SwX1MSuas)** More detailed instructions for setting up your Gatsby development environment can -be found [here](https://www.gatsbyjs.org/contributing/how-to-contribute/). +be found [here](https://www.gatsbyjs.com/contributing/how-to-contribute/). ### Other commands diff --git a/packages/gatsby-link/README.md b/packages/gatsby-link/README.md index e898fb165ff18..7e887d606a311 100644 --- a/packages/gatsby-link/README.md +++ b/packages/gatsby-link/README.md @@ -2,4 +2,4 @@ All components and utility functions from this package are now exported from [`gatsby`](https://github.com/gatsbyjs/gatsby/tree/master/packages/gatsby) package. You should not import anything from this package directly. -The [API reference](https://www.gatsbyjs.org/docs/gatsby-link/) has more documentation. +The [API reference](https://www.gatsbyjs.com/docs/gatsby-link/) has more documentation. diff --git a/packages/gatsby-plugin-catch-links/README.md b/packages/gatsby-plugin-catch-links/README.md index c047830b2d1b6..4445f0698689d 100644 --- a/packages/gatsby-plugin-catch-links/README.md +++ b/packages/gatsby-plugin-catch-links/README.md @@ -1,6 +1,6 @@ # gatsby-plugin-catch-links -This plugin intercepts all local links that have not been created in React using [`gatsby-link`](https://gatsbyjs.org/docs/gatsby-link), and replaces their behavior with that of the `gatsby-link` [`navigate`](https://gatsbyjs.org/docs/gatsby-link/#how-to-use-the-navigate-helper-function). This avoids the browser having to refresh the whole page when navigating between local pages, preserving the Single Page Application (SPA) feel. +This plugin intercepts all local links that have not been created in React using [`gatsby-link`](https://gatsbyjs.com/docs/gatsby-link), and replaces their behavior with that of the `gatsby-link` [`navigate`](https://gatsbyjs.com/docs/gatsby-link/#how-to-use-the-navigate-helper-function). This avoids the browser having to refresh the whole page when navigating between local pages, preserving the Single Page Application (SPA) feel. Example use cases: @@ -39,4 +39,4 @@ Regular expression for paths to be excluded from being handled by this plugin. ## Examples -- Check out this live example [_Using Remark_](https://using-remark.gatsbyjs.org/copy-linked-files-intercepting-local-links/#intercepting-local-links) to see this plugin in action. The full source code for this example can be found [here](https://github.com/gatsbyjs/gatsby/tree/master/examples/using-remark). +- Check out this live example [_Using Remark_](https://using-remark.gatsbyjs.com/copy-linked-files-intercepting-local-links/#intercepting-local-links) to see this plugin in action. The full source code for this example can be found [here](https://github.com/gatsbyjs/gatsby/tree/master/examples/using-remark). diff --git a/packages/gatsby-plugin-create-client-paths/README.md b/packages/gatsby-plugin-create-client-paths/README.md index 85a682367105a..e3958ba1bed11 100644 --- a/packages/gatsby-plugin-create-client-paths/README.md +++ b/packages/gatsby-plugin-create-client-paths/README.md @@ -4,7 +4,7 @@ Use this plugin to simplify creating a “hybrid” Gatsby app with both statically rendered pages as well as "client-paths". These paths exist on the client only and do not correspond to index.html files in an app's built assets. -For more information refer to [client-only routes & user authentication](https://www.gatsbyjs.org/docs/client-only-routes-and-user-authentication/). +For more information refer to [client-only routes & user authentication](https://www.gatsbyjs.com/docs/client-only-routes-and-user-authentication/). ## Migration diff --git a/packages/gatsby-plugin-feed/README.md b/packages/gatsby-plugin-feed/README.md index fdaaeb1789175..00179ab1a4e28 100644 --- a/packages/gatsby-plugin-feed/README.md +++ b/packages/gatsby-plugin-feed/README.md @@ -84,7 +84,7 @@ Each feed must include `output`, `query`, `title`, and `serialize`. You'll need All additional options are passed through to the [`rss`][rss] utility. For more info on those additional options, [explore the `itemOptions` section of the `rss` package](https://www.npmjs.com/package/rss#itemoptions). -Check out an example of [how you could implement](https://www.gatsbyjs.org/docs/adding-an-rss-feed/) to your own site, with a custom `serialize` function, and additional functionality. +Check out an example of [how you could implement](https://www.gatsbyjs.com/docs/adding-an-rss-feed/) to your own site, with a custom `serialize` function, and additional functionality. _**Note**: This plugin only generates the `xml` file(s) when run in `production` mode! To test your feed, run: `gatsby build && gatsby serve`._ diff --git a/packages/gatsby-plugin-gatsby-cloud/README.md b/packages/gatsby-plugin-gatsby-cloud/README.md index 43cb1dd28cab0..46f94aaeae2b3 100644 --- a/packages/gatsby-plugin-gatsby-cloud/README.md +++ b/packages/gatsby-plugin-gatsby-cloud/README.md @@ -95,13 +95,13 @@ have to add to every path. To make this easier, the plugin provides the ### Redirects -You can create redirects using the [`createRedirect`](https://www.gatsbyjs.org/docs/actions/#createRedirect) action. +You can create redirects using the [`createRedirect`](https://www.gatsbyjs.com/docs/actions/#createRedirect) action. In addition to the options provided by the Gatsby API, you can pass these options specific to this plugin: | Attribute | Description | | ------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `statusCode` | Overrides the HTTP status code which is set to `302` by default or `301` when [`isPermanent`](https://www.gatsbyjs.org/docs/actions/#createRedirect) is `true`. You can set one here. For example, `200` for rewrites, or `404` for a custom error page. | +| `statusCode` | Overrides the HTTP status code which is set to `302` by default or `301` when [`isPermanent`](https://www.gatsbyjs.com/docs/actions/#createRedirect) is `true`. You can set one here. For example, `200` for rewrites, or `404` for a custom error page. | An example: @@ -119,7 +119,7 @@ createRedirect({ }) ``` -Redirect rules are automatically added for [client only paths](https://www.gatsbyjs.org/docs/client-only-routes-and-user-authentication). The plugin uses the [matchPath](https://www.gatsbyjs.org/docs/gatsby-internals-terminology/#matchpath) syntax to match all possible requests in the range of your client-side routes and serves the HTML file for the client-side route. Without it, only the exact route of the client-side route works. +Redirect rules are automatically added for [client only paths](https://www.gatsbyjs.com/docs/client-only-routes-and-user-authentication). The plugin uses the [matchPath](https://www.gatsbyjs.com/docs/gatsby-internals-terminology/#matchpath) syntax to match all possible requests in the range of your client-side routes and serves the HTML file for the client-side route. Without it, only the exact route of the client-side route works. If those rules are conflicting with custom rules or if you want to have more control over them you can disable them in [configuration](#configuration) by setting `generateMatchPathRewrites` to `false`. diff --git a/packages/gatsby-plugin-google-analytics/README.md b/packages/gatsby-plugin-google-analytics/README.md index 00c402ff1069a..ea72dbf97d3d2 100644 --- a/packages/gatsby-plugin-google-analytics/README.md +++ b/packages/gatsby-plugin-google-analytics/README.md @@ -121,7 +121,7 @@ If you need to exclude any path from the tracking system, you can add it (one or ### `pageTransitionDelay` -If your site uses any custom transitions on route update (e.g. [`gatsby-plugin-transition-link`](https://www.gatsbyjs.org/blog/2018-12-04-per-link-gatsby-page-transitions-with-transitionlink/)), then you can delay processing the page view event until the new page is mounted. +If your site uses any custom transitions on route update (e.g. [`gatsby-plugin-transition-link`](https://www.gatsbyjs.com/blog/2018-12-04-per-link-gatsby-page-transitions-with-transitionlink/)), then you can delay processing the page view event until the new page is mounted. ### `optimizeId` diff --git a/packages/gatsby-plugin-google-gtag/README.md b/packages/gatsby-plugin-google-gtag/README.md index 0bf7dcad71e88..339e82a9902b0 100644 --- a/packages/gatsby-plugin-google-gtag/README.md +++ b/packages/gatsby-plugin-google-gtag/README.md @@ -4,7 +4,7 @@ Easily add Google Global Site Tag to your Gatsby site. > The global site tag (gtag.js) is a JavaScript tagging framework and API that allows you to send event data to Google Analytics, Google Ads, Campaign Manager, Display & Video 360, and Search Ads 360. -Global site tag (gtag.js) is meant to combine multiple Google tagging systems and can replace older ones such as [analytics.js](https://developers.google.com/analytics/devguides/collection/analyticsjs/) ([gatsby-plugin-google-analytics](https://www.gatsbyjs.org/packages/gatsby-plugin-google-analytics/)). +Global site tag (gtag.js) is meant to combine multiple Google tagging systems and can replace older ones such as [analytics.js](https://developers.google.com/analytics/devguides/collection/analyticsjs/) ([gatsby-plugin-google-analytics](https://www.gatsbyjs.com/packages/gatsby-plugin-google-analytics/)). For more general information on gtag you can read Google's official documentation on the subject: https://developers.google.com/gtagjs/. @@ -89,7 +89,7 @@ import { OutboundLink } from "gatsby-plugin-google-gtag" export default () => (
- + Visit the Google Global Site Tag plugin page!
diff --git a/packages/gatsby-plugin-jss/README.md b/packages/gatsby-plugin-jss/README.md index 0b15ade8e68f1..b950689067910 100644 --- a/packages/gatsby-plugin-jss/README.md +++ b/packages/gatsby-plugin-jss/README.md @@ -34,4 +34,4 @@ plugins: [ ## Example -https://using-jss.gatsbyjs.org/ +https://using-jss.gatsbyjs.com/ diff --git a/packages/gatsby-plugin-layout/README.md b/packages/gatsby-plugin-layout/README.md index 5e0cfc647fab4..83b564f95f503 100644 --- a/packages/gatsby-plugin-layout/README.md +++ b/packages/gatsby-plugin-layout/README.md @@ -50,7 +50,7 @@ Once the plugin is added, you don't need to manually wrap your pages with the La There are a few scenarios where it makes sense to reimplement the V1 layout handling: -1. You have a large or complex V1 site and [refactoring to the new layout component](https://www.gatsbyjs.org/docs/migrating-from-v1-to-v2/#remove-or-refactor-layout-components) is not feasible +1. You have a large or complex V1 site and [refactoring to the new layout component](https://www.gatsbyjs.com/docs/migrating-from-v1-to-v2/#remove-or-refactor-layout-components) is not feasible 2. Your site uses page transitions or other transitions that break if the layout component is unmounted and remounted when routes change 3. Your site attaches global state in the layout that doesn't persist if the component is unmounted and remounted @@ -82,7 +82,7 @@ In version 2, the layout component is no longer special, and it's included in ev ``` -This can make it complicated to support transitions or state without using the [`wrapPageElement` browser API](https://gatsbyjs.org/docs/browser-apis/#wrapPageElement) (and the [SSR equivalent](https://gatsbyjs.org/docs/ssr-apis/#wrapPageElement)). This plugin implements those APIs for you, which reimplements the behavior of Gatsby V1. +This can make it complicated to support transitions or state without using the [`wrapPageElement` browser API](https://gatsbyjs.com/docs/browser-apis/#wrapPageElement) (and the [SSR equivalent](https://gatsbyjs.com/docs/ssr-apis/#wrapPageElement)). This plugin implements those APIs for you, which reimplements the behavior of Gatsby V1. ## Troubleshooting diff --git a/packages/gatsby-plugin-mdx/README.md b/packages/gatsby-plugin-mdx/README.md index feefe00473baa..6933163698d5e 100644 --- a/packages/gatsby-plugin-mdx/README.md +++ b/packages/gatsby-plugin-mdx/README.md @@ -281,7 +281,7 @@ _**Note:** You should rerun your Gatsby development environment to update import If you want to allow usage of a component from anywhere (often referred to as a shortcode), you can pass it to the -[MDXProvider](https://www.gatsbyjs.org/docs/mdx/customizing-components/). +[MDXProvider](https://www.gatsbyjs.com/docs/mdx/customizing-components/). ```js // src/components/layout.js @@ -315,14 +315,14 @@ Here's a YouTube embed #### Gatsby remark plugins This config option is used for compatibility with a set of plugins many people -[use with remark](https://www.gatsbyjs.org/plugins/?=gatsby-remark-) that require +[use with remark](https://www.gatsbyjs.com/plugins/?=gatsby-remark-) that require the gatsby environment to function properly. In some cases, like -[gatsby-remark-prismjs](https://www.gatsbyjs.org/packages/gatsby-remark-prismjs/?=gatsby-remark-), +[gatsby-remark-prismjs](https://www.gatsbyjs.com/packages/gatsby-remark-prismjs/?=gatsby-remark-), it makes more sense to use a library like [prism-react-renderer](https://github.com/FormidableLabs/prism-react-renderer) to render codeblocks using a [React component](/api-reference/mdx-provider). In other cases, like -[gatsby-remark-images](https://www.gatsbyjs.org/packages/gatsby-remark-images/?=gatsby-remark-), +[gatsby-remark-images](https://www.gatsbyjs.com/packages/gatsby-remark-images/?=gatsby-remark-), the interaction with the Gatsby APIs is well deserved because the images can be optimized by Gatsby and you should continue using it. diff --git a/packages/gatsby-plugin-netlify-cms/README.md b/packages/gatsby-plugin-netlify-cms/README.md index 2fa87134c813a..d2cccc2cb12d1 100644 --- a/packages/gatsby-plugin-netlify-cms/README.md +++ b/packages/gatsby-plugin-netlify-cms/README.md @@ -39,7 +39,7 @@ file](https://www.netlifycms.org/docs/add-to-your-site/#configuration) in Netlify CMS can be configured via the plugin options below. You can learn about how to pass options to plugins in the [Gatsby -docs](https://www.gatsbyjs.org/docs/plugins/#how-to-use-gatsby-plugins). +docs](https://www.gatsbyjs.com/docs/plugins/#how-to-use-gatsby-plugins). ### `modulePath` @@ -195,7 +195,7 @@ Function to customize webpack configuration. Function parameters: - config: webpack configuration for NetlifyCMS -- destructured object from onCreateWebpackConfig { store, stage, pathPrefix, getConfig, rules, loaders, plugins} as seen in https://www.gatsbyjs.org/docs/node-apis/#onCreateWebpackConfig +- destructured object from onCreateWebpackConfig { store, stage, pathPrefix, getConfig, rules, loaders, plugins} as seen in https://www.gatsbyjs.com/docs/node-apis/#onCreateWebpackConfig ```javascript plugins: [ diff --git a/packages/gatsby-plugin-offline/src/__tests__/fixtures/public/index.html b/packages/gatsby-plugin-offline/src/__tests__/fixtures/public/index.html index b2b53a8652436..1e5028d179543 100644 --- a/packages/gatsby-plugin-offline/src/__tests__/fixtures/public/index.html +++ b/packages/gatsby-plugin-offline/src/__tests__/fixtures/public/index.html @@ -872,7 +872,7 @@

Modern Development, for the Content Web

Fast sites. Fast iterations. Unlike your CMS, Gatsby engineers the development experience for performance.

+
Get started todayWhy Gatsby?
800+ contributors, 24.2 k stars @@ -1150,7 +1150,7 @@

Product

Why Gatsby?

How It Works

Bring Data From AnywhereWrite Modern AppsUnreal PerformanceOne-Click DeploymentAll Guides
-

Docs & Help

DocumentationTutorialBlogCommunity
+

Docs & Help

DocumentationTutorialBlogCommunity

Company

About UsSupportTraining
diff --git a/packages/gatsby-plugin-offline/src/__tests__/gatsby-browser.test.js b/packages/gatsby-plugin-offline/src/__tests__/gatsby-browser.test.js index 0bbfe7d0b5e87..51a182d1e6f5c 100644 --- a/packages/gatsby-plugin-offline/src/__tests__/gatsby-browser.test.js +++ b/packages/gatsby-plugin-offline/src/__tests__/gatsby-browser.test.js @@ -15,9 +15,9 @@ it(`does not add prefetch for preconnect/prefetch/prerender`, () => { } // Should not be prefetched - addHeadElement(`link`, { rel: `preconnect`, href: `https://gatsbyjs.org` }) - addHeadElement(`link`, { rel: `prefetch`, href: `https://gatsbyjs.org` }) - addHeadElement(`link`, { rel: `prerender`, href: `https://gatsbyjs.org` }) + addHeadElement(`link`, { rel: `preconnect`, href: `https://gatsbyjs.com` }) + addHeadElement(`link`, { rel: `prefetch`, href: `https://gatsbyjs.com` }) + addHeadElement(`link`, { rel: `prerender`, href: `https://gatsbyjs.com` }) addHeadElement(`script`, { src: `https://gats.by/script.js` }) addHeadElement(`style`, { "data-href": `https://gats.by/lazy.css` }) addHeadElement(`link`, { diff --git a/packages/gatsby-plugin-page-creator/src/gatsby-node.ts b/packages/gatsby-plugin-page-creator/src/gatsby-node.ts index d732e1536d695..35795ca580438 100644 --- a/packages/gatsby-plugin-page-creator/src/gatsby-node.ts +++ b/packages/gatsby-plugin-page-creator/src/gatsby-node.ts @@ -81,7 +81,7 @@ export async function createPagesStatefully( context: { sourceMessage: `"path" is a required option for gatsby-plugin-page-creator -See docs here - https://www.gatsbyjs.org/plugins/gatsby-plugin-page-creator/`, +See docs here - https://www.gatsbyjs.com/plugins/gatsby-plugin-page-creator/`, }, }) } diff --git a/packages/gatsby-plugin-react-css-modules/README.md b/packages/gatsby-plugin-react-css-modules/README.md index cc86d09b6ebde..0a0769b7afb65 100644 --- a/packages/gatsby-plugin-react-css-modules/README.md +++ b/packages/gatsby-plugin-react-css-modules/README.md @@ -39,4 +39,4 @@ plugins: [ Files must be named using the pattern `filename.module.css` for Gatsby to treat them as CSS modules. You can change this behavior using a custom webpack config -https://www.gatsbyjs.org/docs/add-custom-webpack-config/ +https://www.gatsbyjs.com/docs/add-custom-webpack-config/ diff --git a/packages/gatsby-plugin-typography/README.md b/packages/gatsby-plugin-typography/README.md index e3a0b0c9edc67..613af43ffe682 100644 --- a/packages/gatsby-plugin-typography/README.md +++ b/packages/gatsby-plugin-typography/README.md @@ -2,7 +2,7 @@ A Gatsby plugin for utilizing the [Typography](https://kyleamathews.github.io/typography.js/) library with minimal configuration. -See it in action in the [Tutorial](https://www.gatsbyjs.org/tutorial/part-3/) +See it in action in the [Tutorial](https://www.gatsbyjs.com/tutorial/part-3/) ([source](https://github.com/gatsbyjs/gatsby/tree/master/packages/gatsby-plugin-typography)) ## Install diff --git a/packages/gatsby-remark-copy-linked-files/README.md b/packages/gatsby-remark-copy-linked-files/README.md index e84328f7431bb..39ac3a4e03aed 100644 --- a/packages/gatsby-remark-copy-linked-files/README.md +++ b/packages/gatsby-remark-copy-linked-files/README.md @@ -30,7 +30,7 @@ The `my-awesome-pdf.pdf` file will be copied to the root directory (i.e., `publi **Default settings:** -Add `gatsby-remark-copy-linked-files` plugin as a plugin to [`gatsby-transformer-remark`](https://www.gatsbyjs.org/packages/gatsby-transformer-remark/): +Add `gatsby-remark-copy-linked-files` plugin as a plugin to [`gatsby-transformer-remark`](https://www.gatsbyjs.com/packages/gatsby-transformer-remark/): ```javascript // In your gatsby-config.js diff --git a/packages/gatsby-remark-custom-blocks/README.md b/packages/gatsby-remark-custom-blocks/README.md index c987d450333e8..daa1fbd488606 100644 --- a/packages/gatsby-remark-custom-blocks/README.md +++ b/packages/gatsby-remark-custom-blocks/README.md @@ -11,7 +11,7 @@ Adds custom blocks to `MarkdownRemark` using [remark-custom-blocks](https://github.com/zestedesavoir/zmarkdown/tree/master/packages/remark-custom-blocks). -Unlike in [gatsby-remark-component](https://www.gatsbyjs.org/packages/gatsby-remark-component/) where you can only use HTML within the custom component tag, custom blocks allow you to use markdown within the block. +Unlike in [gatsby-remark-component](https://www.gatsbyjs.com/packages/gatsby-remark-component/) where you can only use HTML within the custom component tag, custom blocks allow you to use markdown within the block. ## Install diff --git a/packages/gatsby-remark-embed-snippet/README.md b/packages/gatsby-remark-embed-snippet/README.md index 248f9c7ff23b7..80431cca8ac90 100644 --- a/packages/gatsby-remark-embed-snippet/README.md +++ b/packages/gatsby-remark-embed-snippet/README.md @@ -4,7 +4,7 @@ Embeds the contents of specified files as code snippets. ## Installation -**Note**: This plugin depends on [gatsby-remark-prismjs](https://www.gatsbyjs.org/packages/gatsby-remark-prismjs/) and [gatsby-transformer-remark](https://www.gatsbyjs.org/packages/gatsby-transformer-remark/) plugins +**Note**: This plugin depends on [gatsby-remark-prismjs](https://www.gatsbyjs.com/packages/gatsby-remark-prismjs/) and [gatsby-transformer-remark](https://www.gatsbyjs.com/packages/gatsby-transformer-remark/) plugins ```shell npm install gatsby-remark-embed-snippet gatsby-remark-prismjs gatsby-transformer-remark prismjs @@ -14,7 +14,7 @@ npm install gatsby-remark-embed-snippet gatsby-remark-prismjs gatsby-transformer > **Important**: _You must add `gatsby-remark-embed-snippet` before `gatsby-remark-prismjs` in your plugins array!_ > Otherwise, this plugin will not work because the code snippet files first need to be inlined before they can be transformed into code blocks. -> For more information, see [gatsby-remark-prismjs](https://www.gatsbyjs.org/packages/gatsby-remark-prismjs/). +> For more information, see [gatsby-remark-prismjs](https://www.gatsbyjs.com/packages/gatsby-remark-prismjs/). To use `gatsby-remark-embed-snippet` plugin: diff --git a/packages/gatsby-remark-images/README.md b/packages/gatsby-remark-images/README.md index 4beafdb23ad1f..b50a0c907230a 100644 --- a/packages/gatsby-remark-images/README.md +++ b/packages/gatsby-remark-images/README.md @@ -96,7 +96,7 @@ This plugin will support the following formats: - JPEG - PNG -Since [Sharp][5] is used for image processing, this plugin will not support GIFs or SVGs. If you would like to render these file types with the image markdown syntax, use the [`gatsby-remark-copy-linked-files`](https://www.gatsbyjs.org/packages/gatsby-remark-copy-linked-files/) plugin. Do note with this it will load in the images, but won't use the features of [Sharp][5] such as the elastic container or the blur-up enhancements. +Since [Sharp][5] is used for image processing, this plugin will not support GIFs or SVGs. If you would like to render these file types with the image markdown syntax, use the [`gatsby-remark-copy-linked-files`](https://www.gatsbyjs.com/packages/gatsby-remark-copy-linked-files/) plugin. Do note with this it will load in the images, but won't use the features of [Sharp][5] such as the elastic container or the blur-up enhancements. [1]: https://jmperezperez.com/medium-image-progressive-loading-placeholder/ [2]: https://code.facebook.com/posts/991252547593574/the-technology-behind-preview-photos/ diff --git a/packages/gatsby-remark-katex/README.md b/packages/gatsby-remark-katex/README.md index 051f3b62da434..ec355015aac4a 100644 --- a/packages/gatsby-remark-katex/README.md +++ b/packages/gatsby-remark-katex/README.md @@ -1,7 +1,7 @@ # gatsby-remark-katex [gatsby-remark-katex][1] adds math equation support to gatsby using -[remark-math][2] and [katex][3]. Live example at [using-remark.gatsbyjs.org/katex/](https://using-remark.gatsbyjs.org/katex/). +[remark-math][2] and [katex][3]. Live example at [using-remark.gatsbyjs.com/katex/](https://using-remark.gatsbyjs.com/katex/). ## Install @@ -58,7 +58,7 @@ a^2 + b^2 = c^2 $$ ``` -[1]: https://www.gatsbyjs.org/packages/gatsby-remark-katex/ +[1]: https://www.gatsbyjs.com/packages/gatsby-remark-katex/ [2]: https://github.com/Rokt33r/remark-math [3]: https://github.com/KaTeX/KaTeX [4]: https://github.com/gatsbyjs/gatsby/blob/master/examples/using-remark/src/templates/template-blog-post.js diff --git a/packages/gatsby-remark-prismjs/README.md b/packages/gatsby-remark-prismjs/README.md index 9917f8232c55e..7143993dc39ca 100644 --- a/packages/gatsby-remark-prismjs/README.md +++ b/packages/gatsby-remark-prismjs/README.md @@ -94,7 +94,7 @@ plugins: [ PrismJS ships with a number of [themes][5] (previewable on the [PrismJS website][6]) that you can easily include in your Gatsby site, or you can build your own by copying and modifying an example (which is what we've done for -[gatsbyjs.org](https://gatsbyjs.org)). +[gatsbyjs.com](https://gatsbyjs.com)). To load a theme, just require its CSS file in your `gatsby-browser.js` file, e.g. @@ -400,7 +400,7 @@ You can specify language for `diff` code blocks by using `diff-[language]` to en ### Line hiding -As well as highlighting lines, it's possible to _hide_ lines from the rendered output. Often this is handy when using `gatsby-remark-prismjs` along with [`gatsby-remark-embed-snippet`](https://www.gatsbyjs.org/packages/gatsby-remark-embed-snippet/). +As well as highlighting lines, it's possible to _hide_ lines from the rendered output. Often this is handy when using `gatsby-remark-prismjs` along with [`gatsby-remark-embed-snippet`](https://www.gatsbyjs.com/packages/gatsby-remark-embed-snippet/). As with highlighting lines, you can control which lines to hide by adding directives as comments in your source code. @@ -411,7 +411,7 @@ The available directives are: - `hide-start` hides the lines until the matching `hide-end`; - `hide-range{1, 4-6}` will hide the next line, and the fourth, fifth and sixth lines. -The hide-line directives will always be hidden too. Check out [the using-remark example site](https://using-remark.gatsbyjs.org/embed-snippets/) to see how this looks on a live site. +The hide-line directives will always be hidden too. Check out [the using-remark example site](https://using-remark.gatsbyjs.com/embed-snippets/) to see how this looks on a live site. ### Inline code blocks diff --git a/packages/gatsby-source-contentful/README.md b/packages/gatsby-source-contentful/README.md index c3512c12700ba..13a598ef434e6 100644 --- a/packages/gatsby-source-contentful/README.md +++ b/packages/gatsby-source-contentful/README.md @@ -4,7 +4,7 @@ > Contentful spaces. It creates links between entry types and asset so they can be > queried in Gatsby using GraphQL. > -> An example site for using this plugin is at https://using-contentful.gatsbyjs.org/ +> An example site for using this plugin is at https://using-contentful.gatsbyjs.com/
Table of contents @@ -206,7 +206,7 @@ You might query for **all** of a type of node: } ``` -You might do this in your `gatsby-node.js` using Gatsby's [`createPages`](https://next.gatsbyjs.org/docs/node-apis/#createPages) Node API. +You might do this in your `gatsby-node.js` using Gatsby's [`createPages`](https://next.gatsbyjs.com/docs/node-apis/#createPages) Node API. ### Query for a single node @@ -247,7 +247,7 @@ To query for a single `CaseStudy` node with the short text properties `title` an } ``` -You might query for a **single** node inside a component in your `src/components` folder, using [Gatsby's `StaticQuery` component](https://www.gatsbyjs.org/docs/static-query/). +You might query for a **single** node inside a component in your `src/components` folder, using [Gatsby's `StaticQuery` component](https://www.gatsbyjs.com/docs/static-query/). #### A note about LongText fields @@ -263,7 +263,7 @@ On Contentful, a "Long text" field uses Markdown by default. The field is expose } ``` -Unless the text is Markdown-free, you cannot use the returned value directly. In order to handle the Markdown content, you must use a transformer plugin such as [`gatsby-transformer-remark`](https://www.gatsbyjs.org/packages/gatsby-transformer-remark/). The transformer will create a `childMarkdownRemark` on the "Long text" field and expose the generated html as a child node: +Unless the text is Markdown-free, you cannot use the returned value directly. In order to handle the Markdown content, you must use a transformer plugin such as [`gatsby-transformer-remark`](https://www.gatsbyjs.com/packages/gatsby-transformer-remark/). The transformer will create a `childMarkdownRemark` on the "Long text" field and expose the generated html as a child node: ```graphql { @@ -343,7 +343,7 @@ To get **all** the `CaseStudy` nodes with `ShortText` fields `id`, `slug`, `titl ### More on Queries with Contentful and Gatsby It is strongly recommended that you take a look at how data flows in a real Contentful and Gatsby application to fully understand how the queries, Node.js functions and React components all come together. Check out the example site at -[using-contentful.gatsbyjs.org](https://using-contentful.gatsbyjs.org/). +[using-contentful.gatsbyjs.com](https://using-contentful.gatsbyjs.com/). ## Displaying responsive image with gatsby-plugin-image diff --git a/packages/gatsby-source-contentful/src/__tests__/normalize.js b/packages/gatsby-source-contentful/src/__tests__/normalize.js index 45d6699205c3b..0f6ca5884f8ae 100644 --- a/packages/gatsby-source-contentful/src/__tests__/normalize.js +++ b/packages/gatsby-source-contentful/src/__tests__/normalize.js @@ -20,7 +20,7 @@ const { } = require(`./data.json`) const conflictFieldPrefix = `contentful_test` -// restrictedNodeFields from here https://www.gatsbyjs.org/docs/node-interface/ +// restrictedNodeFields from here https://www.gatsbyjs.com/docs/node-interface/ const restrictedNodeFields = [ `id`, `children`, diff --git a/packages/gatsby-source-contentful/src/source-nodes.js b/packages/gatsby-source-contentful/src/source-nodes.js index 1697dcb254ebf..29ab446b43f82 100644 --- a/packages/gatsby-source-contentful/src/source-nodes.js +++ b/packages/gatsby-source-contentful/src/source-nodes.js @@ -17,7 +17,7 @@ import { CODES } from "./report" const conflictFieldPrefix = `contentful` -// restrictedNodeFields from here https://www.gatsbyjs.org/docs/node-interface/ +// restrictedNodeFields from here https://www.gatsbyjs.com/docs/node-interface/ const restrictedNodeFields = [ `children`, `contentful_id`, diff --git a/packages/gatsby-source-drupal/README.md b/packages/gatsby-source-drupal/README.md index 732653c6932fc..2d11967b42fbf 100644 --- a/packages/gatsby-source-drupal/README.md +++ b/packages/gatsby-source-drupal/README.md @@ -7,7 +7,7 @@ It pulls data from Drupal 8 sites with the An example site built with the headless Drupal distro [ContentaCMS](https://twitter.com/contentacms) is at -https://using-drupal.gatsbyjs.org/ +https://using-drupal.gatsbyjs.com/ `apiBase` Option allows changing the API entry point depending on the version of jsonapi used by your Drupal instance. The default value is `jsonapi`, which has @@ -402,4 +402,4 @@ You can query nodes created from Drupal like the following: ``` [dotenv]: https://github.com/motdotla/dotenv -[envvars]: https://www.gatsbyjs.org/docs/environment-variables +[envvars]: https://www.gatsbyjs.com/docs/environment-variables diff --git a/packages/gatsby-source-filesystem/README.md b/packages/gatsby-source-filesystem/README.md index 7853d4ed30234..2501bbe147393 100644 --- a/packages/gatsby-source-filesystem/README.md +++ b/packages/gatsby-source-filesystem/README.md @@ -130,7 +130,7 @@ createFilePath({ #### Example usage -The following is taken from [Gatsby Tutorial, Part Seven](https://www.gatsbyjs.org/tutorial/part-7/) and is used to create URL slugs for markdown pages. +The following is taken from [Gatsby Tutorial, Part Seven](https://www.gatsbyjs.com/tutorial/part-7/) and is used to create URL slugs for markdown pages. ```javascript const { createFilePath } = require(`gatsby-source-filesystem`) diff --git a/packages/gatsby-source-filesystem/index.d.ts b/packages/gatsby-source-filesystem/index.d.ts index d7c02db11d0f2..b2e78493450c6 100644 --- a/packages/gatsby-source-filesystem/index.d.ts +++ b/packages/gatsby-source-filesystem/index.d.ts @@ -1,19 +1,19 @@ import { Node, Store, NodePluginArgs } from "gatsby" /** - * @see https://www.gatsbyjs.org/packages/gatsby-source-filesystem/?=files#createfilepath + * @see https://www.gatsbyjs.com/packages/gatsby-source-filesystem/?=files#createfilepath */ export function createFilePath(args: CreateFilePathArgs): string /** - * @see https://www.gatsbyjs.org/packages/gatsby-source-filesystem/?=files#createremotefilenode + * @see https://www.gatsbyjs.com/packages/gatsby-source-filesystem/?=files#createremotefilenode */ export function createRemoteFileNode( args: CreateRemoteFileNodeArgs ): Promise /** - * @see https://www.gatsbyjs.org/packages/gatsby-source-filesystem/?=files#createfilenodefrombuffer + * @see https://www.gatsbyjs.com/packages/gatsby-source-filesystem/?=files#createfilenodefrombuffer */ export function createFileNodeFromBuffer( args: CreateFileNodeFromBufferArgs @@ -103,7 +103,7 @@ export interface FileSystemConfig { } /** - * @see https://www.gatsbyjs.org/packages/gatsby-source-filesystem/?=filesy#options + * @see https://www.gatsbyjs.com/packages/gatsby-source-filesystem/?=filesy#options */ interface FileSystemOptions { name: string diff --git a/packages/gatsby-source-filesystem/src/gatsby-node.js b/packages/gatsby-source-filesystem/src/gatsby-node.js index 9b319120af77c..4bbe8dc5988de 100644 --- a/packages/gatsby-source-filesystem/src/gatsby-node.js +++ b/packages/gatsby-source-filesystem/src/gatsby-node.js @@ -171,7 +171,7 @@ exports.sourceNodes = (api, pluginOptions) => { The path passed to gatsby-source-filesystem does not exist on your file system: ${pluginOptions.path} Please pick a path to an existing directory. -See docs here - https://www.gatsbyjs.org/packages/gatsby-source-filesystem/ +See docs here - https://www.gatsbyjs.com/packages/gatsby-source-filesystem/ `) } diff --git a/packages/gatsby-source-lever/src/normalize.js b/packages/gatsby-source-lever/src/normalize.js index 9ad163377cb7b..c09d090408566 100644 --- a/packages/gatsby-source-lever/src/normalize.js +++ b/packages/gatsby-source-lever/src/normalize.js @@ -1,7 +1,7 @@ const deepMapKeys = require(`deep-map-keys`) const conflictFieldPrefix = `lever_` -// restrictedNodeFields from here https://www.gatsbyjs.org/docs/node-interface/ +// restrictedNodeFields from here https://www.gatsbyjs.com/docs/node-interface/ const restrictedNodeFields = [`id`, `children`, `parent`, `fields`, `internal`] /** diff --git a/packages/gatsby-transformer-documentationjs/README.md b/packages/gatsby-transformer-documentationjs/README.md index 6b69b82e25561..419dc32e64fab 100644 --- a/packages/gatsby-transformer-documentationjs/README.md +++ b/packages/gatsby-transformer-documentationjs/README.md @@ -4,8 +4,8 @@ Uses [Documentation.js](http://documentation.js.org/) to extract code metadata (JSDocs is supported currently though Flow is also supported by Documentation.js and can be added to this plugin as well). -It's used on gatsbyjs.org and can be seen in use on several pages there e.g. -[https://www.gatsbyjs.org/docs/node-apis/](https://www.gatsbyjs.org/docs/node-apis/) +It's used on gatsbyjs.com and can be seen in use on several pages there e.g. +[https://www.gatsbyjs.com/docs/node-apis/](https://www.gatsbyjs.com/docs/node-apis/) ## Install diff --git a/packages/gatsby-transformer-remark/README.md b/packages/gatsby-transformer-remark/README.md index 6c012fe738ebe..52a0a2c6e797e 100644 --- a/packages/gatsby-transformer-remark/README.md +++ b/packages/gatsby-transformer-remark/README.md @@ -34,7 +34,7 @@ plugins: A full explanation of how to use markdown in Gatsby can be found here: [Adding Markdown Pages](https://www.gatsbyjs.com/docs/how-to/routing/adding-markdown-pages/) -There are many Gatsby Remark plugins which you can install to customize how Markdown is processed. Many of them are demoed at https://using-remark.gatsbyjs.org/. See also the [source code for using-remark](https://github.com/gatsbyjs/gatsby/tree/master/examples/using-remark). +There are many Gatsby Remark plugins which you can install to customize how Markdown is processed. Many of them are demoed at https://using-remark.gatsbyjs.com/. See also the [source code for using-remark](https://github.com/gatsbyjs/gatsby/tree/master/examples/using-remark). ## Parsing algorithm diff --git a/packages/gatsby-transformer-screenshot/README.md b/packages/gatsby-transformer-screenshot/README.md index f9b421371cb1f..09f551f3dc962 100644 --- a/packages/gatsby-transformer-screenshot/README.md +++ b/packages/gatsby-transformer-screenshot/README.md @@ -94,7 +94,7 @@ You can use placeholder image by setting `GATSBY_SCREENSHOT_PLACEHOLDER` environ GATSBY_SCREENSHOT_PLACEHOLDER=true gatsby develop ``` -or by using [`dotenv`](https://www.gatsbyjs.org/docs/environment-variables/#server-side-nodejs) in your `gatsby-config.js` and adding `GATSBY_SCREENSHOT_PLACEHOLDER` to `.env.development` file in root of your project: +or by using [`dotenv`](https://www.gatsbyjs.com/docs/environment-variables/#server-side-nodejs) in your `gatsby-config.js` and adding `GATSBY_SCREENSHOT_PLACEHOLDER` to `.env.development` file in root of your project: ```shell:title=.env.development GATSBY_SCREENSHOT_PLACEHOLDER=true diff --git a/packages/gatsby-transformer-sharp/README.md b/packages/gatsby-transformer-sharp/README.md index 230f9f079a58d..d3c3a42349e39 100644 --- a/packages/gatsby-transformer-sharp/README.md +++ b/packages/gatsby-transformer-sharp/README.md @@ -5,7 +5,7 @@ Creates `ImageSharp` nodes from image types that are supported by the fields in their GraphQL types for processing your images in a variety of ways including resizing, cropping, and creating responsive images. -[Live demo](https://image-processing.gatsbyjs.org/) +[Live demo](https://image-processing.gatsbyjs.com/) ([source](https://github.com/gatsbyjs/gatsby/tree/master/examples/image-processing)) ## Install @@ -23,7 +23,7 @@ module.exports = { Please note that you must have a source plugin (which brings in images) installed in your project. Otherwise, no `ImageSharp` nodes can be created for your files. Examples would be [`gatsby-source-filesystem`](/plugins/gatsby-source-filesystem) or source plugins for (headless) CMSs like [`gatsby-source-wordpress`](/plugins/gatsby-source-wordpress). -**Note**: An exception to this is when using [`gatsby-source-contentful`](/plugins/gatsby-source-contentful/), as the source plugin and the assets are not [downloaded to the local filesystem](https://www.gatsbyjs.org/packages/gatsby-source-contentful/#download-assets-for-static-distribution). By default, the `gatsby-source-contentful` plugin creates a `ContentfulAsset` node for every image with links to Contentful’s CDN, therefore it is not necessary to use `gatsby-transformer-sharp` together with `gatsby-source-contentful`. +**Note**: An exception to this is when using [`gatsby-source-contentful`](/plugins/gatsby-source-contentful/), as the source plugin and the assets are not [downloaded to the local filesystem](https://www.gatsbyjs.com/packages/gatsby-source-contentful/#download-assets-for-static-distribution). By default, the `gatsby-source-contentful` plugin creates a `ContentfulAsset` node for every image with links to Contentful’s CDN, therefore it is not necessary to use `gatsby-transformer-sharp` together with `gatsby-source-contentful`. ## Parsing algorithm diff --git a/packages/gatsby/CHANGELOG.md b/packages/gatsby/CHANGELOG.md index 44d01af447c62..f94a12068df0e 100644 --- a/packages/gatsby/CHANGELOG.md +++ b/packages/gatsby/CHANGELOG.md @@ -7635,7 +7635,7 @@ Our first beta!!! 🎉 ### Added - Allow for gatsby-remark-smartypants options #1166 @mitchejj -- New design (for gatsbyjs.org) + new home page #1170 @kyleamathews +- New design (for gatsbyjs.com) + new home page #1170 @kyleamathews - Add ability to locally define plugins #1126 @0x80 - Add rough draft for docs for creating source plugins #1159 @kyleamathews - Optimizations around prefetching page resources #1133 @kyleamathews @@ -7705,45 +7705,45 @@ Our first beta!!! 🎉 - Add new plugin for extracting JSDocs information from JavaScript files using documentation.js #1053 @kyleamathews - Add new API spec (rough draft) @kyleamathews - https://www.gatsbyjs.org/docs/api-specification/ + https://www.gatsbyjs.com/docs/api-specification/ - Add new API reference pages @kyleamathews e.g. - https://www.gatsbyjs.org/docs/node-apis/ + https://www.gatsbyjs.com/docs/node-apis/ - Add "duotone" image processing option to gatsby-plugin-sharp #1047 @fk - Add example site for image processing @fk - https://image-processing.gatsbyjs.org/ + https://image-processing.gatsbyjs.com/ - Add example site for css-in-js library Glamor @kyleamathews - https://using-glamor.gatsbyjs.org/ + https://using-glamor.gatsbyjs.com/ - Add example site for css-in-js library Styled Components @kyleamathews - https://using-styled-components.gatsbyjs.org/ + https://using-styled-components.gatsbyjs.com/ ### Changed -#### Grand big API renaming based on our new API spec https://www.gatsbyjs.org/docs/api-specification/ +#### Grand big API renaming based on our new API spec https://www.gatsbyjs.com/docs/api-specification/ API changes: -[Action creators](https://www.gatsbyjs.org/docs/bound-action-creators/): +[Action creators](https://www.gatsbyjs.com/docs/bound-action-creators/): - `upsertPage` is now `createPage` - `addFieldToNode` is now `createNodeField` - `deletePageByPath` is now `deletePage` - `addNodeToParent` is now `createParentChildLink` -[gatsby-browser.js APIs](https://www.gatsbyjs.org/docs/browser-apis/): +[gatsby-browser.js APIs](https://www.gatsbyjs.com/docs/browser-apis/): - `clientEntry` is now `onClientEntry` -[gatsby-node.js APIs](https://www.gatsbyjs.org/docs/node-apis/): +[gatsby-node.js APIs](https://www.gatsbyjs.com/docs/node-apis/): - `onNodeCreate` is now `onCreateNode` - `onUpsertPage` is now `onCreatePage` - `extendNodeType` is now `setFieldsOnGraphQLNodeType` -[gatsby-ssr.js APIs](https://www.gatsbyjs.org/docs/ssr-apis/): +[gatsby-ssr.js APIs](https://www.gatsbyjs.com/docs/ssr-apis/): - `modifyHeadComponents` and `modifyPostBodyComponents` were removed in favor of a new API - [`onRenderBody`](https://www.gatsbyjs.org/docs/ssr-apis/#onRenderBody). + [`onRenderBody`](https://www.gatsbyjs.com/docs/ssr-apis/#onRenderBody). - `replaceServerBodyRender` is now `replaceRenderer` ### Fixed @@ -7873,7 +7873,7 @@ export const pageQuery = graphql` ### Added -- Did the intitial build of the new gatsbyjs.org! It's in the `www` subdirectory +- Did the intitial build of the new gatsbyjs.com! It's in the `www` subdirectory on the 1.0 branch and is built on each push! That's my kind of integration testing :-) You can see the early version of the site at https://gatsbyjs.netlify.app/. PRs welcome! diff --git a/packages/gatsby/cache-dir/__tests__/dev-loader.js b/packages/gatsby/cache-dir/__tests__/dev-loader.js index 23ca7fdf85b39..c4d6a17620105 100644 --- a/packages/gatsby/cache-dir/__tests__/dev-loader.js +++ b/packages/gatsby/cache-dir/__tests__/dev-loader.js @@ -438,7 +438,7 @@ describe(`Dev loader`, () => { expect(consoleErrorSpy).toHaveBeenCalledTimes(1) expect(consoleErrorSpy).toHaveBeenCalledWith( - `404 page could not be found. Checkout https://www.gatsbyjs.org/docs/how-to/adding-common-features/add-404-page/` + `404 page could not be found. Checkout https://www.gatsbyjs.com/docs/how-to/adding-common-features/add-404-page/` ) mock.error(defaultXHRMockErrorHandler) diff --git a/packages/gatsby/cache-dir/__tests__/static-entry.js b/packages/gatsby/cache-dir/__tests__/static-entry.js index eee0027d7cc22..5c646917afed5 100644 --- a/packages/gatsby/cache-dir/__tests__/static-entry.js +++ b/packages/gatsby/cache-dir/__tests__/static-entry.js @@ -497,15 +497,15 @@ describe(`sanitizeComponents`, () => { }) it(`strips assetPrefix for manifest link`, () => { - global.__PATH_PREFIX__ = `https://gatsbyjs.org/blog` + global.__PATH_PREFIX__ = `https://gatsbyjs.com/blog` global.__BASE_PATH__ = `/blog` - global.__ASSET_PREFIX__ = `https://gatsbyjs.org` + global.__ASSET_PREFIX__ = `https://gatsbyjs.com` const sanitizedComponents = sanitizeComponents([ , ]) expect(sanitizedComponents[0].props.href).toBe(`/blog/manifest.webmanifest`) diff --git a/packages/gatsby/cache-dir/dev-loader.js b/packages/gatsby/cache-dir/dev-loader.js index b6c16104a7eab..ddc6dad90f491 100644 --- a/packages/gatsby/cache-dir/dev-loader.js +++ b/packages/gatsby/cache-dir/dev-loader.js @@ -93,7 +93,7 @@ class DevLoader extends BaseLoader { rawPath !== `/dev-404-page/` ) { console.error( - `404 page could not be found. Checkout https://www.gatsbyjs.org/docs/how-to/adding-common-features/add-404-page/` + `404 page could not be found. Checkout https://www.gatsbyjs.com/docs/how-to/adding-common-features/add-404-page/` ) return this.loadPageDataJson(`/dev-404-page/`).then(result => Object.assign({}, data, result) diff --git a/packages/gatsby/index.d.ts b/packages/gatsby/index.d.ts index dc9b48971ac09..8a31c5353bffc 100644 --- a/packages/gatsby/index.d.ts +++ b/packages/gatsby/index.d.ts @@ -185,12 +185,12 @@ export interface PageRendererProps { } /** - * PageRenderer's constructor [loads the page resources](https://www.gatsbyjs.org/docs/production-app/#load-page-resources) for the path. + * PageRenderer's constructor [loads the page resources](https://www.gatsbyjs.com/docs/production-app/#load-page-resources) for the path. * - * On first load though, these will have already been requested from the server by `` in the page's original HTML (see [Link Preloads](https://www.gatsbyjs.org/docs/how-code-splitting-works/#construct-link-and-script-tags-for-current-page) in HTML Generation Docs). + * On first load though, these will have already been requested from the server by `` in the page's original HTML (see [Link Preloads](https://www.gatsbyjs.com/docs/how-code-splitting-works/#construct-link-and-script-tags-for-current-page) in HTML Generation Docs). * The loaded page resources includes the imported component, with which we create the actual page component using [React.createElement()](https://reactjs.org/docs/react-api.html). This element is returned to our RouteHandler which hands it off to Reach Router for rendering. * - * @see https://www.gatsbyjs.org/docs/production-app/#page-rendering + * @see https://www.gatsbyjs.com/docs/production-app/#page-rendering */ export class PageRenderer extends React.Component {} @@ -209,7 +209,7 @@ export interface StaticQueryProps { * - StaticQuery does not accept variables (hence the name "static"), but can be used in _any_ component, including pages * - StaticQuery does not work with raw React.createElement calls; please use JSX, e.g. `` * - * @see https://www.gatsbyjs.org/docs/static-query/ + * @see https://www.gatsbyjs.com/docs/static-query/ */ export class StaticQuery extends React.Component< @@ -221,14 +221,14 @@ export class StaticQuery extends React.Component< * * During the Gatsby build process, GraphQL queries are pulled out of the original source for parsing. * - * @see https://www.gatsbyjs.org/docs/page-query#how-does-the-graphql-tag-work + * @see https://www.gatsbyjs.com/docs/page-query#how-does-the-graphql-tag-work */ export const graphql: (query: TemplateStringsArray) => StaticQueryDocument /** * Gatsby configuration API. * - * @see https://www.gatsbyjs.org/docs/gatsby-config/ + * @see https://www.gatsbyjs.com/docs/gatsby-config/ */ export interface GatsbyConfig { /** When you want to reuse common pieces of data across the site (for example, your site title), you can store that here. */ @@ -250,7 +250,7 @@ export interface GatsbyConfig { jsxImportSource?: string /** * Setting the proxy config option will tell the develop server to proxy any unknown requests to your specified server. - * @see https://www.gatsbyjs.org/docs/api-proxy/ + * @see https://www.gatsbyjs.com/docs/api-proxy/ * */ proxy?: { prefix: string @@ -263,7 +263,7 @@ export interface GatsbyConfig { /** * Gatsby API for Node.js. * - * @see https://www.gatsbyjs.org/docs/node-apis/ + * @see https://www.gatsbyjs.com/docs/node-apis/ */ export interface GatsbyNode< TNode extends Record = Record, @@ -274,7 +274,7 @@ export interface GatsbyNode< * sourcing and transformation of nodes plus creation of the GraphQL schema are * complete so you can query your data in order to create pages. * - * @see https://www.gatsbyjs.org/docs/node-apis/#createPages + * @see https://www.gatsbyjs.com/docs/node-apis/#createPages */ createPages?( args: CreatePagesArgs & { @@ -342,7 +342,7 @@ export interface GatsbyNode< * transform nodes created by other plugins should implement this API. * * See also the documentation for `createNode` - * and [`createNodeField`](https://www.gatsbyjs.org/docs/actions/#createNodeField) + * and [`createNodeField`](https://www.gatsbyjs.com/docs/actions/#createNodeField) * @example * exports.onCreateNode = ({ node, actions }) => { * const { createNode, createNodeField } = actions @@ -375,7 +375,7 @@ export interface GatsbyNode< * for programmatically manipulating pages created by other plugins e.g. * if you want paths without trailing slashes. * - * See the guide [Creating and Modifying Pages](https://www.gatsbyjs.org/docs/creating-and-modifying-pages/) + * See the guide [Creating and Modifying Pages](https://www.gatsbyjs.com/docs/creating-and-modifying-pages/) * for more on this API. */ onCreatePage?( @@ -386,7 +386,7 @@ export interface GatsbyNode< /** * Let plugins extend/mutate the site's webpack configuration. - * @see https://www.gatsbyjs.org/docs/node-apis/#onCreateWebpackConfig + * @see https://www.gatsbyjs.com/docs/node-apis/#onCreateWebpackConfig */ onCreateWebpackConfig?( args: CreateWebpackConfigArgs, @@ -488,7 +488,7 @@ export interface GatsbyNode< * * Many transformer plugins use this to add fields that take arguments. * - * @see https://www.gatsbyjs.org/docs/node-apis/#setFieldsOnGraphQLNodeType + * @see https://www.gatsbyjs.com/docs/node-apis/#setFieldsOnGraphQLNodeType */ setFieldsOnGraphQLNodeType?( args: SetFieldsOnGraphQLNodeTypeArgs, @@ -504,7 +504,7 @@ export interface GatsbyNode< * will be called exactly once after all of your source plugins have finished * creating nodes. * - * @see https://www.gatsbyjs.org/docs/node-apis/#sourceNodes + * @see https://www.gatsbyjs.com/docs/node-apis/#sourceNodes */ sourceNodes?( args: SourceNodesArgs, @@ -560,7 +560,7 @@ export interface GatsbyNode< * * This API runs immediately before schema generation. For modifications of the generated schema, e.g. * to customize added third-party types, use the createResolvers API. - * @see https://www.gatsbyjs.org/docs/node-apis/#createSchemaCustomization + * @see https://www.gatsbyjs.com/docs/node-apis/#createSchemaCustomization */ createSchemaCustomization?( args: CreateSchemaCustomizationArgs, @@ -578,7 +578,7 @@ export interface GatsbyNode< /** * Gatsby browser API. * - * @see https://www.gatsbyjs.org/docs/browser-apis/ + * @see https://www.gatsbyjs.com/docs/browser-apis/ */ export interface GatsbyBrowser< DataType = Record, @@ -644,7 +644,7 @@ export interface GatsbyBrowser< /** * Gatsby server-side rendering API. * - * @see https://www.gatsbyjs.org/docs/ssr-apis/ + * @see https://www.gatsbyjs.com/docs/ssr-apis/ */ export interface GatsbySSR< DataSet = Record, @@ -737,7 +737,7 @@ export interface GatsbySSR< * This is useful for setting wrapper component around pages that won't get * unmounted on page change. For setting Provider components use `wrapRootElement`. * - * _Note:_ [There is equivalent hook in Browser API](https://www.gatsbyjs.org/docs/browser-apis/#wrapPageElement) + * _Note:_ [There is equivalent hook in Browser API](https://www.gatsbyjs.com/docs/browser-apis/#wrapPageElement) * @example * const React = require("react") * const Layout = require("./src/components/layout") @@ -759,7 +759,7 @@ export interface GatsbySSR< * This is useful to setup any Providers component that will wrap your application. * For setting persistent UI elements around pages use `wrapPageElement`. * - * _Note:_ [There is equivalent hook in Browser API](https://www.gatsbyjs.org/docs/browser-apis/#wrapRootElement) + * _Note:_ [There is equivalent hook in Browser API](https://www.gatsbyjs.com/docs/browser-apis/#wrapRootElement) * @example * const React = require("react") * const { Provider } = require("react-redux") @@ -1133,7 +1133,7 @@ export interface NodePluginArgs { /** * Set of utilities that allow adding more detailed tracing for plugins. * Check - * [Performance tracing](https://www.gatsbyjs.org/docs/performance-tracing) + * [Performance tracing](https://www.gatsbyjs.com/docs/performance-tracing) * page for more details. */ tracing: Tracing @@ -1166,10 +1166,10 @@ export interface BuildArgs extends ParentSpanPluginArgs { } export interface Actions { - /** @see https://www.gatsbyjs.org/docs/actions/#deletePage */ + /** @see https://www.gatsbyjs.com/docs/actions/#deletePage */ deletePage(this: void, args: { path: string; component: string }): void - /** @see https://www.gatsbyjs.org/docs/actions/#createPage */ + /** @see https://www.gatsbyjs.com/docs/actions/#createPage */ createPage>( this: void, args: Page, @@ -1177,10 +1177,10 @@ export interface Actions { option?: ActionOptions ): void - /** @see https://www.gatsbyjs.org/docs/actions/#deletePage */ + /** @see https://www.gatsbyjs.com/docs/actions/#deletePage */ deleteNode(node: NodeInput, plugin?: ActionPlugin): void - /** @see https://www.gatsbyjs.org/docs/actions/#createNode */ + /** @see https://www.gatsbyjs.com/docs/actions/#createNode */ createNode>( this: void, node: NodeInput & TNode, @@ -1188,10 +1188,10 @@ export interface Actions { options?: ActionOptions ): void - /** @see https://www.gatsbyjs.org/docs/actions/#touchNode */ + /** @see https://www.gatsbyjs.com/docs/actions/#touchNode */ touchNode(node: NodeInput, plugin?: ActionPlugin): void - /** @see https://www.gatsbyjs.org/docs/actions/#createNodeField */ + /** @see https://www.gatsbyjs.com/docs/actions/#createNodeField */ createNodeField( this: void, args: { @@ -1203,7 +1203,7 @@ export interface Actions { options?: ActionOptions ): void - /** @see https://www.gatsbyjs.org/docs/actions/#createParentChildLink */ + /** @see https://www.gatsbyjs.com/docs/actions/#createParentChildLink */ createParentChildLink( this: void, args: { parent: Node; child: NodeInput }, @@ -1221,37 +1221,37 @@ export interface Actions { plugin?: ActionPlugin ): void - /** @see https://www.gatsbyjs.org/docs/actions/#setWebpackConfig */ + /** @see https://www.gatsbyjs.com/docs/actions/#setWebpackConfig */ setWebpackConfig(this: void, config: object, plugin?: ActionPlugin): void - /** @see https://www.gatsbyjs.org/docs/actions/#replaceWebpackConfig */ + /** @see https://www.gatsbyjs.com/docs/actions/#replaceWebpackConfig */ replaceWebpackConfig(this: void, config: object, plugin?: ActionPlugin): void - /** @see https://www.gatsbyjs.org/docs/actions/#setBabelOptions */ + /** @see https://www.gatsbyjs.com/docs/actions/#setBabelOptions */ setBabelOptions(this: void, options: object, plugin?: ActionPlugin): void - /** @see https://www.gatsbyjs.org/docs/actions/#setBabelPlugin */ + /** @see https://www.gatsbyjs.com/docs/actions/#setBabelPlugin */ setBabelPlugin( this: void, config: { name: string; options: object }, plugin?: ActionPlugin ): void - /** @see https://www.gatsbyjs.org/docs/actions/#setBabelPreset */ + /** @see https://www.gatsbyjs.com/docs/actions/#setBabelPreset */ setBabelPreset( this: void, config: { name: string; options: object }, plugin?: ActionPlugin ): void - /** @see https://www.gatsbyjs.org/docs/actions/#createJob */ + /** @see https://www.gatsbyjs.com/docs/actions/#createJob */ createJob( this: void, job: Record & { id: string }, plugin?: ActionPlugin ): void - /** @see https://www.gatsbyjs.org/docs/actions/#createJobV2 */ + /** @see https://www.gatsbyjs.com/docs/actions/#createJobV2 */ createJobV2( this: void, job: { @@ -1263,24 +1263,24 @@ export interface Actions { plugin?: ActionPlugin ): Promise - /** @see https://www.gatsbyjs.org/docs/actions/#setJob */ + /** @see https://www.gatsbyjs.com/docs/actions/#setJob */ setJob( this: void, job: Record & { id: string }, plugin?: ActionPlugin ): void - /** @see https://www.gatsbyjs.org/docs/actions/#endJob */ + /** @see https://www.gatsbyjs.com/docs/actions/#endJob */ endJob(this: void, job: { id: string }, plugin?: ActionPlugin): void - /** @see https://www.gatsbyjs.org/docs/actions/#setPluginStatus */ + /** @see https://www.gatsbyjs.com/docs/actions/#setPluginStatus */ setPluginStatus( this: void, status: Record, plugin?: ActionPlugin ): void - /** @see https://www.gatsbyjs.org/docs/actions/#createRedirect */ + /** @see https://www.gatsbyjs.com/docs/actions/#createRedirect */ createRedirect( this: void, redirect: { @@ -1296,7 +1296,7 @@ export interface Actions { plugin?: ActionPlugin ): void - /** @see https://www.gatsbyjs.org/docs/actions/#addThirdPartySchema */ + /** @see https://www.gatsbyjs.com/docs/actions/#addThirdPartySchema */ addThirdPartySchema( this: void, args: { schema: object }, @@ -1304,7 +1304,7 @@ export interface Actions { traceId?: string ): void - /** @see https://www.gatsbyjs.org/docs/actions/#createTypes */ + /** @see https://www.gatsbyjs.com/docs/actions/#createTypes */ createTypes( this: void, types: @@ -1316,7 +1316,7 @@ export interface Actions { traceId?: string ): void - /** @see https://www.gatsbyjs.org/docs/actions/#createFieldExtension */ + /** @see https://www.gatsbyjs.com/docs/actions/#createFieldExtension */ createFieldExtension( this: void, extension: object, diff --git a/packages/gatsby/src/bootstrap/load-plugins/validate.ts b/packages/gatsby/src/bootstrap/load-plugins/validate.ts index db662b9e5a787..7dffe0706b5cf 100644 --- a/packages/gatsby/src/bootstrap/load-plugins/validate.ts +++ b/packages/gatsby/src/bootstrap/load-plugins/validate.ts @@ -483,7 +483,7 @@ export const handleMultipleReplaceRenderers = ({ reporter.warn(`replaceRenderer API found in these plugins:`) reporter.warn(rendererPlugins.join(`, `)) reporter.warn( - `This might be an error, see: https://www.gatsbyjs.org/docs/debugging-replace-renderer-api/` + `This might be an error, see: https://www.gatsbyjs.com/docs/debugging-replace-renderer-api/` ) } else { console.log(``) @@ -493,7 +493,7 @@ export const handleMultipleReplaceRenderers = ({ reporter.error(rendererPlugins.join(`, `)) reporter.error(`This will break your build`) reporter.error( - `See: https://www.gatsbyjs.org/docs/debugging-replace-renderer-api/` + `See: https://www.gatsbyjs.com/docs/debugging-replace-renderer-api/` ) if (process.env.NODE_ENV === `production`) process.exit(1) } diff --git a/packages/gatsby/src/commands/build.ts b/packages/gatsby/src/commands/build.ts index f2e2aec0942c7..8ea53cfeabd62 100644 --- a/packages/gatsby/src/commands/build.ts +++ b/packages/gatsby/src/commands/build.ts @@ -81,7 +81,7 @@ module.exports = async function build( if (program.profile) { report.warn( - `React Profiling is enabled. This can have a performance impact. See https://www.gatsbyjs.org/docs/profiling-site-performance-with-react-profiler/#performance-impact` + `React Profiling is enabled. This can have a performance impact. See https://www.gatsbyjs.com/docs/profiling-site-performance-with-react-profiler/#performance-impact` ) } diff --git a/packages/gatsby/src/internal-plugins/prod-404-500/gatsby-node.js b/packages/gatsby/src/internal-plugins/prod-404-500/gatsby-node.js index 5a4cfb0fa07eb..3d59d3efc36c9 100644 --- a/packages/gatsby/src/internal-plugins/prod-404-500/gatsby-node.js +++ b/packages/gatsby/src/internal-plugins/prod-404-500/gatsby-node.js @@ -8,7 +8,7 @@ emitter.on(`CREATE_PAGE`, action => { // Copy /404/ to /404.html and /500/ to /500.html. Many static site hosts expect // site 404 pages to be named this. In addition, with Rendering Engines there might // be runtime errors which would fallback to "/500.html" page. - // https://www.gatsbyjs.org/docs/how-to/adding-common-features/add-404-page/ + // https://www.gatsbyjs.com/docs/how-to/adding-common-features/add-404-page/ const result = /^\/?(404|500)\/?$/.exec(action.payload.path) if (result && result.length > 1) { const status = result[1] diff --git a/packages/gatsby/src/query/query-watcher.ts b/packages/gatsby/src/query/query-watcher.ts index ef4bae7168fe3..215ad5bd464d4 100644 --- a/packages/gatsby/src/query/query-watcher.ts +++ b/packages/gatsby/src/query/query-watcher.ts @@ -269,7 +269,7 @@ export const updateStateAndRunQueries = async ( reason. If the failing component(s) is a regular component and not intended to be a page - component, you generally want to use a (https://gatsbyjs.org/docs/static-query) + component, you generally want to use a (https://gatsbyjs.com/docs/static-query) instead of exporting a page query. If you're more experienced with GraphQL, you can also export GraphQL diff --git a/packages/gatsby/src/schema/__tests__/__snapshots__/rebuild-schema.js.snap b/packages/gatsby/src/schema/__tests__/__snapshots__/rebuild-schema.js.snap index 4eaabad246f4a..bb1ea4b22e958 100644 --- a/packages/gatsby/src/schema/__tests__/__snapshots__/rebuild-schema.js.snap +++ b/packages/gatsby/src/schema/__tests__/__snapshots__/rebuild-schema.js.snap @@ -1829,7 +1829,7 @@ If you have explicitly defined a type for those fields, you can safely ignore th Otherwise, Gatsby will omit those fields from the GraphQL schema. If you know all field types in advance, the best strategy is to explicitly define them with the \`createTypes\` action, and skip inference with the \`@dontInfer\` directive. -See https://www.gatsbyjs.org/docs/actions/#createTypes", +See https://www.gatsbyjs.com/docs/actions/#createTypes", ], ], "results": Array [ diff --git a/packages/gatsby/src/schema/infer/type-conflict-reporter.ts b/packages/gatsby/src/schema/infer/type-conflict-reporter.ts index bdad7242cc226..af54563176319 100644 --- a/packages/gatsby/src/schema/infer/type-conflict-reporter.ts +++ b/packages/gatsby/src/schema/infer/type-conflict-reporter.ts @@ -135,7 +135,7 @@ class TypeConflictReporter { `If you know all field types in advance, the best strategy is to ` + `explicitly define them with the \`createTypes\` action, and skip ` + `inference with the \`@dontInfer\` directive.\n` + - `See https://www.gatsbyjs.org/docs/actions/#createTypes` + `See https://www.gatsbyjs.com/docs/actions/#createTypes` ) this.entries.forEach(entry => entry.printEntry()) } diff --git a/packages/gatsby/src/utils/__tests__/api-runner-node.js b/packages/gatsby/src/utils/__tests__/api-runner-node.js index a97ca1e484ab8..7a2d4644f8345 100644 --- a/packages/gatsby/src/utils/__tests__/api-runner-node.js +++ b/packages/gatsby/src/utils/__tests__/api-runner-node.js @@ -298,7 +298,7 @@ describe(`api-runner-node`, () => { 1337: { text: context => `Error text is ${context.someProp}`, level: `ERROR`, - docsUrl: `https://www.gatsbyjs.org/docs/gatsby-cli/#new`, + docsUrl: `https://www.gatsbyjs.com/docs/gatsby-cli/#new`, }, }) @@ -341,7 +341,7 @@ describe(`api-runner-node`, () => { "test-plugin-plugin-prefixes_1337": { text: {}, level: `ERROR`, - docsUrl: `https://www.gatsbyjs.org/docs/gatsby-cli/#new`, + docsUrl: `https://www.gatsbyjs.com/docs/gatsby-cli/#new`, }, }) }) diff --git a/packages/gatsby/src/utils/api-node-helpers-docs.js b/packages/gatsby/src/utils/api-node-helpers-docs.js index 8df66b14c95f1..59280494ec078 100644 --- a/packages/gatsby/src/utils/api-node-helpers-docs.js +++ b/packages/gatsby/src/utils/api-node-helpers-docs.js @@ -294,7 +294,7 @@ module.exports.createNodeId = true; /** * Set of utilities that allow adding more detailed tracing for plugins. * Check - * [Performance tracing](https://www.gatsbyjs.org/docs/performance-tracing) + * [Performance tracing](https://www.gatsbyjs.com/docs/performance-tracing) * page for more details. * @type {GatsbyTracing} */ diff --git a/peril/tests/validate-yaml/validate-yaml-creators.test.ts b/peril/tests/validate-yaml/validate-yaml-creators.test.ts index d323196c7a86e..41bbe63dca912 100644 --- a/peril/tests/validate-yaml/validate-yaml-creators.test.ts +++ b/peril/tests/validate-yaml/validate-yaml-creators.test.ts @@ -70,7 +70,7 @@ describe("a new PR", () => { description: lorem ipsum location: moon github: https://github.com/gatsbyjs - website: https://www.gatsbyjs.org/ + website: https://www.gatsbyjs.com/ for_hire: false portfolio: true hiring: false diff --git a/scripts/i18n/PROGRESS.template.md b/scripts/i18n/PROGRESS.template.md index bc47e7ae768f4..7782311654632 100644 --- a/scripts/i18n/PROGRESS.template.md +++ b/scripts/i18n/PROGRESS.template.md @@ -6,7 +6,7 @@ To translate a page: 2. Comment below with the name of the page you would like to translate. **Please take only one page at a time**. 3. Clone this repo, translate your page, and submit a pull request! -Before contributing, please read the [translation guide](https://www.gatsbyjs.org/contributing/gatsby-docs-translation-guide/#contributing-to-a-translation) to understand the Gatsby translation process. +Before contributing, please read the [translation guide](https://www.gatsbyjs.com/contributing/gatsby-docs-translation-guide/#contributing-to-a-translation) to understand the Gatsby translation process. Please be prompt with your translations! If you find that you can't commit anymore, let the maintainers know so they can assign the page to someone else. diff --git a/scripts/i18n/create.js b/scripts/i18n/create.js index 6d516c2119667..001613c1100f3 100644 --- a/scripts/i18n/create.js +++ b/scripts/i18n/create.js @@ -111,7 +111,7 @@ Please refer to the [Translation Progress Issue](${transRepo.url}/issues/1) to s Useful Links: * [Style Guide](/style-guide.md) -* [Gatsby Translation Guide](https://www.gatsbyjs.org/contributing/gatsby-docs-translation-guide/) +* [Gatsby Translation Guide](https://www.gatsbyjs.com/contributing/gatsby-docs-translation-guide/) * [Gatsby Discord](https://gatsby.dev/discord) (Feel free to translate this document and add any content you feel would be useful to contributors). @@ -277,7 +277,7 @@ If you are not already a member of the [gatsbyjs GitHub organization](https://gi You're free to use the [Gatsby Discord](https://gatsby.dev/discord) to discuss translations. Ask a moderator to create a channel for you in the \`#translations\` channel. -Finally, make sure to check out the [maintainer responsibilities](https://www.gatsbyjs.org/contributing/gatsby-docs-translation-guide/#maintainer-responsibilities) and review your duties as a maintainer. +Finally, make sure to check out the [maintainer responsibilities](https://www.gatsbyjs.com/contributing/gatsby-docs-translation-guide/#maintainer-responsibilities) and review your duties as a maintainer. Feel free to reach out to the Gatsby team if you need any help! diff --git a/scripts/i18n/sync.js b/scripts/i18n/sync.js index 1451ecd217bc8..7c40c69b2f730 100644 --- a/scripts/i18n/sync.js +++ b/scripts/i18n/sync.js @@ -144,7 +144,7 @@ function conflictPRBody(conflictFiles, comparisonUrl, prNumber) { return ` Sync conflicts with the source repo. Please update the translations based on updated source content. -For more information on how to resolve sync conflicts, check out the [guide for syncing translations](https://gatsbyjs.org/contributing/translation/sync-guide/). +For more information on how to resolve sync conflicts, check out the [guide for syncing translations](https://gatsbyjs.com/contributing/translation/sync-guide/).
The following ${ diff --git a/scripts/site-up-checker/index.js b/scripts/site-up-checker/index.js index c7e1323b2689f..d25d95d5a4a2a 100644 --- a/scripts/site-up-checker/index.js +++ b/scripts/site-up-checker/index.js @@ -46,9 +46,9 @@ const checkWebsite = async site => { const main = () => { const websites = [ - `https://www.gatsbyjs.org`, - `https://gatsbygram.gatsbyjs.org`, - `https://using-drupal.gatsbyjs.org`, + `https://www.gatsbyjs.com`, + `https://gatsbygram.gatsbyjs.com`, + `https://using-drupal.gatsbyjs.com`, ] // Run immediately. From fa9d2368aa07bc75257affd5f2e01284639fb74e Mon Sep 17 00:00:00 2001 From: Alex Reed Date: Thu, 10 Mar 2022 11:27:44 -0500 Subject: [PATCH 2/7] fix store.gatsbyjs.org links --- docs/contributing/contributor-swag.md | 6 +++--- docs/docs/conceptual/data-fetching.md | 2 +- .../building-a-site-with-authentication.md | 4 ++-- .../routing/client-only-routes-and-user-authentication.md | 2 +- .../docs/reference/release-notes/migrating-from-v1-to-v2.md | 4 ++-- docs/tutorial/authentication-tutorial.md | 2 +- 6 files changed, 10 insertions(+), 10 deletions(-) diff --git a/docs/contributing/contributor-swag.md b/docs/contributing/contributor-swag.md index e8929f993db8a..92d76c701509b 100644 --- a/docs/contributing/contributor-swag.md +++ b/docs/contributing/contributor-swag.md @@ -10,18 +10,18 @@ To show our appreciation, _**everyone who contributes to Gatsby is eligible to r ## How to claim your free swag -If you contribute to the Gatsby organization on GitHub, you can claim your swag by [logging into the Gatsby Store](https://store.gatsbyjs.com/) and requesting a discount code. With five or more contributions, you can claim your _**Level 2**_ swag. +If you contribute to the Gatsby organization on GitHub, you can claim your swag by [logging into the Gatsby Store](https://store.gatsbyjs.org/) and requesting a discount code. With five or more contributions, you can claim your _**Level 2**_ swag. If you’ve contributed in other ways, such as giving talks about Gatsby, teaching others to use it, writing Gatsby articles/tutorials, participating in a Gatsby research project, or any other way, please fill out [this short form](https://forms.gle/zBnybrZNjsdpXvDx8) to let us know! ## Details about free swag -- We will send one item from our [swag store](https://store.gatsbyjs.com/) per swag tier +- We will send one item from our [swag store](https://store.gatsbyjs.org/) per swag tier - Tier 1 swag includes most items valued 10 dollars or less - Tier 2 swag includes most items valued 31 dollars or less - Not all items are eligible due to high cost to create the swag. We’ll make it clear which items are not eligible - There’s a limit of one free swag item per swag tier - Shipping is free worldwide -- Additional details can be found in our [swag FAQs](https://github.com/gatsbyjs/store.gatsbyjs.com#frequently-asked-questions) +- Additional details can be found in our [swag FAQs](https://github.com/gatsbyjs/store.gatsbyjs.org#frequently-asked-questions) > **NOTE:** Worldwide free shipping is a pilot program. If shipping costs get out of control, we may need to adjust this policy in the future. diff --git a/docs/docs/conceptual/data-fetching.md b/docs/docs/conceptual/data-fetching.md index 135924b68c70c..c5032eadf87d1 100644 --- a/docs/docs/conceptual/data-fetching.md +++ b/docs/docs/conceptual/data-fetching.md @@ -214,7 +214,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][example site] of the code used in this guide -- [Gatsby store](https://github.com/gatsbyjs/store.gatsbyjs.com): with static product pages at build time and client-side interactions for e-commerce features +- [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/how-to/adding-common-features/building-a-site-with-authentication.md b/docs/docs/how-to/adding-common-features/building-a-site-with-authentication.md index 501f115c9da9f..74db050f95f94 100644 --- a/docs/docs/how-to/adding-common-features/building-a-site-with-authentication.md +++ b/docs/docs/how-to/adding-common-features/building-a-site-with-authentication.md @@ -75,9 +75,9 @@ More information on build related errors is available in the guide on [debugging ## Real-world example: Gatsby store -The [Gatsby store](https://github.com/gatsbyjs/store.gatsbyjs.com) is a live application built with Gatsby that implements authentication using Auth0. +The [Gatsby store](https://github.com/gatsbyjs/store.gatsbyjs.org) is a live application built with Gatsby that implements authentication using Auth0. -[Util functions](https://github.com/gatsbyjs/store.gatsbyjs.com/blob/master/src/utils/auth.js) in the Gatsby Store repo make use of Auth0's APIs to authenticate users with GitHub, and wrap Auth0's APIs to check that [some of the Auth0 code runs only in the browser](https://github.com/gatsbyjs/store.gatsbyjs.com/blob/master/src/utils/auth.js#L3). +[Util functions](https://github.com/gatsbyjs/store.gatsbyjs.org/blob/master/src/utils/auth.js) in the Gatsby Store repo make use of Auth0's APIs to authenticate users with GitHub, and wrap Auth0's APIs to check that [some of the Auth0 code runs only in the browser](https://github.com/gatsbyjs/store.gatsbyjs.org/blob/master/src/utils/auth.js#L3). In order to protect authenticated content with a private route, a `` is implemented in the `` component that checks whether a user is authenticated or reroutes them to `/login`. diff --git a/docs/docs/how-to/routing/client-only-routes-and-user-authentication.md b/docs/docs/how-to/routing/client-only-routes-and-user-authentication.md index 75a93d85d0c21..61b47d34695ee 100644 --- a/docs/docs/how-to/routing/client-only-routes-and-user-authentication.md +++ b/docs/docs/how-to/routing/client-only-routes-and-user-authentication.md @@ -127,4 +127,4 @@ Your server configuration should handle `GET` requests to `/app/*` e.g. `/app/wh - [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.app/) -- [The Gatsby store](https://github.com/gatsbyjs/store.gatsbyjs.com) which also implements an authenticated flow +- [The Gatsby store](https://github.com/gatsbyjs/store.gatsbyjs.org) which also implements an authenticated flow diff --git a/docs/docs/reference/release-notes/migrating-from-v1-to-v2.md b/docs/docs/reference/release-notes/migrating-from-v1-to-v2.md index 7536aefd25e9c..707a8a045b3c7 100644 --- a/docs/docs/reference/release-notes/migrating-from-v1-to-v2.md +++ b/docs/docs/reference/release-notes/migrating-from-v1-to-v2.md @@ -509,7 +509,7 @@ export default function Routes() { ``` Here's a more complex example of migrating a `` component (used -in store.gatsbyjs.com) from React Router to @reach/router. +in store.gatsbyjs.org) from React Router to @reach/router. ```diff import * as React from 'react'; @@ -549,7 +549,7 @@ in store.gatsbyjs.com) from React Router to @reach/router. Here are links to diffs for three sites with client routes upgraded to @reach/router: -- [store.gatsbyjs.com](https://github.com/gatsbyjs/store.gatsbyjs.com/pull/111) +- [store.gatsbyjs.org](https://github.com/gatsbyjs/store.gatsbyjs.org/pull/111) - [client-only-routes](https://github.com/gatsbyjs/gatsby/pull/6918/files#diff-69757e54875e28ef83eb8efe45a33fdf) - [simple-auth](https://github.com/gatsbyjs/gatsby/pull/6918/files#diff-53ac112a4b2ec760b26a86c953df2339) diff --git a/docs/tutorial/authentication-tutorial.md b/docs/tutorial/authentication-tutorial.md index 1d629f1f1f47c..40678bca892ff 100644 --- a/docs/tutorial/authentication-tutorial.md +++ b/docs/tutorial/authentication-tutorial.md @@ -415,7 +415,7 @@ If you want to learn more about using production-ready auth solutions, these lin - [Gatsby repo simple auth example](https://github.com/gatsbyjs/gatsby/tree/master/examples/simple-auth) - [A Gatsby email _application_](https://github.com/DSchau/gatsby-mail), using React Context API to handle authentication -- [The Gatsby store for swag and other Gatsby goodies](https://github.com/gatsbyjs/store.gatsbyjs.com) +- [The Gatsby store for swag and other Gatsby goodies](https://github.com/gatsbyjs/store.gatsbyjs.org) - [Building a blog with Gatsby, React and Webtask.io!](https://auth0.com/blog/building-a-blog-with-gatsby-react-and-webtask/) - [JAMstack PWA — Let’s Build a Polling App. with Gatsby.js, Firebase, and Styled-components Pt. 2](https://medium.com/@UnicornAgency/jamstack-pwa-lets-build-a-polling-app-with-gatsby-js-firebase-and-styled-components-pt-2-9044534ea6bc) - [JAMstack Hackathon Starter - Authenticated Gatsby app starter with Netlify Identity](/starters/sw-yx/jamstack-hackathon-starter) From 63eb9b36d136f019e4894d08e57b8f326293c20a Mon Sep 17 00:00:00 2001 From: Alex Reed Date: Thu, 10 Mar 2022 11:31:03 -0500 Subject: [PATCH 3/7] fix using-gatsby-image.gatsbyjs.org and image-processing.gatsbyjs.org links --- deprecated-packages/gatsby-image/README.md | 4 ++-- .../docs/how-to/images-and-media/using-gatsby-image.md | 4 ++-- docs/docs/porting-from-create-react-app-to-gatsby.md | 2 +- .../docs/reference/built-in-components/gatsby-image.md | 10 +++++----- docs/tutorial/wordpress-image-tutorial.md | 2 +- examples/image-processing/README.md | 2 +- examples/using-gatsby-image/README.md | 2 +- packages/gatsby-transformer-sharp/README.md | 2 +- packages/gatsby/CHANGELOG.md | 2 +- 9 files changed, 15 insertions(+), 15 deletions(-) diff --git a/deprecated-packages/gatsby-image/README.md b/deprecated-packages/gatsby-image/README.md index c9424b474604f..a6f066881e160 100644 --- a/deprecated-packages/gatsby-image/README.md +++ b/deprecated-packages/gatsby-image/README.md @@ -8,7 +8,7 @@ Speedy, optimized images without the work. `gatsby-image` is a React component specially designed to work seamlessly with Gatsby's GraphQL queries. It combines -[Gatsby's native image processing](https://image-processing.gatsbyjs.com/) +[Gatsby's native image processing](https://image-processing.gatsbyjs.org/) capabilities with advanced image loading techniques to easily and completely optimize image loading for your sites. `gatsby-image` uses [gatsby-plugin-sharp](/plugins/gatsby-plugin-sharp/) @@ -18,7 +18,7 @@ _Note: gatsby-image is **not** a drop-in replacement for ``. It's optimized for fixed width/height images and images that stretch the full-width of a container. Some ways you can use `` won't work with gatsby-image._ -**[Demo](https://using-gatsby-image.gatsbyjs.com)** +**[Demo](https://using-gatsby-image.gatsbyjs.org)** ## Table of Contents diff --git a/docs/docs/how-to/images-and-media/using-gatsby-image.md b/docs/docs/how-to/images-and-media/using-gatsby-image.md index 65a472eae3af8..689018f7df921 100644 --- a/docs/docs/how-to/images-and-media/using-gatsby-image.md +++ b/docs/docs/how-to/images-and-media/using-gatsby-image.md @@ -10,11 +10,11 @@ Using images in Gatsby components and pages requires four steps to take advantag -`gatsby-image` is a React component designed to work seamlessly with Gatsby’s GraphQL queries ([`gatsby-image` plugin README](/plugins/gatsby-image/)). It combines [Gatsby’s native image processing](https://image-processing.gatsbyjs.com/) capabilities with advanced image loading techniques to easily and completely optimize image loading for your sites. `gatsby-image` uses [gatsby-plugin-sharp](/plugins/gatsby-plugin-sharp/) to power its image transformations. +`gatsby-image` is a React component designed to work seamlessly with Gatsby’s GraphQL queries ([`gatsby-image` plugin README](/plugins/gatsby-image/)). It combines [Gatsby’s native image processing](https://image-processing.gatsbyjs.org/) capabilities with advanced image loading techniques to easily and completely optimize image loading for your sites. `gatsby-image` uses [gatsby-plugin-sharp](/plugins/gatsby-plugin-sharp/) to power its image transformations. > _Warning: gatsby-image is **not** a drop-in replacement for ``. It’s optimized for fixed width/height images and images that stretch the full width of a container. Some ways you can use `` won’t work with gatsby-image._ -Here's a [demo site that uses the gatsby-image plugin](https://using-gatsby-image.gatsbyjs.com/) +Here's a [demo site that uses the gatsby-image plugin](https://using-gatsby-image.gatsbyjs.org/) `gatsby-image` includes the tricks you’d expect from a modern image component. It: diff --git a/docs/docs/porting-from-create-react-app-to-gatsby.md b/docs/docs/porting-from-create-react-app-to-gatsby.md index 0551aefb6edf7..b3bf33a4e1cf7 100644 --- a/docs/docs/porting-from-create-react-app-to-gatsby.md +++ b/docs/docs/porting-from-create-react-app-to-gatsby.md @@ -19,7 +19,7 @@ _Both_ Create React App and Gatsby use React and allow users to build apps more Gatsby enables some useful performance optimizations for you, by default. Route-based code splitting and pre-loading of the _next_ resources make your application lightning fast, without any additional effort! Further still, the following optimizations and techniques are also available to you: - `gatsby-link` uses an [intersection observer to preload linked pages](/blog/2019-04-02-behind-the-scenes-what-makes-gatsby-great/#intersectionobserver) when they appear in the viewport, making them feel like they load _instantly_ -- `gatsby-plugin-image` will create optimized versions of your images in different sizes, loading a smaller, optimized version of an image and replacing it with a higher resolution version when loading has finished. It also uses an intersection observer to cheaply lazy load images. Check out [the demo](https://using-gatsby-image.gatsbyjs.com/) to see for yourself +- `gatsby-plugin-image` will create optimized versions of your images in different sizes, loading a smaller, optimized version of an image and replacing it with a higher resolution version when loading has finished. It also uses an intersection observer to cheaply lazy load images. Check out [the demo](https://using-gatsby-image.gatsbyjs.org/) to see for yourself These features and more work together to make your Gatsby site fast by default. If you'd like a deep dive on these and other performance optimizations, check out [this blog post](/blog/2019-04-02-behind-the-scenes-what-makes-gatsby-great/) diff --git a/docs/docs/reference/built-in-components/gatsby-image.md b/docs/docs/reference/built-in-components/gatsby-image.md index 52233585acf84..efc9c9f24ef1c 100644 --- a/docs/docs/reference/built-in-components/gatsby-image.md +++ b/docs/docs/reference/built-in-components/gatsby-image.md @@ -4,11 +4,11 @@ title: Gatsby Image API _This document talks about the deprecated image plugin. Please check out how to work with the new [gatsby-plugin-image](/docs/how-to/images-and-media/using-gatsby-plugin-image)_ -Part of what makes Gatsby sites so fast is its recommended approach to handling images. `gatsby-image` is a React component designed to work seamlessly with Gatsby’s [native image processing](https://image-processing.gatsbyjs.com/) capabilities powered by GraphQL and [gatsby-plugin-sharp](/plugins/gatsby-plugin-sharp/) to easily and completely optimize image loading for your sites. +Part of what makes Gatsby sites so fast is its recommended approach to handling images. `gatsby-image` is a React component designed to work seamlessly with Gatsby’s [native image processing](https://image-processing.gatsbyjs.org/) capabilities powered by GraphQL and [gatsby-plugin-sharp](/plugins/gatsby-plugin-sharp/) to easily and completely optimize image loading for your sites. > _Note: gatsby-image is **not** a drop-in replacement for ``. It’s optimized for responsive fixed width/height images and images that stretch the full-width of a container. There are also other ways to [work with images](/docs/images-and-files/) in Gatsby that don't require GraphQL._ -Demo: https://using-gatsby-image.gatsbyjs.com/ +Demo: https://using-gatsby-image.gatsbyjs.org/ ## Setting up Gatsby Image @@ -310,11 +310,11 @@ GraphQL includes a concept called "query fragments", which are a part of a query #### About `noBase64` -If you don't want to use the [blur-up effect](https://using-gatsby-image.gatsbyjs.com/blur-up/), choose the fragment with `noBase64` at the end. +If you don't want to use the [blur-up effect](https://using-gatsby-image.gatsbyjs.org/blur-up/), choose the fragment with `noBase64` at the end. #### About `tracedSVG` -If you want to use the [traced placeholder SVGs](https://using-gatsby-image.gatsbyjs.com/traced-svg/), choose the fragment with `tracedSVG` at the end. +If you want to use the [traced placeholder SVGs](https://using-gatsby-image.gatsbyjs.org/traced-svg/), choose the fragment with `tracedSVG` at the end. #### About `withWebp` @@ -333,7 +333,7 @@ file(relativePath: { eq: "images/default.jpg" }) { } ``` -For more info on how these options work, check out the Gatsby Image demo: https://using-gatsby-image.gatsbyjs.com/ +For more info on how these options work, check out the Gatsby Image demo: https://using-gatsby-image.gatsbyjs.org/ #### Additional plugin fragments diff --git a/docs/tutorial/wordpress-image-tutorial.md b/docs/tutorial/wordpress-image-tutorial.md index 6491cd0786884..695864c8ef8dc 100644 --- a/docs/tutorial/wordpress-image-tutorial.md +++ b/docs/tutorial/wordpress-image-tutorial.md @@ -16,7 +16,7 @@ In this tutorial, you will install the several image plugins and components in o Images are one of the most beautiful and striking ways to communicate to people, and are a key part of creating an effective and positive user experience; at the same time, high quality images can load slowly and cause text boxes to jump around, both of which make it difficult for people to be patient with visiting your website. -The Gatsby Way™ of creating images describes a set of best practices that help you optimize performance and responsiveness of images so that you can get the benefits of awesome images that don't slow down your site. This [Gatsbygram site](https://gatsbygram.gatsbyjs.com/) (an Instagram feed fed through Gatsby) shows off the SVG image tracing effect. Here’s an [image processing demo site](https://image-processing.gatsbyjs.com/) exploring how to have fun with images in your Gatsby site. +The Gatsby Way™ of creating images describes a set of best practices that help you optimize performance and responsiveness of images so that you can get the benefits of awesome images that don't slow down your site. This [Gatsbygram site](https://gatsbygram.gatsbyjs.com/) (an Instagram feed fed through Gatsby) shows off the SVG image tracing effect. Here’s an [image processing demo site](https://image-processing.gatsbyjs.org/) exploring how to have fun with images in your Gatsby site. ## Installing the `gatsby-source-wordpress` plugin diff --git a/examples/image-processing/README.md b/examples/image-processing/README.md index 36a84704cd93c..a65b7f1c9f28e 100644 --- a/examples/image-processing/README.md +++ b/examples/image-processing/README.md @@ -1,6 +1,6 @@ # Image Processing -https://image-processing.gatsbyjs.com +https://image-processing.gatsbyjs.org Example site that demonstrates how to use [gatsby-plugin-sharp][1]. diff --git a/examples/using-gatsby-image/README.md b/examples/using-gatsby-image/README.md index b922d7bb5af20..ce03dc79e5e06 100644 --- a/examples/using-gatsby-image/README.md +++ b/examples/using-gatsby-image/README.md @@ -1,6 +1,6 @@ # Using Gatsby Image -https://using-gatsby-image.gatsbyjs.com +https://using-gatsby-image.gatsbyjs.org Gatsby example site that shows how to use [gatsby-plugin-image](https://github.com/gatsbyjs/gatsby/tree/master/packages/gatsby-image). diff --git a/packages/gatsby-transformer-sharp/README.md b/packages/gatsby-transformer-sharp/README.md index d3c3a42349e39..38c1ed6806bd0 100644 --- a/packages/gatsby-transformer-sharp/README.md +++ b/packages/gatsby-transformer-sharp/README.md @@ -5,7 +5,7 @@ Creates `ImageSharp` nodes from image types that are supported by the fields in their GraphQL types for processing your images in a variety of ways including resizing, cropping, and creating responsive images. -[Live demo](https://image-processing.gatsbyjs.com/) +[Live demo](https://image-processing.gatsbyjs.org/) ([source](https://github.com/gatsbyjs/gatsby/tree/master/examples/image-processing)) ## Install diff --git a/packages/gatsby/CHANGELOG.md b/packages/gatsby/CHANGELOG.md index f94a12068df0e..3c9390c99d5f7 100644 --- a/packages/gatsby/CHANGELOG.md +++ b/packages/gatsby/CHANGELOG.md @@ -7710,7 +7710,7 @@ Our first beta!!! 🎉 https://www.gatsbyjs.com/docs/node-apis/ - Add "duotone" image processing option to gatsby-plugin-sharp #1047 @fk - Add example site for image processing @fk - https://image-processing.gatsbyjs.com/ + https://image-processing.gatsbyjs.org/ - Add example site for css-in-js library Glamor @kyleamathews https://using-glamor.gatsbyjs.com/ - Add example site for css-in-js library Styled Components @kyleamathews From 33be31b2cb69f0f8e0d4b8e5b818829ca6cad002 Mon Sep 17 00:00:00 2001 From: Alex Reed Date: Thu, 10 Mar 2022 12:18:10 -0500 Subject: [PATCH 4/7] fix more links that need to be .org --- .../docs/reference/release-notes/migrating-from-v1-to-v2.md | 2 +- docs/docs/reference/release-notes/v1-release-notes.md | 2 +- docs/docs/themes.md | 2 +- docs/tutorial/wordpress-image-tutorial.md | 4 ++-- e2e-tests/development-runtime/README.md | 2 +- examples/gatsbygram/README.md | 2 +- examples/using-css-modules/README.md | 2 +- examples/using-drupal/README.md | 2 +- examples/using-emotion/README.md | 2 +- examples/using-glamor/README.md | 2 +- examples/using-hjson/README.md | 2 +- examples/using-jss/README.md | 2 +- examples/using-medium/README.md | 2 +- examples/using-mongodb/README.md | 2 +- examples/using-redux/README.md | 2 +- examples/using-remark/README.md | 2 +- .../index.md | 2 +- examples/using-sass/README.md | 2 +- examples/using-styled-components/README.md | 2 +- examples/using-styled-jsx/README.md | 2 +- examples/using-stylus/README.md | 2 +- examples/using-wordpress-with-acf/README.md | 2 +- packages/gatsby-plugin-catch-links/README.md | 2 +- packages/gatsby-plugin-jss/README.md | 2 +- packages/gatsby-remark-katex/README.md | 2 +- packages/gatsby-remark-prismjs/README.md | 2 +- packages/gatsby-source-contentful/README.md | 6 +++--- packages/gatsby-source-drupal/README.md | 2 +- packages/gatsby-transformer-remark/README.md | 2 +- packages/gatsby/CHANGELOG.md | 2 +- scripts/site-up-checker/index.js | 4 ++-- 31 files changed, 35 insertions(+), 35 deletions(-) diff --git a/docs/docs/reference/release-notes/migrating-from-v1-to-v2.md b/docs/docs/reference/release-notes/migrating-from-v1-to-v2.md index 707a8a045b3c7..eab564e6fc6f1 100644 --- a/docs/docs/reference/release-notes/migrating-from-v1-to-v2.md +++ b/docs/docs/reference/release-notes/migrating-from-v1-to-v2.md @@ -2,7 +2,7 @@ title: Migrating from v1 to v2 --- -Looking for the v1 docs? [Find them here](https://v1.gatsbyjs.com/). +Looking for the v1 docs? [Find them here](https://v1.gatsbyjs.org/). > This document is a work in progress. Have you run into something that's not covered here? [Add your changes on GitHub](https://github.com/gatsbyjs/gatsby/edit/master/docs/docs/reference/release-notes/migrating-from-v1-to-v2.md)! diff --git a/docs/docs/reference/release-notes/v1-release-notes.md b/docs/docs/reference/release-notes/v1-release-notes.md index 4849b77810d6a..b5cc085be62cb 100644 --- a/docs/docs/reference/release-notes/v1-release-notes.md +++ b/docs/docs/reference/release-notes/v1-release-notes.md @@ -4,6 +4,6 @@ title: v1 Release Notes Check out the following useful links for Gatsby version 1: -- [v1 documentation](https://v1.gatsbyjs.com/) +- [v1 documentation](https://v1.gatsbyjs.org/) - [v1 changelog](https://github.com/gatsbyjs/gatsby/blob/master/packages/gatsby/CHANGELOG.md#100---2017-07-06) - [v1 release announcement](/blog/gatsby-v1/) diff --git a/docs/docs/themes.md b/docs/docs/themes.md index 8df4b2414095e..9dad8de43f229 100644 --- a/docs/docs/themes.md +++ b/docs/docs/themes.md @@ -12,7 +12,7 @@ This means that the configuration and functionality isn’t directly written int ## Browse themes - [Themes in Plugin Library](/plugins/?=gatsby-theme) -- [Theme Jam Showcase](https://themejam.gatsbyjs.com/showcase) +- [Theme Jam Showcase](https://themejam.gatsbyjs.org/showcase) ## Other resources diff --git a/docs/tutorial/wordpress-image-tutorial.md b/docs/tutorial/wordpress-image-tutorial.md index 695864c8ef8dc..08b393760db3d 100644 --- a/docs/tutorial/wordpress-image-tutorial.md +++ b/docs/tutorial/wordpress-image-tutorial.md @@ -10,13 +10,13 @@ Please follow the tutorial on [creating a new site with `gatsby-source-wordpress ## What this tutorial covers: -In this tutorial, you will install the several image plugins and components in order to pull image data from a WordPress account into your Gatsby site and render that data. This [Gatsby + WordPress demo site](https://using-wordpress.gatsbyjs.com/) shows you a sample of what you’re going to be building in this tutorial, although in this tutorial you’ll just focus on adding images. +In this tutorial, you will install the several image plugins and components in order to pull image data from a WordPress account into your Gatsby site and render that data. This [Gatsby + WordPress demo site](https://using-wordpress.gatsbyjs.org/) shows you a sample of what you’re going to be building in this tutorial, although in this tutorial you’ll just focus on adding images. ## Why go through this tutorial? Images are one of the most beautiful and striking ways to communicate to people, and are a key part of creating an effective and positive user experience; at the same time, high quality images can load slowly and cause text boxes to jump around, both of which make it difficult for people to be patient with visiting your website. -The Gatsby Way™ of creating images describes a set of best practices that help you optimize performance and responsiveness of images so that you can get the benefits of awesome images that don't slow down your site. This [Gatsbygram site](https://gatsbygram.gatsbyjs.com/) (an Instagram feed fed through Gatsby) shows off the SVG image tracing effect. Here’s an [image processing demo site](https://image-processing.gatsbyjs.org/) exploring how to have fun with images in your Gatsby site. +The Gatsby Way™ of creating images describes a set of best practices that help you optimize performance and responsiveness of images so that you can get the benefits of awesome images that don't slow down your site. This [Gatsbygram site](https://gatsbygram.gatsbyjs.org/) (an Instagram feed fed through Gatsby) shows off the SVG image tracing effect. Here’s an [image processing demo site](https://image-processing.gatsbyjs.org/) exploring how to have fun with images in your Gatsby site. ## Installing the `gatsby-source-wordpress` plugin diff --git a/e2e-tests/development-runtime/README.md b/e2e-tests/development-runtime/README.md index b6515cbbdd326..5e7b22d66b81d 100644 --- a/e2e-tests/development-runtime/README.md +++ b/e2e-tests/development-runtime/README.md @@ -35,7 +35,7 @@ _Have another more specific idea? You may want to check out our vibrant collecti Your site is now running at `http://localhost:8000`! - \_Note: You'll also see a second link: `http://localhost:8000/___graphql`. This is a tool you can use to experiment with querying your data. Learn more about using this tool in the [Gatsby tutorial](https://www.gatsbyjs.com/tutorial/part-5/#introducing-graphiql).\_ + \_Note: You'll also see a second link: `http://localhost:8000/___graphql`. This is a tool you can use to experiment with querying your data. Learn more about using this tool in the [Gatsby how-to](https://www.gatsbyjs.com/docs/how-to/querying-data/running-queries-with-graphiql/).\_ Open the `my-default-starter` directory in your code editor of choice and edit `src/pages/index.js`. Save your changes and the browser will update in real time! diff --git a/examples/gatsbygram/README.md b/examples/gatsbygram/README.md index 486d09571d56c..f7a37997a9234 100644 --- a/examples/gatsbygram/README.md +++ b/examples/gatsbygram/README.md @@ -1,6 +1,6 @@ # Gatsbygram -https://gatsbygram.gatsbyjs.com/ +https://gatsbygram.gatsbyjs.org/ Built with Gatsby 2.0 as a demo of Gatsby's new built-in image processing capabilities. diff --git a/examples/using-css-modules/README.md b/examples/using-css-modules/README.md index ee6bf817301b2..92eac66c15f26 100644 --- a/examples/using-css-modules/README.md +++ b/examples/using-css-modules/README.md @@ -1,6 +1,6 @@ # using-css-modules -https://using-css-modules.gatsbyjs.com +https://using-css-modules.gatsbyjs.org Demonstrates using css modules in Gatsby with normal (Postcss) css and sass/scss. diff --git a/examples/using-drupal/README.md b/examples/using-drupal/README.md index 079b3fa61d9ba..adeecf6155630 100644 --- a/examples/using-drupal/README.md +++ b/examples/using-drupal/README.md @@ -1,6 +1,6 @@ # Using Drupal -https://using-drupal.gatsbyjs.com +https://using-drupal.gatsbyjs.org Example site that demonstrates how to build Gatsby sites that pull data from the [Drupal CMS](https://www.drupal.org/). diff --git a/examples/using-emotion/README.md b/examples/using-emotion/README.md index fe7f46475085b..b4d63386663f8 100644 --- a/examples/using-emotion/README.md +++ b/examples/using-emotion/README.md @@ -1,6 +1,6 @@ # using-emotion -https://using-emotion.gatsbyjs.com +https://using-emotion.gatsbyjs.org Example site that demonstrates how to build Gatsby sites with [emotion](https://github.com/emotion-js/emotion). diff --git a/examples/using-glamor/README.md b/examples/using-glamor/README.md index ff95982d008bd..e0f2d00a39319 100644 --- a/examples/using-glamor/README.md +++ b/examples/using-glamor/README.md @@ -1,6 +1,6 @@ # Using Glamor -https://using-glamor.gatsbyjs.com +https://using-glamor.gatsbyjs.org Example site that demonstrates how to build Gatsby sites using the [Glamor](https://github.com/threepointone/glamor) css-in-js library. diff --git a/examples/using-hjson/README.md b/examples/using-hjson/README.md index e2009467727eb..dca6b4958dab4 100644 --- a/examples/using-hjson/README.md +++ b/examples/using-hjson/README.md @@ -1,5 +1,5 @@ # using-hjson -https://using-hjson.gatsbyjs.com +https://using-hjson.gatsbyjs.org Gatsby example site demonstrating how to use [HJson](https://hjson.org) diff --git a/examples/using-jss/README.md b/examples/using-jss/README.md index d0dfb9b95ea8a..1609e738db31c 100644 --- a/examples/using-jss/README.md +++ b/examples/using-jss/README.md @@ -1,6 +1,6 @@ # Using JSS -https://using-jss.gatsbyjs.com +https://using-jss.gatsbyjs.org Example site that demonstrates how to build Gatsby sites with [JSS](http://cssinjs.org/). diff --git a/examples/using-medium/README.md b/examples/using-medium/README.md index e3c5984e20ee6..ea77384323866 100644 --- a/examples/using-medium/README.md +++ b/examples/using-medium/README.md @@ -1,6 +1,6 @@ # Using Medium -https://using-medium.gatsbyjs.com +https://using-medium.gatsbyjs.org Gatsby example site that shows how to use the [gatsby-source-medium](https://github.com/gatsbyjs/gatsby/tree/master/packages/gatsby-source-medium) diff --git a/examples/using-mongodb/README.md b/examples/using-mongodb/README.md index 3f8a41df7b2c2..9f4a55771d315 100644 --- a/examples/using-mongodb/README.md +++ b/examples/using-mongodb/README.md @@ -1,5 +1,5 @@ # using-mongodb -https://using-mongodb.gatsbyjs.com +https://using-mongodb.gatsbyjs.org In this example site we will use the gatsby-source-mongodb plugin. diff --git a/examples/using-redux/README.md b/examples/using-redux/README.md index 5b9c8103a49c5..e0073f5d6570d 100644 --- a/examples/using-redux/README.md +++ b/examples/using-redux/README.md @@ -1,6 +1,6 @@ # Redux -https://using-redux.gatsbyjs.com/ +https://using-redux.gatsbyjs.org/ Gatsby example site that shows use of redux. diff --git a/examples/using-remark/README.md b/examples/using-remark/README.md index dbf8739804881..5f345f5a21dcb 100644 --- a/examples/using-remark/README.md +++ b/examples/using-remark/README.md @@ -1,6 +1,6 @@ # Using remark -https://using-remark.gatsbyjs.com +https://using-remark.gatsbyjs.org Example site that demonstrates how to use [gatsby-transformer-remark][1] and its various plugins. It uses [Typography.js][2] and self-hosted fonts via the diff --git a/examples/using-remark/src/pages/2017-03-21---copy-linked-files-intercepting-local-links/index.md b/examples/using-remark/src/pages/2017-03-21---copy-linked-files-intercepting-local-links/index.md index 548b1ee35fffa..9de0f74403d4d 100644 --- a/examples/using-remark/src/pages/2017-03-21---copy-linked-files-intercepting-local-links/index.md +++ b/examples/using-remark/src/pages/2017-03-21---copy-linked-files-intercepting-local-links/index.md @@ -32,7 +32,7 @@ Let's try linking to the "[Code and Syntax Highlighting with PrismJS](/code-and-syntax-highlighting/)" article using a relative path. -Also, let's link to "[Rendering math equations with KaTeX](https://using-remark.gatsbyjs.com/katex/)" article using an absolute path. +Also, let's link to "[Rendering math equations with KaTeX](https://using-remark.gatsbyjs.org/katex/)" article using an absolute path. And this [link will be excluded](/excluded-link). diff --git a/examples/using-sass/README.md b/examples/using-sass/README.md index 16c9789661677..e9f2c322c9a33 100644 --- a/examples/using-sass/README.md +++ b/examples/using-sass/README.md @@ -1,6 +1,6 @@ # Using gatsby-plugin-sass -https://using-sass.gatsbyjs.com +https://using-sass.gatsbyjs.org Example site that demonstrates how to build Gatsby sites using the Gatsby plugin `gatsby-plugin-sass` which sets up webpack to run Sass/Scss code through the diff --git a/examples/using-styled-components/README.md b/examples/using-styled-components/README.md index 02288319851bb..b07601ebd5ad6 100644 --- a/examples/using-styled-components/README.md +++ b/examples/using-styled-components/README.md @@ -1,6 +1,6 @@ # Using Styled Components -https://using-styled-components.gatsbyjs.com +https://using-styled-components.gatsbyjs.org Example site that demonstrates how to build Gatsby sites with [Styled Components](https://styled-components.com/). diff --git a/examples/using-styled-jsx/README.md b/examples/using-styled-jsx/README.md index 37d0ff7beeb3e..bca3f4c64edfc 100644 --- a/examples/using-styled-jsx/README.md +++ b/examples/using-styled-jsx/README.md @@ -1,6 +1,6 @@ # using-styled-jsx -https://using-styled-jsx.gatsbyjs.com +https://using-styled-jsx.gatsbyjs.org Demonstrates using [styled-jsx](https://github.com/vercel/styled-jsx) with the Gatsby plugin diff --git a/examples/using-stylus/README.md b/examples/using-stylus/README.md index 98f45d5941bd7..d22f44a64c3c3 100644 --- a/examples/using-stylus/README.md +++ b/examples/using-stylus/README.md @@ -1,6 +1,6 @@ # Using gatsby-plugin-stylus -https://using-stylus.gatsbyjs.com +https://using-stylus.gatsbyjs.org Example site that demonstrates how to build Gatsby sites using the Gatsby plugin `gatsby-plugin-stylus` which sets up webpack to run [Stylus][] code. diff --git a/examples/using-wordpress-with-acf/README.md b/examples/using-wordpress-with-acf/README.md index 22f0c4c231fe3..5d45a88ca53af 100644 --- a/examples/using-wordpress-with-acf/README.md +++ b/examples/using-wordpress-with-acf/README.md @@ -1,6 +1,6 @@ # Using WordPress With Advanced Custom Fields (ACF) -https://using-wordpress.gatsbyjs.com/ +https://using-wordpress.gatsbyjs.org/ Example site that extends the [using-wordpress](examples/using-wordpress/) example and demonstrates how to build Gatsby sites that pull data from the [WordPress CMS API](https://www.wordpress.com/) using Advanced Custom Fields. diff --git a/packages/gatsby-plugin-catch-links/README.md b/packages/gatsby-plugin-catch-links/README.md index 4445f0698689d..b8806eacdc6b7 100644 --- a/packages/gatsby-plugin-catch-links/README.md +++ b/packages/gatsby-plugin-catch-links/README.md @@ -39,4 +39,4 @@ Regular expression for paths to be excluded from being handled by this plugin. ## Examples -- Check out this live example [_Using Remark_](https://using-remark.gatsbyjs.com/copy-linked-files-intercepting-local-links/#intercepting-local-links) to see this plugin in action. The full source code for this example can be found [here](https://github.com/gatsbyjs/gatsby/tree/master/examples/using-remark). +- Check out this live example [_Using Remark_](https://using-remark.gatsbyjs.org/copy-linked-files-intercepting-local-links/#intercepting-local-links) to see this plugin in action. The full source code for this example can be found [here](https://github.com/gatsbyjs/gatsby/tree/master/examples/using-remark). diff --git a/packages/gatsby-plugin-jss/README.md b/packages/gatsby-plugin-jss/README.md index b950689067910..0b15ade8e68f1 100644 --- a/packages/gatsby-plugin-jss/README.md +++ b/packages/gatsby-plugin-jss/README.md @@ -34,4 +34,4 @@ plugins: [ ## Example -https://using-jss.gatsbyjs.com/ +https://using-jss.gatsbyjs.org/ diff --git a/packages/gatsby-remark-katex/README.md b/packages/gatsby-remark-katex/README.md index ec355015aac4a..a19ffdb35aa1b 100644 --- a/packages/gatsby-remark-katex/README.md +++ b/packages/gatsby-remark-katex/README.md @@ -1,7 +1,7 @@ # gatsby-remark-katex [gatsby-remark-katex][1] adds math equation support to gatsby using -[remark-math][2] and [katex][3]. Live example at [using-remark.gatsbyjs.com/katex/](https://using-remark.gatsbyjs.com/katex/). +[remark-math][2] and [katex][3]. Live example at [using-remark.gatsbyjs.org/katex/](https://using-remark.gatsbyjs.org/katex/). ## Install diff --git a/packages/gatsby-remark-prismjs/README.md b/packages/gatsby-remark-prismjs/README.md index 7143993dc39ca..1a66bf4868cc6 100644 --- a/packages/gatsby-remark-prismjs/README.md +++ b/packages/gatsby-remark-prismjs/README.md @@ -411,7 +411,7 @@ The available directives are: - `hide-start` hides the lines until the matching `hide-end`; - `hide-range{1, 4-6}` will hide the next line, and the fourth, fifth and sixth lines. -The hide-line directives will always be hidden too. Check out [the using-remark example site](https://using-remark.gatsbyjs.com/embed-snippets/) to see how this looks on a live site. +The hide-line directives will always be hidden too. Check out [the using-remark example site](https://using-remark.gatsbyjs.org/embed-snippets/) to see how this looks on a live site. ### Inline code blocks diff --git a/packages/gatsby-source-contentful/README.md b/packages/gatsby-source-contentful/README.md index 13a598ef434e6..027d9a7d08905 100644 --- a/packages/gatsby-source-contentful/README.md +++ b/packages/gatsby-source-contentful/README.md @@ -4,7 +4,7 @@ > Contentful spaces. It creates links between entry types and asset so they can be > queried in Gatsby using GraphQL. > -> An example site for using this plugin is at https://using-contentful.gatsbyjs.com/ +> An example site for using this plugin is at https://using-contentful.gatsbyjs.org/
Table of contents @@ -206,7 +206,7 @@ You might query for **all** of a type of node: } ``` -You might do this in your `gatsby-node.js` using Gatsby's [`createPages`](https://next.gatsbyjs.com/docs/node-apis/#createPages) Node API. +You might do this in your `gatsby-node.js` using Gatsby's [`createPages`](https://gatsbyjs.com/docs/node-apis/#createPages) Node API. ### Query for a single node @@ -343,7 +343,7 @@ To get **all** the `CaseStudy` nodes with `ShortText` fields `id`, `slug`, `titl ### More on Queries with Contentful and Gatsby It is strongly recommended that you take a look at how data flows in a real Contentful and Gatsby application to fully understand how the queries, Node.js functions and React components all come together. Check out the example site at -[using-contentful.gatsbyjs.com](https://using-contentful.gatsbyjs.com/). +[using-contentful.gatsbyjs.org](https://using-contentful.gatsbyjs.org/). ## Displaying responsive image with gatsby-plugin-image diff --git a/packages/gatsby-source-drupal/README.md b/packages/gatsby-source-drupal/README.md index 2d11967b42fbf..a70b5b744dde7 100644 --- a/packages/gatsby-source-drupal/README.md +++ b/packages/gatsby-source-drupal/README.md @@ -7,7 +7,7 @@ It pulls data from Drupal 8 sites with the An example site built with the headless Drupal distro [ContentaCMS](https://twitter.com/contentacms) is at -https://using-drupal.gatsbyjs.com/ +https://using-drupal.gatsbyjs.org/ `apiBase` Option allows changing the API entry point depending on the version of jsonapi used by your Drupal instance. The default value is `jsonapi`, which has diff --git a/packages/gatsby-transformer-remark/README.md b/packages/gatsby-transformer-remark/README.md index 52a0a2c6e797e..6c012fe738ebe 100644 --- a/packages/gatsby-transformer-remark/README.md +++ b/packages/gatsby-transformer-remark/README.md @@ -34,7 +34,7 @@ plugins: A full explanation of how to use markdown in Gatsby can be found here: [Adding Markdown Pages](https://www.gatsbyjs.com/docs/how-to/routing/adding-markdown-pages/) -There are many Gatsby Remark plugins which you can install to customize how Markdown is processed. Many of them are demoed at https://using-remark.gatsbyjs.com/. See also the [source code for using-remark](https://github.com/gatsbyjs/gatsby/tree/master/examples/using-remark). +There are many Gatsby Remark plugins which you can install to customize how Markdown is processed. Many of them are demoed at https://using-remark.gatsbyjs.org/. See also the [source code for using-remark](https://github.com/gatsbyjs/gatsby/tree/master/examples/using-remark). ## Parsing algorithm diff --git a/packages/gatsby/CHANGELOG.md b/packages/gatsby/CHANGELOG.md index 3c9390c99d5f7..116289a6f9f10 100644 --- a/packages/gatsby/CHANGELOG.md +++ b/packages/gatsby/CHANGELOG.md @@ -7714,7 +7714,7 @@ Our first beta!!! 🎉 - Add example site for css-in-js library Glamor @kyleamathews https://using-glamor.gatsbyjs.com/ - Add example site for css-in-js library Styled Components @kyleamathews - https://using-styled-components.gatsbyjs.com/ + https://using-styled-components.gatsbyjs.org/ ### Changed diff --git a/scripts/site-up-checker/index.js b/scripts/site-up-checker/index.js index d25d95d5a4a2a..3da78f95721b1 100644 --- a/scripts/site-up-checker/index.js +++ b/scripts/site-up-checker/index.js @@ -47,8 +47,8 @@ const checkWebsite = async site => { const main = () => { const websites = [ `https://www.gatsbyjs.com`, - `https://gatsbygram.gatsbyjs.com`, - `https://using-drupal.gatsbyjs.com`, + `https://gatsbygram.gatsbyjs.org`, + `https://using-drupal.gatsbyjs.org`, ] // Run immediately. From 74a8872153f87b8b307a705bc93d25fa5ba7c5d1 Mon Sep 17 00:00:00 2001 From: Alex Reed Date: Thu, 10 Mar 2022 12:35:14 -0500 Subject: [PATCH 5/7] gatsby style guide md update --- docs/contributing/gatsby-style-guide.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/contributing/gatsby-style-guide.md b/docs/contributing/gatsby-style-guide.md index 52a6afa925858..f63f22ac53c1a 100644 --- a/docs/contributing/gatsby-style-guide.md +++ b/docs/contributing/gatsby-style-guide.md @@ -32,7 +32,7 @@ Many times, the information that needs to go in your document already exists som Avoid copying and pasting huge chunks of other people's work. Instead, use their work to learn so you can write your own document. If you do quote someone's work verbatim, reference where you got the information. -If the content is already somewhere else on the .org site, feel free to copy and paste without quoting or referencing. +If the content is already somewhere else on the site, feel free to copy and paste without quoting or referencing. Possible sources of great research materials: From 60e974a41677d00674f58ffdfd0acc06339c12cc Mon Sep 17 00:00:00 2001 From: Alex Reed Date: Wed, 16 Mar 2022 14:46:08 -0400 Subject: [PATCH 6/7] updates per PR feedback --- .../src/__tests__/fixtures/data.json | 2 +- deprecated-packages/gatsby-image/src/index.js | 2 +- .../recipes/gatsby-plugin-layout.mdx | 12 +++++----- .../recipes/gatsby-plugin-react-helmet.mdx | 4 ++-- .../recipes/gatsby-theme-blog-core.mdx | 16 +++++++++----- .../recipes/gatsby-theme-blog.mdx | 9 +++++--- .../recipes/gatsby-theme-notes.mdx | 10 +++++---- .../gatsby-recipes/recipes/pwa.mdx | 4 ++-- .../gatsby-config.js | 2 +- .../using-gatsby-source-graphql/README.md | 2 +- packages/gatsby-design-tokens/CHANGELOG.md | 10 ++++----- packages/gatsby-design-tokens/README.md | 2 -- packages/gatsby-plugin-google-gtag/README.md | 4 ++-- packages/gatsby-plugin-mdx/README.md | 4 ++-- .../src/__tests__/fixtures/public/index.html | 10 ++++----- packages/gatsby-plugin-typescript/README.md | 2 +- packages/gatsby-plugin-typography/README.md | 3 --- .../gatsby-remark-copy-linked-files/README.md | 2 +- .../gatsby-remark-custom-blocks/README.md | 2 +- .../gatsby-remark-embed-snippet/README.md | 4 ++-- packages/gatsby-remark-images/README.md | 2 +- packages/gatsby-remark-katex/README.md | 2 +- packages/gatsby-remark-prismjs/README.md | 2 +- packages/gatsby-source-contentful/README.md | 2 +- packages/gatsby-source-filesystem/README.md | 2 -- packages/gatsby-source-filesystem/index.d.ts | 8 +++---- .../src/gatsby-node.js | 2 +- ...uilding-a-new-site-wordpress-and-gatsby.md | 2 +- packages/gatsby-transformer-sharp/README.md | 2 +- packages/gatsby/CHANGELOG.md | 22 +++++++++---------- 30 files changed, 78 insertions(+), 74 deletions(-) diff --git a/.github/actions/high-priority-prs/src/__tests__/fixtures/data.json b/.github/actions/high-priority-prs/src/__tests__/fixtures/data.json index b1553f20c2718..f42c7fd2b544c 100644 --- a/.github/actions/high-priority-prs/src/__tests__/fixtures/data.json +++ b/.github/actions/high-priority-prs/src/__tests__/fixtures/data.json @@ -7356,7 +7356,7 @@ { "commit": { "authoredDate": "2019-06-03T02:42:32Z", - "message": "Made the doc easier to read\n\n- Moved a lot of sentences into active voice\r\n- Removed unnecessary words and sentences\r\n- Fixed some grammatical errors\r\n- Removed potentially confusing emojis as a literary device\r\n- Split up some long sentences into shorter ones\r\n- Added a link to https://www.gatsbyjs.com/blog/2018-06-08-life-after-layouts/ in the layouts section to help people move from Gatsby's layout behavior in v1\r\n- Capitalized instances of \"Babel\" that were lowercase" + "message": "Made the doc easier to read\n\n- Moved a lot of sentences into active voice\r\n- Removed unnecessary words and sentences\r\n- Fixed some grammatical errors\r\n- Removed potentially confusing emojis as a literary device\r\n- Split up some long sentences into shorter ones\r\n- Added a link to https://www.gatsbyjs.org/blog/2018-06-08-life-after-layouts/ in the layouts section to help people move from Gatsby's layout behavior in v1\r\n- Capitalized instances of \"Babel\" that were lowercase" } }, { diff --git a/deprecated-packages/gatsby-image/src/index.js b/deprecated-packages/gatsby-image/src/index.js index 37533e35a8093..923b344a0c0ce 100644 --- a/deprecated-packages/gatsby-image/src/index.js +++ b/deprecated-packages/gatsby-image/src/index.js @@ -192,7 +192,7 @@ function groupByMedia(imageVariants) { if (without.length > 1 && process.env.NODE_ENV !== `production`) { console.warn( - `We've found ${without.length} sources without a media property. They might be ignored by the browser, see: https://www.gatsbyjs.com/packages/gatsby-image/#art-directing-multiple-images` + `We've found ${without.length} sources without a media property. They might be ignored by the browser, see: https://www.gatsbyjs.com/plugins/gatsby-image/#art-directing-multiple-images` ) } diff --git a/deprecated-packages/gatsby-recipes/recipes/gatsby-plugin-layout.mdx b/deprecated-packages/gatsby-recipes/recipes/gatsby-plugin-layout.mdx index 6f3d01b81fa33..4ccd134e4848c 100644 --- a/deprecated-packages/gatsby-recipes/recipes/gatsby-plugin-layout.mdx +++ b/deprecated-packages/gatsby-recipes/recipes/gatsby-plugin-layout.mdx @@ -1,6 +1,6 @@ # Setup gatsby-plugin-layout -This plugin sets up [gatsby-plugin-layout](https://www.gatsbyjs.com/packages/gatsby-plugin-layout/?=gatsby%20layout), which enables adding components that live above the page components and persist across page changes. +This plugin sets up [gatsby-plugin-layout](https://www.gatsbyjs.com/plugins/gatsby-plugin-layout/?=gatsby%20layout), which enables adding components that live above the page components and persist across page changes. This can be helpful for: @@ -15,24 +15,24 @@ This recipe: Installs necessary NPM packages - + --- Installs the Layout plugin in gatsby-config.js - + --- Writes out a sample layout component to get started with. --- Read more about the documentation for Gatsby Layout Component here: -https://www.gatsbyjs.com/packages/gatsby-plugin-layout/ +https://www.gatsbyjs.com/plugins/gatsby-plugin-layout/ diff --git a/deprecated-packages/gatsby-recipes/recipes/gatsby-plugin-react-helmet.mdx b/deprecated-packages/gatsby-recipes/recipes/gatsby-plugin-react-helmet.mdx index 37866a98e2c0d..eee1f4b9c9e3d 100644 --- a/deprecated-packages/gatsby-recipes/recipes/gatsby-plugin-react-helmet.mdx +++ b/deprecated-packages/gatsby-recipes/recipes/gatsby-plugin-react-helmet.mdx @@ -4,7 +4,7 @@ React Helmet is a reusable React component that manages all of your changes to t Helmet takes plain HTML tags and outputs plain HTML tags. -[gatsby-plugin-helmet](https://www.gatsbyjs.com/packages/gatsby-plugin-react-helmet/?=react%20helmet) makes it easy to use React Helmet inside Gatsby projects as it automatically adds title and meta tags to the HTML during SSR. +[gatsby-plugin-helmet](https://www.gatsbyjs.com/plugins/gatsby-plugin-react-helmet/?=react%20helmet) makes it easy to use React Helmet inside Gatsby projects as it automatically adds title and meta tags to the HTML during SSR. This recipe: @@ -33,7 +33,7 @@ Writes out an `` component which helps ensure pages have the necessary titl --- Read more about Gatsby React Helmet here: -https://www.gatsbyjs.com/packages/gatsby-plugin-react-helmet +https://www.gatsbyjs.com/plugins/gatsby-plugin-react-helmet You can also read about the "SEO" component here: https://www.gatsbyjs.com/docs/add-seo-component/ diff --git a/deprecated-packages/gatsby-recipes/recipes/gatsby-theme-blog-core.mdx b/deprecated-packages/gatsby-recipes/recipes/gatsby-theme-blog-core.mdx index 60816bb94a0db..913c19740c920 100644 --- a/deprecated-packages/gatsby-recipes/recipes/gatsby-theme-blog-core.mdx +++ b/deprecated-packages/gatsby-recipes/recipes/gatsby-theme-blog-core.mdx @@ -1,6 +1,6 @@ # Gatsby Theme Blog Core Starter Recipe -[Gatsby theme blog core](https://www.gatsbyjs.com/packages/gatsby-theme-blog-core/) is a great theme for adding blog functionality to your site. It's designed to handle sourcing your blog data for you so you can style it however you like. +[Gatsby theme blog core](https://www.gatsbyjs.com/plugins/gatsby-theme-blog-core/) is a great theme for adding blog functionality to your site. It's designed to handle sourcing your blog data for you so you can style it however you like. This recipe: @@ -14,14 +14,20 @@ Installs necessary NPM packages. Installs the `gatsby-theme-blog-core` plugin in `gatsby-config.js` and makes use of the `basePath` configuration so the blog listing appears at `/blog`. - + --- -Adds some posts. +Adds some posts. - - + + --- diff --git a/deprecated-packages/gatsby-recipes/recipes/gatsby-theme-blog.mdx b/deprecated-packages/gatsby-recipes/recipes/gatsby-theme-blog.mdx index 35b32ded45266..77707843f8132 100644 --- a/deprecated-packages/gatsby-recipes/recipes/gatsby-theme-blog.mdx +++ b/deprecated-packages/gatsby-recipes/recipes/gatsby-theme-blog.mdx @@ -1,6 +1,6 @@ # Setup Gatsby Theme Blog -[Gatsby theme blog](https://www.gatsbyjs.com/packages/gatsby-theme-blog/) is a great theme for adding blog functionality to your site. +[Gatsby theme blog](https://www.gatsbyjs.com/plugins/gatsby-theme-blog/) is a great theme for adding blog functionality to your site. This recipe: @@ -15,13 +15,16 @@ Installs necessary NPM packages. Installs the `gatsby-theme-blog` plugin in `gatsby-config.js` and makes use of the `basePath` configuration so the blog listing appears at `/blog`. - + --- Adds a post. - + --- diff --git a/deprecated-packages/gatsby-recipes/recipes/gatsby-theme-notes.mdx b/deprecated-packages/gatsby-recipes/recipes/gatsby-theme-notes.mdx index 2a92d09e5884d..160e06dadcec5 100644 --- a/deprecated-packages/gatsby-recipes/recipes/gatsby-theme-notes.mdx +++ b/deprecated-packages/gatsby-recipes/recipes/gatsby-theme-notes.mdx @@ -1,6 +1,6 @@ # Gatsby Theme Notes Starter Recipe -[Gatsby theme notes](https://www.gatsbyjs.com/packages/gatsby-theme-notes) is a great theme for adding learning notes to your site. +[Gatsby theme notes](https://www.gatsbyjs.com/plugins/gatsby-theme-notes) is a great theme for adding learning notes to your site. This recipe: @@ -14,13 +14,16 @@ Installs necessary NPM package. Installs the `gatsby-theme-notes` plugin in `gatsby-config.js`. - + --- Adds a note. - + --- @@ -29,4 +32,3 @@ After installing this recipe, you can use your site for notetaking. When you've finished installing the recipe, run `gatsby develop` and check out `http://localhost:8000/notes` for the list of notes. --- - diff --git a/deprecated-packages/gatsby-recipes/recipes/pwa.mdx b/deprecated-packages/gatsby-recipes/recipes/pwa.mdx index 232939ade4d8b..dc2019a79b7be 100644 --- a/deprecated-packages/gatsby-recipes/recipes/pwa.mdx +++ b/deprecated-packages/gatsby-recipes/recipes/pwa.mdx @@ -50,5 +50,5 @@ After running this recipe, your site will be a PWA. Refer to the documentation for the manifest & offline plugins if there are any other edits you'd like to make. -- https://www.gatsbyjs.com/packages/gatsby-plugin-manifest -- https://www.gatsbyjs.com/packages/gatsby-plugin-offline +- https://www.gatsbyjs.com/plugins/gatsby-plugin-manifest +- https://www.gatsbyjs.com/plugins/gatsby-plugin-offline diff --git a/deprecated-packages/gatsby-recipes/src/providers/gatsby/fixtures/gatsby-starter-hello-world/gatsby-config.js b/deprecated-packages/gatsby-recipes/src/providers/gatsby/fixtures/gatsby-starter-hello-world/gatsby-config.js index 8975d05ac7798..ccf4e9671b419 100644 --- a/deprecated-packages/gatsby-recipes/src/providers/gatsby/fixtures/gatsby-starter-hello-world/gatsby-config.js +++ b/deprecated-packages/gatsby-recipes/src/providers/gatsby/fixtures/gatsby-starter-hello-world/gatsby-config.js @@ -1,7 +1,7 @@ /** * Configure your Gatsby site with this file. * - * See: https://www.gatsbyjs.com/docs/gatsby-config/ + * See: https://www.gatsbyjs.org/docs/gatsby-config/ */ module.exports = { /* Your site config here */ diff --git a/examples/using-gatsby-source-graphql/README.md b/examples/using-gatsby-source-graphql/README.md index 00b514c7871c0..cbc10a0747825 100644 --- a/examples/using-gatsby-source-graphql/README.md +++ b/examples/using-gatsby-source-graphql/README.md @@ -2,7 +2,7 @@ Simple gatsby site that displays blog with data inside GraphCMS. -Built using [gatsby-source-graphql](https://www.gatsbyjs.com/packages/gatsby-source-graphql/). +Built using [gatsby-source-graphql](https://www.gatsbyjs.com/plugins/gatsby-source-graphql/). diff --git a/packages/gatsby-design-tokens/CHANGELOG.md b/packages/gatsby-design-tokens/CHANGELOG.md index 2f85f3d48ec8d..8e0907bd0b704 100644 --- a/packages/gatsby-design-tokens/CHANGELOG.md +++ b/packages/gatsby-design-tokens/CHANGELOG.md @@ -343,8 +343,8 @@ Here's all changes listed by "token group": - add `colors.whiteFade[5]` - BREAKING CHANGE: fix `colors.blackFade[80]`, `colors.whiteFade[80]` - both were set to an opacity of `.85`, adjusted to `.8` - - TODO: Adjust a couple of values for gatsbyjs.com; no clue about where we currently might use this in `gatsby-interface` and related (.com/Cloud dashboard). -- feat: port `colors.code` from the gatsbyjs.com `theme-ui` theme to the `colors` tokens + - TODO: Adjust a couple of values for gatsbyjs.org; no clue about where we currently might use this in `gatsby-interface` and related (.com/Cloud dashboard). +- feat: port `colors.code` from the gatsbyjs.org `theme-ui` theme to the `colors` tokens - 💚 This improves compliance with WCAG 2.0 AA color contrasts. - feat: add `colors.code.copyButton` - feat: add `colors.code.lineHighlightBackground` @@ -384,7 +384,7 @@ Here's all changes listed by "token group": ##### `sizes` - BREAKING CHANGE: removed - - As discussed in https://github.com/gatsby-inc/gatsby-interface/issues/181, this moves the current gatsbyjs.com-centric `sizes` tokens to `theme-gatsbyjs-org` for clarity, until a clear pattern emerges. + - As discussed in https://github.com/gatsby-inc/gatsby-interface/issues/181, this moves the current gatsbyjs.org-centric `sizes` tokens to `theme-gatsbyjs-org` for clarity, until a clear pattern emerges. ##### `space` @@ -402,11 +402,11 @@ Here's all changes listed by "token group": ##### `zIndices` - BREAKING CHANGE: removed - - As discussed in https://github.com/gatsby-inc/gatsby-interface/issues/181, this moves the current gatsbyjs.com-centric `zIndices` tokens to `theme-gatsbyjs-org`for clarity, until a clear pattern emerges. + - As discussed in https://github.com/gatsby-inc/gatsby-interface/issues/181, this moves the current gatsbyjs.org-centric `zIndices` tokens to `theme-gatsbyjs-org`for clarity, until a clear pattern emerges. #### Themes -- feat: add base `theme-ui` Gatsby theme, gatsbyjs.com `theme-ui` theme +- feat: add base `theme-ui` Gatsby theme, gatsbyjs.org `theme-ui` theme - Both themes don't tree-shake yet, so no `agadoo` yet in the corresponding `gatsby-design-tokens/package.json` scripts. - Both export the `theme-ui` theme as `theme` and also provide individual token group exports (because we require them in `www` for usage outside of the `theme-ui` context). - Example usage: diff --git a/packages/gatsby-design-tokens/README.md b/packages/gatsby-design-tokens/README.md index c446c82c7d29b..8b859b86f19a1 100644 --- a/packages/gatsby-design-tokens/README.md +++ b/packages/gatsby-design-tokens/README.md @@ -100,8 +100,6 @@ import { - `rem` values are based on a `font-size` of `16px` for the root element. - All tokens work in the context of [Theme UI's Theme Scales](https://theme-ui.com/theme-spec/#theme-scales), with the exception of `breakpoints`: Use `breakpointsArray` for `theme-ui` and its [responsive styles](https://theme-ui.com/getting-started/#responsive-styles) feature. -Find a work-in-progress list of design tokens in the design tokens documentation at [gatsbyjs.com/guidelines/design-tokens](https://www.gatsbyjs.com/guidelines/design-tokens/). - ## `theme-ui` themes 🎨 ### `theme` diff --git a/packages/gatsby-plugin-google-gtag/README.md b/packages/gatsby-plugin-google-gtag/README.md index 339e82a9902b0..6cd023189ccfd 100644 --- a/packages/gatsby-plugin-google-gtag/README.md +++ b/packages/gatsby-plugin-google-gtag/README.md @@ -4,7 +4,7 @@ Easily add Google Global Site Tag to your Gatsby site. > The global site tag (gtag.js) is a JavaScript tagging framework and API that allows you to send event data to Google Analytics, Google Ads, Campaign Manager, Display & Video 360, and Search Ads 360. -Global site tag (gtag.js) is meant to combine multiple Google tagging systems and can replace older ones such as [analytics.js](https://developers.google.com/analytics/devguides/collection/analyticsjs/) ([gatsby-plugin-google-analytics](https://www.gatsbyjs.com/packages/gatsby-plugin-google-analytics/)). +Global site tag (gtag.js) is meant to combine multiple Google tagging systems and can replace older ones such as [analytics.js](https://developers.google.com/analytics/devguides/collection/analyticsjs/) ([gatsby-plugin-google-analytics](https://www.gatsbyjs.com/plugins/gatsby-plugin-google-analytics/)). For more general information on gtag you can read Google's official documentation on the subject: https://developers.google.com/gtagjs/. @@ -89,7 +89,7 @@ import { OutboundLink } from "gatsby-plugin-google-gtag" export default () => (
- + Visit the Google Global Site Tag plugin page!
diff --git a/packages/gatsby-plugin-mdx/README.md b/packages/gatsby-plugin-mdx/README.md index 6933163698d5e..62388d19c9b4b 100644 --- a/packages/gatsby-plugin-mdx/README.md +++ b/packages/gatsby-plugin-mdx/README.md @@ -317,12 +317,12 @@ Here's a YouTube embed This config option is used for compatibility with a set of plugins many people [use with remark](https://www.gatsbyjs.com/plugins/?=gatsby-remark-) that require the gatsby environment to function properly. In some cases, like -[gatsby-remark-prismjs](https://www.gatsbyjs.com/packages/gatsby-remark-prismjs/?=gatsby-remark-), +[gatsby-remark-prismjs](https://www.gatsbyjs.com/plugins/gatsby-remark-prismjs/?=gatsby-remark-), it makes more sense to use a library like [prism-react-renderer](https://github.com/FormidableLabs/prism-react-renderer) to render codeblocks using a [React component](/api-reference/mdx-provider). In other cases, like -[gatsby-remark-images](https://www.gatsbyjs.com/packages/gatsby-remark-images/?=gatsby-remark-), +[gatsby-remark-images](https://www.gatsbyjs.com/plugins/gatsby-remark-images/?=gatsby-remark-), the interaction with the Gatsby APIs is well deserved because the images can be optimized by Gatsby and you should continue using it. diff --git a/packages/gatsby-plugin-offline/src/__tests__/fixtures/public/index.html b/packages/gatsby-plugin-offline/src/__tests__/fixtures/public/index.html index 1e5028d179543..53b9025bf0c93 100644 --- a/packages/gatsby-plugin-offline/src/__tests__/fixtures/public/index.html +++ b/packages/gatsby-plugin-offline/src/__tests__/fixtures/public/index.html @@ -60,11 +60,11 @@ - - + + - + @@ -872,7 +872,7 @@

Modern Development, for the Content Web

Fast sites. Fast iterations. Unlike your CMS, Gatsby engineers the development experience for performance.

+
Get started todayWhy Gatsby?
800+ contributors, 24.2 k stars @@ -1150,7 +1150,7 @@

Product

Why Gatsby?

How It Works

Bring Data From AnywhereWrite Modern AppsUnreal PerformanceOne-Click DeploymentAll Guides
-

Docs & Help

DocumentationTutorialBlogCommunity
+

Docs & Help

DocumentationTutorialBlogCommunity

Company

About UsSupportTraining
diff --git a/packages/gatsby-plugin-typescript/README.md b/packages/gatsby-plugin-typescript/README.md index 852d98762d657..06406d3bbfc22 100644 --- a/packages/gatsby-plugin-typescript/README.md +++ b/packages/gatsby-plugin-typescript/README.md @@ -58,7 +58,7 @@ compiler is not involved, the following applies: > and import x, {y} from "z". > > Does not support baseUrl. -> Workaround: use [gatsby-plugin-root-import](https://www.gatsbyjs.com/packages/gatsby-plugin-root-import/) +> Workaround: use [gatsby-plugin-root-import](https://www.gatsbyjs.com/plugins/gatsby-plugin-root-import/) > and configure it to point the baseUrl value (also set baseUrl option in tsconfig.json file). https://babeljs.io/docs/en/babel-plugin-transform-typescript.html diff --git a/packages/gatsby-plugin-typography/README.md b/packages/gatsby-plugin-typography/README.md index 613af43ffe682..bb3fcfe448258 100644 --- a/packages/gatsby-plugin-typography/README.md +++ b/packages/gatsby-plugin-typography/README.md @@ -2,9 +2,6 @@ A Gatsby plugin for utilizing the [Typography](https://kyleamathews.github.io/typography.js/) library with minimal configuration. -See it in action in the [Tutorial](https://www.gatsbyjs.com/tutorial/part-3/) -([source](https://github.com/gatsbyjs/gatsby/tree/master/packages/gatsby-plugin-typography)) - ## Install `npm install gatsby-plugin-typography react-typography typography` diff --git a/packages/gatsby-remark-copy-linked-files/README.md b/packages/gatsby-remark-copy-linked-files/README.md index 39ac3a4e03aed..5f18d3d3cad30 100644 --- a/packages/gatsby-remark-copy-linked-files/README.md +++ b/packages/gatsby-remark-copy-linked-files/README.md @@ -30,7 +30,7 @@ The `my-awesome-pdf.pdf` file will be copied to the root directory (i.e., `publi **Default settings:** -Add `gatsby-remark-copy-linked-files` plugin as a plugin to [`gatsby-transformer-remark`](https://www.gatsbyjs.com/packages/gatsby-transformer-remark/): +Add `gatsby-remark-copy-linked-files` plugin as a plugin to [`gatsby-transformer-remark`](https://www.gatsbyjs.com/plugins/gatsby-transformer-remark/): ```javascript // In your gatsby-config.js diff --git a/packages/gatsby-remark-custom-blocks/README.md b/packages/gatsby-remark-custom-blocks/README.md index daa1fbd488606..3e7d1e520f156 100644 --- a/packages/gatsby-remark-custom-blocks/README.md +++ b/packages/gatsby-remark-custom-blocks/README.md @@ -11,7 +11,7 @@ Adds custom blocks to `MarkdownRemark` using [remark-custom-blocks](https://github.com/zestedesavoir/zmarkdown/tree/master/packages/remark-custom-blocks). -Unlike in [gatsby-remark-component](https://www.gatsbyjs.com/packages/gatsby-remark-component/) where you can only use HTML within the custom component tag, custom blocks allow you to use markdown within the block. +Unlike in [gatsby-remark-component](https://www.gatsbyjs.com/plugins/gatsby-remark-component/) where you can only use HTML within the custom component tag, custom blocks allow you to use markdown within the block. ## Install diff --git a/packages/gatsby-remark-embed-snippet/README.md b/packages/gatsby-remark-embed-snippet/README.md index 80431cca8ac90..00605410070ae 100644 --- a/packages/gatsby-remark-embed-snippet/README.md +++ b/packages/gatsby-remark-embed-snippet/README.md @@ -4,7 +4,7 @@ Embeds the contents of specified files as code snippets. ## Installation -**Note**: This plugin depends on [gatsby-remark-prismjs](https://www.gatsbyjs.com/packages/gatsby-remark-prismjs/) and [gatsby-transformer-remark](https://www.gatsbyjs.com/packages/gatsby-transformer-remark/) plugins +**Note**: This plugin depends on [gatsby-remark-prismjs](https://www.gatsbyjs.com/plugins/gatsby-remark-prismjs/) and [gatsby-transformer-remark](https://www.gatsbyjs.com/plugins/gatsby-transformer-remark/) plugins ```shell npm install gatsby-remark-embed-snippet gatsby-remark-prismjs gatsby-transformer-remark prismjs @@ -14,7 +14,7 @@ npm install gatsby-remark-embed-snippet gatsby-remark-prismjs gatsby-transformer > **Important**: _You must add `gatsby-remark-embed-snippet` before `gatsby-remark-prismjs` in your plugins array!_ > Otherwise, this plugin will not work because the code snippet files first need to be inlined before they can be transformed into code blocks. -> For more information, see [gatsby-remark-prismjs](https://www.gatsbyjs.com/packages/gatsby-remark-prismjs/). +> For more information, see [gatsby-remark-prismjs](https://www.gatsbyjs.com/plugins/gatsby-remark-prismjs/). To use `gatsby-remark-embed-snippet` plugin: diff --git a/packages/gatsby-remark-images/README.md b/packages/gatsby-remark-images/README.md index b50a0c907230a..f34c9a50de3c0 100644 --- a/packages/gatsby-remark-images/README.md +++ b/packages/gatsby-remark-images/README.md @@ -96,7 +96,7 @@ This plugin will support the following formats: - JPEG - PNG -Since [Sharp][5] is used for image processing, this plugin will not support GIFs or SVGs. If you would like to render these file types with the image markdown syntax, use the [`gatsby-remark-copy-linked-files`](https://www.gatsbyjs.com/packages/gatsby-remark-copy-linked-files/) plugin. Do note with this it will load in the images, but won't use the features of [Sharp][5] such as the elastic container or the blur-up enhancements. +Since [Sharp][5] is used for image processing, this plugin will not support GIFs or SVGs. If you would like to render these file types with the image markdown syntax, use the [`gatsby-remark-copy-linked-files`](https://www.gatsbyjs.com/plugins/gatsby-remark-copy-linked-files/) plugin. Do note with this it will load in the images, but won't use the features of [Sharp][5] such as the elastic container or the blur-up enhancements. [1]: https://jmperezperez.com/medium-image-progressive-loading-placeholder/ [2]: https://code.facebook.com/posts/991252547593574/the-technology-behind-preview-photos/ diff --git a/packages/gatsby-remark-katex/README.md b/packages/gatsby-remark-katex/README.md index a19ffdb35aa1b..82d41e0139e32 100644 --- a/packages/gatsby-remark-katex/README.md +++ b/packages/gatsby-remark-katex/README.md @@ -58,7 +58,7 @@ a^2 + b^2 = c^2 $$ ``` -[1]: https://www.gatsbyjs.com/packages/gatsby-remark-katex/ +[1]: https://www.gatsbyjs.com/plugins/gatsby-remark-katex/ [2]: https://github.com/Rokt33r/remark-math [3]: https://github.com/KaTeX/KaTeX [4]: https://github.com/gatsbyjs/gatsby/blob/master/examples/using-remark/src/templates/template-blog-post.js diff --git a/packages/gatsby-remark-prismjs/README.md b/packages/gatsby-remark-prismjs/README.md index 1a66bf4868cc6..02b57cd0b0dbe 100644 --- a/packages/gatsby-remark-prismjs/README.md +++ b/packages/gatsby-remark-prismjs/README.md @@ -400,7 +400,7 @@ You can specify language for `diff` code blocks by using `diff-[language]` to en ### Line hiding -As well as highlighting lines, it's possible to _hide_ lines from the rendered output. Often this is handy when using `gatsby-remark-prismjs` along with [`gatsby-remark-embed-snippet`](https://www.gatsbyjs.com/packages/gatsby-remark-embed-snippet/). +As well as highlighting lines, it's possible to _hide_ lines from the rendered output. Often this is handy when using `gatsby-remark-prismjs` along with [`gatsby-remark-embed-snippet`](https://www.gatsbyjs.com/plugins/gatsby-remark-embed-snippet/). As with highlighting lines, you can control which lines to hide by adding directives as comments in your source code. diff --git a/packages/gatsby-source-contentful/README.md b/packages/gatsby-source-contentful/README.md index 027d9a7d08905..8463df758e773 100644 --- a/packages/gatsby-source-contentful/README.md +++ b/packages/gatsby-source-contentful/README.md @@ -263,7 +263,7 @@ On Contentful, a "Long text" field uses Markdown by default. The field is expose } ``` -Unless the text is Markdown-free, you cannot use the returned value directly. In order to handle the Markdown content, you must use a transformer plugin such as [`gatsby-transformer-remark`](https://www.gatsbyjs.com/packages/gatsby-transformer-remark/). The transformer will create a `childMarkdownRemark` on the "Long text" field and expose the generated html as a child node: +Unless the text is Markdown-free, you cannot use the returned value directly. In order to handle the Markdown content, you must use a transformer plugin such as [`gatsby-transformer-remark`](https://www.gatsbyjs.com/plugins/gatsby-transformer-remark/). The transformer will create a `childMarkdownRemark` on the "Long text" field and expose the generated html as a child node: ```graphql { diff --git a/packages/gatsby-source-filesystem/README.md b/packages/gatsby-source-filesystem/README.md index 2501bbe147393..41d3a45538bb3 100644 --- a/packages/gatsby-source-filesystem/README.md +++ b/packages/gatsby-source-filesystem/README.md @@ -130,8 +130,6 @@ createFilePath({ #### Example usage -The following is taken from [Gatsby Tutorial, Part Seven](https://www.gatsbyjs.com/tutorial/part-7/) and is used to create URL slugs for markdown pages. - ```javascript const { createFilePath } = require(`gatsby-source-filesystem`) diff --git a/packages/gatsby-source-filesystem/index.d.ts b/packages/gatsby-source-filesystem/index.d.ts index b2e78493450c6..2d578b9e1a3da 100644 --- a/packages/gatsby-source-filesystem/index.d.ts +++ b/packages/gatsby-source-filesystem/index.d.ts @@ -1,19 +1,19 @@ import { Node, Store, NodePluginArgs } from "gatsby" /** - * @see https://www.gatsbyjs.com/packages/gatsby-source-filesystem/?=files#createfilepath + * @see https://www.gatsbyjs.com/plugins/gatsby-source-filesystem/?=files#createfilepath */ export function createFilePath(args: CreateFilePathArgs): string /** - * @see https://www.gatsbyjs.com/packages/gatsby-source-filesystem/?=files#createremotefilenode + * @see https://www.gatsbyjs.com/plugins/gatsby-source-filesystem/?=files#createremotefilenode */ export function createRemoteFileNode( args: CreateRemoteFileNodeArgs ): Promise /** - * @see https://www.gatsbyjs.com/packages/gatsby-source-filesystem/?=files#createfilenodefrombuffer + * @see https://www.gatsbyjs.com/plugins/gatsby-source-filesystem/?=files#createfilenodefrombuffer */ export function createFileNodeFromBuffer( args: CreateFileNodeFromBufferArgs @@ -103,7 +103,7 @@ export interface FileSystemConfig { } /** - * @see https://www.gatsbyjs.com/packages/gatsby-source-filesystem/?=filesy#options + * @see https://www.gatsbyjs.com/plugins/gatsby-source-filesystem/?=filesy#options */ interface FileSystemOptions { name: string diff --git a/packages/gatsby-source-filesystem/src/gatsby-node.js b/packages/gatsby-source-filesystem/src/gatsby-node.js index 4bbe8dc5988de..8a2d70003962d 100644 --- a/packages/gatsby-source-filesystem/src/gatsby-node.js +++ b/packages/gatsby-source-filesystem/src/gatsby-node.js @@ -171,7 +171,7 @@ exports.sourceNodes = (api, pluginOptions) => { The path passed to gatsby-source-filesystem does not exist on your file system: ${pluginOptions.path} Please pick a path to an existing directory. -See docs here - https://www.gatsbyjs.com/packages/gatsby-source-filesystem/ +See docs here - https://www.gatsbyjs.com/plugins/gatsby-source-filesystem/ `) } diff --git a/packages/gatsby-source-wordpress/docs/tutorials/building-a-new-site-wordpress-and-gatsby.md b/packages/gatsby-source-wordpress/docs/tutorials/building-a-new-site-wordpress-and-gatsby.md index 2577382046ed8..cdd61eed9f606 100644 --- a/packages/gatsby-source-wordpress/docs/tutorials/building-a-new-site-wordpress-and-gatsby.md +++ b/packages/gatsby-source-wordpress/docs/tutorials/building-a-new-site-wordpress-and-gatsby.md @@ -13,7 +13,7 @@ gatsby new wordpress-tutorial-site cd wordpress-tutorial-site ``` -Install the `gatsby-source-wordpress` plugin. For extra reading on the plugin’s features and examples of GraphQL queries not included in this tutorial, see the [`gatsby-source-wordpress` plugin’s README file](https://www.gatsbyjs.com/packages/gatsby-source-wordpress). +Install the `gatsby-source-wordpress` plugin. For extra reading on the plugin’s features and examples of GraphQL queries not included in this tutorial, see the [`gatsby-source-wordpress` plugin’s README file](https://www.gatsbyjs.com/plugins/gatsby-source-wordpress). ```shell npm install gatsby-source-wordpress diff --git a/packages/gatsby-transformer-sharp/README.md b/packages/gatsby-transformer-sharp/README.md index 38c1ed6806bd0..05474cc9db7ea 100644 --- a/packages/gatsby-transformer-sharp/README.md +++ b/packages/gatsby-transformer-sharp/README.md @@ -23,7 +23,7 @@ module.exports = { Please note that you must have a source plugin (which brings in images) installed in your project. Otherwise, no `ImageSharp` nodes can be created for your files. Examples would be [`gatsby-source-filesystem`](/plugins/gatsby-source-filesystem) or source plugins for (headless) CMSs like [`gatsby-source-wordpress`](/plugins/gatsby-source-wordpress). -**Note**: An exception to this is when using [`gatsby-source-contentful`](/plugins/gatsby-source-contentful/), as the source plugin and the assets are not [downloaded to the local filesystem](https://www.gatsbyjs.com/packages/gatsby-source-contentful/#download-assets-for-static-distribution). By default, the `gatsby-source-contentful` plugin creates a `ContentfulAsset` node for every image with links to Contentful’s CDN, therefore it is not necessary to use `gatsby-transformer-sharp` together with `gatsby-source-contentful`. +**Note**: An exception to this is when using [`gatsby-source-contentful`](/plugins/gatsby-source-contentful/), as the source plugin and the assets are not [downloaded to the local filesystem](https://www.gatsbyjs.com/plugins/gatsby-source-contentful/#download-assets-for-static-distribution). By default, the `gatsby-source-contentful` plugin creates a `ContentfulAsset` node for every image with links to Contentful’s CDN, therefore it is not necessary to use `gatsby-transformer-sharp` together with `gatsby-source-contentful`. ## Parsing algorithm diff --git a/packages/gatsby/CHANGELOG.md b/packages/gatsby/CHANGELOG.md index 116289a6f9f10..44d01af447c62 100644 --- a/packages/gatsby/CHANGELOG.md +++ b/packages/gatsby/CHANGELOG.md @@ -7635,7 +7635,7 @@ Our first beta!!! 🎉 ### Added - Allow for gatsby-remark-smartypants options #1166 @mitchejj -- New design (for gatsbyjs.com) + new home page #1170 @kyleamathews +- New design (for gatsbyjs.org) + new home page #1170 @kyleamathews - Add ability to locally define plugins #1126 @0x80 - Add rough draft for docs for creating source plugins #1159 @kyleamathews - Optimizations around prefetching page resources #1133 @kyleamathews @@ -7705,45 +7705,45 @@ Our first beta!!! 🎉 - Add new plugin for extracting JSDocs information from JavaScript files using documentation.js #1053 @kyleamathews - Add new API spec (rough draft) @kyleamathews - https://www.gatsbyjs.com/docs/api-specification/ + https://www.gatsbyjs.org/docs/api-specification/ - Add new API reference pages @kyleamathews e.g. - https://www.gatsbyjs.com/docs/node-apis/ + https://www.gatsbyjs.org/docs/node-apis/ - Add "duotone" image processing option to gatsby-plugin-sharp #1047 @fk - Add example site for image processing @fk https://image-processing.gatsbyjs.org/ - Add example site for css-in-js library Glamor @kyleamathews - https://using-glamor.gatsbyjs.com/ + https://using-glamor.gatsbyjs.org/ - Add example site for css-in-js library Styled Components @kyleamathews https://using-styled-components.gatsbyjs.org/ ### Changed -#### Grand big API renaming based on our new API spec https://www.gatsbyjs.com/docs/api-specification/ +#### Grand big API renaming based on our new API spec https://www.gatsbyjs.org/docs/api-specification/ API changes: -[Action creators](https://www.gatsbyjs.com/docs/bound-action-creators/): +[Action creators](https://www.gatsbyjs.org/docs/bound-action-creators/): - `upsertPage` is now `createPage` - `addFieldToNode` is now `createNodeField` - `deletePageByPath` is now `deletePage` - `addNodeToParent` is now `createParentChildLink` -[gatsby-browser.js APIs](https://www.gatsbyjs.com/docs/browser-apis/): +[gatsby-browser.js APIs](https://www.gatsbyjs.org/docs/browser-apis/): - `clientEntry` is now `onClientEntry` -[gatsby-node.js APIs](https://www.gatsbyjs.com/docs/node-apis/): +[gatsby-node.js APIs](https://www.gatsbyjs.org/docs/node-apis/): - `onNodeCreate` is now `onCreateNode` - `onUpsertPage` is now `onCreatePage` - `extendNodeType` is now `setFieldsOnGraphQLNodeType` -[gatsby-ssr.js APIs](https://www.gatsbyjs.com/docs/ssr-apis/): +[gatsby-ssr.js APIs](https://www.gatsbyjs.org/docs/ssr-apis/): - `modifyHeadComponents` and `modifyPostBodyComponents` were removed in favor of a new API - [`onRenderBody`](https://www.gatsbyjs.com/docs/ssr-apis/#onRenderBody). + [`onRenderBody`](https://www.gatsbyjs.org/docs/ssr-apis/#onRenderBody). - `replaceServerBodyRender` is now `replaceRenderer` ### Fixed @@ -7873,7 +7873,7 @@ export const pageQuery = graphql` ### Added -- Did the intitial build of the new gatsbyjs.com! It's in the `www` subdirectory +- Did the intitial build of the new gatsbyjs.org! It's in the `www` subdirectory on the 1.0 branch and is built on each push! That's my kind of integration testing :-) You can see the early version of the site at https://gatsbyjs.netlify.app/. PRs welcome! From e1e89a3836c5ed7863ab5d6bb6f6e8710693d073 Mon Sep 17 00:00:00 2001 From: Alex Reed Date: Wed, 16 Mar 2022 15:18:05 -0400 Subject: [PATCH 7/7] remove dead links from example repo readmes --- examples/no-trailing-slashes/README.md | 2 -- examples/using-asciidoc/README.md | 2 -- 2 files changed, 4 deletions(-) diff --git a/examples/no-trailing-slashes/README.md b/examples/no-trailing-slashes/README.md index 41a7d0879d4f9..4adb24701c8b5 100644 --- a/examples/no-trailing-slashes/README.md +++ b/examples/no-trailing-slashes/README.md @@ -1,5 +1,3 @@ # No trailing slashes -https://no-trailing-slashes.gatsbyjs.com - Gatsby example site that shows how to remove trailing slashes from urls. diff --git a/examples/using-asciidoc/README.md b/examples/using-asciidoc/README.md index 8986d37ae6de1..85373dd634db2 100644 --- a/examples/using-asciidoc/README.md +++ b/examples/using-asciidoc/README.md @@ -1,6 +1,4 @@ # Using AsciiDoc -https://using-asciidoc.gatsbyjs.com - Example site that demonstrates how to build a Gatsby site pulling in data from [asciidoc](http://asciidoc.org/)-files.