j) Repeated Code in Feature Cards

[aliveevie]

Description

In the page.tsx under /packages/nextjs/app/page.tsx file, the two feature cards (Debug Contracts and Block Explorer) share nearly identical structures but are hardcoded separately. This results in code duplication, making it harder to maintain and update the UI consistently.

Each card consists of:

• An icon (BugAntIcon or MagnifyingGlassIcon).
• A short description of the feature.
• A Link component directing the user to a relevant page.

This approach violates the DRY (Don't Repeat Yourself) principle. If we need to update the design, style, or structure of the cards in the future, we would have to modify multiple places in the code instead of a single, centralized component.

---

Goal

The goal of this refactor is to:

• Reduce Code Duplication – Remove repeated code and consolidate logic into a reusable component.
• Improve Maintainability – Make it easier to update styles, structure, or functionality for feature cards in one place.
• Enhance Readability – Create a cleaner and more modular codebase that is easier to understand and extend.
• Promote Reusability – Allow the same component to be used for additional features in the future without writing redundant code.

[aliveevie]

@phipsae I'm proposing this issue!

[phipsae]

Since the whole page will be changed in #2 it doesn't make so much sense in my perspective (sorry).
Why don't you think of a new feature?

[melanke]

@aliveevie Thanks for the suggestion! I agree with Philip, we usually remove this part of the homepage.
How about something web3-related? Maybe pulling data from our contract, interacting with another contract, or even creating a simple new contract? Is up to you.

[aliveevie]

@aliveevie Thanks for the suggestion! I agree with Philip, we usually remove this part of the homepage. How about something web3-related? Maybe pulling data from our contract, interacting with another contract, or even creating a simple new contract? Is up to you.

Okay Noted sir

Since the whole page will be changed in #2 it doesn't make so much sense in my perspective (sorry). Why don't you think of a new feature?

Noted, I'm thinking again

[phipsae]

@aliveevie the issue should be more about implementing new features, so why not contributing to #2?

[aliveevie]

@aliveevie the issue should be more about implementing new features, so why not contributing to #2?

Assigned it to me, issue

[phipsae]

Pls talk in the chat because someone is already working on that. And align, ask where you can support.

[aliveevie]

Pls talk in the chat because someone is already working on that. And align, ask where you can support.

Okay!