How khanhtrinh301103/nutrigen_bot works
Project Type & Purpose
• Full-stack web application (“NutriGen_Bot”) with a Next.js/React frontend, Firebase Functions backend, Firestore/Auth/Storage, plus a small GraphQL “dataconnect” microservice.
• User-facing features: recipe search, nutrition analysis, chat, blog posts, profile management.
• Admin UI: dashboards, analytics, user/chat/post management.
High-level File-Structure & Architectural Clues
Frontend (Next.js + Tailwind + Vercel)
– src/pages: page-level entry points (SSR/SSG)
– src/components & ui: reusable UI primitives (buttons, dialogs, cards)
– src/api: client wrappers for authentication (Firebase Auth), recipeService, chatService, blogService, adminAPI, etc.
Backend (Firebase Functions + dataconnect)
– functions/: Firebase Cloud Functions handlers (index.js registers HTTPS endpoints: searchRecipe, getRecipeDetails, uploadImage, chat, adminStats, etc.)
– dataconnect/: a small GraphQL microservice configured via connector.yaml + .gql files, used to fetch/enhance recipe data.
– src/: server-side business logic (recipeScorer, nutritionSearchProcessor, conflictDetector).
Infra config
– firebase.json & .firebaserc: Firebase project config
– vercel.json & next.config.mjs: Vercel/Next.js deployment
Key System Components
A. Clients
• Web browsers (Users & Admins) running Next.js pages (CSR/SSR)
• Components call frontend/src/api/* services under the hood
B. Presentation & BFF (Next.js)
• Page routes (e.g. /recipes, /profile, /adminUI)
• Server-side functions (getServerSideProps) & API routes proxying to Firebase Functions or direct calls to Firebase services
C. API Layer (Firebase Functions)
• HTTPS endpoints for recipes, nutrition profile, chat, image upload, admin analytics
• Invoke business logic in backend/src, call dataconnect GraphQL or external recipe APIs via public keys
D. GraphQL Microservice (dataconnect)
• Connector definitions + schema in backend/dataconnect
• Exposes a GraphQL endpoint that Functions can query/mutate for data enrichment or search enhancements
E. Authentication & Data Stores (Firebase)
• Firebase Auth for user identity
• Firestore for user profiles, chats, posts, search history
• Firebase Storage for uploaded images (chat photos, post images)
F. External Recipe/Nutrition APIs
• Called from Functions (getRecipeDetails.js, enhanceSearchRecipe.js) using public API keys
Interactions & Data Flow
1. User visits a page → Next.js SSR/CSR
2. Client calls a service in frontend/src/api → either Next.js API route or directly an HTTPS trigger on Firebase Functions
3. Firebase Function executes →
a. Optional: call dataconnect GraphQL endpoint for enriched search/queries
b. Optional: call external recipe APIs using public keys
c. Execute business logic in backend/src (scoring, conflict detection)
d. Read/write Firestore or Storage
e. Return JSON to frontend
4. Frontend displays results (recipes, nutrition profile, chat thread, dashboards)
Architectural Patterns & Principles
• “Backend-for-Frontend” with Next.js as both UI and API proxy
• Microservices in Functions & GraphQL “dataconnect”
• Separation of concerns: UI vs API vs business logic vs data layer
• Serverless & BaaS (Firebase Auth, Firestore, Storage, Functions)
• CI/CD via Vercel and Firebase CLI
Final Checklist
• Clear labels on each component (e.g. “Next.js SSR”, “searchRecipe HTTPS Function”, “dataconnect GraphQL”)
• Critical config points (firebase.json, next.config.mjs, public API keys)