Destination & trip websites
Main-brand pages and dedicated Israel and Seven Churches experiences with destination photography, itinerary content, pricing, brochures, galleries, and reservation entry points.
Travel platform / reservations / custom CMS
Holy Land Encounters
06 / 11A multi-trip travel platform connecting destination storytelling, trip content, reservations, payment workflows, customer accounts, and a custom administration system.
Main website: a shared brand and entry point into the destination experiences.
THE BRIEF
What the project
needed to do.
This project needed more than a travel landing page. Each departure has its own dates, itinerary, pricing, images, payment schedule, and registrants. The public experience needed to make a journey understandable, while the team needed practical tools to maintain trips and manage the resulting reservations.
MY APPROACH
Connecting the design
with the work.
I worked across the customer-facing experience and the operational platform: a main brand website, dedicated trip experiences, reusable trip content, a staged reservation flow, and administrative tools. The project spans PHP and Flutter work with a shared Firebase foundation and external payment and email connections.
PROJECT SCOPE
The work in detail.
Configurable trip model
Per-trip settings for hosts, dates, destinations, sections, prices, payment schedules, publication state, and reusable itinerary content.
Reservation experience
A staged flow for traveler details, review, payment, and account continuation, with reservation records kept distinct from payment records.
Payments & accounts
Stripe checkout and payment-intent integration, customer account paths, and server-side payment-event handling.
Custom administration
Tools for trips, reusable templates, destinations, galleries, registrants, payments, uploads, and CSV exports.
Email & audience systems
Transactional notifications, email-list integration, and additional signup flows supporting the wider travel and content relationship.
THE EXPERIENCE
How the pieces connect.
- 01
Explore
Find a destination and review the trip details.
- 02
Reserve
Provide traveler information and review the reservation.
- 03
Pay
Continue through the trip's configured payment process.
- 04
Manage
Keep reservations, payment records, and trip content available to the team.
01 / PROJECT DETAIL
A platform built around the trip, not a duplicated page.
Trip content is modeled as structured information: dates, departure details, price, deposit, payment schedule, hero media, brochure, destinations, itinerary, galleries, and section choices. Reusable templates support material that should remain consistent across related departures.
The implementation includes hostname-based trip resolution and shared services, allowing destination experiences to have their own public entry points while using common operational infrastructure. That reduces the need to maintain unrelated copies of the same system.
02 / PROJECT DETAIL
A distinct visual experience for the Holy Land.
The Israel trip gives one journey its own visual presentation within the wider HLE platform. Large destination photography, host and departure context, location cards, and a day-by-day itinerary help a visitor move from interest into the practical details. The page also brings brochures, trip video, a guidebook invitation, and gallery imagery into the same experience.
The itinerary uses expandable daily sections rather than an uninterrupted wall of travel copy. Persistent navigation keeps trip information, pricing, brochure access, and the deposit path within reach. The portfolio includes public captures of the hero, destinations, and itinerary; the live trip remains the source for current dates, pricing, and availability.
03 / PROJECT DETAIL
Reservation and payment are separate events.
A submitted reservation and a completed payment are not the same thing. The source keeps those stages distinguishable and includes server-side payment-event processing, event deduplication, invoice records, and reservation status updates.
The reservation interface also accounts for different trip payment models, including configured deposits and installment schedules. Those settings belong to the trip record, so pricing and payment instructions can vary by departure without requiring a separate reservation application for each one.
04 / PROJECT DETAIL
Administration is part of the product.
The admin surface includes trip editing, destination and itinerary templates, media uploads, photo ordering and captions, registrant tables, payment tables, and exports. Authentication and administrative permissions protect the operational tools.
The platform source also includes audit records and soft-deletion patterns that preserve related reservation and payment information. These are the less visible details that let a public website support a real ongoing operation.
SELECTED SCREENS
A closer look at the work.
HAVE SOMETHING IN MIND?