NyayMargadarshak
Indian legal information and access to lawyers are hard for citizens to navigate.
- My role
- Full-stack developer.
- Status
- Deployed (frontend on Vercel, backend on AWS EC2)
- Technologies
- ReactNode.jsExpressPythonJWTAWS EC2PM2Vercel
Key contribution
Built a legal explorer for the new criminal codes, advocate discovery, client–lawyer communication and role-specific dashboards, plus the supporting data pipeline and APIs.
How it fits together
Who
- Citizen
- Advocate
Client
- React frontend (Vercel) (my contribution)
API
- Express API, JWT + role-based access (AWS EC2, PM2) (my contribution)
Features
- Legal explorer: BNS, BNSS, BSA (my contribution)
- Advocate discovery (my contribution)
- Client–lawyer communication (my contribution)
- Role-specific dashboards (my contribution)
Data
- Python legal-update scraper (my contribution)
What it does
- Legal explorer covering BNS, BNSS and BSA
- Advocate discovery
- Client–lawyer communication
- Role-specific dashboards
Problem and context
India’s criminal law was restructured into the Bharatiya Nyaya Sanhita (BNS), Bharatiya Nagarik Suraksha Sanhita (BNSS) and Bharatiya Sakshya Adhiniyam (BSA). NyayMargadarshak makes that material, and the lawyers who work with it, easier for citizens to reach.
User workflows
Citizens browse and search the legal explorer, find advocates, and communicate with them. Advocates and clients each get a role-specific dashboard.
Architecture
A React frontend deployed on Vercel talks to Node.js / Express APIs on AWS EC2, managed with PM2. APIs are secured with JWT and role-based access control.
A Python scraping pipeline collects legal updates so the explorer can stay current.
Constraints
Legal information is not legal advice. A platform like this needs clear provenance for every provision it shows and a clear boundary between information and representation.
Links and artifacts
No public repository or deployment link is listed. Code and demonstrations are available on request, as stated on the CV.