How saufi-opi/event-management-app works
Project type and purpose
• This is a full-stack web application (“Event Management App”) built on Next.js (App Router), Prisma ORM, and NextAuth.
• Purpose: allow authenticated users to create/manage events (dashboard), and allow participants to register or join public event pages.
File structure
• Top level:
• prisma/schema.prisma → database schema definitions (PostgreSQL/MySQL)
• src/app → Next.js App Router routes
– (dashboard) subfolder: authenticated UI for event & participant management
– (home) subfolder: login & landing pages
– api/auth → NextAuth API route
– participate → public event participation pages
• src/components → reusable UI elements (forms, table, navigation, primitives)
• src/server → server-side business logic
– actions/*.action.ts → data-mutation functions
– data/*.data.ts → query helpers
– db.ts → Prisma client instantiation
– auth.ts & permission/permission.ts → auth & ACL
• src/providers/next-auth-provider.tsx → client-side NextAuth context
• middleware.ts → request middleware (auth guard, redirects)
• env.js, .env.example → environment variables
• Configuration: next.config.js, tailwind.config.ts, tsconfig.json, lint/format configs.
README for insights
• Confirmation of Next.js + Prisma tech stack.
• Feature set: event creation, participant management, sign-in.
Main system components & their interactions
a. Frontend (Next.js App Router)
• Layout & page components under src/app drive SSR/SSG UI
• Client-side React components under src/components render forms, tables, navigation
• NextAuth React hooks (supplied by next-auth-provider) manage session state
b. API / Server Layer
• Next.js API route at /api/auth/[...nextauth] handles OAuth/session flows
• Server Actions (inside src/server/actions) exposed via form submissions / fetch calls
• Middleware routes requests; enforces auth/permissions via src/server/auth + permission
c. Database Layer
• Prisma client (src/server/db.ts) connects to relational database defined in prisma/schema.prisma
• Data access functions (src/server/data) encapsulate Prisma queries for events & participants
d. External Services
• OAuth providers configured by NextAuth (e.g., Google, GitHub—implicit in env)
• Optional external email/SMS services if notifications were added (not explicit here)
Architectural patterns & design principles
• Monolithic, single-repo full-stack: UI + API + DB in one Next.js project
• Separation by concern:
• Presentation: src/app + src/components
• Business logic: src/server/actions + src/server/data
• Persistence: Prisma + schema
• Cross-cutting: middleware, auth, permissions
• React server components vs. client components (Next.js 13 App Router)