Travel & hospitality website templates
Five complete websites for travel and hospitality, built in Astro 7 and Tailwind 4 — a coastal house hotel, a private events estate, a travel quarterly, an alpine cableway and a travel journal. Each is a finished site: individually routed rooms or articles, a booking or enquiry path, seasonal content, and the booking terms a property taking deposits needs.
Every business shown is invented and the demos are the templates themselves, running. You buy the source through private GitHub access, change the copy, and deploy it anywhere static. One licence covers unlimited sites, your own or a client's. $49 each, or all 62 templates for $199.
- In this set
- 5
- Each
- $49
- Sites per licence
- Unlimited
- Third-party requests
- 0
The 5 builds
Each is loud in exactly one channel — display type, palette, a moving set-piece, texture or the imagery — and deliberately quiet in the other three. That rule is what stops a set like this reading as one layout in different paint. Click any of them to read the build in full and open the live demo.
MERECOMBE
Coastal house hotel
Loud
Texture
Marémont
Event venue
Loud
Display type
Out of Season
Travel magazine / editorial quarterly
Loud
Display type
Vordergrat Seilbahn
Aerial cableway
Loud
Moving set-piece
Postmarked
Travel journal
Loud
Texture
What travel & leisure sites have to carry
Every build in this set ships all of it. It is the difference between a template that looks finished and one that is.
- 01 A page per room, venue or destination
- Five rooms with their own rates and photography, twenty-five magazine routes, eight stations. A room grid sells the cheapest room; a page per room sells the suite and earns search for the room type.
- 02 The practical page
- Getting there, timetables, wind holds, travel and stay. The page that absorbs most of a property’s inbound questions and that almost every travel site treats as an afterthought.
- 03 A second revenue line, routed
- Dining and a bathhouse on the hotel. Accommodation on the venue. A print edition on the journal. These are the lines that turn a day rate into a weekend and a reader into a customer.
- 04 An enquiry path that captures the detail
- Pre-filled mailto: paths that arrive with the date and guest number already in them, plus a live tel:. No booking engine is wired in — every property already has one, and the CTA is a link you point at yours.
- 05 Seasonal content that earns off-season search
- The coast path in October. The Faroes in November. What a wind hold actually is. Written articles that work when the property is quiet, which is exactly when you need them.
- 06 Photography under one treatment
- Warm dusk and split, pressed into wet plaster, one underexposed grade. A property shot across three seasons by three photographers ends up reading as one commission.
What every build includes
- Astro 7 · static output, no client framework
- Tailwind 4 · one @theme block holds the palette
- Content in typed files under src/data
- MDX blog collection, wired to the sitemap
- Self-hosted woff2 — no Google Fonts request
- Zero third-party requests · strict CSP-ready
- Vitest + Playwright suites in the repository
- Designed 404, sitemap, canonicals, per-route meta
- Private GitHub repo access, with updates
Questions
Does any of these connect to a booking engine?
No, deliberately. Every property already has a channel manager or booking provider, and hard-wiring one in would date the template. The availability CTA is a link you point at yours; meanwhile the pre-filled enquiry path takes direct bookings, which are the ones you actually want.
Which one for a B&B or guest house?
The hotel build. It is designed for five to twenty rooms, with separate dining and spa routes you can delete if you do not have them. The events estate build is the one for whole-property hire.
I run tours, not a property.
The cableway build is the closest — timetable, tickets, operating status, safety. It is built for a lift-served operation but the structure is any scheduled attraction’s, and it reads as infrastructure rather than as a booking widget.
What is the difference between the magazine and the journal?
Scale and intent. The magazine is a masthead: twenty-five routes, two content types, an FAQ section, built for a publication with contributors. The journal is a personal record — seven routes, a scrapbook register, and a print edition to sell.
Can I use one template for several client sites?
Yes. The licence is per buyer, not per project — build as many sites as you like, for yourself or for clients. You may not resell the source itself as a template or starter kit.
Other sets
All 62 templates, $199
Every template here plus every future one, delivered as private GitHub repository access with updates. Single templates are $49 each — the 5 on this page alone are $245 bought separately.