How anujbag012/fortscape-visuals works
Main components
a. Developer Environment
• IDE/Code Editor
• Git/GitHub (Version Control)
• Node.js & npm
b. Build Toolchain
• Vite Dev Server (Dev-Time HMR)
• TypeScript Compiler
• PostCSS & Tailwind CSS Processor
c. Project Static Assets
• public/index.html, robots.txt, assets
d. React SPA
• Entry Point: src/main.tsx → App.tsx
• Router & Pages (src/pages)
• Sections Components (src/components/sections)
• UI Components Library (src/components/ui + shadcn-ui)
• Hooks (src/hooks) & Utilities (src/lib/utils.ts)
e. Hosting & Deployment
• Lovable Hosting / Static File Host (Netlify, Vercel, etc.)
• Custom Domain (optional)
f. End User
• Web Browser
Relationships and data flow
• Developer edits code → commits to GitHub → triggers CI or direct build
• npm install & “npm run dev” launches Vite Dev Server
• Vite watches source, compiles TS, applies Tailwind CSS → serves SPA assets
• On build (“npm run build”), Vite bundles React code + CSS → outputs static files
• Static files are deployed to Lovable Hosting
• Browser requests index.html → loads JS/CSS → React hydrates the SPA
• User navigates via React Router → components render (UI library + custom sections)
Architectural patterns
• SPA architecture with client‐side routing
• Component‐based UI (atomic UI in src/components/ui + domain sections in src/components/sections)
• Separation of concerns:
– Layout & Pages (src/pages)
– Reusable UI primitives (buttons, dialogs, cards…)
– Business/feature sections (tourist‐spots, places)
– Shared hooks and utilities
• Build‐time CSS extraction and tree‐shaking via Tailwind & Vite
Relevant technologies
• React & React Router (client‐side rendering)
• TypeScript (static typing)
• Vite (dev server + bundler)
• Tailwind CSS + PostCSS (utility‐first CSS)
• shadcn-ui (prebuilt React components styled with Tailwind)
• Labels for technologies and functions (e.g., “TypeScript Compiler”, “Tailwind Processor”)