How keval06/edusity works
Project Type and Purpose
• This is a client-side, single-page React application bootstrapped with Vite.
• Its sole purpose is to deliver a static website (with video assets) rendered in the browser, using modern tooling (ESLint, Vite dev server, HMR) for development and build-time bundling for production.
File Structure Analysis
• Top-level:
• index.html – entry HTML served to the browser
• vite.config.js – Vite build/dev configuration
• eslint.config.js – linting rules
• package.json / package-lock.json – dependencies & scripts
• src/
• main.jsx – React root-render call (hydrate <App /> into index.html)
• App.jsx – application shell (routes or static layout)
• index.css – global styles
• Components/ – all UI components (Navbar, Hero, About, Programs, Campus, Testimonials, VideoPlayer, Contact, Footer, Title) each with .jsx + .css
• assets/ – static media (video.mp4)
Key Insights from README
• Uses Vite with React plugin (either Babel-based or SWC-based) for fast refresh.
• Minimal setup: no TypeScript by default, but ESLint is active.
Main Components
A. Developer Environment
• VS Code (or IDE)
• ESLint + Prettier (linting pipeline)
• Vite Dev Server (serves modules over native ESM, provides HMR)
B. Build Pipeline
• Vite Bundler
• Plugins: @vitejs/plugin-react or plugin-react-swc
• Output: production‐ready JS/CSS assets (bundles + manifest)
C. Runtime Environment (Browser)
• index.html (bootstraps the app)
• React App (main.jsx → <App />)
• Component Tree (Navbar → Hero → About → Programs → VideoPlayer → Campus → Testimonials → Contact → Footer → Title)
• Static Assets (video.mp4)
D. External Services (none in this template)
Relationships & Data Flow
1. Developer edits .jsx/.css → ESLint runs on save → Vite picks up changes via file watcher → HMR pushes updates to the browser.
2. Vite Dev Server serves index.html and modules as ESM.
3. Browser fetches index.html → main.jsx loads → App and child components mount.
4. Components load CSS via JS imports, and fetch static assets (video.mp4) from assets folder.
5. On build: Vite bundles modules → outputs /dist folder → served by a static web server in production.
Architectural Patterns & Design Principles
• Modular UI: clearly separated presentational components under src/Components.
• Single‐page application: routing (if any) is client‐side and lives in App.jsx.
• Build‐time optimizations by Vite (tree‐shaking, code splitting if configured).
• Hot Module Replacement for rapid iteration.