How ymadhumohanreddy/the-preppal works
Project type and purpose
• PrepPal is a full-stack AI-driven web application built with Next.js (App Router), React and Tailwind CSS on the frontend, Node.js + Drizzle ORM on the backend, and PostgreSQL as the primary data store.
• Its goal is to serve interactive interview sessions: generate questions, collect user responses, send them to an AI service for feedback, and persist sessions for later review.
File structure
• Top-level “app” directory: Next.js App Router pages and nested routes for auth (sign-in, sign-up), static pages (aboutme, giveup), and the core “dashboard” section.
• “components”: shared UI elements (buttons, cards, modals, etc.).
• “utils” and “lib”: database connector (utils/db.js), ORM schema (utils/schema.js), AI-modal wrapper (utils/GeminiAIModal.js), general helpers (lib/utils.js).
• Configuration and build scripts: drizzle.config.js, next.config.mjs, postcss.config.mjs, tailwind.config.js.
• “public”: static assets (videos, fonts).
• Middleware (middleware.js) manages auth or route protections.
Readme insights
• Features: question generation, real-time feedback, session storage.
• Tech stack: React/Next.js, Tailwind, Node.js, Drizzle ORM, PostgreSQL, external AI APIs.
• Project structure hints at clear separation: frontend components vs. data/DB utilities.
a. Main components to show
• Client (Browser/Mobile) running Next.js React App (Client Components)
• Next.js Server (Server Components + API Routes)
• Drizzle ORM Layer (drizzle.config.js + utils/db.js + utils/schema.js)
• PostgreSQL Database
• External AI Service (OpenAI or Gemini via GeminiAIModal)
• Static Asset Server (Next.js “public”)
• Authentication/Middleware
b. Relationships and interactions
• Browser ↔ Next.js Server: page requests, API calls, client-server component hydration
• Next.js Server ↔ Database: ORM queries for session data, user profiles, interview logs
• Next.js Server ↔ AI Service: HTTP/gRPC calls for question generation or feedback
• Next.js Server ↔ Static Assets: CSS, fonts, videos served from “public”
• Middleware enforces auth on protected routes (dashboard, interview)
c. Architectural patterns / design principles
• Layered architecture: Presentation (React UI) → Application (Next.js SSR/Server Components) → Data (Drizzle ORM → PostgreSQL)
• Component-based UI (isolated, reusable UI bits under “components” and “app/dashboard/_components”)
• Route grouping and nested layout using Next.js App Router conventions
• Separation of concerns: AI integration encapsulated in utils/GeminiAIModal.js
d. Key technologies / frameworks
• Next.js App Router & Server Components
• React + Tailwind CSS for UI
• Drizzle ORM + PostgreSQL for persistence
• External AI API (via GeminiAIModal or OpenAI wrapper)
• Middleware.js for request guards