TorbatYar/frontend/modules
Mortezakoohjani 625275e55b feat(healthcare): add backend service and finalize frontend build
Add the Healthcare platform backend (phases 13.0–13.7) with Alembic migration revision fix, production deploy script, validation reports, shared UI exports, and loyalty list page client directives so Next.js build succeeds.

Co-authored-by: Cursor <cursoragent@cursor.com>
2026-07-27 11:38:31 +03:30
..
beauty feat(loyalty): add Loyalty Platform Frontend module 2026-07-27 10:50:55 +03:30
communication feat(communication): add SMS MVP frontend with governance artifacts. 2026-07-27 11:11:25 +03:30
crm Ship enterprise CRM frontend with real API wiring and thin app routes. 2026-07-26 20:58:17 +03:30
hospitality feat(loyalty): add complete Loyalty Platform Frontend module 2026-07-27 10:46:45 +03:30
loyalty feat(healthcare): add backend service and finalize frontend build 2026-07-27 11:38:31 +03:30
sports-center Migrate Beauty, Healthcare, and Accounting frontend to modular src/modules architecture. 2026-07-26 22:28:27 +03:30
README.md Add complete Torbat Food hospitality frontend connected to backend APIs. 2026-07-26 20:54:26 +03:30

frontend/modules/

Status: Scaffold — business modules not migrated yet
Phase: Migration Phase 1 (shared architecture creation)

Purpose

Future home for self-contained business module packages. Each module will own its routes (via app/ re-exports or colocated route adapters), components, hooks, API client, and types — without importing sibling modules.

Current state

Module Status Location
beauty Migrated modules/beauty/ — see beauty-migration-report.md
hospitality Migrated modules/hospitality/ — Torbat Food
accounting Legacy components/accounting/, lib/accounting-api.ts
healthcare Legacy components/healthcare/, lib/healthcare-api.ts
admin Legacy components/admin/

Business modules not yet migrated remain in legacy paths until their migration phase:

Module ID Route prefix Legacy component root Legacy API client
accounting /accounting components/accounting/ lib/accounting-api.ts
beauty /beauty components/beauty/ lib/beauty-business-api.ts
healthcare /healthcare components/healthcare/ lib/healthcare-api.ts
admin /admin components/admin/ lib/api.ts

CRM and other future modules will be scaffolded here when added.

Planned structure (per module)

modules/
└── {module-id}/
    ├── README.md           # Module ownership and boundaries
    ├── components/         # Module-only UI (portals, pages, DS)
    ├── hooks/              # Module-only hooks
    ├── api/                # Module API client (split from lib/)
    ├── types/              # Module TypeScript types
    └── constants/          # Nav configs, feature flags

Import rules

  • Modules MAY import from shared/ and platform utilities (lib/auth.ts, lib/utils.ts).
  • Modules MUST NOT import from other modules/* or legacy components/{other-module}/.
  • app/{module}/ routes stay unchanged during Phase 1; they continue importing legacy paths.