[#1019] Redesign milestone section into 3 narrative blocks#1024
[#1019] Redesign milestone section into 3 narrative blocks#1024realproject7 merged 2 commits intomainfrom
Conversation
Replace flat milestone rows with three narrative sections: 1. "Your airdrop grows with $PLOT" — value table with Now + 4 steps 2. "Four steps — not unrealistic" — 4 MCap cards with CMC rank + unlock % 3. "Not reached? Burned forever." — burn callout + holder benefit Responsive: cards 2×2 on mobile, 4-col on desktop. CMC rank text and "thousands have done it" copy hidden in test mode. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
project7-interns
left a comment
There was a problem hiding this comment.
Verdict: APPROVE
Summary
The PR matches issue #1019 and rewrites the old flat milestone rows into the requested three-block narrative layout: value-growth table, milestone cards, and burn callout. It also preserves the earlier constraints for MCap terminology and hiding CMC rank messaging in test mode.
Findings
- No code findings.
- CI note:
e2eandlint-and-typecheckwere still pending at review time.
Decision
Approved because the implementation is narrowly scoped, aligns with the acceptance criteria, and the user-facing narrative now matches the intended product message.
realproject7
left a comment
There was a problem hiding this comment.
re2 — APPROVE
All 7 acceptance criteria met. The 3-section layout follows the wireframe closely:
- Section 1: "Now" row + 4 milestone steps with pool values ✓
- Section 2: 4 cards (2×2 mobile / 4-col desktop) with MCap + CMC rank + unlock % ✓
- Section 3: burn callout with trust message + "either way" conclusion ✓
- MCap terminology throughout ✓
- CMC ranks + "thousands have done it" hidden in test mode ✓
- Responsive grid ✓
Nit (non-blocking): In the Section 1 milestone rows, milestoneRows.indexOf(row) is used instead of the map index parameter. indexOf does a linear scan and is fragile if two rows ever share the same fdv reference. Consider milestoneRows.map((row, i) => ...) and use i + 1 for the step number. Not a blocker since milestone FDVs are always unique.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Fixes #1019
Summary
Test plan
🤖 Generated with Claude Code