A system, in context.
A tourism platform for Puerto Vallarta, with experience discovery, reservation planning and an operational back office.
From discovering an experience to planning a reservation. One connected journey.

A tourism platform for Puerto Vallarta, with experience discovery, reservation planning and an operational back office.
A booking journey needs more than a beautiful catalog: dates, travelers, availability confirmation and payment state must remain connected.

Separate the public, statically rendered experience from authenticated account workflows. Keep monetary rules in a domain layer and reconcile test payments through server-side functions.
Product and frontend implementation, with booking workflows and backend integration represented in the repository.
View full screenshot (new tab) ↗
View full screenshot (new tab) ↗A visitor can move from the catalog to a reservation intent with dates, travelers and a visible test-payment state. Live payments and commercial adoption are not claimed.
The repository implements the catalog, booking intent, account shells and test-payment infrastructure. Live payments are disabled; catalog fixtures are marked as demo. No revenue or adoption claim is made.
Original schematic below. Not a production screenshot. Payment integration is test-only.
Payment success and confirmed availability are different states. The interface must communicate both explicitly.