A frontend mockup for a campus security management system, with separate interfaces for guards and administrators.
This repo lays out the interface layer for a campus security system with role-based views:
index.html— landing/entry pageguard-login.html— login screen for security guard accountsguard.html— guard-facing dashboard (presumably for logging entries/exits or flagging incidents)admin.html— administrator dashboard (presumably for managing guard accounts, viewing logs, or configuring access rules)
The role split (guard vs. admin) suggests the intended design separates day-to-day monitoring from system administration — a reasonable structure for a real access-control product, even though the logic behind both views isn't implemented yet.
Designed as a concept for campus/smart-building security — RFID-based entry validation with guard oversight and unauthorized-entry alerting was the original idea, tying directly into coursework on authentication and access control.
- Frontend: HTML (100% of current codebase — no CSS/JS framework or backend committed yet)
This is the honest next-steps list, not a finished feature set:
- Add actual authentication logic for guard/admin login (currently
guard-login.htmlis presumably a static form with no backend validation) - Implement the RFID validation logic this project was originally scoped around — either as a backend service or, if simulating without hardware, a mock validation layer
- Add a database or storage layer for guard accounts, access logs, and unauthorized-entry records
- Add CSS for actual usable styling — current pages are plain HTML
- Add a README description in GitHub's "About" section so the repo isn't unlabeled to visitors
- Once logic is added: write proper setup/run instructions here
MIT (or your choice) — add a LICENSE file at repo root if missing.
Built by Rithwik K R