gatsbyjs · Aug 27, 2021 · Aug 30, 2021 · Aug 30, 2021 · Aug 30, 2021 · Aug 30, 2021
Showing 465 changed files with 11,170 additions and 22,089 deletions.
diff --git a/.circleci/config.yml b/.circleci/config.yml
@@ -354,6 +354,15 @@ jobs:
       - run: # Quick upgrade to the v2 (any version, we just need the real set version)
           command: yarn policies set-version berry
           working_directory: /tmp/e2e-tests/gatsby-pnp
+      - run: # Explicitly set nodeLinker to avoid Yarn selecting node_modules due to the Yarn 1.x lockfile
+          command: yarn config set nodeLinker pnp
+          working_directory: /tmp/e2e-tests/gatsby-pnp
+      - run: # Allow installs to change the lockfile
+          command: yarn config set enableImmutableInstalls false
+          working_directory: /tmp/e2e-tests/gatsby-pnp
+      - run: # Don't allow any fallback to root dependencies
+          command: yarn config set pnpFallbackMode none
+          working_directory: /tmp/e2e-tests/gatsby-pnp
       - run: # Forces to use the local packages
           command: yarn link --all --private ~/project
           working_directory: /tmp/e2e-tests/gatsby-pnp
@@ -482,6 +491,7 @@ jobs:
       - checkout
       - run: apt-get update && apt-get install jq python -y
       - <<: *restore_cache
+      - <<: *install_node_modules
       - run: git config --global user.name "GatsbyJS Bot"
       - run: git config --global user.email "core-team@gatsbyjs.com"
       - run: node scripts/gatsby-changelog-generator/update-and-open-pr.js
@@ -626,6 +636,22 @@ workflows:
           requires:
             - bootstrap-with-experimental-react
 
+  # Ideally, we should trigger this when any new release is created, sadly there is no easy way to do it:
+  # - Can't rely on tags: GitHub won't send webhook to CircleCI when there are more than 3 tags in one push
+  #   See: https://docs.github.com/en/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#push
+  # - Can't rely on pushes to "release/*" branches because we have "Only build pull requests" option enabled
+  #   (so pushes without pull requests are ignored by CircleCI)
+  nightly-update-changelogs:
+    triggers:
+      - schedule:
+          cron: "0 0 * * 1,2,3,4,5"
+          filters:
+            branches:
+              only:
+                - master
+    jobs:
+      - update_changelogs
+
   build-test:
     jobs:
       - bootstrap
@@ -713,8 +739,3 @@ workflows:
             branches:
               only:
                 - master
