How backofficeproject/frontend works
Project type and purpose
• This is a React-based single-page “Backoffice” frontend application (no backend code here) whose role is to provide HR dashboards (Attendance, Benefits, Employees, Performance, Recruitment, Reports) behind an authentication layer.
File structure
• Top-level build & config:
• index.html, public/ (fonts, static assets)
• vite.config.js, postcss.config.js, tailwind.config.js, eslint.config.js
• Application entry & styling:
• src/main.jsx (mounts App into index.html)
• src/App.jsx + App.css + index.css
• Routing & navigation:
• src/router/ (routes.js, index.jsx, PrivateRoutes.jsx)
• Global state & auth:
• src/store/AuthContext.jsx
• Pages (one per feature):
• src/pages/{Attendance, Benefits, Dashboard, Employees, Performance, Recruitment, Reports}.jsx
• UI components organized by domain:
• src/components/auth (LoginPage, ProtectedRoute)
• src/components/layout (Header, Sidebar, Layout)
• src/components/common (Card, Stats)
• src/components/dashboard, employees
• Utilities & abstractions:
• src/hooks (custom React hooks)
• src/lib (API clients, helpers)
README.md
• Confirms this is the “Backoffice frontend App.” No additional architecture docs, so we infer based on code.
Diagramming essentials
• User → Browser → App
• App → Router → Pages
• Pages → Hooks/Lib → External API
• External API → Pages → UI components → Browser render
• Blue for UI (Layout, Pages, Components)
• Green for Logic (AuthContext, Hooks, Lib)
• Orange for Routing (Router, PrivateRoutes)
• Gray for Tools/Pipeline (Vite, Tailwind, ESLint)