How sunnyspringwind/portfolio-site works
Project type and purpose
• This is a full-stack portfolio site (“JAMstack”-style) with
• A React + TypeScript + Vite + Tailwind frontend
• A Node/TypeScript + Express backend exposing a “message” REST API
• A serverless function (Netlify Functions/sendEmail.ts) for handling outbound emails
• A MongoDB (via Mongoose) datastore for persisting incoming messages
File structure
• Top level splits into frontend/ and backend/
• backend/src/config – app & DB config (db.ts likely uses Mongoose to connect MongoDB)
• backend/src/controllers & models & routes – classic MVC arrangement
• backend/src/server.ts – Express app entrypoint
• frontend/src – React component tree, pages, services, and assets
• frontend/netlify/functions – serverless function(s) to send email directly from browser requests
• Config and build files
• tsconfig.json in both tiers, package.json scripts, Vite config, Netlify redirect rules
Insights from README
• It’s deployed as a portfolio on GitHub Pages (static) but contains Netlify function config – likely deployed on Netlify or similar CDN+serverless platform
• Core features: show projects, roadmap, contact form