Remove upvote counter from landing-page cards#495
Merged
soyalejolopez merged 1 commit intoJul 22, 2026
Merged
Conversation
The card upvote count was baked into a static resource-stats.json that is only regenerated by a daily CI job (cron 0 6 * * *), so a fresh reaction would not show up for up to ~24h. Combined with the fact that only one resource currently has a backing discussion, the counter was misleading. This removes the upvote count *display* from both the comfortable and compact card views (and the compact 'Votes' header column + orphaned CSS). Voting itself is unchanged: the giscus-backed 'Community & upvotes' panel on the detail page still works, and the upvotes value is still loaded in getStats and used by the Popular/Trending/Engaging sort logic. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 888b1353-6309-4a90-bb0f-9b7b716a32dc
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What & why
The card upvote count was baked into a static
resource-stats.jsonthat is only regenerated by a daily CI job (cron: 0 6 * * *). A fresh reaction wouldn't surface on the cards for up to ~24h, and today only one resource has a backing discussion, so the counter read as stale/misleading and looked like something you could vote on directly from the card (you can't).What this changes
Votesheader column and the orphaned.compact-votes/.ch-votesCSSWhat is intentionally preserved
upvotesis still loaded ingetStatsand still drives the Popular / Trending / Engaging sort logicDisplay-only removal — no data or sort behavior changes.