How 5umitra/claim-management works
Project type and purpose
• This is a full-stack MERN-style insurance “Claim Management System” currently shipping a React/TypeScript single-page frontend (using Vite + Tailwind + Material-UI) with a backend in active development (Node/Express + MongoDB + JWT + AWS serverless).
• The README clarifies core features (user onboarding, policy purchase, claims submission) and planned extensions (microservices, analytics, CI/CD, event streaming).
File structure
• Top-level files: Vite config (vite.config.ts), Tailwind config, TS config, index.html, package.json.
• /src holds the React app:
• main.tsx & index.css bootstrap the app
• /components contains shared UI (Header, Sidebar, Layout)
• /pages implements each route (Login, Register, Dashboard, Claims, ClaimDetails, NewClaim, Analytics, AdminPanel, Profiles, Policies)
• /contexts implements React Contexts (AuthContext, DataContext) for global state
• No server folder yet; backend, Docker, GitHub Actions, and serverless (AWS Lambda/Step Functions/SNS) are “coming soon.”
Key README insights
• Frontend currently uses LocalStorage for persistence
• Backend stack: Node.js, Express, MongoDB, JWT
• Cloud & DevOps: AWS Lambda, Step Functions, SNS for serverless; Airflow & Redshift for analytics; Kafka & Spark for streaming; Docker & GitHub Actions for CI/CD