How jrg-one/finsage works
Project type and purpose
• This is a full-stack Next.js (v13 App Router) application for personal finance management: tracking income, expenses, uploading bank/receipt files (with OCR), generating insights/statistics, and user authentication.
• It’s bootstrapped with create-next-app, styled with Tailwind CSS, and integrates Firebase for auth (and likely for data persistence/storage).
File structure
• src/app ⇒ Next.js pages (account, login, register, dashboard, expense, income, statistics, upload-transactions, settings) and API routes under src/app/api.
• Each route (file-transaction, gemini, insight, ocr, stats/insights, stats/summary) is a serverless function (route.ts).
• src/components ⇒ reusable UI primitives (ui/), layout components, domain widgets (dashboard charts and tables, expense/income forms and lists, receipt uploader).
• src/context/AuthContext.tsx ⇒ React Context for managing user session.
• src/lib ⇒ core utilities: firebase.ts (initializes Auth & likely Firestore/Storage SDK), parseForm.ts, utils.ts.
• public ⇒ static files (404.html, index.html) and any static assets.
• Config files: next.config.ts, tailwind.config.js, ESLint/PostCSS configs.
• test/data ⇒ sample PDF and its text for tests.
Inspect the README for insights
• Confirms Next.js usage, development workflow, optimized fonts, and recommended Vercel deployment.