Case study

Reservation — 2D plan reservations

Hierarchical real-estate model: master plan images, nested “small” projects, units positioned on front/back elevations—with availability states driving reservations.

Laravel Vite Tailwind Image plans

What it is

Staff upload plan assets and define boxes (coordinates, size) for units. Buyers or agents interact with the visual layer while the backend enforces states: available, reserved, sold. Guides cover admin usage and security for field rollout.

Architecture

Laravel owns persistence, validation, and transitions. Vite + Tailwind build the interactive front end (click/drag overlays, forms). The hardest coupling is between normalized tables (projects → properties → units) and pixel-perfect overlays on raster images.

Project (master plan image) └── Property (front/back images) └── Unit (x, y, w, h, view side, status) Laravel: REST/blade/live endpoints + storage for images Browser: Tailwind UI + JS for hit-testing / marking

Highlights

Visual UX maps directly to how sales teams think about inventory.
Laravel remains a solid place for rules, audit, and integrations.
Vite gives a modern front-end loop without a heavy SPA framework requirement.
Clear domain tree simplifies reporting per project.