Community hub page at /community

未关闭
  • 哪里不对？
#2,453 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

@riddhij-7 已经在做这个了。

开始于 2026年7月3日。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
52/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
冷清
技术栈
next.js, typescript
领域
content, frontend, web-dev

调研方向

从 src/app/(main)/resources/page.tsx 和提议的 src/app/(main)/community/page.tsx 开始，然后检查 ResourcesHero、category-card components、AmbassadorGrid、LookingForMore 以及 src/pages/_meta.tsx 中的社区菜单。在实现 involvement ladder 之前，先确定 v1 的范围和数据决策。完成的标准是：/community 能渲染已约定的 sections 和 CTAs，菜单包含“Explore Community”，并且现有的 /resources 链接不再返回 404。

由索引模型根据 Issue 内容生成。

描述

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).
主要语言
TypeScript
星标
889
派生
1.5k
平均合并
3 天 6 小时
30 天内合并 PR
32

环境准备

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

graphql/graphql.github.io 的其他 Issue

查看 graphql/graphql.github.io 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。