How elevateedorg/elevateed-frontend-web works
Project type and purpose
• This is a Single-Page Application (SPA) front-end for an e-learning platform, built with React, TypeScript, and Vite.
• It provides authentication flows, course browsing/enrollment, chat support, instructor listings, user profile & dashboard pages.
File structure
• Top-level files & folders:
• package.json, vite.config.ts, ESLint configs → build & tooling
• public & index.html → static assets & host page
• src/ → all source:
– src/pages/ → route-level React components
– src/components/ → reusable UI blocks grouped by feature (Auth, Course, ChatWidget, Navbar, etc.)
– src/api/ → HTTP service modules (authService.ts, courseService.ts)
– src/redux/ → global state management (store.ts, slices)
– src/lib/ → shared utilities (axios wrapper, helpers)
– src/hooks/ → custom hooks (e.g., useMobile)
– src/assets/ → images & media imports
– src/types/ → TypeScript type declarations
• Architectural patterns:
• Component-driven (feature folders)
• Unidirectional data flow (React → Redux → API → Redux → React)
• Separation of concerns: UI vs. state vs. network vs. utilities
README for additional insights
• It’s the default Vite + React + TypeScript template.
• No built-in backend—API endpoints will be external services.
• ESLint config is pluggable for TypeScript-aware linting but not central to runtime design.