WhatWhereVacay

Travel tools where the URL is the share link and nothing is ever guessed at.

Type
Product
Industry
Travel / tourism
Platform
Web application
Role
Design, build, deploy
WhatWhereVacay destination guide page

What made this hard.

A travel planning platform: destinations and guides, hotels on an interactive map, flights and bus routes, a food and restaurants directory, and a set of free planning tools that work without an account.

Free travel tools are only useful if someone can hand them to a travel companion. The moment a packing list needs an account to share, it stops being used.

And entry requirements are the kind of content where being approximately right is worse than saying nothing: a stale visa fee presented confidently is a real problem for a real traveller.

What we built.

  • Made the packing-list generator deliberately stateless: all state lives in the query string, so the URL is the share link: no table, no token, no expiry, no sign-in. The rejected alternatives are recorded with the decision.
  • Inferred climate from a curated, versioned lookup (destination to zone, hemisphere and wet months, crossed with month to band, southern hemisphere shifted six months) rather than a live weather API, because a shareable URL shouldn't pay a network round trip on every open. Unknown destinations are explicitly never guessed at.
  • Built the visa and entry-requirements checker depth-first: one official government source per destination, seven entry-authorisation schemes documented with their official application URLs, every figure rendered with a CHECKED date so staleness is visible rather than silent, and undetermined pairs stated plainly instead of dressed up as guidance. An automated pass verifies the official URLs.
  • Shipped restaurant submissions as a one-shot unauthenticated flow with self-attested ownership and reCAPTCHA v3, rather than reopening the site's settled rule about who can log in, with three-state moderation, a confirm-and-resolution email loop, and the codebase's first public image-upload path.
  • Ran the redesign as a spec-first programme: design treated as visual spec only with Blade keeping all data and SEO wiring, tokens and shared chrome landed sequentially, then per-section work parallelised across disjoint view files with only the orchestrator touching shared layout and builds.
  • Enforced a per-section verification gate (unit tests green, live content check, desktop and mobile screenshots, functional smoke) with one commit per verified section.

What it runs on.

Chosen to be maintainable for years, not to win an argument on the internet.

  • PHP 8.2+
  • Laravel 12
  • Blade
  • Filament
  • Tailwind CSS
  • Vite
  • Leaflet / OpenStreetMap
  • Spatie Sitemap

Where it landed.

One product rule is enforced by the design itself: no fake urgency, no discount ribbons, no strikethrough pricing, because the data model has no such columns to draw them from.

A shared reCAPTCHA verifier was prefactored out only once duplication actually crossed the threshold, which is the habit we'd defend hardest: extract on the second real occurrence, not the first imagined one.

Need something in this territory? This is Custom web app development work. Start from all services or see pricing.

Your project

Tell us what you're building. We reply within two business days.

Hour Blocks from $180reply within two business days Start a project