How jefffreyli/visage works
Project type and purpose
• This is a full-stack media-editing web application built on Next.js (uses both the App Router under /app and some pages under /pages).
• The user can sign up/sign in via Firebase Authentication, upload audio/video, manipulate a timeline UI (DND-kit, Framer Motion), and then call serverless API routes to run FFmpeg video/audio processing.
File structure
• Top level:
• app/ → Next.js App Router UI for home (app/page.tsx), global layout (app/layout.tsx), dashboard (app/dashboard/*) and auth pages (app/signin, app/signup).
• pages/api/ → Next.js serverless functions: upload, download, merge, export, thumbnail, waveform, dynamic video retrieval.
• components/ → Reusable React components: home page (Hero, Features, CTA, Navbar, Footer), loading screens, media‐library & timeline helpers, animations, utility code (trim algorithm).
• firebase/ → Firebase config + signIn, signUp helper modules.
• public/, styles & config (tailwind.config.ts, postcss.config.js), TypeScript & ESLint configs.
• Key patterns:
• UI layer (React + Tailwind/DaisyUI) separated from backend logic (serverless functions).
• Modular components for media list, timeline blocks, audio/video cards.
• API layer orchestrates storage (Firebase Storage?), database (Firestore?), and FFmpeg processing.
README
• Confirms major dependencies: Next.js, Firebase, FFmpeg, DaisyUI (component library), DND-kit (drag/drop), Axios (HTTP), Framer Motion (animation).
Detail without over-complicating
• Break the system into these discrete components and flows.
• API route as part of the processing tier.
• How Firebase Auth sits between the client and backend.