How diegopluna/vitaes works
Main System Components
a) Client Layer:
• Next.js Frontend (app directory structure)
• UI Components (components directory)
• State Management (store directory)
b) API Layer:
• Authentication endpoints (app/api/auth)
• PDF generation endpoints (app/api/pdf)
• File upload handling (app/api/uploadthing)
c) Database Layer:
• Neon PostgreSQL Database
• Drizzle ORM integration
Key Architectural Elements to Highlight
Frontend:
• Main UI Routes (/dashboard, /builder, /cv_only)
• Template System (components/cv/templates)
• Form Components (components/cv/form)
• Shared Components (components/ui)
Backend:
• Authentication System (Auth.js)
• PDF Generation Service (Puppeteer)
• File Upload Service (UploadThing)
• Database Operations (Drizzle ORM)
Flow Representations
• User authentication flow
• Resume creation and editing flow
• PDF generation and export flow
• Data persistence flow
Specific Implementation Details
a) Frontend Architecture:
• Next.js 13+ App Router structure
• Component hierarchy (templates, forms, UI elements)
• State management with stores
b) Backend Services:
• API route handlers
• Authentication flow with Github
• PDF generation pipeline
• File upload handling
c) Data Flow:
• User session management
• Resume data persistence
• Template rendering
• Export operations
Integration Points
Connections with:
• Github OAuth
• Neon Database
• UploadThing service
• Vercel deployment