How satyam-code45/workwave works
Project type and purpose
• This is a full-stack, server-centric web application built on Next.js (App Router).
• It’s essentially a job board platform: users can sign up (via NextAuth), post jobs, browse and favourite listings, pay to feature jobs (Stripe), and background‐process tasks (Inngest) like email notifications (Resend) and file uploads (UploadThing).
File structure
• Top-level “app” directory: Next.js app-router pages & layouts.
• (auth) subfolder for authentication UI & flow.
• pages under app/(auth)/login, app/onboarding, app/post-job, app/my-jobs, app/job/[jobId], app/favourites, app/payment.
• app/api: serverless routes (NextAuth, Inngest, UploadThing, Stripe webhook).
• app/utils: client-side helper modules (db, auth, stripe, inngest client, Zod schemas).
• “components”: UI components split into forms, general UI, rich text editor, theme provider, primitive “ui” library.
• “prisma”: database schema and migrations (likely PostgreSQL).
• “lib”: utility scripts (e.g., Resend email integration).
• Configuration: next.config.ts, tsconfig.json, Tailwind, ESLint.
Important architectural patterns & third-party integrations
• App Router with nested layouts for auth gating.
• Serverless API routes handle authentication (NextAuth), payments (Stripe webhook), background tasks (Inngest), file uploads (UploadThing).
• Prisma ORM for DB access.
• Background workers triggered by Inngest functions.
• External services: Stripe (payments & webhooks), UploadThing (file uploads), Resend (email), maybe Google/GitHub OAuth providers.