Hotel Website Template
Demo brand: MERECOMBE · Coastal house hotel · 17 routes · Astro 7 + Tailwind 4
Live preview
The demo is a full desktop site. Open it in a new tab ↗
About this hotel website template
A complete site for a small hotel: seventeen built routes covering five individual room pages, dining, a spa route, availability and booking, booking terms, privacy and a three-post journal.
Aged rose-clay lime plaster with one sea-glass accent, in Marcellus against Mulish. The whole house is finished in one hand-trowelled, isotropic plaster tooth, carried on every surface and pressed into every photograph. Texture is the loud channel; type, palette and motion are held quiet beneath it.
The signature move is the finish setting. A pinned, scrub-driven panel where scroll position is the cure of a fresh lime skim — a wet sheen recedes and the trowelled wall resolves from soft to matte as the coat carbonates. Beside it, the control: a lime-wash swatch that never burnishes, matte at every scroll position.
The 17 pages you get
- Home
/ - The plaster set-piece, the house above the cove, the rooms and the booking close.
- Rooms & rates
/rooms/ - The index with rates — the page that converts.
- Five room pages
/rooms/… - The Cove Suite, The Garden Room, The Harbour Double, The Lantern, The Snug. Each a full route with its own photography and rate, which is how a small hotel sells its best rooms rather than an average.
- Dining
/dining/ - The restaurant. For a house hotel this is half the reason people book and often a separate revenue line.
- The Bathhouse
/spa/ - The third revenue line, separately routed.
- Visit & availability
/book/ - A working enquiry form with a pre-filled mailto: fallback and a live tel:.
- Journal
/blog/ - A wired content collection — add an .mdx file and it appears here and in the sitemap.
- Three worked articles
/blog/… - The coast path in October, what the walled garden is giving, and why the whole house is finished in lime. Seasonal content that also earns off-season search.
- Booking terms & privacy
/terms/ · /privacy/ - Real legal routes — required once you are taking bookings and deposits.
- 404
/404 - Designed, not default. Keeps the navigation.
What is in the build
- A scrub-driven lime-plaster cure, from wet sheen to matte trowel, with a never-burnishing lime-wash swatch shipped beside it as the control
- One isotropic plaster tooth carried across every surface and pressed into all ten photographs, so interface and imagery share one material
- Five individual room routes with their own rates, which is how a small hotel sells the suite rather than the average room
- Separate dining and spa routes — the two revenue lines a house hotel most often under-sells
- Rooms, dining and rates as typed data in
src/data - Marcellus with Mulish, both self-hosted; a working enquiry form with a pre-filled mailto: fallback and a live tel:
- Vitest and Playwright suites included in the repository
The design decision
Every template in this catalog is loud in exactly one channel and deliberately quiet in the other three. That single rule is what stops 62 different worlds reading as one design system in different paint.
- The world
- Aged rose-clay lime plaster with one sea-glass accent. The whole house is finished in one hand-troweled, isotropic plaster tooth, carried on every surface and pressed into every photograph — texture is loud; type, palette and motion held quiet.
- The mechanic
- "The Finish Sets": a pinned, scrub-driven panel where scroll position is the cure of a fresh lime skim — a wet sheen recedes and the troweled wall resolves from soft to matte as the coat carbonates.
- Loud channel
- Texture
- Imagery. Pressed into wet plaster
- Type & palette
- Marcellus · Mulish
-
#6e4a3f#f6efe6#a6ddcf - The control case
- A lime-wash swatch beside it that never burnishes — same scrub, matte at every position. Drawn, not labelled.
Who it is for
Built for small hotels, guest houses, inns and boutique properties of five to twenty rooms. It suits a property whose material and location do the selling. For a venue hired whole for events, the event-location build is the right one; for a restaurant with rooms, this one already has the dining route.
Under the hood
- Astro 7 · static output, zero client framework
- Tailwind 4 · one @theme block holds the palette
- MDX content collections for the blog
- GSAP + Lenis for the scroll work, reduced-motion aware
- Self-hosted woff2 — no Google Fonts request
- Sitemap, canonicals and per-route meta wired
- Vitest + Playwright suites in the repository
- Zero third-party requests · strict CSP-ready
How to get started
- 01 Accept the repository invite and clone it.
- 02 Run
npm install, thennpm run dev. - 03 Replace the content in
src/data/with your own — that is where the brand, the copy and every list live. - 04 Swap the images in
public/images/and the palette in the@themeblock. - 05 Run
npm run buildand deploydist/anywhere static.
Questions
Does it connect to a booking engine?
Not out of the box. Every property already has a channel manager or booking engine, and the availability CTA is a link you point at yours. In the meantime the pre-filled enquiry path takes direct bookings, which are the ones you actually want.
Why give each room its own page?
Because a room grid sells the cheapest room. A page per room lets the Cove Suite have its own photography, its own rate and its own URL to send to someone — and it earns search for the room type rather than only the hotel name.
Will the plaster texture survive my own photography?
That is the design: the tooth is pressed into the images rather than sitting behind them, so a mixed shoot ends up sharing one surface. Replace the photographs and the material holds.
What exactly do I get for $49?
Access to a private GitHub repository holding the complete Astro source of this template — every route you see in the preview, the content model, the images and the tests. Updates arrive in that same repository.
How many sites can I build with one licence?
As many as you like, for yourself or for clients. The licence is per buyer, not per project. The one thing you may not do is resell or redistribute the source as a template, theme or starter kit.
Do I need to know Astro?
It helps, but the common case is editing content and colour. Content lives in typed objects under src/data, colour lives in one @theme block, and npm run dev shows the result. Deploying is a static folder — Cloudflare Pages, Netlify and Vercel all take it as-is.
Is anything loaded from a third party?
No. Fonts are self-hosted woff2, there is no analytics, no tag manager, no CDN script and no external CSS. The build ships static HTML under a strict Content-Security-Policy.
More travel & leisure templates
Vordergrat Seilbahn
Aerial cableway
Loud
Moving set-piece
Out of Season
Travel magazine / editorial quarterly
Loud
Display type
Postmarked
Travel journal
Loud
Texture
Marémont
Event venue
Loud
Display type