Two builds static HTML and Next.js in one purchase

A tour operator site with a booking flow that actually works.

NOMADX ships the same 17-page site twice: plain static HTML with no build step, and a Next.js app with typed data and reusable components. The occupancy, deposit and balance logic is a working engine, not a mock-up.

See the demo What you get

one purchase · both builds · listing URL TBC

Pages, each build

HTML + Next.js

First load

0.74 MB

0.36 MB is photos

Accessibility

17/17

WCAG 2.1, both themes

Build steps, HTML

edit, upload, done

Live demo

One site, two stacks, both running

same content · same engine

17 pages · 0.74 MB first load · light and dark

Open HTML demo Open Next.js demo

Features

Ten things you can check before you buy

Every row carries the measured number behind it — nothing rounded up, nothing you cannot open the file and confirm.

A · Build and deliver

A booking flow, not a booking form

Age bands, party cap, deposit and balance date are computed by a real occupancy engine. Point it at your backend or run it as shipped.

occupancy engine included

Swap client content without a toolchain

The HTML build is edited in place and uploaded. No package install, no bundler, nothing new to learn the week a site is due.

0 build steps

The demo photography is in the download

Every photograph in the demo ships with credits recorded per file, so the site you hand over looks like the site you clicked.

CC0, credits included

B · Measured, all 17 pages

Accessibility measured, not asserted

Checked page by page in light and dark, so the conformance line in a client proposal is one you can defend.

WCAG 2.1 AA — 17/17

Two themes and a visitor panel

Light and dark ship as equals. The visitor accessibility panel maps each control to the named WCAG criterion it serves.

2 themes + a11y panel

A payload you can account for

First load is 0.74 MB and photographs are 0.36 MB of it. Swap in lighter imagery and you know exactly what you get back.

0.74 MB / 0.36 MB photos

C · What the files are like

Typed data and reusable components

In the React build, tours, departures and pricing are typed data files. Wiring a real API touches one layer.

typed tour + departure data

Source written to be read

Unminified and commented throughout, including the booking logic.

unminified + commented

One token file feeds both builds

Palette, type scale and spacing live in one place. Retune it and both builds change together.

1 source, 2 builds

The pricing agrees across both builds

The occupancy engine exists twice — ES5 and TypeScript — because it is control flow, not data. A test asserts the two return the same figures, so the React build cannot quietly drift.

16 cases + 6 rates

FAQs

Questions worth asking before you buy

Including the two this category tends to go quiet about: whether the photographs are really in the download, and whether the booking flow calculates anything.

10 answered

What do I get for one purchase?

Both builds. A static HTML site and a Next.js app of the same 17 pages, in one zip, under the single Envato licence you buy. There is no upgrade tier and no second purchase for the React build.

Can I use it for client work?

Yes, under Envato's Regular Licence — one licence per end product. If the end product charges its own users a fee, that needs the Extended Licence. Envato sets those terms, not us; the licence you choose at checkout is the one that applies.

Are the demo photographs really included?

Yes, and this is the question worth checking on any template you buy here. Every photograph in the demo is CC0 or public domain, ships in the download, and has its source recorded per file in CREDITS.md. Nothing in the preview is a stock image you would have to license separately.

Do I have to run a build?

Not for the HTML build. Edit a page, upload it, done — no package install and no bundler. Gulp, Vite and the Dart Sass CLI are all included if you want to work in SCSS, and none of them is required to serve the site. The Next.js build needs npm install, as any React project does.

Is the booking flow real or a mock-up?

Real. Age bands, the party cap, the single supplement, insurance, deposit and the balance date are computed by an occupancy engine you can read and change. Open the demo above and book a departure end to end.

Can I connect it to a real booking system?

Yes. Tours, departures and pricing sit behind one data layer — typed in the Next.js build. Replacing that layer with API calls does not touch the pages.

Which build should I start with?

Take the HTML build if you are delivering a site to a client on a deadline and want to swap content and hand it over. Take the Next.js build if you are wiring it to a backend or want components and typed data. Both are in the download, so this is not a decision you make at checkout.

What support and updates come with it?

Envato standard: six months of item support with the purchase, extendable at checkout. Support covers defects and questions about the template as shipped, not custom development for your project.

How accessible is it?

WCAG 2.1 AA is a stated commitment, not a bullet point. Text contrast is verified on all 17 pages in both light and dark themes against the computed cascade. There is a visitor accessibility panel whose controls each map to a named success criterion, and keyboard paths and focus states are part of the template rather than an afterthought.

Does anything break with JavaScript disabled?

The pages render and the imagery still paints — backgrounds come from a generated stylesheet rather than from script. The interactive parts, filtering, the booking calculator and the search overlay, need JavaScript, as they would in any build.