How lidorbenhamo26/webteam works
Project type and purpose
• It consists of a React-based client (in HM2/client) and an Express.js-based backend (in HM2/backend), with Mongoose-style models under “models” and REST endpoints under “routes/controllers.”
• It provides functionality for students and teachers: authentication, exercises, theory, progress tracking, reports, and even an external “gemini” AI integration.
File structure
• Top-level:
• /backend – Express server, controllers, models, routes, seed scripts, .env, vercel.json
• /client – React app with public/index.html, component tree (shared, student, teacher), context, services calling backend APIs, Tailwind config, vercel.json
• package.json at root (likely scripts to run simultaneously or monorepo tools)
• Architectural patterns:
• Backend follows MVC (models/controllers/routes)
• Frontend follows component-based UI plus service layer for API calls plus React Context for theme, private routing
• External service integration: geminiController & geminiService
• Deployment: Both tiers have vercel.json → likely deployed on Vercel (two separate projects or monorepo deploy).
README for additional insights
• The README only lists team members. No architectural overview—so we must infer architecture solely from the file structure.