Mission Marketplace Page (Full Data UI State Handling)

[lishmanTech]

Goal
Build the Mission listing page with full UI states.
📁 Files
/pages/missions
/components/missions

Tasks
• Mission cards
• Filters (status, category, reward)
• Sorting (newest, reward high→low)
• Search input
• Pagination
• Loading skeleton
• Empty state
• Error state

Must Handle
• Loading
• No results
• API error
• Wallet not connected

---

[drips-wave]

This issue has been added to the Stellar Wave Program and is worth 100 Points.

🧑‍💻 Interested in contributing? Apply to work on this issue on Drips Wave, earn points, and receive rewards.

Warning

Only applications submitted via the apply link above will be considered. Please do not apply by commenting on the issue or opening a PR directly.

🤠 Repo maintainers: You can manage this issue's Points and Complexity on your Maintainer Dashboard here. Please keep an eye on applications and respond quickly 💙

ℹ️ Learn more about Drips Wave

[Austinaminu2]

@Austinaminu2 has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

Hello maintainers,

My name is Austin, and I’m a dedicated open-source contributor with hands-on experience building and maintaining production level applications across Web3 and full-stack ecosystems.
I’ve worked extensively with Stellar based infrastructure, Soroban smart contracts, backend services, and modern React development, with a strong focus on UI structure, state management, and user experience.

This issue aligns closely with my skill set, and I’d like to contribute the Mission Marketplace Page with full data UI state handling.

Objective
Build a fully functional Mission listing page that handles all UI states including loading, empty, error, and disconnected wallet scenarios.

Implementation Plan

• Mission Cards: Display mission details with reward, category, and status.
• Filters & Sorting: Implement filtering by status, category, and reward, and sorting by newest or reward high→low.
• Search & Pagination: Add live search input and paginated results.
• UI States: Handle loading skeletons, empty results, API errors, and wallet not connected state.
• Ensure responsive design and seamless state transitions.
• Add unit and integration tests to cover all scenarios.

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

[drips-wave]

Congratulations, @Austinaminu2! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on February 26, 2026.

🧑‍💻 @Austinaminu2: 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 issued 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 🌊

[Austinaminu2]

Hi maintainer, i still havent gotten my points

[Austinaminu2]

good day maintainer

[Agbasimere]

@Agbasimere has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

Can I work on this?

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

[chiemezie1]

@chiemezie1 has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

I’d like to work on #37 – Mission Marketplace Page (Full Data UI State Handling).

I’ll build the /pages/missions view along with reusable components under /components/missions, implementing:

Mission cards
Filters (status, category, reward)
Sorting (newest, reward high → low)
Search input
Pagination
I’ll ensure the page properly handles all required UI states:
Loading (with skeleton UI)
No results (empty state)
API error (clear retry-friendly error state)
Wallet not connected (actionable prompt)

The implementation will be clean, modular, and consistent with the project’s design patterns to ensure maintainability and scalability.

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