How plismun/website works
Project type and purpose
• This is a full-stack event management website built with Next.js (App Router), TypeScript, and Tailwind CSS.
• It serves public pages (conference info, FAQs, schedule), handles user flows (signup, login, payment, application), and exposes serverless API endpoints for database operations.
• It uses NextAuth for authentication, TursoDB (LibSQL-style cloud database) for persistence, and integrates external services (SMTP for email, Behold for Instagram feeds).
File structure
• src/app/
• Next.js App Router structure: each folder under /app corresponds to a route (e.g. /app/about/page.tsx → /about).
• Global layout and CSS, metadata, sitemap.
• src/components/
• Reusable UI components (buttons, cards, tables in /components/ui) and page-specific widgets (hero, footer, forms, dashboards).
• src/pages/api/
• Serverless functions organized by purpose:
– /auth (NextAuth)
– /components (dbAuth utility)
– /internal (admin pre-flight, email sending)
– /modify (write operations: signup, setApplication, etc.)
– /retrieve (read operations: getUsers, getApplications, etc.)
– /utils (seedDb, sendEmail)
• src/lib & src/hooks
• Shared utilities and custom React hooks (e.g. useMobile).
• public
• Static assets: images, PDFs, schedule files.
• config, .github/workflows, next.config.ts, postcss.config.mjs
• Environment configuration, CI/CD, build settings, linting.
README for additional insights
• Tech stack summary: Next.js, TypeScript, Tailwind, Vercel, NextAuth, TursoDB, Shadcn UI, Radix UI.
• Database schema overview: tables for users, applications, supervisors, payments, people, delegations, committees.
• Deployment workflow: private repo → public mirror via GitHub Actions → Vercel preview & production.
• Environment variables for DB connection, auth secrets, email, feature flags, pricing.
Final recommendations
• Be exhaustive: include all API groups (retrieve, modify, internal).
• Both runtime interactions (user requests, DB queries) and deployment pipelines (CI/CD).
• Critical environment variables or feature flags that drive behavior (e.g., NEXT_PUBLIC_STAGE_*).
• Keep it up to date each year as routes, tables, or services change.