How navuluribalaji/ai-inventory works
Project type and purpose
• Frontend: React + TypeScript + Tailwind CSS (SPA served via Vite)
• Backend: Node.js + Express (newsletter endpoint, plus MongoDB integration for data persistence)
• Database: MongoDB (user subscriptions, potentially news or model metadata)
• External Services: Email/SMS provider via Nodemailer, optional news‐API
File structure
• Top‐level:
• package.json / lock: Node deps
• vite.config.ts, tsconfig*.json, tailwind.config.js, postcss.config.js, eslint.config.js: build/tooling
• index.html + public/: static assets (robots.txt, sitemap.xml, ads.txt)
• backend/ newsletter.js: Express route to accept newsletter signup & send email
• src/: React app
– src/main.tsx → React entry point
– src/App.tsx → root component
– src/components/: UI widgets (SEO, cards, footer, newsletter form, etc.)
– src/pages/: route components (Home, CategoryPage, ModelDetail, Terminology)
– src/data/models.ts: static model data
– src/utils/seo.ts: SEO helper functions
– src/types/: TypeScript types
• The split between “backend” folder and “src” clearly indicates a two-tier separation: browser app vs. REST API.
README for additional insights
• Confirms the architecture: React SPA + Express API + MongoDB + Nodemailer