Community hub page at /community

Aperta
#2,453 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@riddhij-7 ci sta già lavorando.

Dal 3/7/2026.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
52/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Tranquilla
Stack tecnologico
next.js, typescript

Direzione di ricerca

Inizia da src/app/(main)/resources/page.tsx e dalla proposta src/app/(main)/community/page.tsx, quindi esamina ResourcesHero, category-card components, AmbassadorGrid, LookingForMore e il menu della community in src/pages/_meta.tsx. Risolvi l’ambito di v1 e le decisioni sui dati prima di implementare la scala di coinvolgimento. Il lavoro è completato quando /community esegue il rendering delle sezioni e dei CTAs concordati, il menu include “Explore Community” e il link esistente a /resources non restituisce più 404.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Summary

Create a /community landing page whose explicit goal is to get more people actively involved in the GraphQL community. Today "Community" is a dropdown menu with no page behind it — there's no single place that invites people to participate, and /community currently 404s (even though /resources already links to it).

Goal

Turn visitors into participants. The page is an on-ramp, organized as an involvement ladder from lowest-friction to deepest commitment, each step with a clear call to action.

Proposed structure (involvement ladder)

  1. Hero — "Get involved with GraphQL" + primary CTAs.
  2. Connect (lowest friction) — join Official / Community / Vendor channels (chat, forums, social). CTA: say hi.
  3. Show up — attend or run a meetup; GraphQLConf. Pulls a highlight from the existing /community/events data. CTA: find/host an event.
  4. Contribute — code, docs, Working Groups, governance. CTA: make your first contribution.
  5. Lead — Ambassador Program (+ spotlight grid via AmbassadorGrid); later the Team page (#2428). CTA: become an ambassador.
  6. Support — the Foundation: join, members, grants. CTA: join the Foundation.
  7. Looking for more — cross-link Learn / Resources (reciprocate the link /resources already points here).

Implementation notes

  • App Router page src/app/(main)/community/page.tsx, mirroring /resources (src/app/(main)/resources/page.tsx).
  • Reuse ResourcesHero, category-card components, AmbassadorGrid, LookingForMore.
  • Menu wiring: add route: "/community" + an index item to the community menu in src/pages/_meta.tsx → dropdown automatically gains an "Explore Community" link (same code path /resources uses).

Why now

/resources already links to /community, which 404s — the page is already expected to exist.

Open questions

  1. Which sections are v1 vs. later.
  2. Curated cards vs. live data (events feed, ambassadors grid).
  3. Relationship to Team page #2428 (where ambassadors/TSC render) and to /resources (avoid Tools & Libraries / training overlap).
  4. Success metric for "more involved" — is there anything measurable we care about (channel joins, event signups, contributions)?

Out of scope

  • Reworking the individual subpages (channels, foundation, etc.) — this page links to them.

Related

  • #2428 — Team page on graphql.org (the Lead/People section renders here once it exists).
Lingua principale
TypeScript
Stelle
889
Fork
1.5k
Merge medio
3g 6h
PR unite (30g)
32

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di graphql/graphql.github.io

Tutte le issue di graphql/graphql.github.io

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.