How to join a working group (#2158)

We had many people ask how to get involved in the working groups at
GraphQL Conference. Many times, I was told that they had tried to join
before but there were no easy steps to follow when it came to signing
the required CLA.

We even had questions asked about it during workshops, but because we
had all filled it out a long time ago it was easy to forget that it can
be a convoluted process.

---------

Co-authored-by: Benjie <benjie@jemjie.com>

Author: jemgillam

src/pages/_meta.tsx

@@ -24,7 +24,7 @@ export default {
       events: { title: "Events & Meetups" },
       contribute: {
         title: "Contribute to GraphQL",
-        href: "/community/contribute/essential-links",
+        href: "/community/contribute/governance",
       },
       foundation: { title: "Foundation" },
     },

src/pages/community/contribute/_meta.ts

@@ -1,9 +1,9 @@
 export default {
-  "essential-links": "",
-  grant: "Community Grant Program",
-  development: "Participating in Development",
   governance: "GraphQL Project Governance",
   "how-graphql-is-developed": "",
-  "project-resources": "",
   "project-meetings": "",
+  development: "Participating in Development",
+  grant: "Community Grant Program",
+  "essential-links": "",
+  "project-resources": "",
 }

src/pages/community/contribute/development.mdx

@@ -1,17 +1,76 @@
+import { Cards } from "../../../components/cards"
+
 # Participating in Development
 
 GraphQL is developed in the open, through [GitHub](https://github.com/graphql) and working group meetings that are open for anyone to attend (so long as they are covered under the [free membership agreement](https://github.com/graphql/graphql-wg/tree/HEAD/membership)). In addition, anybody is welcome to view the [recordings of our meetings on YouTube](https://youtube.graphql.org)
 
-## First steps
-
-If you want to get involved in GraphQL, add yourself to the meeting agenda for one of our [working groups or implementations](https://github.com/graphql/graphql-wg/blob/main/GraphQL-TSC.md#about-the-graphql-specification-project), sign the document if you haven't already, and show up! Or, if you prefer, just open a PR against our projects as this will also initiate the spec membership signature process.
-
-We welcome your participation!
-
 ## Getting up to speed
 
-All of our work [happens in the open](https://github.com/graphql). In addition, we record our workgroups' meetings on [YouTube](https://youtube.graphql.org). If you are interested in quickly getting up to speed on what's happening in a working group, the meeting minutes and [replays](https://youtube.graphql.org) are a great place to begin.
+All of our work [happens in the open](https://github.com/graphql). In addition, we record our workgroups' meetings on [YouTube](https://youtube.graphql.org). If you are interested in quickly getting up to speed on what's happening in a working group, the meeting minutes (`notes` folder in the relevant repository) and [replays](https://youtube.graphql.org) are a great place to begin.
 
 ## Asking questions
 
 The best place to ask a development-related question is in a working group meeting, or by opening a GitHub issue. Please note that if you have an implementation question, you may get a faster answer by [asking in one of the channels more geared toward users](/community/resources/official-channels/).
+
+
+## GraphQL projects and implementations
+
+<Cards
+  items={[
+
+    {
+      title: "GraphQL Specification",
+      link: "https://github.com/graphql/graphql-spec",
+      description: "This is a Working Draft of the Specification for GraphQL, a query language for APIs created by Facebook. The target audience for this specification is not the client developer, but those who have, or are actively interested in, building their own GraphQL implementations and tools. To join in with its development, join the main GraphQL Working Group",
+    },
+    {
+      title: "GraphQL.js",
+      link: "https://github.com/graphql/graphql-js",
+      description: "The JavaScript reference implementation for GraphQL.",
+    },
+    {
+      title: "GraphiQL IDE",
+      link: "https://github.com/graphql/graphiql",
+      description: "Whether you want a simple GraphiQL IDE instance for your server, or a more advanced web or desktop GraphQL IDE experience for your framework or plugin, or you want to build an IDE extension or plugin, you've come to the right place!",
+    },
+    {
+      title: "GraphQL Website",
+      link: "https://github.com/graphql/graphql.github.io",
+      description: "The source repository for this very website: GraphQL Documentation, community initiatives and more",
+    },
+    {
+      title: "GraphQL over HTTP Specification",
+      link: "https://github.com/graphql/graphql-over-http",
+      description: "HTTP is the most common choice as the client-server protocol when using GraphQL because of its ubiquity. However the GraphQL specification deliberately does not specify the transport layer. This specification is intended to fill this gap by specifying how GraphQL should be served over HTTP. ",
+    },
+    {
+      title: "graphql-http",
+      link: "https://github.com/graphql/graphql-http",
+      description: "Simple, pluggable, zero-dependency, GraphQL over HTTP spec compliant server, client and audit suite.",
+    },
+        {
+      title: "GraphQL Composite Schema Spec",
+      link: "https://github.com/graphql/composite-schemas-spec",
+      description: "Describes how to construct a single unified GraphQL schema, the composite schema, from multiple GraphQL schemas, each termed a source schema.",
+    },
+    {
+      title: "GraphQL Scalars Specification",
+      link: "https://github.com/graphql/graphql-scalars",
+      description: "Providing a directory of GraphQL Custom Scalar specifications, contributed by the community. GraphQL Custom Scalar specifications are language agnostic and thus can be used to document and standardize behavior across different languages.",
+    },
+    {
+      title: "Dataloader",
+      link: "https://github.com/graphql/dataloader",
+      description: "A generic utility to be used as part of your application's data fetching layer to provide a simplified and consistent API over various remote data sources such as databases or web services via batching and caching.",
+    },
+    {
+      title: "SWAPI GraphQL Wrapper",
+      link: "https://github.com/graphql/swapi-graphql",
+      description: "A wrapper around the Star Wars API, or \"swapi\" (Swah-pee) the world's first quantified and programmatically-accessible data source for all the data from the Star Wars canon universe, converting it into a GraphQL schema.",
+    },
+  ]}
+  />
+
+If you want to get involved in GraphQL, add yourself to the meeting agenda for one of our [working groups or implementations](./project-meetings/#quick-guide-how-to-join), sign the document if you haven't already, and show up! Or, if you prefer, just open a PR against our projects as this will also initiate the spec membership signature process.
+
+We welcome your participation!

src/pages/community/contribute/how-graphql-is-developed.mdx

@@ -9,7 +9,7 @@ import {
 
 At its core, the GraphQL project is organized around the [specification](https://spec.graphql.org), with a wide variety of supporting implementations and tools.
 
-GraphQL has an active and mutually beneficial relationship with its many implementations. The GraphQL specification is continuously evolving under the care of the [GraphQL Working Group](https://github.com/graphql/graphql-wg), which consists of GraphQL spec experts, contributors to public [reference implementations](/code), and implementers. At any given time, GraphQL specification updates are a combination of anticipatory planning with documentation of patterns and behaviors that are already proven in production, sometimes at very large scale.
+GraphQL has an active and mutually beneficial relationship with its many implementations. The GraphQL specification is continuously evolving under the care of the [GraphQL Working Group](https://github.com/graphql/graphql-wg), which consists of GraphQL spec experts, contributors to public [reference implementations](/community/contribute/development/#graphql-projects-and-implementations), and implementers. At any given time, GraphQL specification updates are a combination of anticipatory planning with documentation of patterns and behaviors that are already proven in production, sometimes at very large scale.
 
 ## Working Groups
 
@@ -18,7 +18,7 @@ The GraphQL specification, sub-specifications, and official reference implementa
 <div className="border-l-2 border-primary pl-6 md:pl-10">
   ### The GraphQL Working Group
 
-  The [GraphQL Working Group](https://github.com/graphql/graphql-wg) is the main group that plans and implements changes to the [GraphQL specification](https://spec.graphql.org). It meets actively and is the default place for discussion for topics which do not have a separate breakout working group (breakout working groups include the [Input Union WG](https://github.com/graphql/graphql-spec/blob/main/rfcs/InputUnion.md) and the [GraphQL-over-HTTP WG](https://github.com/graphql/graphql-over-http)).
+  The [GraphQL Working Group](https://github.com/graphql/graphql-wg) is the main group that plans and implements changes to the [GraphQL specification](https://spec.graphql.org). It meets actively and is the default place for discussion for topics which do not have a separate breakout working group (breakout working groups include the [Composite Schemas WG](https://github.com/graphql/composite-schemas-wg/) and the [GraphQL-over-HTTP WG](https://github.com/graphql/graphql-over-http), see [GraphQL subcommittee meetings](/community/contribute/project-meetings/#graphql-subcommittee-meetings) for more).
 
   <Cards
     items={[