How saurabhog/portfolio works
Project Type and Purpose
• This is a single‐page portfolio website (JAMstack style) built with React/Vite, styled by Tailwind CSS, and backed by Supabase for data storage (portfolio items, certificates, comments).
• It’s not a microservices‐based backend—Supabase provides the database, auth, and storage as a service.
File Structure
• src/ → React application code
• main.jsx + index.html → entry points
• App.jsx → root component, routes to pages
• Pages/ → individual route components (Home, About, Contact, etc.)
• components/ → reusable UI pieces (Navbar, CardProject, InputField, Modal, LoadingScreen, etc.)
• supabase.js → Supabase client configuration
• public/ → static assets (Lottie animations, resume PDF, robots.txt, sitemap)
• config files → vite.config.js, tailwind.config.js, eslint.config.js, postcss.config.js
• vercel.json → deployment settings
README for Additional Insights
• Confirms tech stack: React, Tailwind, Supabase, AOS, Framer Motion, Material UI, SweetAlert2.
• Environment variables (VITE_SUPABASE_URL, VITE_SUPABASE_ANON_KEY) injected at build time.
Main Components
a. User’s Browser (Client)
b. CDN/Hosting Layer (Vercel or any static‐site host)
c. React Single‐Page Application
– App Routes (Pages folder)
– UI Components (components folder)
– Asset loading (public folder)
d. Supabase Backend
– Database (tables for portfolio, certificates, comments)
– Auth (optional user accounts)
– Storage (for files such as resume.pdf, images)
e. External Libraries & Services
– AOS, Framer Motion (animations)
– Lucide & Material UI (iconography, UI components)
– SweetAlert2 (modal dialogs)
f. CI/CD Pipeline (GitHub → Vercel)
Architectural Patterns & Design Principles
• SPA Pattern: one HTML shell, dynamic routing in client
• JAMstack: prebuilt assets served via CDN, API calls to backend‐as‐a‐service
• Component‐based UI: reusable, composable React components
• Separation of Concerns: presentation (React/Tailwind) vs. data (Supabase) vs. build (Vite)