How aakash-73/my_portfolio works
Project type + purpose (what you’re diagramming)
This repo is a static, client-side single-page portfolio website built with:
• React 18 (component UI)
• Vite (dev server + bundling)
• Tailwind CSS + PostCSS (styling pipeline)
• Framer Motion (animations)
There is no backend service and no database in the repository. “Full Stack” in the README refers to the *portfolio theme/content*, not the architecture.
From the tree:
Runtime (browser) artifacts
• index.html – the HTML entry point Vite serves and injects the bundle into.
• src/main.jsx – bootstraps React (creates root, mounts <App />).
• src/App.jsx – top-level composition of sections.
• src/components/* – page/section components (Hero/Header, About, Experience, Projects, Skills, Education, Contact, etc.).
• src/data.js – central content model (resume data in one place).
• src/index.css – global styles (plus Tailwind directives/overrides).
• src/assets/ – static assets (images, etc., if present).
Tooling / build-time artifacts
• package.json / package-lock.json – dependencies, scripts (dev, build, preview).
• vite.config.js – Vite configuration (build outputs to dist/).
• postcss.config.js – PostCSS pipeline (Tailwind + autoprefixing).
• .github/workflows/deploy.yml – CI/CD automation for deployment (likely GitHub Pages or similar).
• .gitignore, .github/* – repo hygiene + automation.
Main components
For accuracy, split into Runtime (client) and Build/Deploy lanes.
React App
• Entry: main.jsx
• Root: App.jsx
• Header.jsx (Hero + Navigation)
• PersonalSticker.jsx (animated branding centerpiece)
• GeometricBackground.jsx (visual background system)
• About.jsx, Experience.jsx, Projects.jsx, Skills.jsx, Education.jsx, Contact.jsx
Content/Data Layer
• data.js as the single source of truth for content
Animation/Interaction
• Framer Motion (used inside components)
Developer Machine
• npm run dev → Vite Dev Server (HMR)
CI/CD
• GitHub Actions: .github/workflows/deploy.yml
Build Toolchain
• Vite Build (npm run build) → outputs dist/
• PostCSS + Tailwind compilation → generates final CSS
Hosting
• GitHub Pages / Netlify / Vercel (README lists options)
End Users
• fetch static assets (HTML/CSS/JS) from hosting CDN/origin
Architectural patterns/design principles evident here
• Component-based UI architecture (React): sections are separate components.
• Data-driven rendering: src/data.js is the content source; components consume it.
• Separation of concerns:
• Content (data.js)
• Presentation/behavior (components/*.jsx)
• Global styling (index.css + Tailwind config)
• Build tooling (vite, PostCSS, Tailwind)
• Deployment automation (GitHub Actions)
• SPA delivery model: static assets served; no server-side rendering indicated.
• Containers: Browser, Static Hosting/CDN, React SPA bundle
• Inside React SPA: major subsystems (Sections, Data, Styling, Animation)
• Developer → GitHub → GitHub Actions → Vite build → dist/ → Hosting → Users
• Lane 1: *Developer/CI*
• Lane 2: *Hosting*
• Lane 3: *Browser Runtime*
• “Entry Point” → src/main.jsx
• “App Shell / Section Orchestrator” → src/App.jsx
• “Content Model (Resume Data)” → src/data.js
• “Sections” → src/components/{Header,About,Experience,Projects,Skills,Education,Contact}.jsx
• “Branding/Animation Centerpiece” → src/components/PersonalSticker.jsx
• “Background System” → src/components/GeometricBackground.jsx
• “Styling” → tailwind.config.js, src/index.css, postcss.config.js
• “Bundler/Dev Server” → vite.config.js (Vite)
• “CI/CD” → .github/workflows/deploy.yml
• “Static Build Output” → dist/ (generated)
“As many components as possible” (without inventing architecture)
To increase detail while staying true:
• Break “Components” into:
• Layout & Navigation: Header.jsx
• Brand/Visual: PersonalSticker.jsx, GeometricBackground.jsx
• Content Sections: About/Experience/Projects/Skills/Education/Contact
• Break “Styling” into:
• Tailwind theme tokens (tailwind.config.js)
• Global CSS (index.css)
• PostCSS pipeline (postcss.config.js)
• Break “Build” into:
• Dev mode (Vite dev server + HMR)
• Prod build (Vite bundling)
• Preview (npm run preview)