How omercikan/nexthire-job-platform works
Project type and purpose
• NextHire is a full-stack job-platform built with Next.js (App Router), React, TypeScript, Tailwind/SCSS, Firebase (Auth + Firestore), and Redux Toolkit.
• The user flows include: public landing page, candidate/employer signup & login, newsletter subscription, and (under development) job listings with search & filters.
File structure
• app/ → Next.js “App Router” pages and layouts:
• (auth)/… → signup/login/password-reset routes
• api/firebase/… → serverless API routes (candidate/employer login/signup, reset-password, subscribe, fetchBlogs, favorites, employers by slug)
• is-ilanlari → job listings page
• layout.tsx, globals.css → top-level layout & global styles
• components/ → reusable UI components (layout/Header, layout/Footer, pages/home, pages/jobPostings, ui primitives)
• lib/ → client- and server-side utilities:
• lib/firebase.ts + api routes → Firebase SDK config
• lib/redux/ → Redux Toolkit store, feature slices, RTK Query services
• misc helpers: fetchData, deleteCookie, formatText, setUserDatabase, etc.
• context/ → React Context for authentication state
• public/ → static assets (images, JSON data for cities/districts)
• scss/ → custom styling modules
• configuration files: next.config.ts, netlify.toml, ESLint, Turbopack, sitemap
README for architecture notes
• Tech stack confirms:
• Next.js App Router
• Serverless API routes calling Firebase
• React Firebase Hooks + custom Firestore logic
• Redux Toolkit + RTK Query for global state & data fetching
• Formik & Yup for form validation
• Recent changes highlight organized Redux folder, RTK Query integration, Framer Motion, and new job-listing features.
Detail
• CS S/SCSS styling layer as a note (global styles, modules).
• Do not omit the context layer for client-side auth state.