How mobakour/peeko works
Project type and purpose
• Peeko is a full-stack social media web application (short video reels) built with the MERN stack (MongoDB, Express, React, Node) plus AWS S3 for video storage and an email service for account verification.
• Users can register/login, upload videos, comment/like/share infinite-scroll feeds, and view profiles.
File structure
• Top-level directories:
• client/ – React front end
• server/ – Node/Express TypeScript back end
• client/src: React entry points (index.jsx, App.jsx), pages (Auth, Home, Profile, Video, NotFound), shared components, custom hooks, global state stores (Zustand or similar).
• server/src: Express app, controllers (video, comment, user, feedback), middleware (auth, file upload via multer, resource checks), Mongoose models (User, Video, Comment), utils (mailer, S3, validation), type definitions.
• Config/build files: client package.json + Tailwind, server tsconfig.json + nodemon.json + api.md.
README for additional insights
• Confirms technologies: React + TailwindCSS, Node + Express in TypeScript, MongoDB via Mongoose, AWS S3 for video, SMTP or AWS SES for email.
• Features: authentication, email verification, file uploads, social interactions (comment/like/share), infinite scroll.
Diagramming conventions & elements
• Use clear labels: e.g., “React Client,” “Express API,” “MongoDB,” “AWS S3,” “SMTP Service.”
• Blue rectangles for frontend components.
• Green rectangles for backend modules.
• Annotations:
• Ports (e.g., 3000 for client, 5000 for server).
• Authentication flow (login → JWT issuance → protected endpoints).