JustStart.now

Winery Website Template

Demo brand: MARLEDON ESTATE · Winery / vineyard estate · 23 routes · Astro 7 + Tailwind 4

Live preview

Winery Website Template — the MARLEDON ESTATE homepage

The demo is a full desktop site. Open it in a new tab ↗

About this winery website template

A complete website for a wine estate or vineyard: a wine shop with eight product pages, tasting and tour booking with a live availability calendar, a wine club with a case comparison, the estate story, a vintage-notes journal, an FAQ and a contact form that fills itself from every button. Twenty-three built pages, all driven by content files.

It looks like a cellar door on a bright day. Chalk-white pages and white cards, one dark cellar band over oak, real vineyard, harvest, barrel and poured-glass photography carrying the colour, and one claret accent. Gilda Display for headings, Raleway for everything else.

Every section answers what a visitor or buyer wants to know: which wines, what they cost, when you can visit, what a tasting includes, how fast delivery is and what the club saves. The booking calendar and the club table do that on the page. Motion is one quiet reveal.

The 23 pages you get

Home /
Centred headline over a vineyard panorama, a "this week at the cellar door" strip, promises, featured wines, the chalk story band, the year on the slope, the booking widget, club tiers, visitor notes, journal and FAQ.
Wines /wines/
All eight wines grouped by style (sparkling, white, rosé, red), with price, tasting notes and an order button.
Wine pages /wines/…/
Eight wines. Gallery, price, tasting notes, stock status, order a bottle or six, palate, food, how it is made, a visitor quote and related wines.
Tastings and tours /visit/
Three experiences with prices and what is included, the booking calendar, directions, opening hours and visiting questions.
Wine club /club/
How the club works, a three-tier case comparison with price per bottle, member benefits and club questions.
The estate /estate/
The chalk, a short history timeline, the people (no face photos) and the farming numbers.
Journal /journal/
One lead article and a grid. Add a Markdown file and it appears here.
Articles /journal/…/
Four written pieces: a veraison report, a harvest report, why chalk matters and how to serve sparkling wine.
FAQ /faq/
Open questions and answers under Visiting, Buying and Club.
Contact /contact/
One form for bookings, orders, club, groups and trade, showing the right fields for each and pre-filled from any button on the site.
Privacy and terms /legal/…/
Starter privacy policy and terms of sale and visits on a shared layout.
404 /404
Designed, with a way back to the wines.

What is in the build

  • Tasting and tour booking: experience, a two-month calendar with fully booked days struck out, time, guests and a live total, handed to the contact form
  • Availability in one JSON file: add a date to mark it full, remove it to reopen
  • Wines as content: price, style, tasting notes, food, stock and gallery in one Markdown file per wine, with an optional payment link
  • A wine club comparison table that stacks cleanly on phones
  • A "this week at the cellar door" strip worked out from the same booking data
  • Real vineyard and cellar photography with no labels or faces, optimised to AVIF and WebP by Astro
  • All estate details in one file, and one accent colour that rebrands the whole site
  • Vitest and Playwright suites included

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 65 different worlds reading as one design system in different paint.

The world
Chalk-white ground with white cards and one dark cellar band, Gilda Display over Raleway, real vineyard, harvest, barrel and poured-glass photography, one claret accent.
The mechanic
Tasting and tour booking with a two-month availability calendar (fully booked days struck out), time, guests and live total pre-filling the contact form, plus a wine shop of eight wines and a three-tier wine club table. Motion is one quiet reveal.
Loud channel
Imagery
Imagery. Vine rows, harvest hands, barrels, unlabelled pours
Type & palette
Gilda Display · Raleway
#f8f6f1 #211a1d #6b1d3a

Who it is for

Built for vineyards, wineries and wine estates with a cellar door, and a good fit for cideries, breweries, distilleries or farm shops that sell bottles and book tastings or tours. It suits a business that earns from visitors as well as from the shop, and wants a club or subscription on the side.

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

  1. 01 Accept the repository invite and clone it.
  2. 02 Run npm install, then npm run dev.
  3. 03 Replace the content in src/data/ with your own — that is where the brand, the copy and every list live.
  4. 04 Swap the images in public/images/ and the palette in the @theme block.
  5. 05 Run npm run build and deploy dist/ anywhere static.

Questions

How do I mark a day as fully booked?

Add the date to data/availability.json under the experience. It is struck out on the calendar at the next build. Weekly opening days, times and prices live in src/data/booking.ts.

Can I take payment for wine?

Add a checkoutUrl to a wine file with a Stripe Payment Link or a Shopify Buy Button URL and the order button goes there. Without one, it opens the contact form with the wine pre-selected.

Where do booking requests go?

"Request this booking" opens the contact form with experience, date, time and guests filled in. The form posts nowhere by default: point it at your form backend, or link the button to your booking tool instead.

Can I use the photographs?

Yes. They are from Pexels, which allows commercial use, and each one is listed in LICENSING.md. None shows a wine label, a brand or a recognisable face.

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.