How seanchenr/sean-portfolio works
Project type and purpose
• This is a single-page, frontend-only portfolio website built with React, TypeScript and Vite.
• It renders a 3D interactive scene (using Three.js) with animations (GSAP) and Tailwind CSS styling.
File structure
• Top-level config:
• vite.config.ts, tsconfig*.json, tailwind.config.js, eslint.config.js
• package.json / lock files
• public/ :
• index.html
• Static assets: GLTF/GLB 3D models, textures, videos, images, license files
• src/ :
• main.tsx (React entrypoint)
• App.tsx
• components/ : reusable UI & 3D sub-components (NavBar, Button, AnimatedCounter, HeroModels/*)
• layout/ : page sections (Hero, FeatureCards, Info, ShowcaseSection, LogoSection)
• assets/ and constants/
• types/ : shared TypeScript interfaces
README for additional insights
• Tech stack badges confirm use of React, Three.js, GSAP, Tailwind, Vite, TypeScript
• No backend or external data services are mentioned
Main components & interactions (
a. Hosting & Deployment pipeline
• Git repository → CI/CD (e.g. GitHub Actions) → Vite build (bundle JS/CSS/assets) → Deploy to static host/CDN (Netlify, Vercel, S3+CloudFront)
b. Client-side architecture
1. Browser loads index.html and bundled assets
2. React app bootstrap (main.tsx → App.tsx)
3. Tailwind CSS provides styling layer
4. React component tree:
– Layout components render page sections
– HeroModels components mount a Three.js canvas
5. Three.js:
– Loads GLTF/GLB models from public/models and textures
– Builds scene graph (Scene, Camera, Renderer)
6. GSAP:
– Drives timeline and animations on 3D objects and UI elements
7. User interactions (scroll, clicks) propagate through React state/hooks → trigger GSAP/Three.js updates
Architectural patterns & design principles
• SPA (Single-Page Application) with clear separation:
• Entry & routing (none here—just one page)
• Presentation/Layout layer vs. 3D rendering layer
• Component-driven UI (React)
• Modular asset pipeline (Vite) for fast HMR and optimized production build
• Static-site deployment with CDN for performance
1. Developer & CI/CD
2. Build & Deployment (Vite bundling, CDN)
3. Browser Runtime (React + Tailwind + Three.js + GSAP)
4. Public Assets Store (models, textures, index.html)
• Inside Browser Runtime, break out:
• React Root → Layout Components → HeroModels
• Three.js Scene (Scene, Camera, Renderer) → GLTF Loader → Model Nodes
• GSAP Timeline & Animations
• React Components (NavBar, Buttons, AnimatedCounter)
• Developer → CI/CD → Build → Deploy → CDN → Browser
• Browser fetches index.html & bundles → React bootstrap → Three.js load assets → Render → GSAP drives animations → User events flow back into React/GSAP
• Rectangles (modules/components)
• Vite (bundler/dev server)
• TypeScript (typing layer)
• Tailwind CSS (utility classes)
• Three.js (3D engine)
• GSAP (animation engine)