Website: GitHub stars / forks / PRs counter in navbar
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 3/5
- 预计耗时
- 1-2 天
- 新手友好度
- 62/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- nextjs, react, tailwindcss, typescript
- 领域
- frontend
调研方向
Start with src/components/landing/navbar.tsx to see the current desktop and mobile GitHub buttons, then create GitHubCounter in src/components/landing/. Read the caching guide in node_modules/next/dist/docs/ before writing the server-side fetch with hourly revalidation, and add a unit test for the count formatter with the listed values. Done when the stars pill replaces the round icon on desktop and mobile, no client-side GitHub requests appear, and bun run lint, typecheck, test and build pass.
由索引模型根据 Issue 内容生成。
描述
Website: GitHub stars / forks / PRs counter in the navbar
The landing navbar currently shows a bare round GitHub icon (src/components/landing/navbar.tsx, desktop + mobile) and a plain "Star on GitHub" link in the mobile menu. Replace them with a live counter badge that shows the project's traction and nudges visitors to star it.
Design
A segmented pill with two parts and a divider between them:
┌──────┬──────────────┐
│ ⬤ │ 500+ ☆ │ ← stars
└──────┴──────────────┘
GitHub count + metric icon
logo
- Left: GitHub mark
- Divider: a 1px vertical line in the border colour
- Right: a rounded count followed by the icon for that metric
- Stars → star outline icon (
Starfrom lucide-react) - Forks → fork icon (
GitFork) - Pull requests → PR icon (
GitPullRequest)
- Stars → star outline icon (
- Rounded rectangle,
border-white/[0.1], dark background, white text — matching the existing navbar buttons - Hover: subtle
bg-white/5, same as the current GitHub button - Whole pill links to the repo (or
/stargazers,/forks,/pullsfor each metric)
Behaviour
- Count formatting: round down to a friendly bucket followed by
+(e.g.10+,150+,500+,1k+,1.2k+). UseIntl.NumberFormatwithnotation: "compact"for 1000 and above. - Data source: GitHub REST API
GET /repos/babelize/babelize-elements(stargazers_count,forks_count) and the search API for open PRs (is:pr is:open repo:babelize/babelize-elements). - Fetch on the server, cached. Unauthenticated GitHub API calls are capped at 60/hour per IP, so never fetch from the client. Fetch in a server component or route with time-based revalidation (e.g. every hour). Read the caching guide in
node_modules/next/dist/docs/first — this Next.js version differs from older ones. - Public, unauthenticated API only. No token, no GitHub App, no secrets — contributors and the deployment won't be given repo access or credentials. All the data needed (stars, forks, open PRs) is public, so the unauthenticated endpoints are enough; server-side caching keeps us well under the 60 req/hour limit.
- Fallback: if the request fails, render the pill with no count (logo + icon only). Never show
0or an error. - Accessibility:
aria-label="Star babelize-elements on GitHub (500+ stars)"; mark the iconsaria-hidden.
Placement
- Desktop navbar: the stars pill replaces the round GitHub icon
- Mobile navbar: compact stars pill (it may hide the count below
sm) - Mobile menu: replace the "Star on GitHub" text link with the pill
- Optional: show stars, forks and PRs together in the landing "Community" / "Contribute" section
Acceptance
- Reusable
GitHubCountercomponent insrc/components/landing/with ametric: "stars" | "forks" | "prs"prop - Unit test for the count formatter (
0,9,10,150,999,1000,1234,12500) - No extra client-side network requests (confirm in the Network tab)
- Works in light and dark mode on the docs site if reused there
bun run lint,typecheck,testandbuildpass
- 主要语言
- TypeScript
- 星标
- 39
- 派生
- 16
- 平均合并
- 2 天 12 小时
- 30 天内合并 PR
- 10
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
babelize/babelize-elements 的其他 Issue
-
bug website
难度 2/5 1-3 小时 新手友好度 78/100
babelize/babelize-elements#46 ·
维护者通常 1 天内回复
-
bug language-switcher priority: medium
难度 2/5 1-3 小时 新手友好度 72/100
babelize/babelize-elements#26 ·
维护者通常 1 天内回复
-
component enhancement help wanted
难度 5/5 一周以上 新手友好度 35/100
babelize/babelize-elements#47 ·
维护者通常 1 天内回复
-
bug component rtl-layout
难度 3/5 1-2 天 新手友好度 68/100
babelize/babelize-elements#45 ·
维护者通常 1 天内回复
-
Website: revamp and improve the landing page可能已有人在做 @anjalinayak01 于 4 天前认领。 未关闭enhancement help wanted priority: medium website
难度 4/5 一周以上 新手友好度 30/100
babelize/babelize-elements#37 · 已指派 1 人 ·
维护者通常 1 天内回复
查看 babelize/babelize-elements 的全部 Issue
相似的 Issue
-
afk-ok area:data-quality importer size:S
难度 2/5 1-3 小时 新手友好度 74/100
enorm-labs/event-junkie#3301 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 62/100
one-zero-eight/apply-bot#39 ·
-
难度 2/5 1-3 小时 新手友好度 72/100
bigbluebutton/bbb-ui-components-react#108 ·
维护者通常 2 天内回复
-
area: app type: bug
难度 2/5 1-3 小时 新手友好度 70/100
ExpidetGames/code-reviewer#308 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复