How dodao123/cout-love works
Project Type and Purpose
• This is a full-stack Next.js application (React-based front end + serverless back-end APIs) for managing and viewing albums, audio clips, user notes, and basic analytics, with an admin interface.
• Key features (from file tree & README):
• Server-side rendered pages & client components under src/app
• API routes under src/app/api for albums, notes, uploads, admin auth, analytics, categories
• MongoDB for persistence (scripts/init-db.js, src/lib/mongodb.ts)
• Local file storage for uploads (public/uploads & storage/uploads)
• Tailwind CSS for styling
File Structure & Architectural Choices
• Top-level front end: src/app – Next.js App Router directories for pages and UI components
• Top-level back end: src/app/api – Serverless functions (Route Handlers)
• Configuration: next.config.ts, postcss.config.mjs, tailwind.config.js, eslint.config.mjs
• Database abstraction: src/lib/mongodb.ts, src/lib/database.ts, plus init/seed/test scripts in scripts/
• File upload handling: src/app/api/upload, lib/upload.ts, public/uploads & storage/uploads
• Caching/utilities: src/lib/clientCache.ts, lib/albumCache.ts, lib/cacheDebug.ts, lib/fetchWithCache.ts
Main Components & Their Roles
A. Client (Browser)
• Renders pages (React Server & Client Components)
• Invokes RESTful APIs for data (fetch/populate albums, notes, categories, analytics)
• Upload interface for audio & avatars
B. Next.js Server
• Serves SSR/SSG pages & static assets (public/)
• Hosts serverless API routes (src/app/api/…)
• Middleware (middleware.ts) for cross-cutting concerns (auth/session)
C. Database (MongoDB)
• Stores albums metadata, notes, user/admin credentials, analytics events, categories
• Initial setup & seeding via scripts
D. File Storage
• Local disk (public/uploads & storage/uploads) for audio, album text, avatars
• Served as static assets by Next.js
E. External/Platform Services
• Vercel (or similar) for deployment (serverless runtime)
• CDN (Next.js automatic) for static asset delivery
Relationships & Data Flow
1. User requests page → Next.js App Router → Server Component renders with data.
2. Client-side fetch → API route handler → lib/database or lib/mongodb → MongoDB
3. Upload flow: Client → upload API → lib/upload saves file to storage/uploads → metadata saved in MongoDB → file served from public/uploads on next deploy or via proxy route.
4. Admin login: Client → /api/admin/login → verify credentials in MongoDB → set cookie/session → protected API calls (/api/admin/albums, /api/admin/logout, /api/admin/verify).
5. Analytics: Client events → /api/analytics → store in MongoDB
Architectural Patterns & Principles
• Full-stack React with Next.js App Router (Server & Client components)
• Serverless functions (one Route Handler per endpoint)
• Single codebase for front end + back end
• Separation of concerns: UI (app/) vs. API (app/api/) vs. data layer (lib/)
• Modular utilities (caching, fetch wrappers)
• Static asset management & incremental regeneration