tour de wonder
A logistics platform for a company that ran on notebooks
client
Tour De Wonder, Kashmir travel agency
Role
Full-Stack Developer
Timeline
1 week
Platform
React
Built the agency's first website — houseboats on Dal Lake, trekking packages, hotel bookings, and vacation bundles — as a pure showcase site with no backend, routing every booking through WhatsApp by design.
There was no existing digital presence to migrate or fix — this wasn't a redesign, it was a first website from zero. That's a different problem than Printkul or Upkaar: no legacy system to replace, no bad data to clean up, no old workflow to respect. Just an agency that needed to exist online, built around packages — houseboat stays, treks, hotels, vacation bundles — that are inherently visual and destination-driven.
The same booking logic as Printkul applied here, for the same reason: travel packages get customized — dates, group size, add-ons — and the business closes deals over a phone call, not a checkout button. No backend, no user accounts, no payment integration. A frontend built to sell the trip, then hand off to WhatsApp to close it.
A destination-first site built around what actually sells a Kashmir trip: houseboats on Dal Lake, trekking routes, curated vacation bundles, hotel listings — presented the way a travel brochure would, not a generic template with stock photography swapped in.
Each package page is built to do the selling on its own — enough detail and imagery that a visitor arrives at the WhatsApp handoff already sold, not still asking basic questions.
Every booking path — houseboat, trek, hotel, bundle — resolves thesame way: a direct, pre-contextualized handoff to WhatsApp. No account creation, no cart, no payment friction standing between interest and a real conversation.
With no backend, the judgment calls live entirely in what to build and what to deliberately leave out.
No backend, on purpose — not as a limitation. A travel agency selling custom, negotiated trips doesn't need a database of listings with live availability — it needs a site that sells the destination and gets the visitor to a conversation fast. Building a backend, auth, and booking state machine here would have added real engineering cost to solve a problem the business didn't have. The discipline was in recognizing that "simple frontend" was the correct architecture, not a compromise.
WhatsApp as the actual conversion point, not an afterthought link. The temptation on a travel site is to build a booking form that collects details and emails them somewhere. Instead, every path — houseboat, trek, hotel — was designed to end in a pre-filled WhatsApp message, matching exactly how the agency already closes deals. The site's job is to get someone interested and informed; the agency's job, unchanged, is to close.
Visual-first package presentation over generic listing cards. Kashmir sells itself on imagery — Dal Lake, the trek routes, the houseboats. A dense, spec-sheet-style listing grid (common on budget travel templates) would have undersold the product. Each package got built as its own visual moment rather than a row in a table.
