How onetalentteam/hrm-project-temp works
Project type and purpose
• This is a front-end monorepo containing two single-page applications (SPAs) built with React + TypeScript + Vite:
– An “Admin” SPA under src/admin for HR management (attendance, recruitment, tasks, teams, etc.)
– A “Client” SPA under src/client for public-facing career pages, sign-in, forgot-password, home, etc.
• It relies on a shared API service layer (src/api) to communicate with backend REST endpoints (auth, attendance, project, user, etc.).
File structure
• Top-level:
– public/: static assets (PDFs, favicon)
– src/:
· admin/: all admin pages, layouts, components, React Query hooks for data
· client/: all client pages, shared UI components, layouts, React Query hooks
· api/: axios configuration and typed services for each resource
· components/: design-system and general UI building blocks
· hooks/, lib/, types/: shared logic and typings
· main.tsx & vite.config.ts: entrypoints and build configuration
• Patterns & conventions:
– Component-based design in React, Atomic-style under components/ui
– Data fetching via custom hooks (useXxxQuery) and React-Query
– Modular pages for each feature (attendance, recruitment/jobs/applications/letters/posts, etc.)
– Monorepo style with shared code for both SPAs
Key insights from README
• Uses Vite as build tool with Fast Refresh (plugin-react or plugin-react-swc)
• ESLint and Prettier configured for TypeScript + React