-#      - update_changelogs:
-#          filters:
-#            branches:
-#              only:
-#                - /release\/.+/
diff --git a/docs/contributing/docs-and-blog-components.md b/docs/contributing/docs-and-blog-components.md
@@ -201,7 +201,7 @@ Doing so will break localized versions of the page, which are stored in other re
 
 New docs and blog posts are added to the [docs](https://github.com/gatsbyjs/gatsby/tree/master/docs/) folder inside the Gatsby repository. They are stored as `.md` (Markdown) or `.mdx` (MDX) files and can be written using Markdown, or using inline JSX thanks to MDX. Writing in Markdown will output tags that are styled according to [Gatsby's design guidelines](/guidelines/color/).
 
-You can read more about writing in Markdown in the [Markdown syntax guide](/docs/how-to/routing/mdx/markdown-syntax).
+You can read more about writing in Markdown in the [Markdown syntax guide](/docs/reference/markdown-syntax/).
 
 ### Frontmatter
 

diff --git a/docs/contributing/docs-contributions/index.md b/docs/contributing/docs-contributions/index.md
@@ -10,7 +10,7 @@ When writing (or reviewing) learning materials that show Gatsby users how to com
 
 ## Top priorities
 
-Check the GitHub repo for issues labeled with ["type: documentation" and "good first issue"](https://github.com/gatsbyjs/gatsby/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+label%3A%22type%3A+documentation%22+label%3A%22good+first+issue%22) for your first time contributing to Gatsby, or [type: documentation" and "help wanted"](https://github.com/gatsbyjs/gatsby/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+label%3A%22type%3A+documentation%22+label%3A%22help+wanted%22) to see all documentation issues that are ready for community help. Once you start a Pull Request to address one of these issues, you can remove the "help wanted" label. As well, examine the list of articles that haven't been fully fleshed out at the [Stub List](/contributing/stub-list).
+Check the GitHub repo for issues labeled with ["type: documentation" and "good first issue"](https://github.com/gatsbyjs/gatsby/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+label%3A%22type%3A+documentation%22+label%3A%22good+first+issue%22) for your first time contributing to Gatsby, or [type: documentation" and "help wanted"](https://github.com/gatsbyjs/gatsby/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+label%3A%22type%3A+documentation%22+label%3A%22help+wanted%22) to see all documentation issues that are ready for community help. Once you start a Pull Request to address one of these issues, you can remove the "help wanted" label.
 
 ## Options for contributing to the Gatsby docs
 
@@ -37,7 +37,7 @@ For the purposes of an accessible document outline, content headings should go i
 
 ## Modifying Markdown files
 
-> 💡 New to writing Markdown? Check out the Gatsby [guide on Markdown Syntax](/docs/how-to/routing/mdx/markdown-syntax/)!
+> 💡 New to writing Markdown? Check out the Gatsby [guide on Markdown Syntax](/docs/reference/markdown-syntax/)!
 
 1. If you want to add/modify any Gatsby documentation, go to the
    [docs folder](https://github.com/gatsbyjs/gatsby/tree/master/docs) or [contributing folder](https://github.com/gatsbyjs/gatsby/tree/master/docs/contributing) on GitHub and
@@ -86,9 +86,9 @@ The docs include custom-built components to aid with navigation. In order to cus
 
 ### Adjusting breadcrumb titles
 
-The `<Breadcrumb />` component is used in layout files to display the hierarchy of pages a user is currently browsing on at the top of each doc.
+The `<Breadcrumb />` component is used in layout files to display the hierarchy of pages a user is currently browsing on at the top of each doc. Currently, you can only change the breadcrumb titles if you have access to the private GitHub repo where the Gatsby docs site is built. (This is only available to internal Gatsby staff at this time. We plan to make this available to open-source community members in the future, but we don't yet have a timeline for when that will happen.)
 
-To alter the title of a doc that is displayed in the Breadcrumb component, `breadcrumbTitle` is supported as a key in the [sidebar YAML files](https://github.com/gatsbyjs/gatsby/tree/master/www/src/data/sidebars). It is commonly used to provide an abbreviated version of a doc's title when displayed next to its parent page title, e.g. shortening "Adding a Custom webpack Config" to "webpack Config".
+To alter the title of a doc that is displayed in the Breadcrumb component, `breadcrumbTitle` is supported as a key in the sidebar YAML files. It is commonly used to provide an abbreviated version of a doc's title when displayed next to its parent page title, e.g. shortening "Adding a Custom webpack Config" to "webpack Config".
 
 ```yaml
 - title: Adding Page Transitions
@@ -145,9 +145,9 @@ Sometimes it makes sense to move or rename a file as part of docs restructuring
 
 - Run proposed structure changes by the Gatsby docs team in [a GitHub issue](/contributing/how-to-file-an-issue/) to ensure your change is accepted.
 - Update all instances of the old URL to your new one. [Find and replace](https://code.visualstudio.com/docs/editor/codebasics#_search-across-files) in VS Code can help. Check that the context of the original link reference still makes sense with the new one.
-- For SEO purposes, add a redirect to [`www/redirects.yaml`](https://github.com/gatsbyjs/gatsby/tree/master/www/redirects.yaml). Here's an example:
+- For SEO purposes, add a redirect to `legacy-redirects.yaml`. (This file currently only exists in the private repo where the Gatsby docs site is built. Only internal Gatsby staff have access to it.) Here's an example:
 
-```yaml:title=www/redirects.yaml
+```yaml:title=legacy-redirects.yaml
 - fromPath: /docs/source-plugin-tutorial/
   toPath: /tutorial/source-plugin-tutorial/
 ```

diff --git a/docs/contributing/docs-writing-process.md b/docs/contributing/docs-writing-process.md
@@ -14,13 +14,11 @@ When identifying a topic, start by:
 
    - This part may be covered if a docs issue is assigned to you, or if you’re signing up voluntarily to take on an issue.
 
-2. Look at the [stub list](/contributing/stub-list/) to find docs that need contributions.
+2. Look at the [learning workflow meta issue](https://github.com/gatsbyjs/gatsby/issues/13708) to find active areas looking for docs.
 
-3. Look at the [learning workflow meta issue](https://github.com/gatsbyjs/gatsby/issues/13708) to find active areas looking for docs.
+3. Read through the existing Gatsby docs information and find gaps in topic coverage. Is there an area you feel is missing? [File an issue](/contributing/how-to-file-an-issue/) to discuss it. If the team determines it warrants documentation, implement in a PR.
 
-4. Read through the existing Gatsby docs information and find gaps in topic coverage. Is there an area you feel is missing? [File an issue](/contributing/how-to-file-an-issue/) to discuss it. If the team determines it warrants documentation, implement in a PR.
-
-5. Observe common points of confusion or rough edges through user feedback and recommend solutions.
+4. Observe common points of confusion or rough edges through user feedback and recommend solutions.
 
 > _Note: It’s required to open a GitHub issue before submitting a PR if one does not already exist._
 
@@ -58,7 +56,7 @@ Create demo sites and examples to provide more authoritative material that suppo
 
 Follow the [docs structure](/contributing/docs-contributions/docs-structure/) to ensure you’re producing content in the right format for its purpose.
 
-Use the [Markdown syntax doc](/docs/how-to/routing/mdx/markdown-syntax/) to understand your options for formatting text with Markdown, and follow [accessibility recommendations](/docs/conceptual/making-your-site-accessible/#how-to-improve-accessibility) for [heading levels](/contributing/docs-contributions/#headings) and image alt text.
+Use the [Markdown syntax doc](/docs/reference/markdown-syntax/) to understand your options for formatting text with Markdown, and follow [accessibility recommendations](/docs/conceptual/making-your-site-accessible/#how-to-improve-accessibility) for [heading levels](/contributing/docs-contributions/#headings) and image alt text.
 
 Run the docs site locally to check formatting and functionality. There are instructions in the [contributing docs](/contributing/docs-contributions/).
 
@@ -76,7 +74,7 @@ Apply feedback from pull request reviews in order for them to be accepted. Furth
 - [Docs Structure](/contributing/docs-contributions/docs-structure/)
 - [How to File an Issue](/contributing/how-to-file-an-issue/)
 - [Gatsby Style Guide](/contributing/gatsby-style-guide/)
-- [Markdown Syntax Doc](/docs/how-to/routing/mdx/markdown-syntax/)
+- [Markdown Syntax Doc](/docs/reference/markdown-syntax/)
 - [Blog Post Guidelines](/contributing/blog-contributions/)
 - [Docs site setup instructions](/contributing/docs-contributions/#docs-site-setup-instructions)
 - [How to Open a Pull Request](/contributing/how-to-open-a-pull-request/)
diff --git a/docs/contributing/how-to-open-a-pull-request.md b/docs/contributing/how-to-open-a-pull-request.md
@@ -157,4 +157,4 @@ For more information on working with upstream repos, [visit the GitHub docs](htt
 - [Feature Branching and Workflows](https://git-scm.com/book/en/v1/Git-Branching-Branching-Workflows)
 - [Resolving merge conflicts](https://help.github.com/en/articles/resolving-a-merge-conflict-on-github)
 - [Managing Pull Requests](/contributing/managing-pull-requests/) on the Gatsby core team
-- [Guide on Markdown Syntax](/docs/how-to/routing/mdx/markdown-syntax/)
+- [Guide on Markdown Syntax](/docs/reference/markdown-syntax/)
diff --git a/docs/docs/conceptual/making-your-site-accessible.md b/docs/docs/conceptual/making-your-site-accessible.md
@@ -7,7 +7,9 @@ examples:
 
 The Gatsby team is passionate about helping you create websites that work for everyone, with helpful defaults that bake in web accessibility as well as performance optimizations. By making your website accessible to people with disabilities, you can make more inclusive sites that reach and remove barriers for more people on the Internet.
 
-## What is accessibility?
+## What is web accessibility?
+
+[Web accessibility](https://www.w3.org/WAI/fundamentals/accessibility-intro/#what) means that websites, tools, and technologies are designed and developed so that people with disabilities can use them. But not only people with permanent disabilities benefit from it. Accessibility also benefits people with temporary disabilities. For example, imagine being in an environment where you cannot listen to audio or you can't use a computer because of a broken arm.
 
 Back in the early days of the Web, Tim Berners-Lee, inventor of the World Wide Web, [said](https://www.w3.org/Press/IPO-announce):
 
@@ -16,11 +18,9 @@ Back in the early days of the Web, Tim Berners-Lee, inventor of the World Wide W
 
 The web of today is an important resource in many aspects of life such as health care, education, or commerce. Accessibility is an important consideration when building for the web.
 
-[Web accessibility](https://www.w3.org/WAI/fundamentals/accessibility-intro/#what) means that websites, tools, and technologies are designed and developed so that people with disabilities can use them. But not only people with permanent disabilities benefit from it. Accessibility also benefits people with temporary disabilities. For example, imagine being in an environment where you cannot listen to audio or you can't use a computer because of a broken arm.
-
 Accessibility supports [social inclusion for everyone](https://www.w3.org/standards/webdesign/accessibility#case), and has a strong [business case](https://www.w3.org/WAI/business-case/).
 
-## Gatsby helps build in accessibility
+## Gatsby makes accessibility easier
 
 While ultimately it's up to you to develop your site with accessibility in mind, Gatsby aims to provide as much out-of-the-box support as possible.
 
@@ -56,7 +56,7 @@ Note: Including a local `.eslintrc` file will [override](/docs/how-to/custom-con
 
 This is a start to testing for accessibility: [further recommendations](#how-to-improve-accessibility) can be found below.
 
-## How to improve accessibility?
+## Tips for improving web accessibility
 
 Accessibility by default is a win for everyone. Here's a starting point for accessibility testing when making a Gatsby site or theme:
 

diff --git a/docs/docs/glossary/decoupled-drupal.md b/docs/docs/glossary/decoupled-drupal.md
@@ -1,15 +1,11 @@
 ---
-title: Decoupled Drupal
+title: What Is Headless or Decoupled Drupal?
 disableTableOfContents: true
 ---
 
-Learn what <q>decoupled Drupal</q> means, how it differs from other ways of using Drupal, and how you can use decoupled Drupal with Gatsby.
+_Decoupled Drupal_ is the practice of using Drupal as a [headless CMS](/docs/how-to/sourcing-data/headless-cms/) for your [Jamstack](/docs/glossary/jamstack/) site. Decoupled Drupal separates the content layer from the presentation layer, so that you can use Drupal, as the content management systems, with whatever frontend you choose.
 
-## What is Decoupled Drupal?
-
-_Decoupled Drupal_ is the practice of using Drupal as a [headless CMS](/docs/how-to/sourcing-data/headless-cms/) for your [JAMstack](/docs/glossary/jamstack/) site. Decoupled Drupal separates the content layer from the presentation layer, so that you can use Drupal with whatever frontend you choose.
-
-In a tightly coupled Drupal architecture, themes control your site's appearance. A theme is a collection of HTML-based template files, each of which manages the layout for a particular Drupal node or content type.
+In a tightly coupled Drupal architecture, themes control your site's appearance using PHP and bit of Drupal DSL. A theme is a collection of HTML-based template files, each of which manages the layout for a particular Drupal node or content type.
 
 When a visitor requests a URL, Drupal retrieves the requested content from the database and merges it with the appropriate template to create an HTML response. The downside of such an architecture is that your site's content is only available as HTML. HTML limits where and how your content can be used.