How changteezy/cv-manager works
Main Components
• Frontend SPA
• Hosted as a static site (e.g. Vercel, Netlify)
• Built with React + TypeScript (client/src)
• UI via ShadCN UI & Tailwind CSS
• Form validation with React Hook Form & Zod
• BaaS Backend (Supabase)
• Authentication (supabaseAuth)
• PostgreSQL database (applicant, event, assessment tables)
• Storage (for file metadata)
• Edge functions or triggers (optional)
• External File Storage
• AWS S3 bucket (CV uploads, assignment files, offer/rejection letters)
• Email Service (can be via Supabase SMTP or third-party)
• CDN/Hosting
• Vercel (via vercel.json) or similar for static assets
Relationships & Data Flows
a. User (HR or Candidate) opens browser → requests static files from CDN
b. React SPA makes REST/Real-Time calls to Supabase Auth & Postgres via supabaseClient.ts
c. For file uploads/downloads → SPA uses presigned URLs to AWS S3
d. When sending emails → SPA invokes Supabase Function or direct SMTP/API call to email service
e. Analytics dashboard reads aggregated data from Postgres via Supabase queries
Architectural Patterns
• Single-Page Application (SPA) on the client
• Backend-as-a-Service (BaaS): no custom Node server
• “Jamstack” style: pre-built frontend + API integrations
• Event-driven file storage (uploads → S3 + metadata in Postgres)
• Component-based UI (client/src/components/*) following Atomic/UI library
Relevant Technologies
• Frontend: React, TypeScript, Vite, Tailwind CSS, ShadCN UI
• Forms & Validation: React Hook Form + Zod
• Data Layer: Supabase JS client (supabaseClient.ts)
• File Storage: AWS S3
• Hosting: Vercel (vercel.json)
• CI/CD: pnpm, Github Actions (optional)
• User → CDN (GET index.html)
• SPA → Supabase Auth (login/token)
• SPA → Supabase DB (CRUD queries)
• SPA → S3 (PUT/GET files)
• SPA → Email Service (POST email)
• Blue for client components
• Green for Supabase services
• Orange for AWS S3
• Gray for external email service