Skip to content
UpHive
Back to project
Case Study · Booking & Tourism Website · Luxury & Tourism

Curve of Time Charters

A WordPress destination-marketing site for a British Columbia expedition charter operator, selling the experience of a converted 1959 vessel before the booking.

Website DesignWordPress DevelopmentWordPressElementor
https://curveoftimecharters.com/

Business

Expedition charter operator, British Columbia

Built

WordPress site with photography-led marketing and booking inquiries

Stack

WordPress, Elementor

Engineering focus

Image-heavy performance, seasonal content, inquiry-based booking

Why this project matters

Why this project matters

A premium charter experience is sold on atmosphere, not specs — the interesting problem is carrying large-format photography and video without slowing the site down, since a slow-loading "adventure" site undercuts its own pitch.

The business

Who this is for

Who they are

Curve of Time Charters operates expedition cruises along British Columbia's West Coast aboard a 12-passenger vessel — a former North Sea fishing trawler built in 1959, later used by Greenpeace, converted for eco-tourism in 1997.

What they do

They run multi-day expedition trips — Desolation Sound, the Broughton Archipelago, Gulf Islands, Grizzlies & Fjords — combining kayaking, Zodiac excursions, wildlife viewing and onboard dining.

Who they serve

Families, friend groups, corporate teams and adventure travelers seeking small-group, nature-based experiences.

Requirements

What the live site required

Not a wishlist from a kickoff call — what the delivered site visibly had to solve. Every requirement here is paired with the evidence that makes it true today.

Large-format photography and video without a slow-loading experience

Technical

The homepage runs an extensive photo carousel plus embedded YouTube video within a responsive layout with separate mobile and desktop logo variants.

A seasonal, date-driven rates structure

Content

"Dates & Rates" is a dedicated navigation item covering both 2026 and 2027 seasons, kept separate from the general expedition pages.

An inquiry-first booking path, not instant checkout

UX

"Reserve Your Expedition" and "Request a Reservation" buttons lead to booking forms rather than an e-commerce checkout — appropriate for a multi-day trip that needs a conversation before payment.

Engineering decisions

Why this stack, not just what stack

Every technology on this project was a specific answer to a specific problem — never a default.

  1. 01

    WordPress

    Chosen because the site is content and photography-driven with seasonal updates — new dates, rates, expedition details — the operator needs to manage without a developer each year.

    Trade-off — WordPress lets the operator swap photography and seasonal copy directly, but image performance still depends on what gets uploaded — the platform doesn't stop an oversized, unoptimized photo from being published the way a locked-down asset pipeline would.

  2. 02

    Elementor

    Chosen for the visual, image-forward homepage layout (hero, expedition previews, photo carousel) so seasonal photography and copy can be swapped without touching templates.

Key features

What the site can actually do

Expedition preview cards

Four named trips, each with its own description and call to action.

Photo carousel

Rotating gallery of wildlife, passengers and coastal scenery.

Booking inquiry flow

"Reserve Your Expedition" routes to a reservation request rather than direct checkout.

Seasonal rates pages

Separate "Dates & Rates" content maintained for the 2026 and 2027 seasons.

Implementation notes

What the finished build shows

Specific, verifiable patterns in how this project is put together — not a feature list, but how the pieces fit.

Pattern

Logo swaps at breakpoint rather than just resizing

The header uses distinct logo variants for desktop and mobile instead of one logo scaled down — a deliberate adjustment for a photography-heavy layout where header space is tight on small screens.

Content

Each expedition treated as its own product

Desolation Sound, the Broughton Archipelago, Gulf Islands and Grizzlies & Fjords each get a dedicated preview card and call to action, rather than being listed as line items on one shared tours page.

Navigation

Rates kept separate from the sell

"Dates & Rates" lives as its own navigation item, apart from the four expedition preview pages — pricing doesn't interrupt the photography-led pitch on the pages built to sell the experience.

Gallery

The live experience

Every screen, captured directly from the live site — desktop, tablet and mobile.

Homepage hero and expedition previews, desktop
Homepage hero and expedition previews, desktop
Photo carousel and testimonials, desktop
Photo carousel and testimonials, desktop
Homepage at mobile width (390px)
Homepage at mobile width (390px)
Homepage at tablet width (834px)
Homepage at tablet width (834px)
How this applies to you

How this project's engineering applies to your business

  • The image-forward, performance-conscious approach here applies to any experience-led business — hospitality, tourism, events — where photography and video carry the sale and a slow site actively undermines the pitch.

  • The inquiry-first booking pattern, rather than instant checkout, transfers to any high-consideration purchase that genuinely benefits from a conversation before payment, from consulting engagements to custom services.

The recap

If you remember four things

  • Photography-first, performance-aware

    Large-format imagery and video carried without the site feeling slow.

  • Seasonal content structure

    Dates and rates maintained as their own content area, updated year over year without restructuring the site.

  • Inquiry-based conversion

    Booking built as a conversation starter, matched to a multi-day, high-consideration purchase.

  • Editor-managed expedition content

    New trips and seasonal details addable without developer involvement.

Need a content-managed website?

Tell us about your project and current platform. You'll hear back from a senior engineer within one business day.