docs: clean up legacy references

Author: serhalp

docs/contributing/blog-contributions.md

@@ -86,7 +86,7 @@ If you create a loader or plugin, we would love for you to open source it and pu
 
 Gatsby's policy is that "Using" example sites (like those in the [examples part of the repo](https://github.com/gatsbyjs/gatsby/tree/master/examples)) should only be around plugins that are maintained by the core team as it's hard to keep things up to date otherwise.
 
-To contribute example sites, it is recommended to create your own GitHub repo and link to it from your source plugin, etc. You can also create a starter project and submit it to the [starter showcase](/starters/submissions).
+To contribute example sites, it is recommended to create your own GitHub repo and link to it from your source plugin, etc.
 
 ## Debugging the build process
 

docs/contributing/code-contributions.md

@@ -124,7 +124,3 @@ 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.
-
-## Claim your swag
-
-After your first code contribution to the Gatsby repo (including documentation) you become eligible for a free shirt or pair of socks. See the [swag page](/contributing/contributor-swag/) for more details!

docs/contributing/contributor-swag.md

@@ -35,7 +35,7 @@ We accept all types of contributions to [`packages`](https://github.com/gatsbyjs
 - [`gatsby`](https://github.com/gatsbyjs/gatsby/tree/master/packages/gatsby)
 - [`gatsby-core-utils/remote-file-utils`](https://github.com/gatsbyjs/gatsby/tree/master/packages/gatsby-core-utils/src/remote-file-utils)
 
-For these two packages, we ask you to open a [feature request](#feature-requests) (or for larger changes an [RFC](/contributing/rfc-process/)) before opening PRs for features. Contributions, such as bug fixes and documentation updates, can be made without any prior interaction with the team and don't require a feature request/RFC.
+For these two packages, we ask you to open a [feature request](#feature-requests) before opening PRs for features. Contributions, such as bug fixes and documentation updates, can be made without any prior interaction with the team.
 
 ## Contributor levels
 
@@ -54,7 +54,7 @@ Have you done something (big or small) to contribute to the health, success, or
 #### Recognized contributions
 
 - **GitHub:** Submitting a merged pull request
-- **GitHub:** Sending in a detailed feature request or RFC
+- **GitHub:** Sending in a detailed feature request
 - **GitHub:** Updating documentation
 - Helping people on GitHub and other platforms.
 - Answering questions on Stack Overflow, Twitter, etc.
@@ -63,7 +63,7 @@ Have you done something (big or small) to contribute to the health, success, or
 
 #### Privileges
 
-At this time we have no specific privileges for this role except that you can claim yourself [free Gatsby swag](/contributing/contributor-swag/). If you have ideas here please let us know!
+At this time we have no specific privileges for this role. If you have ideas here please let us know!
 
 #### Responsibilities
 
@@ -87,8 +87,8 @@ The Maintainer role is critical to the long-term health of Gatsby. Maintainers s
 
 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
+- **GitHub:** Submitting non-trivial pull requests
+- **GitHub:** Reviewing non-trivial pull requests
 - Supporting users and participating in community events
 - **GitHub:** Triaging and confirming user issues
 - This list is incomplete! Similar contributions are also recognized.
@@ -174,11 +174,7 @@ If you’d like to learn more about how we approach the relationship between our
 
 ### Feature requests
 
-Please open a [feature request on GitHub Discussions](https://github.com/gatsbyjs/gatsby/discussions/categories/ideas-feature-requests) to voice your ideas. For larger changes please consider opening an [RFC](/contributing/rfc-process/). The **Team** will review incoming requests and give a first assessment.
-
-### RFCs
-
-Please see the dedicated [RFC Process document](/contributing/rfc-process/) for more details.
+Please open a [feature request on GitHub Discussions](https://github.com/gatsbyjs/gatsby/discussions/categories/ideas-feature-requests) to voice your ideas. The **Team** will review incoming requests and give a first assessment.
 
 ## Voting
 

docs/contributing/docs-contributions/index.md

@@ -17,7 +17,6 @@ In the interest of fostering an open and welcoming environment, we as contributo
 
 ### Gatsby news
 
-- 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/)
 
@@ -38,7 +37,7 @@ Read the [Gatsby Style Guide](/contributing/gatsby-style-guide/) to learn more a
 
 ## How to contribute
 
-We want contributing to Gatsby to be fun, enjoyable, and educational for anyone and everyone. If you're interested in participating in the Gatsby community, contributions go far beyond pull requests and commits. We are thrilled to receive a variety of other contributions and as our way of saying “thank you” to our contributors, **all contributors are eligible for [free Gatsby swag](/contributing/contributor-swag/)** — whether you’re contributing code, docs, a talk, an article, or something else that helps the Gatsby community. [Learn how to claim free swag for contributors](/contributing/contributor-swag/).
+We want contributing to Gatsby to be fun, enjoyable, and educational for anyone and everyone. If you're interested in participating in the Gatsby community, contributions go far beyond pull requests and commits.
 
 ### Help fellow users
 
@@ -56,11 +55,10 @@ Contributing bug fixes or new features are the most direct form of contribution
 
 There are a few other ways of contributing to the Gatsby ecosystem:
 
-- **Contribute to Gatsby's blog**. Want to write about Gatsby? Read the [blog contributions doc](/contributing/blog-contributions) to get your blog post onto gatsbyjs.com.
 - **Develop learning materials.** Strengthen your expertise by writing a blog post, developing a workshop, creating video tutorials, or present your knowledge as a presentation on meetups and conferences.
-- **Create a plugin.** Learn how to [create a plugin](/docs/how-to/plugins-and-themes/) and [submit it to the Plugin Library](/docs/how-to/plugins-and-themes/submit-to-plugin-library/).
+- **Create a plugin.** Learn how to [create a plugin](/docs/how-to/plugins-and-themes/).
 - **Contribute to the Gatsby User Collective.** Interested in working on plugins that benefit the whole community? You can find them in the [Gatsby User Collective repository](https://github.com/gatsby-uc/plugins).
-- **Create a Gatsby starter.** Created a starter? Share it with the community and [submit it to the Starter Library](/starters/submissions).
+- **Create a Gatsby starter.** Created a starter? Share it with the community.
 
 ### Help triage issues
 
@@ -74,8 +72,6 @@ There are many reasons to contribute to Gatsby and open source software in gener
 
 - **Improving your skills.** When you work on a Gatsby issue or pull request, inevitably you'll learn more about how something works in the project; either by asking questions and gathering info or by digging deeper into the code yourself. There's a skill-building benefit to contributing to OSS!
 
-- **Getting free swag!** By participating in the repo on GitHub, you can become eligible for free swag that the Gatsby team offers as a way to say thank you. With 5 contributions, you can advance to a second level with even more swag options! Learn more about this [sweet swag deal](/contributing/contributor-swag/).
-
 - **Becoming an expert.** You might start off totally new to a project like Gatsby or React.js, and by building things and [opening issues](/contributing/how-to-file-an-issue/) when you encounter a new challenge or a bug, you'll learn a ton over time. Staying current with your favorite framework through its open source repo can also give you a leading edge on forthcoming changes. Eventually, you could find your knowledge of said project has grown so much that you've become an expert. Celebrate by updating your résumé!
 
 - **Speaking at conferences.** With those skills you've earned yourself working in open source, why not share that knowledge with the world? Web platform conferences the world over are continually looking for speakers and fresh takes on popular topics. Did you build something with Gatsby that you're excited about? The [industry would love to hear from you](http://weareallaweso.me/)!