How y0ar/jobboard works
Project type and purpose
• This is a full-stack “job board” application, comprising:
– A .NET Web API backend (ASP.NET Core, EF Core migrations, SQL database)
– A React + TypeScript single-page application frontend (Vite, component-based)
• Purpose: allow administrators, recruiters, candidates to manage jobs, applications, interviews, resumes, etc.
File structure
• Backend (folder: backend/JobBoard/JobBoard)
– Controllers: REST endpoints for Users, Jobs, Applications, Candidates, Companies, Authentication (JWT), Documents, Statistics, etc.
– Data: JobBoardContext (EF Core DbContext)
– Migrations: database schema evolution (InitialCreate, updates to recruiter, salary, job type)
– Models: domain entities mapping to database tables
– Configuration: appsettings.json (connection strings), launchSettings.json, Program.cs (middleware, routing, authentication)
• Frontend (folder: frontend)
– src/pages: route-level views (Home, Login, Register, Dashboard, JobDetails, AdminDashboard, AddJob, NotFound)
– src/components: reusable UI pieces (Header, Footer, JobCard, SearchBar, ProtectedRoute, etc.)
– src/contexts/AuthContext: authentication state management
– src/services: API wrapper modules (jobService, userService, applicationService, etc.)
– build & config: package.json, tsconfig, vite.config.js
Essential architectural elements
• Don’t add unnecessary components—focus on how data flows:
1. User interacts with React UI
2. UI invokes service methods (Axios)
3. HTTP request hits API Controller
4. Controller validates JWT, uses DbContext
5. Data persisted in SQL DB
6. Response flows back to UI
• Authentication flow, major entity domains (Jobs, Applications, Users), and configuration surfaces