How manikanteshwarareddy/schedio works
Project Type and Purpose
• This is a full-stack web application (“Schedio”) that connects three user types—students/employees (T1), colleges/organizations (T2), and recruiters (T3)—to share, search, and analyze project portfolios.
• Frontend: React SPA served from the frontend folder (built and served under backend/build or deployed separately on Vercel).
• Backend: Express.js REST API in the backend folder.
• Database: MongoDB for storing users, projects, comments, likes, bookmarks, analytics.
• External Services:
• RapidAPI Plagiarism Checker API
• Google Gemini API (code explanation)
• SMTP/email provider for authentication flows
Main Components
a. Client Layer (React SPA)
• Entry point: frontend/src/index.js → App.jsx
• Components directory: dozens of UI modules (e.g., SignIn.jsx, ProjectCard.jsx, FileExplorer.jsx)
• Settings: frontend/src/settings/axiosInstance.js configures Axios with base URL and interceptors.
• Build artifacts: backend/build (static HTML, JS, CSS) when frontend is packaged.
b. API Layer (Express.js)
• backend/index.js: Express server setup, middleware, session and JWT configuration.
• backend/route.js: Defines REST endpoints (Auth, Project Upload/Download, Search, Analytics).
• backend/controllers/*.js: Controllers implement business logic (login, main page data, file upload).
• Settings: backend/settings/env.js reads environment variables; axiosInstance.js may be used for internal HTTP calls (e.g., to external APIs).
• backend/vercel.json: Vercel deployment configuration.
c. Persistence Layer
• MongoDB collections: Users (T1/T2/T3 roles), Projects with metadata, Comments/Likes, Bookmarks, Analytics.
• File storage on server filesystem (uploads or similar) or a mounted cloud bucket (if extended).
d. External Integrations
• RapidAPI Plagiarism Checker invoked during upload or project save.
• Google Gemini for code explanations.
• SMTP/email service (using EMAIL and PASSWORD from env) for signup, password reset.
Relationships and Data Flows
• User → Browser → React SPA
• UI dispatches HTTP requests via Axios to Express API
• React SPA → Express API (REST endpoints)
• Authentication (login/signup/forgot password)
• Project CRUD (upload videos, code, images)
• Search/filter (language, institute, domain)
• Likes/comments/bookmarks
• Profile PDF download
• Express API → MongoDB
• Read/write user profiles, projects, analytics
• Express API → External Services
• Plagiarism check: HTTP request to RapidAPI endpoint
• Code explanation: request to Gemini API
• Express API → File Storage
• Save uploaded files, serve static assets
Architectural Patterns and Design Principles
• Client-server separation: clear boundary between React SPA and Express API
• MVC-inspired structure on backend: route definitions + controllers + settings
• RESTful API design for resources (Users, Projects, Comments, Bookmarks)
• Environment-driven configuration (env vars in .env files)
• Single-page app with component-based design on frontend