How fouziya-1903/fouziya-portfolio works
Project Type and Purpose
• This is a static single-page application (SPA) built with Vite, TypeScript, React, shadcn-ui and Tailwind CSS.
• No backend API or database—everything runs in the browser.
File Structure
• Top-level files:
• package.json, tsconfig*, vite.config.ts, tailwind.config.ts (build & config)
• public/index.html, public/robots.txt (static assets)
• src/ contains:
• main.tsx + App.tsx (entry point & root component)
• components/ (About, Projects, Contact, plus UI primitives from shadcn-ui)
• pages/ (Index.tsx, NotFound.tsx)
• hooks/, lib/utils.ts (custom hooks & utilities)
• styles (App.css, index.css)
• No server/ backend folder—this is pure front end.
README
• Confirms tech stack and deployment via Lovable (static hosting).
• No external API or data store mentioned.
Main Components
a. Developer Environment
• IDE (local)
• Git repository (push/pull via GitHub & Lovable)
b. Build Pipeline
• Vite (bundler / dev server)
• PostCSS / Tailwind / TypeScript compiler
c. Static Hosting
• Lovable platform (publishes to CDN)
d. Runtime in Browser
• index.html + JS bundles
• React app (App → pages → components → UI library)
Relationships & Data Flow
• Developer commits code → Git repo → triggers (optional) CI or direct Lovable sync
• Vite bundler (locally or in Lovable) processes src/ + public/ → static assets
• Assets deployed to CDN (Lovable)
• End user’s browser requests index.html → loads JS/CSS → React hydrates UI
• No API calls or backend interactions
Architectural Patterns & Design Principles
• SPA: single entry point (index.html → main.tsx)
• Component-based: functional React components + custom hooks
• Utility-first CSS: Tailwind for styling
• Design system: shadcn-ui primitives in src/components/ui
• Folder segregation: pages vs. components vs. ui primitives vs. hooks vs. lib
Technologies & Frameworks to Annotate
• Vite (dev server / bundler)
• React + TypeScript
• Tailwind CSS + PostCSS
• shadcn-ui component library
• Lovable static hosting / CDN