chore: remove Gatsby Discord references (#39351)

* chore: remove AskGatsbyJS Twitter link

* Apply suggestion from @serhalp

* chore: remove more outdated social refs

Author: serhalp

.github/ISSUE_TEMPLATE/config.yml

@@ -3,12 +3,6 @@ contact_links:
   - name: Gatsby Documentation
     url: https://www.gatsbyjs.com/docs/
     about: Check out the Gatsby documentation for answers to common questions
-  - name: Gatsby Discord
-    url: https://gatsby.dev/discord
-    about: Ask questions, get help and discuss new things you're building with the Gatsby community
   - name: Gatsby Discussions
     url: https://github.com/gatsbyjs/gatsby/discussions
     about: Ask questions, request features & discuss RFCs
-  - name: AskGatsbyJS Twitter
-    url: https://twitter.com/AskGatsbyJS
-    about: The official Twitter account to ask questions and get help with Gatsby

README.md

@@ -34,9 +34,6 @@
   <a href="https://gatsbyjs.com/contributing/how-to-contribute/">
     <img src="https://img.shields.io/badge/PRs-welcome-brightgreen.svg" alt="PRs welcome!" />
   </a>
-  <a href="https://twitter.com/intent/follow?screen_name=gatsbyjs">
-    <img src="https://img.shields.io/twitter/follow/gatsbyjs.svg?label=Follow%20@gatsbyjs" alt="Follow @GatsbyJS" />
-  </a>
 </p>
 
 <h2 align="center">
@@ -52,9 +49,7 @@
   <span> · </span>
   <a href="https://www.gatsbyjs.com/contributing/how-to-contribute/">Contribute</a>
   <br />
-  Support: <a href="https://twitter.com/AskGatsbyJS">Twitter</a>, <a href="https://github.com/gatsbyjs/gatsby/discussions">Discussions</a>
-  <span> & </span>
-  <a href="https://gatsby.dev/discord">Discord</a>
+  Support: <a href="https://github.com/gatsbyjs/gatsby/discussions">Discussions</a>
 </h2>
 
 Gatsby helps professional developers efficiently create maintainable, highly-performant, content-rich websites.
@@ -160,6 +155,6 @@ Licensed under the [MIT License](./LICENSE).
 
 ## 💜 Thanks
 
-Thanks go out to all our many contributors creating plugins, starters, videos, and blog posts. And a special appreciation for our community members helping with issues and PRs, or answering questions on Discord and GitHub Discussions.
+Thanks go out to all our many contributors creating plugins, starters, videos, and blog posts. And a special appreciation for our community members helping with issues and PRs, or answering questions on GitHub Discussions.
 
 A big part of what makes Gatsby great is each and every one of you in the community. Your contributions enrich the Gatsby experience and make it better every day.

docs/contributing/code-contributions.md

@@ -66,7 +66,7 @@ If you're adding e2e tests and want to run them against local changes:
 
 ### Troubleshooting
 
-At any point during the contributing process the Gatsby team would love to help! For help with a specific problem you can [open an Discussion on GitHub](https://github.com/gatsbyjs/gatsby/discussions/categories/help). Or drop in to [our Discord server](https://gatsby.dev/discord) for general community discussion and support.
+At any point during the contributing process the Gatsby team would love to help! For help with a specific problem you can [open an Discussion on GitHub](https://github.com/gatsbyjs/gatsby/discussions/categories/help).
 
 - When you went through the initial setup some time ago and now want to contribute something new, you should make sure to [sync your fork](https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/syncing-a-fork) with the latest changes from the primary branch on [gatsbyjs/gatsby](https://github.com/gatsbyjs/gatsby). Otherwise, you might run into issues where files are not found as they were renamed, moved, or deleted.
 - After syncing your fork, run `yarn run bootstrap` to compile all packages. When files or tests depend on the build output (files in `/dist` directories) they might fail otherwise.
@@ -94,4 +94,4 @@ Check [Debugging the build process](/docs/debugging-the-build-process/) page to
 
 ## Feedback
 
-At any point during the contributing process the Gatsby team would love to help! For help with a specific problem you can [open an Discussion on GitHub](https://github.com/gatsbyjs/gatsby/discussions/categories/help). Or drop in to [our Discord server](https://gatsby.dev/discord) for general community discussion and support.
+At any point during the contributing process the Gatsby team would love to help! For help with a specific problem you can [open an Discussion on GitHub](https://github.com/gatsbyjs/gatsby/discussions/categories/help).

docs/contributing/gatsby-governance-model.md

@@ -43,9 +43,9 @@ We recognize different degrees of contribution as levels, and most levels can be
 
 - **Being here** - Everyone's time is valuable, and the fact that you're here and contributing to Gatsby is amazing! Thank you for being a part of this journey with us.
 
-- **Being a positive member of our community** - Go above and beyond our Code of Conduct, and commit to healthy communication in pull requests, issue discussions, Discord conversations, and interactions outside of our community.
+- **Being a positive member of our community** - Go above and beyond our Code of Conduct, and commit to healthy communication in pull requests, issue discussions, and interactions outside of our community.
 
-Each level unlocks new privileges and responsibilities on Discord and GitHub. Below is a summary of each contributor level.
+Each level unlocks new privileges and responsibilities on GitHub. Below is a summary of each contributor level.
 
 ### Level 1 (L1) - Contributor
 
@@ -56,7 +56,7 @@ Have you done something (big or small) to contribute to the health, success, or
 - **GitHub:** Submitting a merged pull request
 - **GitHub:** Sending in a detailed feature request or RFC
 - **GitHub:** Updating documentation
-- Helping people on GitHub, Discord, etc.
+- Helping people on GitHub and other platforms.
 - Answering questions on Stack Overflow, Twitter, etc.
 - Blogging, Vlogging, Podcasting, and Livestreaming about Gatsby
 - This list is incomplete! Similar contributions are also recognized.
@@ -79,46 +79,39 @@ n/a
 
 The **Maintainer** role is available to any contributor who wants to join the team and take part in the long-term maintenance of Gatsby.
 
-The Maintainer role is critical to the long-term health of Gatsby. Maintainers support the **Team** members and together they act as the first line of defense when it comes to new issues, pull requests and Discord activity. Maintainers are most likely the first people that a user will interact with on Discord or GitHub.
+The Maintainer role is critical to the long-term health of Gatsby. Maintainers support the **Team** members and together they act as the first line of defense when it comes to new issues and pull requests. Maintainers are most likely the first people that a user will interact with on GitHub.
 
-**A Maintainer is not required to write code!** Some Maintainers spend most of their time inside of Discord, maintaining a healthy community there. Maintainers can also be thought of as **Moderators** on Discord and carry special privileges for moderation.
+**A Maintainer is not required to write code!** Some Maintainers focus on community support and can also be thought of as **Moderators** who carry special privileges for moderation.
 
 #### Recognized contributions
 
 There is no strict minimum number of contributions needed to reach this level, as long as you can show **sustained** involvement over some amount of time (at least a couple of weeks).
 
 - **GitHub:** Submitting non-trivial pull requests and RFCs
 - **GitHub:** Reviewing non-trivial pull requests and RFCs
-- **Discord:** Supporting users in Discord, especially in the "Help" category
-- **Discord:** Active participation in RFC calls and other events
-- **GitHub + Discord:** Triaging and confirming user issues
+- Supporting users and participating in community events
+- **GitHub:** Triaging and confirming user issues
 - This list is incomplete! Similar contributions are also recognized.
 
 #### Privileges
 
 - All privileges of the [Contributor role](#level-1-l1---contributor), plus...
-- Invitation to the `@Maintainer` role on [Discord](https://gatsby.dev/discord)
 - Invitation to the `Maintainers` team on GitHub.
-- New name color on Discord: **Blue**.
-- Invitation to the private `#maintainers` channel on Discord.
-- Ability to moderate Discord to remove spam, harmful speech, etc.
-- Ability to join the `@Moderator` role on Discord (optional, opt-in).
 - Ability to review GitHub PRs.
 - Ability to vote on _some_ initiatives (see [Voting](#voting) below).
 
 #### Responsibilities
 
 - Participate in the project as a team player.
 - Bring a friendly, welcoming voice to the Gatsby community.
-- Be active on Discord, especially in the "Help" category.
 - Triage new issues.
 - Review pull requests.
 - Merge some, non-trivial community pull requests.
 - Merge your own pull requests (once reviewed and approved).
 
 #### Nomination
 
-To be nominated, a nominee is expected to already be performing some of the responsibilities of a Maintainer over the course of at least a couple of weeks. You can apply through contacting one of the `@Team` members on Discord who then in turn will trigger a [Voting](#voting) process.
+To be nominated, a nominee is expected to already be performing some of the responsibilities of a Maintainer over the course of at least a couple of weeks. You can apply through contacting one of the `@Team` members who then in turn will trigger a [Voting](#voting) process.
 
 In some rare cases, this role may be revoked by an **Admin**. However, under normal circumstances this role is granted for as long as the contributor wishes to engage with the project.
 
@@ -131,8 +124,6 @@ Team is a special designation for employees of [Gatsby, Inc.](https://www.gatsby
 #### Privileges
 
 - All privileges of the [Maintainer role](#level-2-l2---maintainer), plus...
-- `@Team` role on [Discord](https://gatsby.dev/discord)
-- New name color on Discord: **Purple**.
 - `Team` on GitHub.
 - Ability to merge all GitHub PRs.
 - Ability to vote on all initiatives (see [Voting](#voting) below).
@@ -165,9 +156,7 @@ Admin is an additional privilege inside the **Team** and is mainly an administra
 #### Privileges
 
 - All privileges of the [Team](#team), plus...
-- `@Admin` role on [Discord](https://gatsby.dev/discord)
 - Administration privileges on GitHub.
-- Administration privileges on Discord (optional).
 
 #### Responsibilities
 
@@ -210,7 +199,7 @@ This process kicks off once a valid nomination has been made.
 
 **Who can vote:** All Maintainers (L2 and above).
 
-1. A vote thread should be created in Discord #maintainers channel (the private channel for all maintainers).
+1. A vote thread should be created in the private #maintainers channel.
 2. A vote thread can be created by any maintainer, team member, or Admin.
 3. Once a vote thread is created, existing Maintainers can discuss the nomination in private.
 4. The normal 3 day voting & discussion window begins with the thread creation.
@@ -229,9 +218,8 @@ Outlined below is the process for Code of Conduct violation reviews.
 Anyone may report a violation. Violations can be reported in the following ways:
 
 - In private, via email to [[email protected]](mailto:[email protected]).
-- In private, via direct message to a team member on Discord.
+- In private, via direct message to a team member.
 - In public, via a GitHub comment (mentioning `@gatsbyjs/team`).
-- In public, via the project Discord server.
 
 ### Who gets involved?
 
@@ -261,7 +249,7 @@ Responses will be determined by the reviewers on the basis of the information ga
 - taking no further action
 - issuing a reprimand (private or public)
 - asking for an apology (private or public)
-- permanent ban from the GitHub org and Discord server
+- permanent ban from the GitHub org
 - revoked contributor status
 
 ---

docs/contributing/gatsby-style-guide.md

@@ -39,7 +39,7 @@ Possible sources of great research materials:
 - blogposts (on gatsbyjs.com and other sites)
 - docs (on gatsbyjs.com and other sites)
 - video tutorials
-- Discord or Twitter conversations
+- Twitter conversations
 - search engine results
 - presentations you or others have given
 - textbooks
@@ -53,8 +53,7 @@ because it requires you to take a technical (usually abstract) topic and explain
 it in a clear, accurate, and objective manner. You'll likely go through several
 rounds of proofreading and editing before you're happy with your writing.
 
-Also, there's a community of contributors to support you. Bounce ideas off of them and ask for input on your writing in the
-[Gatsby Discord](https://gatsby.dev/discord) and in the [GitHub repo](https://github.com/gatsbyjs/gatsby).
+Also, there's a community of contributors to support you. Bounce ideas off of them and ask for input on your writing in the [GitHub repo](https://github.com/gatsbyjs/gatsby).
 
 ## Word choice
 

docs/contributing/index.md

@@ -17,14 +17,12 @@ In the interest of fostering an open and welcoming environment, we as contributo
 
 ### Gatsby news
 
-- Follow [Gatsby](https://twitter.com/gatsbyjs) and [Gatsby Changelog](https://twitter.com/GatsbyChangelog) on Twitter
 - Read and discuss about [Request for Comment (RFC) proposals](/contributing/rfc-process)
 - Watch videos on [Gatsby's YouTube channel](https://www.youtube.com/c/Gatsbyjs/videos) to see past GatsbyConf presentations and tutorial walkthroughs
 - Follow the [official blog](/blog/)
 
 ### Get support
 
-- [Discord Chat](https://gatsby.dev/discord): Real time chat with community & team members. Let's chat!
 - [GitHub Discussions](https://github.com/gatsbyjs/gatsby/discussions/categories/help): Best place to ask and discuss longer questions about Gatsby and its ecosystem.
   - [Feature Requests](https://github.com/gatsbyjs/gatsby/discussions/categories/ideas-feature-requests): Here's also where you can post your feature requests.
 - [GitHub Issues](https://github.com/gatsbyjs/gatsby/issues/new/choose): Have you found a bug or a problem in our documentation? Open an issue!
@@ -44,7 +42,7 @@ We want contributing to Gatsby to be fun, enjoyable, and educational for anyone
 
 ### Help fellow users
 
-Answering questions for fellow Gatsby users on [Discord](https://gatsby.dev/discord) or [GitHub Discussions](https://github.com/gatsbyjs/gatsby/discussions/categories/help) are valuable contributions. You can also help out users on issues and Pull Requests to contribute or fix their issues.
+Answering questions for fellow Gatsby users on [GitHub Discussions](https://github.com/gatsbyjs/gatsby/discussions/categories/help) is a valuable contribution. You can also help out users on issues and Pull Requests to contribute or fix their issues.
 
 ### Contribute documentation
 

docs/docs/cheat-sheet.md

@@ -181,9 +181,6 @@ Get the PDF: <a href="/gatsby-cheat-sheet.pdf" download>gatsby-cheat-sheet.pdf</
   <p>
     <a href="https://www.gatsbyjs.com/">gatsbyjs.com</a>
   </p>
-  <p>
-    <a href="https://twitter.com/gatsbyjs">twitter.com/gatsbyjs</a>
-  </p>
   <h2>Gatsby CLI Commands</h2>
   <p>
     First, install the global executable:

docs/docs/reference/release-notes/v4.14/index.md

@@ -93,7 +93,7 @@ Drupal now has Image CDN support. Enable it in your site by following the offici
 
 We updated our [default Starter template `gatsby-starter-default`](https://www.gatsbyjs.com/starters/gatsbyjs/gatsby-starter-default/) to contain references to documentation, tutorial, our monorepo examples folder, and more – and aligned its look-and-feel to that of our `gatsby new`/`npm init gatsby` experience. It shows you how to use TypeScript, Server Side Rendering, and Deferred Static Generation in your Gatsby application.
 
-![Preview of the new landing page. At the top it says "Welcome to Gatsby", below that it links to the separate subpages like "TypeScript" or "Server Side Rendering". Then four blocks linking out to sections like the tutorial or examples are shown. The footer contains links to Discord, Documentation, and more.](https://user-images.githubusercontent.com/16143594/167383192-e33e7b23-fa70-4a3f-8238-97f6273cecdc.png)
+![Preview of the new landing page. At the top it says "Welcome to Gatsby", below that it links to the separate subpages like "TypeScript" or "Server Side Rendering". Then four blocks linking out to sections like the tutorial or examples are shown. The footer contains links to Documentation and more.](https://user-images.githubusercontent.com/16143594/167383192-e33e7b23-fa70-4a3f-8238-97f6273cecdc.png)
 
 ## Notable bugfixes & improvements
 

docs/docs/reference/release-notes/v4.21/index.md

@@ -55,7 +55,7 @@ If you're already using `gatsby-plugin-mdx` v3 and want to migrate, you can foll
 
 We did our best to strike a balance between introducing meaningful breaking changes and keeping old behaviors. For example, while a lot of people use GraphQL nodes like `timeToRead` or `wordCount`, over the years it has become increasingly hard to fulfill every feature request and behavior that users wanted (e.g. correctly providing `timeToRead`/`wordCount` for every language is hard). One the one hand removing default fields like these means that you have to reimplement them on your own, but on the other hand this also means that you can more granularly customize them to your needs. Read [Extending the GraphQL MDX nodes](/plugins/gatsby-plugin-mdx#extending-the-graphql-mdx-nodes) for guidance on how to migrate.
 
-If you have any questions along the way, post them either into the [umbrella discussion](https://github.com/gatsbyjs/gatsby/discussions/25068) or into the [`mdx-v2` channel on Discord](https://gatsby.dev/discord).
+If you have any questions along the way, post them into the [umbrella discussion](https://github.com/gatsbyjs/gatsby/discussions/25068).
 
 The [using-mdx example](https://github.com/gatsbyjs/gatsby/tree/master/examples/using-mdx) also showcases some of the necessary migration steps.
 

docs/docs/reference/release-notes/v4.24/index.md

@@ -27,7 +27,7 @@ You probably noticed that in the last couple of releases we mostly focused on bu
 
 For the Alpha the big new feature you'll be able to test out is [Partial Hydration](https://github.com/gatsbyjs/gatsby/discussions/36608). With Partial Hydration you gain the ability to mark specific parts of your site/application as “interactive”, while the rest of your site is static by default. This will result in shipping less JavaScript to your users and improved Lighthouse scores. For a quick preview of these great features, you can [watch the showcase on YouTube](https://www.youtube.com/watch?v=C-WrnfUm33k)
 
-Please take part in the [Gatsby 5 Umbrella Discussion](https://github.com/gatsbyjs/gatsby/discussions/36609), **try it out**, and let us know what works and doesn't work. If Discord is more your jam, you can also join the [`gatsby-5` Discord channel](https://discord.gg/MhfpnT4cNg).
+Please take part in the [Gatsby 5 Umbrella Discussion](https://github.com/gatsbyjs/gatsby/discussions/36609), **try it out**, and let us know what works and doesn't work.
 
 ## Updating File System Routes on data changes