How muratozte/unisocial works
Project Type and Purpose
• This is a full-stack, Next.js-based social/community platform.
• Frontend: React components under src/app for pages like feed, clubs, events, messages, profile, registration flows (student/teacher/community).
• Backend: Next.js API routes (serverless functions) under src/app/api that handle authentication, user profiles, posts, comments, events, communities, followers, messaging.
• Data layer: Prisma ORM (prisma/schema.prisma) connecting to a relational database (e.g. PostgreSQL).
• State management: Redux Toolkit slices in src/store and React hooks for data fetching.
• Styling: Tailwind CSS and global styles.
File Structure
• Top-level config: next.config.mjs, tailwind.config.js, jsconfig.json.
• prisma/schema.prisma: defines your data model.
• src/app: Next.js App Router directory.
• (site) subtree: UI pages and layout, page.jsx files for each route.
• api subtree: REST-style endpoints grouped by domain (auth, user, post, comment, event, community, news, following).
• src/components: UI component library organized by feature (Login, Nav, Profile, Register, Feed, Clubs, Events, Messages, Settings, common, etc.).
• src/hooks: custom React hooks for data fetching and local UI state.
• src/store: Redux Toolkit store and slices for global state (login, feed, events, ui, register).
• src/util: service modules (authService, feedService, timeService).
• Static assets: src/assets (images, logos), fonts, global CSS.
README for Additional Insights
• Confirms Next.js App Router, font optimization, Vercel deployment path.
a. Main Components
• Client Browser: React/Next.js pages, components, client-side routing & state store.
• Next.js Runtime (Vercel/Serverless):
– App Router rendering (SSR, SSG, ISR)
– API Routes (serverless functions)
• State Management: Redux store (slices), React Query-style hooks.
• Business Logic / Services: authService, feedService, timeService.
• ORM Layer: Prisma Client.
• Database: PostgreSQL (or equivalent).
• Static Assets & CDN: images, fonts, global CSS, Tailwind.
• Optional External Services: Email/SMS provider, third-party OAuth, analytics.
b. Relationships & Data Flow
1. User → Browser UI → Next.js Pages
2. Browser UI dispatches actions to Redux store and calls React hooks → calls API endpoints.
3. API Route receives HTTP request → invokes service module → uses Prisma Client → reads/writes Database.
4. Database response bubbled up → Prisma → service → API Route → JSON → UI.
5. SSR/SSG data fetching: Next.js page gets data server‐side via API/services/Prisma.
6. Static assets served from CDN or Vercel edge.
c. Architectural Patterns & Design Principles
• Separation of concerns:
• UI components vs. data hooks vs. services vs. database schema.
• Modular API: each domain has its own folder grouping related routes.
• State centralization: Redux Toolkit for global state slices.
• File‐based routing: Next.js App Router for pages and API.
• Serverless functions: stateless, auto-scaled endpoints.
• ORM-based data modeling and migrations with Prisma.
• Component Driven Development: reusable UI building blocks.
d. Key Technologies & Frameworks
• Next.js (App Router, serverless API routes)
• React (functional components, hooks)
• Redux Toolkit (store, slices)
• Prisma ORM (schema, migrations, client)
• PostgreSQL or MySQL
• Tailwind CSS, postcss
• Vercel (hosting, CDN)
• Node.js runtime