How mazharuldev/interspace works
Main System Components
a) Client Layer:
• Next.js Frontend (src/app directory structure)
• Routes into three main sections:
• Public Routes (root)
• Authentication Routes
• Dashboard Routes (with role-based access)
b) Application Layer:
• Components (src/components)
• Redux Store (src/redux)
• API Services (src/redux/api)
• Form Schemas (src/schemas)
• Helpers & Utils (src/helpers, src/utils)
c) External Services:
• SSLCommerz Payment Gateway
• Authentication System (JWT)
Architectural Patterns to Highlight
• Feature-based modular architecture (shown in the dashboard structure)
• Redux state management pattern
• Role-based access control (RBAC) with three distinct roles:
• Super Admin
• Admin
• User
Component Relationships
Client Browser → Next.js Frontend → Redux Store → API Services → External Services
Specific Elements
Frontend Layer:
Public Routes:
• Home
• Packages
• Booking
• Reviews
Auth Routes:
• Login
• Sign Up
• Profile Management
Dashboard Routes (Role-based):
• Super Admin Section
• Admin Section
• User Section
State Management:
Redux Store
• API Slices
• Admin API
• Auth API
• Booking API
• FAQ API
• Payment API
• Review API
• Service API
• User API
• Root Reducer
Important Flows to Highlight
a) Authentication Flow:
Login/Signup → JWT Generation → Role-based Routing
b) Booking Flow:
Service Selection → Booking Creation → Payment Processing (SSLCommerz) → Confirmation
c) Admin Management Flow:
Super Admin → Admin Management → User Management → Service Management