How hikmetbozkurt/learnlinkproject works
Project type and purpose
• LearnLink is a full-stack educational platform comprising two main deliverables:
• learnlink_gui (a React+TypeScript SPA)
• learnlink_api (a Node.js/Express REST+WebSocket API with PostgreSQL)
• Purpose: to deliver course management, real-time chat, assignments, events, notifications, user profiles and collaboration features.
File structure
• Top-level directories:
• learnlink_api – backend code (MVC controllers/models/routes, service layer, middleware, socket handlers, config)
• learnlink_gui – frontend code (React components, routes, context, hooks, services, styles)
• Patterns & conventions:
• Backend follows MVC + Service pattern + Middleware pipeline + Socket.IO handlers
• Frontend organized by features/components, uses Context API and custom hooks
• Config/deployment files: .env, nginx_timeout.config, DEPLOYMENT.md, package.json, pnpm-lock, tsconfig.json
README for additional insights
• Tech stack: React, TS, Express, Node.js, PostgreSQL, Socket.IO, JWT, Multer, Nodemailer
• Architectural notes: client-server separation, RESTful API, real-time bidirectional events, MVC, service layer, component-based UI, Context API
Elements
• Labels: “React SPA”, “Nginx/Load Balancer”, “Express API”, “PostgreSQL DB”, “Amazon S3”, “SMTP Server”
• API server & middleware in another (e.g., green)
• Data stores/external services in a third (e.g., orange)
• Rounded rectangles for services
• Clouds for external services
7. Middleware on the path (AuthMiddleware, ErrorMiddleware, UploadMiddleware).
8. CI/CD or deployment infra if relevant (e.g., AWS Elastic Beanstalk).