How nikhil-coder390/hernest works
Project type and purpose
• HerNest is a full-stack, single-page web application for menstrual cycle tracking, AI health guidance, and online doctor consultations.
• Frontend: React + TypeScript (Vite, Tailwind CSS).
• “Backend”: Supabase (Auth, Database, Edge Functions) with migrations in the repo. The README also references a Node.js + Express layer (not shown in this tree), plus external services: OpenAI API for chatbot, payment gateway, video‐consultation links.
File structure
• Top‐level: configuration files (tsconfig, eslint, tailwind, Vite).
• src/
• App.tsx + main.tsx: entrypoints.
• components/: shared UI (DashboardLayout, Navbar, NotificationBell).
• pages/: route components (Auth, Home, BookAppointment, Chat, DoctorDashboard, PatientDashboard, HealthRecords, Prescriptions, Profile, Payment).
• lib/: client abstractions (supabase client, global store).
• types/: TypeScript types for database schema.
• supabase/migrations/: SQL files pushing schema changes.
• No visible Express server code in this tree—likely separate or in Supabase Edge Functions.
Key insights from README
• Core flows:
• User registration & login (Supabase Auth).
• Period logging (Supabase DB).
• AI chatbot queries (OpenAI).
• Appointment booking & payment (Payment API).
• Video consultation link generation (external video service).
• Security & compliance: HIPAA/GDPR.
Detail
• Break the client into sub-components if needed (e.g., Auth module, Chat module, Appointment module).
• Global store as a connector between UI components and API calls.
• Migrations folder to indicate continuous schema evolution.
• Security: annotate the Auth flows, JWT tokens, and compliance boundary (HIPAA/GDPR).