How pheeloque/devtalk works
Project type and purpose
• DevTalk is a full-stack, real-time interview and meeting platform.
• Frontend: Next.js (App Router) + React + TypeScript + Shadcn/UI + Tailwind.
• Backend & data: Convex (serverless functions + database).
• Auth: Clerk.
• Real-time & streaming: Stream.
File structure (folders only)
• /src/app → Next.js routes & pages (UI entry points)
• /src/components → Reusable React components & providers
• /convex → Serverless functions & data schema (backend)
• /public → Static assets
• root config files → next.config.mjs, tailwind.config.ts, package.json, etc.
Key external services (from README & env vars)
• Clerk → User authentication & session management
• Convex → Data storage & serverless API
• Stream → Real-time messaging & call handling
Main components
• Browser / Client
• Next.js App (represented by /src/app + /src/components)
• Convex Backend (represented by /convex folder)
• Static Assets (/public)
• External Services (Clerk, Stream)
Relationships & data flows
• Browser ↔ Next.js App:
• SSR & static page requests
• React hydration, interactive UI
• Next.js App ↔ Convex:
• Convex client calls serverless functions in /convex
• Reads/writes to Convex database
• Next.js App ↔ Clerk:
• Auth flows (login, JWT validation, user data)
• Next.js App ↔ Stream:
• Real-time messaging, live interview audio/video
Architectural patterns & tech roles
• Component-based UI: /src/components provides provider wrappers (ConvexClerkProvider, StreamClientProvider)
• App Router: /src/app organizes pages (admin, home, meeting, recordings, schedule)
• Serverless functions: /convex contains all backend logic & data model
• “/src/app & /src/components” (Frontend)
• “/convex” (Backend)
• “/public” (Static Assets)
• “Clerk” (Auth Service)
• “Stream” (Real-time Service)
Browser → /src/app & /src/components → /convex
/src/app & /src/components ↔ Clerk
/src/app & /src/components ↔ Stream
Browser ← /public
• Blue for internal code folders
• Green for external services
• Gray for static assets