How ndbao1803/interview-tracker works
Project type and purpose
• This is a full-stack, Next.js 14 (app directory) web application called “Interview Tracker.”
File structure
• Top-level:
• app/ – Next.js front-end pages (React/TSX), protected routes, and serverless API endpoints under app/api/*
• components/ – reusable UI components (split into apps-wide UI, application-specific, company-specific, dashboard widgets, form steps, shadcn/ui primitives)
• utils/ & src/lib/ & src/services/ – utility functions, Prisma client setup, business logic/service layer for applications and companies
• prisma/ (and src/prisma/) – schema.prisma and seed scripts for database modeling & seeding
• supabase/ – config.toml, seed.sql, and middleware for integrating Supabase (Auth & Storage)
• public/ – static assets (animations, logos)
• middleware.ts – Next.js middleware for route protection via Supabase Auth
• next.config.js, tailwind.config.ts, tsconfig.json – project and styling configuration
README for additional insights
• Confirms tech stack: Next.js (frontend + backend), Supabase (Auth & Postgres DB), Prisma ORM, Tailwind CSS, Nivo for charts, shadcn/ui for UI primitives.
• Authentication and protected routes are central.
Detail
• API route group as a sub-component under the API Layer.
• Folder-based routing: e.g., app/api/applications/[id]/route.ts.
• Service modules (src/services/*) connected to specific API endpoints.
• Both SSR and client-side data fetching flows.