How pkm69/tourism-jharkhand works
Project type and purpose
• This is a full-stack monorepo for an interactive tourism platform (“Tourism-Jharkhand”).
• Frontend: Next.js 13 (app router), React components, SSR/SSG, client APIs under app/api/*.
• Backend: Node.js + Express REST API in backend/ (MVC pattern with controllers, routes, services, middleware).
• Database: MongoDB with GridFS for image storage.
• External integrations: AI/chatbot, Razorpay (payments), a simple blockchain service for provenance, mapping (GeoJSON).
File structure
• Top-level app/ → Next.js application source (pages, layouts, API routes, React components under components/).
• .next/ → build output (SSR chunks, static assets).
• backend/ → Express server:
• config/ (DB connection)
• controllers/ (business logic per resource)
• routes/ (REST endpoints)
• services/ (blockchainService, paymentService)
• models/ (Mongoose schemas)
• middleware/ (auth, error handling, upload)
• db/ and backend/scripts/ for seed data and DB initialization.
• components/, hooks/, lib/ for shared UI widgets, React hooks, and client-side service wrappers.
• public/ for static assets (maps, geoJSON).
Key README insights
• Platform features interactive maps, AR/VR previews, image management, search/filter, analytics.
• Tech: Node/Express, MongoDB/GridFS, Multer, Helmet/CORS.
• Execution: seed data, dev / production scripts.
Elements
• Clear labels for each component (e.g., “Next.js App”, “Express API”, “MongoDB/GridFS”)
• User → Next.js → API → Database
• Backend → External services
• Frontend → AI library
• Blue rectangles for application components
Summary:
• Tier 1: Next.js front-end (SSR + client components + built-in API)
• Tier 2: Express REST API (controllers, routes, middleware, services)
• Tier 3: MongoDB + GridFS data store