sudeepjoshi456/imageholidays

Purpose and entry points

Image Holidays is a full-stack Next.js car-rental catalog for a Nepal travel agency. It supports public vehicle discovery and agency contact, plus a single-admin fleet-management workflow; bookings, payments, and customer accounts are intentionally absent. The App Router root is src/app/layout.tsx; public routes are grouped under src/app/(public)/, while administration begins at src/app/admin/page.tsx.

Public catalog experience

Public pages render the home/search, vehicle catalog, vehicle details, agency information, and contact surfaces. Catalog and detail routes use slugs as the public vehicle identity:

• src/app/(public)/page.tsx

• src/app/(public)/cars/page.tsx

• src/app/(public)/cars/[slug]/page.tsx

Shared catalog presentation is split into cards, filters, galleries, and hero search components under src/components/CarCard.tsx, src/components/CatalogFilters.tsx, and src/components/CarGallery.tsx.

Domain and persistence boundary

PostgreSQL is the system of record, accessed through Prisma. The schema and initial migration define the data model, while seeding provisions the sole admin and sample fleet. Server-side data access and derived car presentation logic are centralized in library modules:

• prisma/schema.prisma

• src/lib/prisma.ts

• src/lib/cars.ts

Deployment requires a hosted PostgreSQL provider and Prisma migrations; Prisma 7 uses the PostgreSQL driver adapter at runtime.

Admin fleet lifecycle

The protected admin area provides fleet overview, create/edit forms, deletion, and photo management. Admin mutations are implemented as server-side actions/validation rather than a separate CRUD API layer:

• src/app/admin/cars/new/page.tsx

• src/app/admin/cars/[id]/edit/page.tsx

• src/components/admin/CarForm.tsx

• src/lib/actions.ts

• src/lib/validations.ts

The control flow is: authenticate admin → access fleet/dashboard → submit validated create/update/delete action → persist through Prisma → refresh rendered catalog/admin state.

Authentication and authorization

NextAuth credentials authentication gates the single-admin workflow. The catch-all auth route exposes NextAuth handlers, auth configuration lives in the library layer, and middleware protects admin routes:

• src/app/api/auth/[...nextauth]/route.ts

• src/lib/auth.ts

• src/lib/login-action.ts

• src/middleware.ts

Credentials are seeded/configured from ADMIN_EMAIL and ADMIN_PASSWORD; AUTH_SECRET and AUTH_URL support session security and deployment origin configuration.

External service boundaries

Vercel Blob is isolated behind the upload route used by admin photo management; missing credentials produce upload errors without preventing seeded remote-image demos:

• src/app/api/upload/route.ts

• src/components/admin/PhotoManager.tsx

The contact workflow is a server action that sends through Resend when configured, otherwise logs demo submissions server-side:

• src/components/ContactForm.tsx

• src/lib/actions.ts

Runtime and deployment

The application runs on Next.js 16, TypeScript, and Tailwind CSS, targeting Vercel (vercel.json). Required runtime configuration connects PostgreSQL, NextAuth, agency contact CTA values, and optionally Vercel Blob and Resend. Database evolution is represented by prisma/migrations/, with initial/demo state created through prisma/seed.ts.