How brownie1100/finance_dashboard works
Project type and purpose
• This is a full-stack Finance Dashboard application.
• Frontend: a React/Next.js (TypeScript) UI with Tailwind CSS for building interactive financial views (expenses, income, goals, savings).
• Backend: a Spring Boot (Java) REST API with layered architecture (controllers, services, repositories) persisting to a relational database.
• Database: SQL scripts live in the Database folder.
File structure
• Top level:
• Dashboard-backend/financedashboard – Java/Spring Boot monolith.
• Dashboard-frontend/financedashboard – Next.js app directory structure with pages in app/(dashboard) and reusable UI components.
• Database/Scripts.sql – DDL/DML for schema and sample data.
• Backend layering:
• controller/ – REST endpoints (ExpenseController, IncomeController, etc.).
• service/ + service/impl/ – business logic interfaces and implementations.
• DBBean/ – Spring Data JPA repositories.
• entities/ – JPA entity classes (User, Expense, Income, Goal).
• Frontend conventions:
• app/ – Next.js 13 nested routes for dashboard, expenses, goals, income, savings.
• components/ – UI primitives and domain components (tables, charts, forms).
• hooks/ + lib/ – custom React hooks and utility functions.
• styles/, public/, package.json, next.config.mjs – styling, static assets, build config.
README for additional insights
• The README is generic CRA boilerplate and doesn’t reflect the actual Next.js setup; ignore or update it.
Packing the details
• Frontend’s folder decomposition: App Router (pages), components, hooks, lib.
• Build tools: Maven and NPM/PNPM as side annotations.