Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Discover Starknet DeFi Ecosystem - Add New Section #1090

Open
Kevils opened this issue Feb 3, 2025 · 6 comments
Open

Discover Starknet DeFi Ecosystem - Add New Section #1090

Kevils opened this issue Feb 3, 2025 · 6 comments

Comments

@Kevils
Copy link
Collaborator

Kevils commented Feb 3, 2025

Description 📹

Current :
https://starknet.quest/discover/defi

New design :
Image

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

Here is the new section we want to add to our DeFi page. This section is made up of filters that allow displaying different DApps by category. The user will have the option to click on a card, and a new window will open to access the selected DApp. You don’t need to create the cards for the different categories since they will be on the other issues. However, you need to develop the section with the title, clickable filters, and the structure of a card as shown in the design.

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.

@BigBen-7
Copy link

BigBen-7 commented Feb 6, 2025

i have read all guidlines and will adhere to them, mind if I try this out?

@chiscookeke11
Copy link
Contributor

I'd be happy to do this.

@Viktohblake
Copy link

I’d like to help with this.

@PedroCo3lho
Copy link
Contributor

Can I work on this?
I'm a full-stack dev with experience working with Typescript, Next.js an TailwindCSS.
I going to raise a PR to review quickly, so the other contributors can start their work

@Verifieddanny
Copy link

Can I attempt this issue?

@Elite-tch
Copy link
Contributor

May I be assigned to this?

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

No branches or pull requests

7 participants