How vishalmet/vibecoded-portfolio works
Project type and purpose
• This is a full-stack portfolio web application
• Frontend: React + Vite + TypeScript, serves a personal portfolio UI (About, Experience, Projects, Admin dashboard)
• Backend: Node.js + TypeScript + Express (implied by folder layout), providing RESTful APIs and file‐upload support
• Database: MongoDB for storing experiences and project metadata
File structure
• Top level
– client/ : React/Vite front-end code with pages, UI components, assets, environment config
– server/ : Node/TypeScript back-end code with config, database connection, middleware, models, routes, uploads folder
– package.json (root) orchestrates install and dev scripts for both sides
• client/ highlights
– src/pages/ : the routed UI pages (About, Experience, Projects, admin)
– src/components/ : reusable React components (Navbar, Footer, cursor effects, scroll behaviors)
– src/lib/utils.ts : shared utilities
– public/ : static assets, manifest, robots.txt, sitemap.xml
• server/ highlights
– src/config/db.ts : MongoDB connection logic
– src/middleware/upload.ts : handles multipart file uploads
– src/models/ : Mongoose (or equivalent) schemas for experience and project
– src/routes/ : Express route definitions for CRUD on experience, projects, admin actions
– uploads/projects/ : persisted project images or attachments
README for additional insights
• Scripts to install both sides and run in parallel (npm run dev, client, server)
• Environment variables used:
– Client: VITE_API_URL pointing to backend
– Server: PORT, NODE_ENV, MONGODB_URI
Detail without over-splitting
• Every major folder function (routes vs. middleware vs. models)
• Build/deploy artifacts (Vite, nodemon.json) only if they affect runtime behavior