How mohammadnawawra2003/mohammad-portfolio works
Project type and purpose
• This is a single‐page, static portfolio website built with React, Tailwind CSS, and Framer Motion.
• It is intended to showcase Mohammad’s profile, experience sections (Home, About, Education, Experience, Skills, Contact), and provide a downloadable CV.
File structure
• Top level:
• index.html – SPA entry point
• MohammadAlnawawrehCV.pdf – downloadable resume
• README.md – project documentation
• assets/ folder:
• index-*.css – bundled Tailwind CSS styles
• index-*.js – bundled React/Framer Motion code
• (Plus any image files, e.g. profile photos, favicon.ico in deployment)
• There is no backend code—everything is pre‐built and served as static files.
README for additional insights
• Deployment target: any static host (Netlify, GitHub Pages, S3/CloudFront).
• Mobile-first, responsive design with modern typographic focus.
a. Main components:
– Client (Web Browser)
– CDN or Static Web Host (e.g., Netlify/Vercel/S3 + CloudFront)
– Static Asset Store (HTML, CSS, JS, PDF, images)
b. Relationships & interactions:
1) Browser requests index.html from CDN/Host
2) CDN serves index.html → Browser parses & loads
3) Browser fetches index-*.js and index-*.css from CDN
4) React app renders sections and triggers smooth-scrolling, animations via Framer Motion
5) When user clicks “Download CV,” browser GETs MohammadAlnawawrehCV.pdf from CDN
c. Architectural patterns & design principles:
– Single‐Page Application (SPA)
– Static site hosting (no server-side logic)
– Asset bundling and cache busting (hashed filenames)
– Responsive, component-driven UI
d. Key technologies & frameworks:
– React (UI), Framer Motion (animations)
– Tailwind CSS (utility classes)
– Vite (local dev server, build tool)
• Blue for runtime components (Browser, CDN)
• Green for static assets (HTML/CSS/JS/PDF)
• Orange for build-time tools (Vite, npm)