Hospitality website · Product concept
Dalisara
A cinematic resort experience that becomes calmer and more precise as visitors move toward booking.
Dalisara is a self-initiated, fictional hospitality concept, not an operating hotel or client engagement. Availability and pricing are deterministic simulations. No reservation, payment, or hotel enquiry is created.
- Role
- Product design, UI/UX, visual direction, front-end
- Product
- Fictional hospitality website concept
- Scope
- Discovery through simulated booking
- Technology
- Next.js, React, TypeScript, CSS Modules
What to notice
The live product is the primary proof.
- Route-specific art direction gives discovery, place, dining, and accommodation pages distinct jobs without breaking the visual system.
- Five accommodation categories make setting, capacity, spatial character, and price easier to compare.
- A six-stage simulated booking journey moves from availability to confirmation with deterministic pricing and explicit truth boundaries.
- Responsive composition, reduced motion, accessibility checks, and constrained client JavaScript shaped the production implementation.
Interactive experience
Explore the website at your own pace.
Navigate the real production interface, compare its desktop, tablet, and mobile behavior, and enter the simulated booking flow without leaving this portfolio.
Build note
Expressive early, literal when choices matter.
Discovery routes use photography, spatial pacing, and restrained motion to establish place. Accommodation comparison introduces practical differences earlier, while booking removes spectacle in favor of validation, running totals, and recovery.
The implementation is static-first and uses a typed booking domain. Reduced-motion behavior, keyboard paths, responsive reflow, security headers, and cross-browser regression were treated as product requirements rather than release cleanup.
That progression lets early routes create desire while keeping consequential states understandable. A shared content model preserves consistent facts without forcing every route into one visual template.
Continue