Skip to content

Refresh hardcoded GitHub stats on the AI page - #121

Merged
guanzhousongmicrosoft merged 1 commit into
documentdb:mainfrom
GuanzhouSong:homepage-messaging
Jul 30, 2026
Merged

Refresh hardcoded GitHub stats on the AI page#121
guanzhousongmicrosoft merged 1 commit into
documentdb:mainfrom
GuanzhouSong:homepage-messaging

Conversation

@GuanzhouSong

@GuanzhouSong GuanzhouSong commented Jul 30, 2026

Copy link
Copy Markdown
Contributor

What

The /ai community section showed 3.2k+ stars / 200+ forks; live values are 3,424 / 249 (GitHub API, 2026-07-30). Bumps to 3.4k+ / 240+.

Originally this PR also carried a homepage messaging rework (hero badges, press refresh, ecosystem section, FAQ) — dropped per review direction; only the stats refresh remains. The homepage still shows 3.2k+/200+ in its own community section; happy to bump that too or wire both to a build-time fetch so the numbers stop rotting.

🤖 Generated with Claude Code

https://claude.ai/code/session_01XGMeNSmhAgmqzkdc7cQQgf

The /ai community section showed 3.2k+ stars and 200+ forks; the live
values are 3,424 and 249 (GitHub API, 2026-07-30). Bump to 3.4k+ and
240+.
@GuanzhouSong GuanzhouSong changed the title Sharpen homepage positioning: governance, compatibility, ecosystem, FAQ Refresh hardcoded GitHub stats on the AI page Jul 30, 2026
@guanzhousongmicrosoft
guanzhousongmicrosoft merged commit 9e46914 into documentdb:main Jul 30, 2026
2 checks passed
guanzhousongmicrosoft pushed a commit that referenced this pull request Aug 3, 2026
The star and fork counts were hardcoded independently in app/page.tsx
and app/ai/page.tsx with no shared constant, so they drifted: the
homepage said 3.2k+ stars and 200+ forks while /ai said 3.4k+ and 240+.
Both sections render adjacent copy about the project being built in the
open, so a visitor moving between the two pages saw two different star
counts.

Neither figure was false - the + suffix covers the actual 3423 stars and
248 forks - but nothing stopped the next refresh from updating one page
and leaving the other behind, which is exactly what happened when the AI
page was refreshed in #121.

Both pages now read from app/services/projectStats.ts, which also holds
the TSC member and organization counts quoted on both pages (verified
against upstream MAINTAINERS.md: 11 members across Microsoft 4, Amazon 4,
AB InBev 1, Rippling 1, YugabyteDB 1). Values stay hardcoded rather than
fetched so the build keeps no network dependency; the refresh command and
the date last checked are recorded next to them.

Addresses the second half of #128. The create_indexes_background row in
the first half is content in documentdb/docs and needs a separate PR
there.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants