How tuankietcoderr/drd-fe works
Project type and purpose
• This is a Next.js (v13+) full-stack (primarily front-end + BFF) web application generated with create-next-app.
• It targets three user roles—candidates (user), recruiters (nha-tuyen-dung), and administrators (quan-tri)—each with its own auth flows, dashboards, and pages.
• It uses React (app-directory routing), Redux Toolkit (RTK Query for remote data), Contexts/hooks, Tailwind CSS, Docker, and external backend services (authentication, job data, file uploads, chatbot AI, etc.).
File structure
• Top level: configuration files (.eslintrc, prettier, Dockerfile, docker-compose.yml, deploy.sh), README, package.json.
• “src/app”: Next.js app router with nested folders for each role and auth vs. root layouts/pages.
• “src/components”: shared UI primitives (ui/…), views organized by domain (user, recruiter, admin).
• “src/redux”: Redux store config, RTK Query feature slices for auth, candidate, recruiter, job, cv-review, chatbot, etc.
• “src/hooks” & “src/context”: custom React hooks and contexts for audio recorder, chat widget, mobile detection, etc.
• “src/lib”, “src/utils”, “src/validator”: helper functions and validation logic.
• “next.config.mjs”, PostCSS/Tailwind config, jsconfig.json for path aliases.
README for additional insights
• Standard Next.js dev/start scripts, font optimization with next/font, Vercel deployment recommended. No mention of an internal API layer—instead the app relies on external REST endpoints surfaced via RTK Query.
Final advice
• Be exhaustive: break the app into logical layers (presentation, state, data-fetching, external services).
• Call out key cross-cutting concerns (authentication, file uploads, chatbot).
• Related components (e.g., Redux feature slices) to reduce clutter but still show their interactions.