How che3sy/face-it works
Project type and purpose
• Face‑It is a full‑stack financial management web application built on Nuxt.js (Vue 3). It provides a client‑side UI for tracking transactions, analytics, reporting, and AI‑powered tips, and a server‑side layer for data persistence, AI integration, and PDF generation.
File structure
• Top level:
• nuxt.config.ts, pages/, components/, composables/, stores/, assets/, public/, server/
• Frontend:
• pages/ defines routes (login, dashboard, reports, analytics)
• components/ contains reusable Vue UI elements and page‑specific components
• composables/ holds business logic (fetch financial data, regression analysis, AI tips, PDF generation)
• stores/ (Pinia) holds shared state (dateRange, triggers)
• assets/, public/ static files, Tailwind CSS config
• Backend/API:
• server/ likely holds API endpoints (server/api) and server‑side logic
• server/tsconfig.json indicates TypeScript support for server code
README for technical stack
• Nuxt.js (Vue 3 SSR/SSG)
• Tailwind CSS + shadcn components for styling
• Pinia for state management
• @google/generative-ai for AI tips
• PDF generation (useGenerateReportPDF composable)
• @unovis/vue, @tanstack/vue-table for charts/tables
• No explicit DB mentioned—assume a database layer behind server endpoints
Main components & interactions
a. Frontend (Browser)
• UI Layer: pages/, components/ (shadcn UI primitives + custom charts)
• State Management: Pinia stores
• Business Logic: composables (financial data fetch, AI tips, PDF gen)
• Routing: Nuxt pages (client and server‐side capable)
b. Server/API Layer (Nuxt Server / Node.ts)
• REST or RPC endpoints under server/ (CRUD transactions, fetch/persist data)
• AI Integration: calls Google Generative AI via @google/generative-ai
• PDF Service: generates and returns report PDFs
• Data Persistence: calls database (Postgres, Mongo, or other—add actual tech)
c. External Services
• Google Generative AI service
• (Optional) Authentication provider, Data storage provider
d. Database
• Transaction store, user profiles, analytics data
Architectural patterns & design principles
• Modular folder structure: separation of UI components, pages, state, and business logic
• Composition API + composables for reusable logic
• Pinia for centralized state management
• Layered architecture: Presentation (components/pages) → Application Logic (composables/stores) → API (server/) → Data (DB/External)
• Use of shadcn fosters design consistency; Tailwind for utility styling