How sumankhan18/kissan_helper works
Project type and purpose
• This is a full-stack web application comprised of two parallel portals:
– An Admin portal (React + Vite frontend, Node/Express backend) for managing users, payments, broadcasts, shipments, policies, etc.
– A User portal (React + Vite frontend) with an AI-agent sub-application (Next.js) for interactive agricultural guidance (crop advice, weather, disease detection, etc.).
• Key use cases: Admins log in to configure and monitor the system; end users browse features, interact with the AI agent, view dashboards, and transact (payments, notifications).
File structure
Top-level modules:
• Admin/
– backend/ (Express server.js, Twilio service, phone utils)
– server/ (Express routes for auth, database utils, email service)
– src/ (React/Vite app + components, pages, context, services: Firebase, Twilio, Razorpay, EmailJS)
• User/
– src/ (React/Vite app with features for crop yield, sensors, disease detection, etc.)
– src/ai-agent/ (Next.js application for chat & domain pages, caching, SSR build artifacts)
Common patterns:
– MVC-like separation in Admin (server/routes, server/utils)
– Feature-driven structure in User/src/features
– Service modules to abstract external integrations (Twilio, EmailJS, Razorpay, Firebase)
Deployment/config: Vite configs (vite.config.js), ESLint, CORS, package.json at each module.
Insights from README
– The README is minimal, so infer architecture from folder names and code organization.
Final recommendations
– Be exhaustive: include every service folder (e.g., twilioService.js) to show how external interactions occur
– Capture context providers (AuthContext) and their role in the UI flow
– Represent the AI agent’s build and runtime artifacts as a micro-service sub-system