Skip to content

Add achievement explainability and mentor boost section#269

Open
gregv wants to merge 1 commit intodevelopfrom
feature/leaderboard-explainability-and-mentor-boost
Open

Add achievement explainability and mentor boost section#269
gregv wants to merge 1 commit intodevelopfrom
feature/leaderboard-explainability-and-mentor-boost

Conversation

@gregv
Copy link
Copy Markdown
Contributor

@gregv gregv commented Mar 30, 2026

Summary

  • Explainability: Shows achievement description as a small caption under each value, so users understand what metrics mean (e.g., "Commits between 10pm–4am MST" under Night Owl's count)
  • Mentor boost section: New "Teams Ready for a Boost" section with rocket icon, warning-colored cards, and encouraging framing for teams that could use mentor support
  • Adds RocketLaunchIcon import and rocket_launch to icon map
  • Consumes new mentorOpportunities from leaderboard API

Companion PRs:

  • Stats collector: opportunity-hack/github-stats-collector (unique files tracking + boost generation)
  • Backend: opportunity-hack/backend-ohack.dev (mentor opportunities API support)

Test plan

  • Verify achievement cards show description caption below the bold value
  • Verify "Teams Ready for a Boost" section appears when mentorOpportunities data exists
  • Verify section is hidden when no mentor opportunities
  • Check mobile layout doesn't break with new caption text

🤖 Generated with Claude Code

- Show achievement description as caption under each value for context
- Add RocketLaunch icon and "Teams Ready for a Boost" section for mentor visibility
- Add mentorOpportunities state and API consumption
- Boost cards use warning-colored left border and encouraging framing

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@vercel
Copy link
Copy Markdown
Contributor

vercel bot commented Mar 30, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
frontend-ohack-dev Ready Ready Preview Mar 30, 2026 9:28pm

Request Review

Copy link
Copy Markdown

@rohithkn rohithkn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added nit comments

>
{achievement.value}
</Typography>
{achievement.description && (
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why not use a lodash isEmpty or a ternary op instead of && ?

const hasTeamPage = opportunity.teamPage;

return (
<Grid size={{ xs: 12, md: 6 }} key={index}>
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why not make sure key is just not index as index might have been already used some where as a key?

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