How webdevsimplified/job-board-ai works
Project type and purpose
• This is a full-stack, multi‐tenant job‐board platform built with Next.js (App Router). It serves two main user types—job-seekers and employers—providing authentication, job listings, application workflows, notifications, file uploads, and background processing.
• Key indicators: Next.js app directory (src/app), Clerk authentication, Drizzle ORM (SQL migrations), Inngest background functions, Resend email service, UploadThing file uploads.
File structure
• Top-level:
• src/app: the Next.js App Router code (React server/client components organized into (clerk), (job-seeker), (employer) layouts).
• src/app/api: Next.js server routes for background APIs (Inngest, UploadThing).
• src/components, src/features, src/services: shared UI components, feature modules (jobListings, organizations, users, applications), and wrappers around external services.
• src/drizzle: ORM config, schema definitions, and migrations (PostgreSQL).
• docker-compose.yml: local dev environment, likely spins up the database + Inngest.
• Patterns:
• “Feature folder” per domain (jobListings, organizations, users, jobListingApplications) with its own actions, DB queries, components, and client caches—this follows a modular “vertical slices” architecture.
• Next.js App Router file conventions map UI routes to folder structure.
• Services under src/services encapsulate integration with Clerk, Inngest, Resend, and UploadThing.
README for additional insights
• Dependencies: Next.js, Clerk, Drizzle, Inngest, Resend, UploadThing.
Detail
• Break the Next.js App Server into sub‐components if desired: App Router, API Routes, Feature modules.
• Drizzle schema directory and migrations as part of the Data Layer.