How sumitha05/finchamp-24 works
Project type and purpose
• FinChamp is a full-stack Next.js web application providing a financial companion platform with personalized advice, interactive learning, product comparisons, news feeds, a chatbot, and virtual trading.
• The README confirms key technologies: Next.js (app router), Drizzle + Neon (database), Clerk (authentication), Botpress (chatbot), plus various React components and static assets.
File structure
• Top-level “app” directory: Next.js app-router pages and layouts for “main” (courses, leaderboard, shop, learn), “marketing,” and dozens of domain-specific routes (comparisons, news, banks, loans, etc.).
• “components”: reusable UI pieces (Navbar, Footer, modals, trade-app widgets, home cards).
• “app/api”: server-side API endpoints (Clerk webhooks).
• “db” + “migrations”: Drizzle ORM layer and SQL migrations targeting a Neon database.
• “lib”: business-logic helpers and modal state controllers.
• “store”: client-side modal state (Zustand hooks).
• “public”: static assets (videos, audio, images).
• Configuration and build files: next.config.mjs, tsconfig.json, tailwind.config.ts, lint/build scripts.
README for additional insights
• The system uses server-side rendering (SSR) and static assets via Next.js app router.
• Authentication is offloaded to Clerk (OTP flow).
• Chatbot uses Botpress for AI-driven assistance.
• Database operations are managed by Drizzle (TypeScript ORM) over a Neon Postgres instance.
Detail
• Every major feature area (courses, quizzes, comparisons, trade app, news feeds).
• UI components back to the app router layout structure.
• Where static assets are served from public/.