How qawsed123144/mindflow works
Project Type and Purpose
• This is a full-stack web application (“Mindflow”) for visual project planning with mind-maps, collaboration, and progress tracking.
• Frontend: Next.js (App Router) using React + Tailwind + custom UI components.
• Backend: Express.js + Mongoose connecting to MongoDB Atlas.
File Structure
• Top-level:
• frontend/ – Next.js application
• backend/ – Express API server
• frontend/app/api – Next.js API routes for mindmaps, signin, signup
• frontend/components & frontend/hooks & frontend/context – UI modules, state hooks, context providers
• frontend/lib – utilities, types, mock data, i18n
• backend/server.js – Express entry point
• backend/package.json – server dependencies (express, mongoose, jwt, etc.)
README for Additional Insights
• Explicit call-out of MongoDB Atlas via Mongoose
• Environment variables for PORT, MONGO_URI, JWT_SECRET
• Deployment targets: Vercel (frontend), Render/Railway (backend)
Main Components & Their Interactions
a. Next.js Frontend
• Hosts React UI, layouts, pages
• API routes under /api serve as middle-tier or pass-throughs
• Fetches authentication & mindmap data over HTTP
• Uses context providers (auth, language) + custom hooks (use-mindmap, use-toast)
b. Express Backend
• RESTful API endpoints (server.js + Mongoose models)
• Handles user signup/signin, CRUD operations on mindmap collections
• Issues JWT tokens, enforces authorization
c. MongoDB Atlas (via Mongoose)
• Persistent storage of users and mindmap documents
d. External Services
• Vercel – deploy Next.js frontend & API routes
• Render/Railway – host Express API
• MongoDB Atlas – managed database
Architectural Patterns & Design Principles
• Clear separation of concerns: frontend (presentation + client-side logic) vs. backend (data + business logic)
• RESTful API with JWT-based authentication
• React Context for global state (auth, language)
• Component-based UI library (reusable primitives in frontend/components/ui)
• Side effects/hooks pattern for data fetching