How youzri/ahmedyousriportofolio works
Project type and purpose
• This is a single-page front-end web application built with Vite, TypeScript, React, shadcn-ui and Tailwind CSS.
• It has no custom backend code; it’s intended to be deployed as a static site (e.g., via Lovable’s hosting).
File structure
• Top-level assets:
• index.html – entry point served to the browser
• css/styles.css, js/booking.js, js/main.js – legacy or additional static assets
• public/robots.txt – static file copied verbatim
• Source code (src/):
• main.tsx – bootstraps React app via Vite dev server
• index.css & tailwind.config.ts / postcss.config.js – Tailwind CSS pipeline
• components/ui/ – all presentational shadcn-ui wrappers and custom components
• hooks/ – shared React hooks (useMobile, useToast)
• lib/ – utility functions (utils.ts)
• pages/ – React Router pages (Index, NotFound)
• Tooling & config:
• vite.config.ts – Vite build & dev server settings
• tsconfig*.json – TypeScript config
• package.json / bun.lockb – dependencies & scripts
• eslint.config.js – linting rules
README for additional insights
• Confirms tech stack: Vite, TypeScript, React, shadcn-ui, Tailwind CSS
• Deployment via Lovable (static hosting with optional custom domains)
• Development: clone, npm i, npm run dev
Diagramming recommendations
• Use clear, concise labels for each component (e.g., “Vite Dev Server”, “React App (src/)”, “Lovable CDN”)
• Code push → Build
• Build → Deployment
• Browser → CDN → Browser loads assets
• React App → Hooks / UI Components
• CI/CD & Build (Vite, Tailwind) – another
• Hosting & CDN – another
• Client Runtime (Browser, React) – another
Detail
1. Entry Point (index.html)
2. Asset Pipeline (Tailwind, PostCSS)
3. Bundler (Vite)
4. React App (main.tsx → pages & components/ui & hooks & lib)
5. Hosting (Lovable)
6. Client Browser