Command Palette

Search for a command to run...

Case study

Multilingual Tour Booking Platform

Multilingual tour booking for international travelers — filter, request, pay.

Role
Frontend Developer
Period
04.2025 — 06.2025
Stack
WordPress (Headless CMS) · REST API · GSAP

Private client project

This is anonymized client work. The brand, live site, and visuals are covered by an NDA — reach out and I'll walk you through the details, the decisions, and the results.

Contact to discuss this project

Filter UI demo

Try the filter rail

  • Highland loop3d · $420
  • Coastal escape5d · $680
  • Delta discovery2d · $310
  • Mountain trek4d · $540

Anonymized demo — no client branding or live inventory.

Overview

A personalized tour platform with destination/date/duration/budget filters, custom tour requests, payment-gateway checkout, and EN/ZH support for international guests.

Interface sketch

Interface sketchWireframe · NDA-safe
ENZH
→Locale switch
→Filter + detail

The problem

01

International travelers need confidence in language, pricing, and availability. A brochure site can't carry filters, custom requests, and payment without a real product architecture.

Approach

02
  • Next.js UI from Figma with motion
  • Headless WordPress CPT/ACF → REST
  • Tour filters + custom request flows
  • Payment gateway + booking forms
  • Performance (CWV-minded) and multilingual support

Key decisions

03
  • Multilingual as a product requirement, not a plugin afterthought
  • Reuse the earlier tour-booking lessons with payment gateway differences
  • Optimize for mobile networks common to traveling users

Impact

Lab / shipping

LCP

1.5s

Mobile lab

Mobile lab on a production-like build — client URL stays private.

Locales

EN/ZH

International guests

Tour filters

4

Incl. budget

LCP

1.5s

Mobile lab

Checkout

1

Payment wired

Before / after

Lab mobile scores from a production-like build — client URL stays private.

Before

Performance62

LCP 4.8s

After

Performance96

LCP 1.4s

Outcomes

  • Filterable tour discovery with custom request support

  • Payment-gateway-integrated booking path

  • EN/ZH experience with stronger performance baselines

Technologies

  • WordPress (Headless CMS)
  • REST API
  • GSAP

Architecture

How the build is wired. Client UI stays off this page — names, logos, and screenshots are covered by NDA.

  1. 01EN/ZH copy
  2. 02Next.js
  3. 03WordPress REST
  4. 04Filters
  5. 05Checkout

Need a multilingual booking product for guests who don't share one language?