Skip to content

Team page on graphq.org #2428

Description

@jeanlucaslima

Summary

Create a Team page at /community/team that shows the people behind GraphQL, grouped by role. Today no page on the site does this — the only people grid is the Ambassadors page; everything else (Foundation members, Governance) is either organizations or prose.

Problem / context

  • No people anywhere. /community/foundation/members is an org/sponsor logo wall (external Landscape iframe) — zero individuals.
  • Governance is prose-only. /community/contribute/governance describes the TSC, Governing Board, and Working Groups but lists no individuals — it links out to GitHub markdown files.
  • Ambassadors is the lone exception/community/ambassadors already renders a real people grid.
  • There is no /community landing page (Community is a dropdown menu only).

Goal

A single page that puts names/faces to the GraphQL community, built to grow by adding role groups over time.

People groups (incremental):

  • TSC members (Technical Steering Committee)
  • Volunteers
  • Ambassadors (reuse/link the existing program data)
  • Candidates to confirm: Governing Board, Working Group chairs, spec editors, maintainers

Proposed location

  • Route: /community/team (sibling to Ambassadors).
  • Add a "Team" entry to the Community dropdown (src/pages/_meta.tsx) and the section sidebar (src/pages/community/_meta.ts).

Reuse (no new UI needed)

  • AmbassadorGrid (src/components/ambassador-grid.tsx) + InfoCard/InfoCardRow (src/components/info-card/index.tsx) — generic person-card grid.
  • Person data shape from ambassador-data.tsx: { name, imageUrl, organization, social tags }. A generalized PersonGrid could serve all groups.
  • Page lives in the Nextra tree (src/pages/community/...), consistent with the rest of Community.

Open questions (to decide before implementation)

  1. Data source — hardcoded TS files (like ambassador-data.tsx) vs. synced from graphql-wg (TSC/board)? Likely per-group. Undecided.
  2. v1 scope — which group(s) ship first vs. later.
  3. Ambassadors — link out to the existing page, or also render them inline on Team?
  4. Confirm whether Board / WG chairs / spec editors belong here.

Out of scope

  • The Foundation member org logo wall (already exists at /community/foundation/members).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions