Refactor large components into smaller, single-responsibility pieces

[Akatenvictor]

What

Identify and break down components over 200 lines into smaller, focused components that each handle a single responsibility.

Why

Large components are harder to test, understand, and maintain. Smaller components are reusable and have clearer APIs.

Scope

In: Identify oversized components, extract sub-components, create focused composition patterns
Out: Full component library restructuring

Acceptance Criteria

• No component exceeds 200 lines (excluding tests)
• Each sub-component has a single responsibility
• Sub-components are independently testable
• No prop drilling increased by refactoring
• All existing functionality preserved
• No visual regressions

Technical Context

• Run line count analysis on all components
• Focus on Player, NftCollections, dashboard components
• Extract header, body, footer sections

[SMOGZ6783]

@SMOGZ6783 has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

i want to handle this issue please thank you

ℹ️ Repo Maintainers: To accept this application, review their application or assign @SMOGZ6783 to this issue.

[drips-wave]

Congratulations, @Rickyy1017! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on July 30, 2026.

🧑‍💻 @Rickyy1017: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[drips-wave]

Congratulations, @karanjadavi! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on July 30, 2026.

🧑‍💻 @karanjadavi: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[drips-wave]

This issue has been completed by @karanjadavi as part of the Stellar Wave Program's 7th Wave 🥳

😎 @karanjadavi: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.