How sathytrench/punk-calendar works
Main System Components
A. Frontend Layer:
• Next.js Application (Pages Router)
• TailwindCSS Styling
• Client-side tRPC API Integration
B. API Layer:
• tRPC Router System
• NextAuth Authentication
• API Routes (/api/events, /api/auth)
C. Database Layer:
• PostgreSQL Database
• Prisma ORM
D. External Services:
• Discord OAuth Provider
[Client Layer]
• ↕
[Server Layer]
• ↕
[Data Layer]
Detailed Component Breakdown
Frontend Layer (Blue):
[Next.js Pages] → [TailwindCSS Styles]
• ↓
[tRPC Client Hooks]
API/Server Layer (Green):
[tRPC Router] → [Event Routes]
• ↓
[NextAuth.js] → [Auth Routes]
• ↓
[Prisma Client]
Database Layer (Yellow):
[PostgreSQL Database]
External Services (Purple):
[Discord OAuth]
Key Relationships to Highlight
• TRPC connection between frontend and backend
• Authentication flow through Discord
• Demonstrate the Prisma ORM connection to PostgreSQL
• API routes for events and authentication
Important Implementation Details
• File structure organization (/src/pages, /src/server)
• Separation of API routes and tRPC endpoints
• Authentication integration points
• Database schema connection through Prisma
Specific Project Elements
For this punk calendar application, emphasize:
• Event data flow from submission to storage
• User authentication process via Discord
• API routes for event retrieval and manipulation
• Database schema for events and users
Remember to include a notes section explaining:
• The T3 Stack integration
• The role of NextAuth with Discord
• The PostgreSQL + Prisma implementation
• The tRPC API layer's significance
This will provide a complete picture of both the technical architecture and the business logic implementation specific to a community-driven calendar application.