How slab10000/porfolio-web works
This repository is a static, single-page portfolio website:
• Frontend-only SPA built with React + TypeScript, bundled by Vite
• Runs entirely in the browser; no server-side backend, no database
• “Dynamic” content is mostly data-driven UI (from constants.ts / types.ts) plus visual effects (Framer Motion + Three.js)
• External integrations appear limited to outbound social links (via services/socialMediaService.ts), not API calls
• Build/deploy pipeline (source → Vite build → dist/ → static hosting/CDN)
• Runtime architecture in the browser (React component tree + data/service modules + assets)
File structure analysis (map folders/files to architectural components)
From the tree and README:
Entry points / composition
• index.html – Vite HTML entry
• index.tsx – React root render (mounts into DOM)
• App.tsx – top-level composition of the page sections
UI component layer (components/)
• Navbar.tsx
• Hero.tsx
• Experience.tsx
• Projects.tsx
• ProjectModal.tsx (overlay/modal interaction pattern)
• Skills.tsx
• Socials.tsx
• Visual/FX components:
• StarBackground.tsx, ShootingStars.tsx (Three.js / canvas/WebGL background)
• LiquidGlassCard.tsx (reusable UI look & feel / card primitive)
Data + types
• constants.ts – likely holds arrays/objects for projects, experience, skills, etc.
• types.ts – TypeScript types for those models
Service layer
• services/socialMediaService.ts – “integration boundary” for social links (even if it’s just a mapping/formatter). Treat it as a service module that isolates “external destinations” and keeps UI components clean.
Build outputs / static assets
• public/astronaut/... – static assets copied as-is by Vite
• project images/ – project imagery (treat as static assets)
• dist/ – production build output (deployment artifact)
• vite.config.ts, tsconfig.json, package.json – build/tooling configuration
What the README adds (architecture cues)
• Component-based architecture with separation of concerns
• Animations: Framer Motion is central to the interaction design
• 3D background: Three.js is a notable subsystem (render loop, canvas/WebGL)
• Fully responsive (implies layout/styling layer is important, but still a browser-only system)
For this particular project, accuracy comes from representing:
• No backend: don’t invent APIs, databases, auth, or server components.
• Two “engines” at runtime:
1) React rendering lifecycle (DOM updates, state)
2) Three.js render loop (canvas/WebGL)
• Stateful interaction hotspot: Projects + ProjectModal (selection state, modal visibility)
• Build vs runtime: Vite/Tailwind/TypeScript are build-time concerns; React/Three.js/Framer Motion are runtime concerns.
Don’t overthink, separate into many components (but keep them truthful)
• Calling out the two major subsystems: UI sections and 3D/animation
• Separating data/constants, types, and service(s) as distinct modules
That will be both accurate and as componentized as possible given the codebase.