How aarishirfan/portfolio works
Project type and purpose
• This is a personal portfolio website built as a React single-page application (SPA) that uses HTML, CSS, and Bootstrap for layout and styling.
• The README also indicates a Node.js + Express.js backend layer to serve the static files and handle any API requests (e.g., contact form submissions).
File structure
• Top-level files:
• package.json / package-lock.json (project dependencies, scripts)
• README.md / .gitignore
• public/
• Static assets (index.html, manifest.json, robots.txt, and your PDF resume)
• src/
• src/index.js (application entry point)
• src/App.js / App.css (root React component)
• src/components/… (modular React components organized by feature: Navbar, Home, About, Projects, Footer, etc.)
• src/Assets/Projects (images or data for projects)
• test harness: App.test.js, setupTests.js, reportWebVitals.js
• No explicit “server/” directory is present, so the Express layer may live in a separate repo or be a simple static‐serving server embedded in package.json scripts.
README for additional insights
• Tech stack: ReactJS, HTML, CSS, Bootstrap on the frontend; Node.js + Express.js on the backend.
• Multi-page layout—implemented either via React Router or separate HTML files, but the file tree suggests a SPA with dynamic sections.
a. Main components
• Developer workstation (code editor, Git)
• Version Control (GitHub)
• CI/CD pipeline (optional—e.g., GitHub Actions, Netlify CI)
• Build toolchain (npm scripts, Webpack/Babel under the hood)
• Frontend SPA (ReactJS + Bootstrap)
• Backend server (Node.js + Express.js)
• Static file hosting / CDN (e.g., Netlify, Vercel, or your own host)
• External services (optional—email service for contact form, analytics, GitHub API)
b. Relationships & data flow
1. Developer → Git push → GitHub
2. CI/CD → triggers build → runs npm build → generates optimized static bundle
3. Build artifacts → deploy → Static host / CDN
4. User browser requests index.html → served by host/CDN → loads React bundle
5. React app renders Home, About, Projects, etc.
6. On contact or dynamic requests → React → HTTP call → Express API endpoint → processes / forwards to email service or database → response back to React
c. Architectural patterns & design principles
• Component-based UI (React), single-page application
• Separation of concerns: UI vs. API layer
• Static build pipeline for optimized delivery
• Optional microservices or serverless functions for light back-end tasks
d. Key technologies & frameworks
• ReactJS (frontend framework)
• Bootstrap (UI layout)
• Node.js + Express.js (server)
• npm / Webpack / Babel (build toolchain)
• Git / GitHub (version control)
• Optional: Netlify/Vercel (hosting), SendGrid/Mailgun (email), Google Analytics