How neeexxxx/wanderwise works
Project type and purpose
• WanderWise is primarily a single-page, AI-powered travel-planning web application.
• It’s built with React (via Vite), styled with Tailwind CSS, and uses Firestore (Firebase) for backend persistence and authentication. Gemini AI serves as an external AI service to generate itineraries.
File structure
• Top-level files:
• index.html and vite.config.js indicate a Vite-based React front-end.
• tailwind.config.js and postcss.config.js configure styling.
• jsconfig.json, eslint.config.js enforce code conventions.
• package.json/package-lock.json show dependencies (React, Firebase SDK, Gemini AI client).
• There is no custom server code here—everything runs client-side and interacts with cloud services.
README for additional insights
• Confirms tech stack: React, Tailwind, Firestore (data store + auth), Gemini AI (external ML), hosted on Vercel.
• Describes user flows: sign-in → enter trip parameters → call AI → display/save itinerary → persist in Firestore.
a. Main components:
1. Client (Browser SPA)
2. Firebase Authentication
3. Firestore Database
4. Gemini AI Service
5. Vercel Hosting/CDN
b. Relationships & interactions:
• SPA fetches React bundle & assets from Vercel CDN.
• User signs in via Firebase Auth SDK in the client → Firebase Auth service.
• Authenticated client reads/writes user trip histories to Firestore.
• When generating an itinerary, client sends user preferences to Gemini AI API → receives plan back.
• Client augments the plan (e.g., hotel pricing) and optionally persists final itineraries in Firestore.
c. Architectural patterns & principles:
• Single-page client-driven architecture.
• BaaS (Backend-as-a-Service) using Firebase for auth + data.
• External microservice (Gemini AI) for specialized processing.
• CDN for static asset delivery (Vercel).
d. Key technologies:
• React + Vite – component rendering, routing, dev server.
• Tailwind CSS – utility-first styling.
• Firebase SDK – Authentication and Firestore CRUD.
• Gemini AI client library – plan generation API calls.
• Vercel – build & deploy pipeline for static SPA.
Key recommendations
• Be very detailed—capture each distinct service and interaction.
• Differentiate build-time (CI/CD → Vercel → CDN) from run-time (client ↔ services).
• Don’t over-abstract—list all four managed services and the SPA as separate nodes.