How osamaakiladev/majlis-app works
Majlis is a university club and event management product. Students and staff use the Next.js web app to discover clubs and events, manage membership and event participation, and receive attendance records and certificates; administrators manage users and departments. The NestJS API handles authentication, permissions, domain operations, and persistence, with shared Zod contracts between packages. The README identifies PostgreSQL and Supabase image storage. Web-to-API wiring and several unsampled domain implementations are inferred only at a high level; their links are dashed where source evidence is unavailable.
Main entry points: api.ts Web API client · clubs.service.ts Club management · transaction.host.ts Transaction host · src Zod contracts
Components 21
Web experience
- Web application
apps/web/src/app - Web API client
apps/web/src/lib/api.ts
API domains
- Authentication
apps/api/src/auth/auth.service.ts - Club management
apps/api/src/clubs/clubs.service.ts - Membership and teams
apps/api/src/clubs/membership/membership.service.ts - Event management
apps/api/src/events/events.service.ts - Event registration
apps/api/src/events/registrations.service.ts - Attendance
apps/api/src/attendance/attendance.service.ts - Certificates
apps/api/src/certificates/certificates.service.ts - User administration
apps/api/src/users/users.service.ts - Departments
apps/api/src/departments/departments.service.ts - Reporting
apps/api/src/reporting/reporting.service.ts - Audit trail
apps/api/src/audit/audit.service.ts - Notifications
apps/api/src/notifications/notification.service.ts
Shared contracts
- Zod contracts
packages/contracts/src
Persistence and integrations
- Transaction host
apps/api/src/prisma/transaction.host.ts - PostgreSQL
- Image storage
apps/api/src/storage/storage.service.ts
Other components
- Students and staff
- Supabase Storage
- Email provider
Connections 28
- Students and staff → Web application: uses
README.md - Web application → Web API client: requests data
- Web API client → Authentication: calls API
- Web API client → Club management: calls API
- Web API client → Event management: calls API
- Web API client → Attendance: calls API
- Club management → Membership and teams: uses
- Event management → Event registration: uses
- Event registration → Attendance: enables check-in
- Attendance → Certificates: invokes
apps/api/src/attendance/attendance.service.ts - Authentication → Notifications: requests delivery
apps/api/src/auth/auth.service.ts - Club management → Image storage: requests upload
apps/api/src/clubs/clubs.service.ts - Image storage → Supabase Storage: signs uploads
apps/api/src/storage/storage.service.ts - Club management → Audit trail: records changes
apps/api/src/clubs/clubs.service.ts - Membership and teams → Audit trail: records changes
apps/api/src/clubs/membership/membership.service.ts - Certificates → Audit trail: records changes
apps/api/src/certificates/certificates.service.ts - Certificates → Notifications: notifies users
apps/api/src/certificates/certificates.service.ts - Notifications → Email provider: delivers email
apps/api/src/notifications/notification.service.ts - Attendance → Transaction host: runs transactions
apps/api/src/attendance/attendance.service.ts - Authentication → Transaction host: queries and writes
apps/api/src/auth/auth.service.ts - Audit trail → Transaction host: writes audit rows
apps/api/src/audit/audit.service.ts - Notifications → Transaction host: stores notifications
apps/api/src/notifications/notification.service.ts - Transaction host → PostgreSQL: persists data
- Web application → Zod contracts: shares schemas
README.md - Authentication → Zod contracts: uses schemas
apps/api/src/auth/auth.service.ts - Club management → Zod contracts: uses schemas
apps/api/src/clubs/clubs.service.ts - Event management → Zod contracts: uses schemas
- User administration → Zod contracts: uses schemas