How ayazsa/my-portfolio works
Project type and purpose
• This is a single-page portfolio website built with React and Vite.
• Purpose: showcase the author’s resume, projects, experience, education, and contact info in a smooth, responsive UI.
File structure
• Top-level files & config
– package.json / package-lock.json: dependencies (React, Vite, Tailwind) and scripts (dev, build, serve).
– vite.config.js, postcss.config.js, tailwind.config.js: build tooling & CSS framework setup.
– eslint.config.js: lint rules.
– index.html: root HTML template.
• public/
– Static assets (favicon, AyazResumeFr.pdf).
• src/
– main.jsx: app entry point—mounts React into index.html.
– App.jsx & App.css: top-level layout and global styles.
– routes.js: React Router configuration.
– data/projectList.js: JSON-like list of portfolio projects.
– components/: reusable UI pieces (Header, Footer, HeroSection, AboutSection, ProjectsSection, ModalProjectDetails, ContactSection, AnimatedSection).
– pages/: page-level views (Home, Projects, Experience, Education, Contact).
README for additional insights
• Minimal React + Vite template with HMR and ESLint.
• Recommends TypeScript for production—this is currently JavaScript.
a. Main components
1. Client Browser (user interface)
2. Static Asset Server (serves index.html, JS/CSS bundles, PDF)
3. React Application
• Router layer (routes.js)
• Page components (Home, Projects, Experience, Education, Contact)
• Shared components (Header, Footer, sections)
• Data layer (projectList.js)
4. Build Toolchain (Vite + plugins + Tailwind + PostCSS + ESLint)
b. Relationships & interactions
– Browser requests index.html → Vite dev server or static host → serves JS/CSS.
– React Application boots in browser → React Router picks page based on URL → loads corresponding page component.
– Page component pulls in sections (components/) and data (projectList.js) → renders UI.
– User actions (e.g., “View project details”) trigger component state changes or modal display.
c. Architectural patterns & design principles
– Component-based UI (React).
– Unidirectional data flow (props down, events up).
– Client-side routing (React Router).
– Separation of concerns:
• Layout vs. page vs. section components
• Static data vs. component logic
– Build-time vs. runtime separation:
• Vite handles dev+build, Tailwind processes styles at build time.
d. Key technologies
– React (UI library)
– Vite (bundler / dev server with HMR)
– React Router (routing)
– Tailwind CSS & PostCSS (styling)
– ESLint (linting)