feat(site): redesign /community — lead with proven savings, not $0.00#133
Merged
Conversation
The page led with a giant "saved $0.00" headline because the live community aggregate is genuinely zero (the feature is new; stats sync is Pro-gated). That read as "ashlr saves nothing" — the opposite of true. Reframe so it's accurate AND compelling: - Hero now leads with what ashlr actually does — a measured −79.5% on large reads (real benchmark figure) — instead of the empty community $ total. - New CommunityProof component: animated, REAL benchmark data (before/after 100k→20.5k tokens per read + per-file breakdown from @/lib/tools, reproducible via `bun run bench`). This is "what the ledger is counting." - Graceful empty states everywhere: a "Ledger live · awaiting the first synced session" panel instead of three "0" tiles; an elegant "first synced session draws the first point" placeholder instead of a blank chart. - When real community data exists, the hero switches to the "Together, we've saved $X" headline + KPI tiles. Site-only; no plugin version bump. Verified: typecheck + next build green; rendered locally (hero, proof, empty states) via the production server. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Problem (from the live page): the Community Ledger led with a giant "saved $0.00" headline — because the live aggregate is genuinely zero (the feature is brand-new and stats-sync is Pro-gated). That reads as "ashlr saves nothing," the opposite of true.
Fix — accurate and compelling:
CommunityProofcomponent — animated, real benchmark data: before/after (100k → 20.5k tokens per read) + per-file breakdown from@/lib/tools(reproducible viabun run bench). This concretely shows what the ledger is counting.0tiles; an elegant "first synced session draws the first point" chart placeholder.Verified locally (production server, screenshots in the thread): hero, animated proof, and all empty states render cleanly.
Site-only — no plugin version bump.
bun run check+next buildgreen.🤖 Generated with Claude Code