Refactor: Reorganize Frontend Monorepo into Domain-Driven Modules

[Smartdevs17]

Context

The frontend codebase has grown organically. Components, hooks, and utilities are spread across folders without clear domain boundaries.

Current Limitation/Problem

Feature code is scattered across generic directories (components/, hooks/, utils/). Related code for a feature (e.g., payments) is not colocated, making navigation and maintenance difficult.

Expected Outcome

A domain-driven directory structure where each business domain (payments, merchants, wallets, analytics, settings) is a self-contained module with its own components, hooks, API calls, and types.

Acceptance Criteria

• Define domain modules: payments, merchants, wallets, analytics, settings, developers
• Each domain has: components/, hooks/, api/, types/, pages/ subdirectories
• Shared/common code in @/shared/ or @/ui/
• Barrel exports per domain module
• Imports use domain aliases (e.g., @payments/hooks/usePaymentList)
• All existing imports updated to new structure
• No circular dependencies between domains
• Lint rule enforcing domain boundary rules
• Migration guide in CONTRIBUTING.md

Technical Scope

• frontend/src/domains/{payments,merchants,wallets,analytics,settings,developers}/
• frontend/src/shared/ - shared utilities and UI primitives
• frontend/src/ui/ - design system components
• ESLint plugin for boundary enforcement
• Codemod script for automated import migration
• Edge cases: cross-domain shared state, global providers

[Heazzy500]

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

my applications

Hello @maintainer, I’ve reviewed the issue description and I’m confident I can work on it effectively. Please assign it to me.

Hi! I’d love to contribute to this issue. It looks interesting and I’d be happy to take it on if it’s still available.

Hello, I’ve gone through the requirements and I’m confident I can implement a proper solution that matches the acceptance criteria. Kindly assign this issue to me.

Hi Maintainer, I’d like to work on this issue. I have experience handling similar tasks and can start immediately.

Hello, I’m interested in working on this issue and would appreciate being assigned to it. Thank you.

Hi there, I carefully reviewed the issue details and I’m confident I can deliver a clean and efficient solution.

Hello Maintainer, I’d love to take ownership of this issue and submit a high-quality pull request once completed.

Hi, I’m a full-stack Web2 & Web3 developer with open-source contribution experience, and I’d be glad to work on this issue.

Hello, this issue aligns well with my skill set and I’m confident I can resolve it properly. Please assign it to me.

Hi Maintainer! I’m interested in contributing to this task and can ensure timely delivery with clean implementation.

Hello, I’ve thoroughly read the issue description and understand the expected outcome. I’d love to work on it.

Want me to clean these up into one stronger template you can reuse?

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

[CeceOs92]

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

may I jump on this?

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

[drips-wave]

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

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