How aaryanharshalpawar/aaryan-pawar-persona-web works
Project type and purpose
• This is a TypeScript-based, single-page web application (SPA) built with React and Vite.
• It uses shadcn-ui (a set of Radix-powered, Tailwind CSS-styled components) to render UI primitives.
• There is no backend or server logic in this repo—this project focuses entirely on the client side.
File structure
• Top-level files and folders
– package.json, tsconfig.json, vite.config.ts, tailwind.config.ts → build and dev server configuration
– public/ → static assets (robots.txt, favicon, etc.)
– src/ → the heart of the application
• src/ sub-structure
– main.tsx → entry point, mounts React tree to index.html
– App.tsx → root component, holds routing/navigation logic
– pages/ → routeable components (Home, About, Contact, Index, NotFound)
– components/ → reusable feature components (AuthDialog, Navigation)
– components/ui/ → low-level UI primitives (button, card, dialog, tooltip, etc.)
– hooks/ → custom React hooks (useMobile, useToast)
– lib/ → helper utilities (utils.ts)
• Config and build scripts
– vite.config.ts & tsconfig.*.json define compilation, module resolution, and path aliases
– tailwind.config.ts & postcss.config.js for styling pipeline
README for additional insights
• Confirms tech stack (Vite, TypeScript, React, shadcn-ui, Tailwind)
• Describes development workflows via Lovable, IDE, or Codespaces
• Mentions hosting and custom domain setup via Lovable platform
• No backend or API references → purely static front-end
a. Main components to represent
– Developer environment
• IDE or Lovable web editor
• Git repository (GitHub)
– Build & CI/CD
• Vite development server (hot-reload)
• Vite build pipeline → output to dist/
• Optional CI/CD step (Git hooks or Lovable auto-deploy)
– Deployment & hosting
• Lovable hosting platform (static asset CDN)
• Custom domain DNS configuration
– Runtime application
• Browser running React SPA
• React root → App.tsx → Router layer → pages
• Components layer → feature & UI primitives
• Tailwind & shadcn-ui as styling/rendering engines
b. Relationships and interactions
• Developer commits → Git push → (CI/CD) → Vite build → deploy static files
• Browser requests index.html → loads JS/CSS bundles → React hydration
• App.tsx uses router to render pages → pages compose feature components → UI primitives call hooks/utilities
c. Architectural patterns & design principles
• Component-driven architecture (atomic design pattern for UI)
• Separation of concerns: routing vs pages vs components vs UI primitives vs utilities
• Declarative styling via Tailwind + shadcn-ui wrappers
• Client-only SPA model—no server logic in repo
d. Key technologies & libraries
• React & React Router (or similar) for client routing
• Vite for ES module dev server + bundler
• TypeScript for static typing
• Tailwind CSS for utility-first styling
• shadcn-ui (Radix UI underpinnings) for accessible components
• Custom hooks (useMobile, useToast) for shared state/behavior
Detail without overcomplicating
• Essential layers: developer tools, build pipeline, hosting, runtime application
• Interactions between layers rather than every single file