How siddharthjiyani/knots-social-media-app works
Project Type & Purpose
• Full-stack community discussion platform (“Knots App”)
• Built on Next.js 14+ (App Router), MongoDB/Mongoose, Clerk Auth, Tailwind CSS/Shadcn‐UI
• Features: user authentication, communities, threads & nested comments, file uploads, webhooks for real‐time events
File Structure & Architectural Insights
• app/… : Next.js App Router with grouped layouts for auth flows vs. main routes (home, communities, threads, profile)
• app/api/… : serverless Route Handlers for file uploads (UploadThing) and Clerk webhooks
• components/… : UI atoms/molecules/organisms (cards, forms, shared layouts)
• lib/actions/… : server actions (business logic controllers) for community, thread, user operations
• lib/models/… : Mongoose schemas (User, Thread, Community)
• middleware.ts : Clerk authentication middleware
• config & styles: next.config.js, tailwind.config.js, globals.css
Main System Components
a. Frontend (Next.js App)
• React Server Components & Client Components under app/
• Shadcn-UI + Tailwind for styling
b. Backend/API Layer
• Server Actions (imported in RSCs) for CRUD operations
• API Routes (/api/uploadthing, /api/webhook/clerk)
• Middleware for auth/authorization
c. Database
• MongoDB (external) via Mongoose models
d. External Services
• Clerk (user auth, social login, organizations & webhooks)
• UploadThing (file storage & React helpers)
• Svix (webhook signature verification)
Relationships & Data Flows
1. Browser → Next.js Pages (SSR/SSR via RSCs)
2. Pages → Server Actions (createThread, updateUser, etc.)
3. Pages → API Routes (upload, webhook)
4. Server Actions/API → Mongoose → MongoDB
5. Clerk handles login; middleware injects session → Next.js
6. UploadThing receives files; responds to client
7. Clerk emits org events → Svix‐verified webhook → Community actions
Architectural Patterns
• App Router & Route Groups for logical separation
• Server Actions as BFF/controller layer
• MVC-like layering: Models (Mongoose), Actions (Controllers), Views (React)
• Serverless functions for APIs
• Shared code monorepo (frontend + backend)
Elements
• Labels: “Browser”, “Next.js App”, “Server Actions”, “API Routes”, “MongoDB”, “Clerk”, “UploadThing”
• Frontend (Blue),
• Next.js Server/API (Green),
• Database (Orange),
• External Services (Purple)
• Rectangles for modules/services,
• Clouds for third-party services