How yagmurduman/manage-it works
Project type and purpose
• Manage-IT is a full-stack, cloud-based project management platform consisting of:
• A React/Redux/Tailwind front-end (“frontend-main”)
• A Node.js/Express back-end REST API (“backend-main”)
• A database layer (implied by models/schemas.js)
• External services (e.g., payment processing, email notifications, Swagger for API docs)
File structure
• Top-level directories:
• backend-main/
– server.js (entry point)
– api/controllers (Express controllers by entity)
– api/routes/routes.js (API routing)
– api/middlewares (authentication, authorisation, Swagger)
– api/models/schemas.js (data schemas; likely MongoDB/Mongoose)
– api/ssl (certificates for HTTPS)
– swagger.json (API spec)
• frontend-main/
– public/ (static HTML, CSS, images)
– src/ (React app)
· components/ (UI components grouped by feature)
· redux/ (store, feature slices)
· services/ (API service wrappers: HttpService, PaymentService, etc.)
· views/ (page‐level components)
– tailwind.config.js, postcss.config.js (CSS build)
Key insights from README
• Provides task tracking, scheduling, reporting, project analysis
• Allows booking sessions with business analysts
• Screenshots and user workflows are documented on the GitHub page
Main components
a. Front-end SPA
– React application
– Redux store (application state)
– UI components, routing (React Router implied)
b. Back-end API
– Express server
– Middlewares (auth, authorization, Swagger docs)
– Controllers (action items, backlog, checkout, company, consultants, project, user)
– Models (data schemas)
c. Database
– MongoDB (or another document‐store; indicated by schemas.js)
d. External services
– Payment gateway (Stripe/PayPal via PaymentService)
– Email/SMS notifications (if applicable)
– Swagger UI (for API documentation)
e. Infrastructure/DevOps
– SSL termination (certificates in api/ssl)
– Environment variables (.env files)
Relationships and interactions
• Front-end ↔ Back-end
• HTTP(S) calls via HttpService → endpoints in backend-main/api/routes
• JWT or session token flows through authentication middleware
• Back-end ↔ Database
• Controllers call models → perform CRUD on data store
• Back-end ↔ External services
• CheckoutController uses PaymentService for subscription/payments
• Notification services after booking or account events
• Swagger middleware exposes swagger.json → Swagger UI endpoint
Architectural patterns and design principles
• Monolithic API server organized by feature‐based modules
• MVC-style layering (routes → controllers → models)
• Separation of concerns: authentication and authorization as middleware
• Redux for centralized client-side state management
• PSR-like service wrappers in front‐end/services for API abstraction
Essential details to capture
• All seven controllers as subcomponents of the back-end
• Authentication and authorization middleware on the request pipeline
• The Swagger docs endpoint and SSL certificate layer
• Redux store slices for each entity mirrored by backend controllers/models
• Service layer in front-end that decouples UI from API endpoints