How akshaylavan/akshay_portfolio works
Project type and purpose
• This is a single-page portfolio website built with React.js and GSAP for animations.
• It’s purely front-end: there is no backend service or database. The site is compiled into static assets and deployed (e.g., via Netlify).
File structure
• Top level:
• public/ – static HTML (index.html), manifest, redirects
• src/ – React source code
• package.json & lock – dependency and build scripts
• src/ contains:
• index.js – mounts the React App
• App.js & App.css – root component and styling
• components/ – modular React components (Navbar, Hero, About, Skills, Projects, Contact, etc.), each with its own CSS
• netlify.toml – configuration for Netlify deployment
README for additional insights
• Frameworks: React, GSAP, custom CSS
• Build & deployment steps: npm install, npm run build, deploy static build folder to Netlify (or similar)
• No external data sources—projects, skills, and content are defined in component arrays and JSX.
Main components
a. User Browser (Client)
b. Static Asset Hosting (Netlify or CDN)
c. React Application
– index.html → index.js → App.js
– Component tree: Navbar, Hero, About, Skills, Projects, Contact, Achievements, Experience
– GSAP animation layer interacting with DOM elements
d. Build Pipeline
– Node.js/npm install → Webpack (via Create React App) → Production bundle
Relationships and data flow
• User’s browser requests “/” → Hosting/CDN serves index.html and JS/CSS bundles
• index.js bootstraps React in the DOM
• App.js orchestrates child components, passing props or importing content arrays
• GSAP triggers animations on component mount or scroll events
• Build pipeline is triggered on code change or Git push (CI/CD) → automated deploy to Netlify
Architectural patterns and design principles
• Component-based architecture (React) for separation of concerns
• Static site generation/build → no runtime backend dependencies
• Modular CSS per component
• Responsive design principle baked into each component’s CSS