fahamidanimra173/learniqe-learning-website

1. This repo is a React single-page frontend for LearnIQ.

The architecture is client-side UI focused, with routing, auth, dashboards, payment screens, and content discovery. There is no backend implementation in this tree, so the app is designed to consume external APIs/services rather than host server logic itself.

2. The app shell is split into route layouts.

src/Router/Router.jsx coordinates navigation, while src/LayOuts/Root.jsx, src/LayOuts/AuthLayout/*, and src/LayOuts/DashBoard.jsx separate the public site, auth pages, and dashboard area. This is the main structural boundary in the UI.

3. Authentication and user state are centralized in context.

src/Context/AuthProvider.jsx and src/Context/AuthContext.jsx provide global auth state, likely wrapping Firebase auth and/or JWT-backed session info. Protected routes are enforced through src/Routes/PrivateRoute.jsx, which gates student/teacher/admin-only sections.

4. Data access is isolated through an Axios wrapper.

src/Axios/AxiosSecure.jsx is the main boundary for authenticated API calls. This suggests the app talks to a separate backend for users, courses, enrollments, teacher requests, and dashboards, while attaching auth credentials where needed.

5. The public experience is organized around discovery and marketing pages.

src/Pages/Home/Home.jsx composes many sections such as banners, platform discovery, categories, testimonials, enrolled-course highlights, newsletter, and “become an instructor” prompts. Other public pages include About, Contact, Explore, Privacy Policy, Terms, All Teachers, Free Courses, and All Approved Classes.

6. LearnIQ’s LMS flow is represented by course discovery, enrollment, and payment pages.

src/Pages/AllApprovedClasses/* appears to be the catalog of approved courses, with CourceDetails.jsx as the detail view. src/Pages/Payment/* handles paid enrollment, and Stripe is the external payment boundary implied by the README. This is the transition from marketing/discovery into transactional LMS usage.

7. Role-based dashboards are the core application subsystem.

The src/DashBoard/* tree is split by role: student, teacher, and admin. Each area has its own feature pages and analytics widgets, such as class requests, teacher requests, enrolled classes, class management, and user analytics. This is the main business-logic surface of the frontend.

8. Student dashboard focuses on enrolled learning activity.

src/DashBoard/StudentDashBoard/* contains enrolled class views and class detail pages, indicating the student flow is centered on tracking enrolled courses and accessing related information, likely including assignments or progress tied to backend data.

9. Teacher dashboard supports course authoring and class management.

src/DashBoard/TeacherDashBoard/AddClass/* and src/DashBoard/TeacherDashBoard/MyClass/* indicate teachers can submit new classes, manage their own courses, and inspect class details. src/DashBoard/TeacherRequests/TeacherRequests.jsx suggests a workflow where users request teacher status or approvals.

10. Admin/dashboard analytics are visualized with chart components.

src/DashBoard/AllUsers/* includes charts for role distribution, category enrollment, student assignments, and teacher class counts. This shows the admin view is not just CRUD; it also aggregates platform usage into visual insights.

11. Shared UI and presentation components are heavily reused across pages.

src/Shared/*, src/components/ui/*, src/components/etheral-shadow.jsx, and src/Pages/Home/Component/* provide reusable visual building blocks. The presence of Flowbite/shadcn-style component configs, Tailwind CSS, and utility helpers indicates a component-driven UI layer rather than page-specific styling.

12. Static assets and curated datasets are part of the content layer.

public/data/globe.json, dataset_10min_ostad_alison_khan.json, and the PDF/font assets under public/ support homepage visuals and platform/course discovery content. These assets help the frontend render rich marketing sections and educational platform references without requiring live content for every view.

13. Firebase is part of the deployment and likely auth/runtime integration.

Firebase.init.js, .firebaserc, and firebase.json indicate Firebase is used operationally, most likely for authentication and/or hosting. The public/404 Page not found.json and hosting cache files reinforce that this app is deployed as a hosted SPA.

14. The app is built as a modern React frontend stack.

vite.config.js, main.jsx, App.jsx, Tailwind-related config, Axios, and React component organization point to a Vite-based React build. The architecture is therefore: browser UI → routed layouts/pages → context/auth layer → secure API calls/payment/auth providers → role-specific dashboards and course workflows.