lfglabs-dev / lfglabs-dev/starknet.quest

Refont of reward section - Refont the data cards

Open
#1,073 14 comments 0 reactions 1 assignee View on GitHub

@adrianvrj is already working on this.

Since Jun 29, 2025.

Good first issue onlydust-wave open for contribution
Dominant language
TypeScript
Stars
39
Forks
180
PR merge metrics
No merged PRs in 30d

Description

Description 📹

Current :
Image

New design :
Image

Figma File :
https://www.figma.com/design/fh0OAvj4AS08kHoSxu3DkE/%F0%9F%9A%80-Starknet-Quest?node-id=5827-17656&t=ZvvWJW4vZ48J0Mi6-1

Refont the data cards to match the design.

The purpose of this issue is to refactor the data cards to match the new design on the Starknet Quest platform.
Issue Details
• Current State: The data cards do not match the new design.
• Proposed State: Refactor the data cards to align with the specifications provided in the Figma design.
• Design: The updated design is available on Figma (link provided in the issue description).
Actions to Take
1. Fork and Branch Creation:
• Fork the repository and create a new branch using the issue number.
2. Implementation of Changes:
• Refactor the data cards to match the Figma design.
3. Testing and Validation:
• Make sure your changes don’t break existing functionality.
• Test your PR locally before pushing and verify that tests and build are working after pushing.
• Ensure all changes align with the Figma design.
4. Commit and Submission:
• Make a commit with a clear message describing the refactoring of the data cards.
• Submit a pull request closing the issue.

Proposed Actions 🛠️

Here’s a checklist of actions to follow for resolving this issue:

  1. Fork and Create Branch:
    Fork the repository and create a new branch using the issue number:

    git checkout -b fix-[issue-number]
    
  2. Implement Changes:
    [Insert Code snippet if needed with a mardown todo list]

  3. Run Tests and Commit Changes:
    Make sure your changes don't break existing functionality and commit with a clear message:

    git commit -m "Fix: [Short description of the fix]"
    

Required 📋

To keep our workflow smooth, please make sure you follow these guidelines:

  • Assignment: Don't create a pull request if you weren’t assigned to this issue.
  • Timeframe: Complete the task within 3 business days.
  • Closing the Issue: In your PR description, close the issue by writing Close #[issue_id].
  • Review Process:
    • Once you've submitted your PR, change the label to "ready for review".
    • If changes are requested, address them and then update the label back to "ready for review" once done.
  • Testing: Test your PR locally before pushing, and verify that tests and build are working after pushing.

Thank you for your contribution 🙏

⚠️ WARNING: Failure to follow the requirements above may result in being added to the OnlyDust blacklist, affecting your ability to receive future rewards.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.