How harshitpg/mfc-recruitment-portal-fe works
Main Application Architecture Components
a) Frontend Layer
• Divide into sub-components:
• 3D Experience Module (based on /component3d directory)
• Core UI Components (/components directory)
• Application Sections (/sections directory)
• Layout Wrappers (/wrappers directory)
State Management & Context
• A store module (based on store.ts)
• Context providers (based on /context directory)
• Data flow patterns
Key Architectural Patterns to Highlight
a) Component Layer Structure:
┌─ Application Shell
• Wrappers (BaseWrapper, MainWrapper, NavWrapper)
• Core Components
• Navigation
• UI Components
• 3D Components
• Application Sections
• Context & State Management
b) 3D Integration Layer:
• Connection between the 3D experience components and the model assets
• Relationship between Experience.tsx, Fox.tsx, and the model files
Feature Modules
Sections into logical feature modules:
• Authentication (Signup, ForgotPassword, VerifyOTP)
• Task Management (various Task and TaskSubmission components)
• Application Status (TechApplicationStatus, ManagementApplicationStatus, etc.)
• Profile Management (Profile, ChangeProfile)
Technical Stack Indicators
• React + TypeScript (based on tsconfig)
• Vite (based on vite.config.ts)
• Tailwind CSS (based on configuration files)
• 3D rendering library (likely Three.js based on the 3D components)
Important Details
• Routing structure
• State management flow
• Entry points (main.tsx)
• Build/deployment configuration
┌─ UI Layer
• Components
• Sections
• Wrappers
• Business Logic Layer
• Context
• State Management
• 3D Rendering Layer
• Experience
• Models
• Animations
• Configuration Layer
• Build Tools
• Deployment
Remember to:
• Use consistent styling and spacing
• Notes for any complex interactions
• Build/deployment pipeline
• External dependencies and services