prasannashrestha011/portal-ui

Purpose and Runtime

This is a Next.js App Router frontend for student and employer account/profile workflows, including authentication, employer profiles, student profiles, resume documents, and job/company service integration. It runs as a TypeScript React application under Next.js, with global styling and root layout defined in app/layout.tsx and app/globals.css.

Route Entry Points

App Router pages establish the user-facing flow:

• Landing page: app/page.tsx

• Authentication: app/login/page.tsx, app/register/page.tsx

• Employer profile: app/employer/profile/page.tsx

• Student profile lifecycle: app/student/profile/page.tsx, app/student/profile/upsert/page.tsx

• Student document/resume area: app/student/profile/document/page.tsx

middleware.ts is the cross-route boundary likely used for request-time access control, redirects, or session-aware routing.

Authentication Boundary

Authentication UI is separated from API and state concerns:

• UI components: src/components/Login.tsx, src/components/Register.tsx

• Authentication state/context: src/context/useAuth.ts

• Remote operations: src/services/auth.ts

• Auth contracts: src/types/auth.ts

Pages consume the components/context, while service code centralizes calls to the external backend rather than embedding HTTP behavior in route components.

HTTP and Service Layer

src/api/client.tsx is the shared API-client boundary. Domain services organize remote operations by business capability:

• src/services/studentProfile.ts

• src/services/employerProfile.ts

• src/services/company.ts

• src/services/job.ts

Typed request/response models in src/types/http.ts, src/types/studentProfile.ts, src/types/employerProfile.ts, src/types/company.ts, and src/types/job.ts constrain data crossing the frontend/backend boundary. The backend/API host and its infrastructure are not represented in the repository tree.

Student Profile Flow

The student flow supports viewing, editing/creating, and document handling:

• Presentation: src/components/StudentProfile/DisplayStudentProfile.tsx

• Edit form composition: src/components/StudentProfile/StudentProfileForm.tsx, src/components/StudentProfile/FormContent.tsx

• Resume upload: src/components/StudentProfile/UploadResume.tsx

• State access: src/context/useStudentProfile.ts

Data flows from profile pages into form/display components, through student-profile context and service calls, then returns as typed student-profile data. Resume upload is a distinct document boundary, likely requiring multipart or file-oriented API behavior.

Employer and Company Flow

Employer profile editing/display is encapsulated separately from student concerns:

• Employer UI: src/components/EmployerProfile/ProfileCard.tsx, src/components/EmployerProfile/ProfileForm.tsx

• Employer state: src/context/useEmployerProfile.ts

• Company state: src/context/useCompanyStore.ts

• Remote domains: src/services/employerProfile.ts, src/services/company.ts

This separation suggests employer identity/profile data and company data may be independently loaded and persisted, while sharing the common API client and auth context.

Shared UI and Deployment

Shared form primitives reside in src/components/Form/common.tsx, allowing profile and authentication screens to use consistent input behavior. Next.js configuration is in next.config.ts; the application is suitable for standard Node/Next.js hosting, including Vercel as indicated by the project scaffold. No server-side API routes, database implementation, or external storage provider are present in this repository.