How jamal474/portfolio works
Project Type and Purpose
• This is a single‐page portfolio website built with React (JSX/CSS) and Vite, deployed as a static site on Netlify.
• Its purpose is to showcase projects, experience, education, and generate SEO/schema data (see SEO.jsx, WebsiteSchema.jsx, PersonSchema.jsx, SitemapRoute.jsx).
File Structure Analysis
• Top level:
• index.html, netlify.toml → static host entry point and Netlify config
• package.json, vite.config.js → dependencies and build setup
• public/ → static assets (Google verification HTML, sitemap.xml) served as‐is
• src/ → application source
• assets/ → images, data JSON, fonts (custom typography)
• components/ → reusable React components (company cards, project cards, ML component, etc.)
• pages/ → high‐level views (Header, Footer, Main sections, SEO/schema wrappers)
• style/ → component/page‐specific CSS
• utils.js → shared helper functions
• App.jsx, index.jsx → SPA root and ReactDOM bootstrap
Key Technologies and Patterns
• React SPA using Vite for fast build/dev server
• Component‐based UI (atomic components in components/ and pages/)
• Static hosting on Netlify (continuous deploy via netlify.toml hook)
• SEO and schema generation routes (dynamic React routes to output JSON‐LD and sitemap)
Main Components and Their Relationships
• Developer Workstation
– Source files (src/) → Vite dev server & HMR → Browser
• Build Pipeline
– Vite build → bundles JS/CSS, copies public/ → /dist
• Hosting & CDN
– Netlify picks up /dist → serves HTML, static assets via CDN
• Client Browser
– Requests index.html → loads JS/CSS bundles → React router renders pages/
– Fetches JSON data from bundled experienceData.json, projectData.json for dynamic content
Architectural Patterns and Design Principles
• SPA with client‐side routing (React Router implied by SitemapRoute.jsx)
• Separation of concerns:
– Presentation (JSX in components/),
– Styling (style/),
– Data (assets/data/),
– Configuration (vite.config.js, netlify.toml)
• Static hosting model: build–>deploy–>serve