How nirmannext/nirmannext-website works
Project Type and Purpose
• This is a JAMstack full-stack web application: a modern, responsive marketing/site built with React (TSX), Vite, Tailwind CSS, hosted via Firebase Hosting, with a small serverless backend (Firebase Cloud Functions) for dynamic tasks (e.g., form submissions).
• Purpose: deliver a fast, easily maintainable static site (landing pages, ROI calculator, trust signals, etc.) while offloading dynamic logic (forms, data writes) to Firebase Functions and Firestore.
File Structure Analysis
• Top-level directories:
• src/ – React application (components/, pages/, hooks/, lib/, services/, data/)
• public/ – Static assets (robots.txt, index.html template)
• functions/ – Firebase Cloud Functions (Node.js entry point, package.json)
• Config files: firebase.json (hosting & functions), firestore.rules/indexes, tsconfig.*, vite.config.ts, tailwind.config.ts, ESLint configs.
• Patterns:
• Component-based UI (src/components/ui/*)
• Page routing via Vite/React Router or file-based imports in src/main.tsx → src/App.tsx → pages/*.tsx
• JAMstack: static build → CDN, dynamic calls → Cloud Functions + Firestore
README Insights
• Emphasizes static hosting deployment (Vercel, Netlify, Firebase Hosting).
• Build & dev scripts: npm run dev, build, preview.
a. Main Components
• Browser / Client (User’s device)
• CDN / Static Host (Firebase Hosting serving Vite-built assets)
• Frontend SPA (React + TypeScript + Tailwind)
• Serverless Functions (Firebase Cloud Functions)
• Database (Firestore)
• External Services (optional: Analytics, Email service, Payment gateway if used)
b. Relationships & Data Flow
1. User → Browser → requests index.html & static bundle (JS/CSS) from CDN
2. SPA loads: React components render pages (Index, Products, Contact, etc.)
3. User actions (form submits, ROI calculator) call REST endpoints on Firebase Functions via HTTPS
4. Functions perform logic (validate, write to Firestore, send emails)
5. Firestore stores/retrieves data on behalf of functions or direct client SDK usage (if applicable via src/lib/firebase.ts)
c. Architectural Patterns & Principles
• JAMstack separation: pre-built assets vs. on-demand backend.
• Component-driven UI (UI library in src/components/ui).
• Single Responsibility: services folder handles data fetching, hooks handle cross-cutting concerns, lib contains shared utils and Firebase initialization.
• Security: Firestore rules, functions restricted via firebase.json.
d. Key Technologies
• Frontend: React, TypeScript, Vite, Tailwind CSS, PostCSS
• Backend: Firebase Cloud Functions (Node.js), Firestore (NoSQL)
• Tooling: ESLint, Prettier, bun (lockfile), npm, Vite dev server