Skip to main content

Platforms & products

Website rebuild on the new booking platform

In preview

We rebuilt the company's website so it shows inventory and prices straight from the new booking software, with no second copy to fall out of date. It is in preview and goes live with that software.

A full rebuild of a rental operator's website that owns no data of its own. Every item, price, and open date comes from the new booking platform's public API, and booking hands straight into the platform's checkout. It is in preview and goes live with the platform.

Client
Multi-location rental operator
Engagement
Design and build
Status
In preview
Discipline
Front-end engineering
What we built
  • Location & category pages
  • Live availability
  • Booking checkout
  • Event & guide pages
  • Outage fallback
Stack
  • Next.js 16
  • React 19
  • TypeScript
  • Tailwind v4
  • Framer Motion
  • Stripe embedded checkout

Before

The operator's current website runs on WordPress, with booking widgets from its current booking tool. With the new booking platform on the way, the website needed to be rebuilt on top of it: fast, organized around five locations, and showing exactly what the platform holds. The usual approach copies the catalog into the website, where it drifts. We built the site with no database at all, so it can only show what the platform says. The platform's catalog was loaded from the operator's current booking tool.

What made it hard

01

The site could hold no inventory of its own. Every item, price, and open date had to come from the platform's API, through a server-side client that keeps the key out of the browser.

02

Five locations, each with its own fleet, rules, and booking paths, had to sit under one design.

03

Search engines had to receive complete pages, so data renders on the server, not late in the browser.

04

If the platform is slow or down, renters had to see a clear message instead of a broken page.

05

The new site had to match the old one before it replaces it, page by page and price by price.

What we built

01

Built 33 page templates: home, location, category, and item pages, item booking, event and guide pages, blog, deals, a resource center, booking management, a customer portal, and legal pages, about 424 pages in all.

02

Connected every page to the platform's public API with no database of its own, and handed booking into the platform's checkout with Stripe embedded payments, an availability calendar, a held cart, and protection against double submissions.

03

Added a signed webhook so the platform can tell the site to refresh, and a six-second timeout that shows a clear outage screen instead of hanging.

04

Ran a parity audit against the live site, checking every production URL and every category price, and listed the gaps to close before switchover.

05

Rendered the full search surface on the server: sitemaps, structured data, and social images.

Results

33Page templates

About 424 pages in preview across five locations, each rendered on the server.

0Databases of its own

Everything a renter sees comes from the booking platform, so the site cannot keep a stale copy of its own.

155Live URLs checked for parity

A September 2026 audit compared every production URL and 58 category prices against the preview, and listed what to close before switchover.

Where it stands

In preview on a private address, hidden from search. The current website stays live until the booking platform switches over on January 1, 2027.