How panduthegang/verifai-news_detection-system works
Project Type & Purpose
• Type: A single-page, front-end-centric, React-TypeScript application that leverages BaaS (Firebase) and external AI/ML services.
• Purpose: Provide AI-powered content verification and analytics (credibility scoring, bias detection, OCR, news monitoring) with multilingual support.
File Structure
• Top-level:
• public/: static assets, HTML, locale JSON
• src/: React app (pages/, components/, lib/, utils/, i18n/)
• config files: Vite, Tailwind, ESLint, Firebase
• Key directories:
• src/pages: Route-level React components (Home, Analysis, News, Social…)
• src/components: Reusable UI pieces, patterns, charts, chatbot, private routes
• src/lib: Firebase setup (auth.ts, firestore.ts), utility functions
• src/utils: Wrappers around AI & search APIs (geminiHelper, serperApi, imageAnalyzer, newsAnalyzer)
• No custom backend: all “server” functionality is via Firebase (Authentication + Firestore) and direct calls to external APIs using client-side keys (secured in Vercel env).
README Insights
• Frontend tech: React 18, TypeScript, Vite, Tailwind CSS, Framer Motion, Radix UI
• AI/ML: Google Gemini, OCR
• BaaS: Firebase Auth + Firestore
• External search: Serper API
• Deployment: Vercel (vercel.json)
Main Components & Their Relationships
a. Frontend SPA (browser)
• UI Layer: pages & components render views, handle routing (React Router)
• State & Theme: context providers (AuthProvider, theme-provider), i18n (i18next)
b. Data Access Layer (lib/)
• Firebase SDK wrappers → Authentication & Firestore queries
• Utils → format data, handle environment variables
c. External AI/ML Services
• Google Gemini API (via geminiHelper.ts)
• OCR engine (imageAnalyzer.ts)
• Serper search API (newsAnalyzer.ts, serperApi.ts)
d. Persistence & Hosting
• Firestore Database: stores user profiles, history, community feed, bookmarks
• Vercel: hosts static SPA, injects env vars for APIs
Architectural Patterns & Principles
• Component-based UI (atoms → molecules → pages)
• Separation of concerns:
• Presentation (components/)
• Business logic & API orchestration (utils/, lib/)
• Routing & page layouts (pages/)
• BaaS micro-services approach (outsourced Auth + DB)
• Client-driven API orchestration (calls from browser)