The Weinland map, where the wine comes from.

Wine is origin. Buy a bottle from Naoussa and you are buying the soil, the climate and the slope — and all of that disappears when a region is just a word in a filter menu. The Weinland map at /weinland turns abstract names into a place you can point to.

Why a map matters for a wine merchant

Trust in the wine trade begins with origin. A customer who can see where an estate sits — on a hillside, by the coast, in the north or out on an island — understands the bottle differently before the first sip. The map sells nothing directly. It does something more important: it makes the story behind the catalogue visible, and it gives the customer a reason to stay.

That is why the Weinland map is not a gimmick tucked into a corner but a page of its own. It covers the Greek wine regions across the country and arranges the wineries geographically instead of burying them in a list. Someone looking for “something from the north” finds it with a finger rather than a search box.

The engineering: Mapbox GL and regional clusters

The map runs on Mapbox GL JS. Each winery sits as its own marker. With many markers in a tight space, a naïve build would produce an unreadable cloud of needles. So the map uses regional clustering: pins that sit close together collapse into a single cluster and only open up as you zoom in.

That is not only prettier, it is faster. Instead of drawing and moving dozens of markers at once, the map renders grouped clusters — the interaction stays smooth as the customer pans and zooms. Mapbox GL’s vector tiles and GPU rendering do the rest: the map feels like an app, not an embedded picture.

Mobile first, not mobile as an afterthought

Most wine browsing happens on a phone, in the evening, on the sofa. The map is fully responsive — clusters, markers and tapping through to a winery work as well with a thumb as with a mouse. There is no second, stripped-down mobile version that quietly drops features. It is the same map, adapting to the screen.

Consent done right: the click first, then the script

Where Google Maps is used near the map, it loads only after a clear two-click consent. Before the customer agrees, not a single Google script runs — no silent third-party connections, no data leaving behind the visitor’s back. That is the lawful way to embed a map, and at the same time the decent one.

The rest of the page stays true to that line. CAVA measures with Vercel Analytics — cookieless. There are no tracking cookies, only technically-necessary ones. A map need not be the point where a shop loses its privacy discipline. Here it is not.

What the map ultimately does

A good origin map does three things at once: it builds trust, because it shows that a real place stands behind every bottle; it keeps the visitor longer, because exploring is enjoyable; and it leads back to the catalogue, because the route from any winery into the shop is short. Performance, clustering and consent are not separate topics — they are three faces of the same care.

— Dimitrios