Uh oh!
There was an error while loading. Please reload this page.
fix(ui): clear landing neon-blue + gradebook category stripe (closes #106, #112) - #310
Conversation
…, #112) #106 — replace the #3B82F6 neon-blue on landing/hero surfaces with the warmer --info (#3e6f8a), per the issue's fix note: - globals.css: the intro-orbit blue node -> var(--info) (base + .landing-page rule) - (public)/page.tsx: hero-canvas graph palette + CLUSTER_COLORS + OB_STEP_COLORS blue entries -> #3e6f8a (concrete hex; JS canvas / inline sinks where var() doesn't resolve) The hero stat tiles / glass cards were already removed by #102, so #106's AC1 was already met on main; this clears AC2. #112 — the assignment-category list used `2px solid ${color}` as its ONLY category-color indicator, which fails the "no >1px colored side-stripe" bar. Move the category color to a leading dot in the header (the issue's recommended treatment) and make the list border a 1px neutral --border divider — no info lost. #112's other three items (off-white panels, --ease easing, Inter->DM Sans) were already done on main. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Warning Review limit reached
Next review available in:9 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (3)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Deploying with |
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs | frontend-staging | 236c3d8 | Commit Preview URL Branch Preview URL | Jul 08 2026, 06:41 AM |
The hero-canvas orb palettes hardcode #3e6f8a because canvas fillStyle can't resolve CSS var(); the CSS orbit node uses var(--info). Comment records that provenance so the two stay intentionally in sync. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Uh oh!
There was an error while loading. Please reload this page.
What & why
Clears the last residuals on two frontend-audit issues that were mostly already resolved on
main(by #102's glass removal, the token migration, and prior polish). Verified each acceptance box, then fixed only what genuinely remained.Closes#106
Closes#112
#106 — landing hero glass cards + neon-blue accents
main--bg-panel)#3B82F6neon-blue on hero surfacesglobals.css:.landing-intro-orbit-node--blue→background: var(--info)(both the base rule and the.landing-page-scoped duplicate).(public)/page.tsx: the hero-canvaspalette,CLUSTER_COLORS, andOB_STEP_COLORSblue entries →#3e6f8a(the concrete--infovalue — these are JS canvas / inline sinks wherevar()doesn't resolve). This is exactly the shift the issue's Fix note requested ("toward the warmer--info #3e6f8a").#112 — polish (side-stripes / white panels / easing / Inter)
mainborder-left/right > 1pxcolored accent stripes--bg-panel/--bg-input=#fdfcf9warm paper)--easeused instead of overshoot easingvar(--ease)--font-inter→ DM Sanslayout.tsx;--font-inter→--font-sans)Gradebook/AssignmentList.tsx: the category<ul>usedborderLeft: 2px solid ${color}as its only category-color indicator. Moved the color to a leading dot in the category header (the treatment the issue recommends, matching the existingAchievementUnlockToastdot) and made the list border a 1px neutral--borderdivider. No information lost.Not in scope (flagged, deliberate)
OnboardingFlow.tsx:12still has#3B82F6for the "Academics" onboarding step — a categorical step color in the onboarding modal, a separate surface from [P1] Replace landing hero-metric glass cards + neon-blue accents #106's hero. Left as-is; trivial follow-up if the team wants it to match the landing's shifted blue.HowItWorks.tsxframer-motion[0.34, 1.56, 0.64, 1]overshoot curves are a deliberate landing spring-reveal motion (12 of them), not the CSS hover overshoot [P2] Polish: side-stripe borders, white panels, overshoot easing, Inter font #112 targeted (which is fixed). Left intentionally.Test plan
npm ci+ build/lint) is the gate; changes are color-value swaps + one standard JSX dot span (mirrorsAchievementUnlockToast).--infoand#3e6f8aare the same color, so the orbit node + canvas stay in sync.🤖 Generated with Claude Code