How ealanisln/vet-family-23 works
Project type and purpose
• Vet Family is a full-stack web application for veterinary clinic management.
• Built on Next.js (App Router) + TypeScript, with a Prisma-powered MongoDB backend.
• Key domains: user & pet management, appointments, billing, reminders, multi-role admin panel, public site and blog (via Sanity).
File structure
• Top-level files: next.config.js, Docker Compose, Prisma folder (schema + migrations), Sanity config, scripts for DB sync.
• src/app: App Router pages split into route groups:
• (admin) – admin dashboard and POS system
• (main) – public customer portal (view/edit profile, pet info, booking)
• (contact) – blog and public pages
• api – Next.js API routes for auth, CRUD on clients/pets/inventory/pos, health checks
• components/ – reusable UI components organized by domain (Admin, POS, Inventory, Blog, etc.)
• lib/, services/, utils/ – data-access helpers, external integration code (mailer, Cloudinary, Kinde)
• prisma/ – ORM schema.prisma defining User, Pet, MedicalHistory, Appointment, Billing, Reminder, Staff models
• sanity/ – headless CMS for blog (schemas, client utilities)
README for additional insights
• Confirms tech stack: Next.js + TypeScript, MongoDB + Prisma, Sanity CMS, Kinde for authentication
• Summarizes domain models and relationships
• Lists major features (appointments, billing, reminders, multi-role support)
• Browser / Client (React + Next.js pages)
• Next.js Server (App Router + API Routes)
• Authentication Service (Kinde)
• Database (MongoDB via Prisma ORM)
• Headless CMS (Sanity)
• External Media Service (Cloudinary)
• Email Service (mailer.ts)
• Scripts / Cron Jobs (db-sync.sh, reminder emails)
• Client ↔ Next.js Server (SSR, CSR, API calls)
• Server → MongoDB (queries/mutations via Prisma)
• Server ↔ Kinde (auth flows, token validation)
• Server ↔ Sanity API (fetch blog content)
• Server ↔ Cloudinary SDK (upload/fetch images)
• Server → Email Service (send reminders/invoices)
• Cron/Script → Server → DB (sync/data-maintenance)
c. Architectural patterns & design principles:
• Monolithic “full-stack” SSR/CSR application using Next.js App Router
• File-system routing divides public vs admin UI
• Domain layering: UI components → actions/services → API routes → ORM → DB
• Dependency injection via lib/ and services/ for third-party clients
• Headless CMS decoupled from main DB
d. Key technologies & libraries:
• Next.js, React, TypeScript, Tailwind CSS
• Prisma ORM → MongoDB
• Kinde SDK for authentication
• Sanity headless CMS
• Cloudinary for image hosting
• Node mailer or custom mailer.ts for emails
• Docker Compose for local dev
Elements
• Orange for database
• Gray for external services
• Annotations for major route groups (/(admin), /(main), /api)