Manamanee — one page that answers every question a venue gets asked

The problem

A venue outside the city loses bookings to questions it never gets to answer. How big is the room. What does it cost. Is there food. Can we stay the night. How far is it, really. Every one of those was a phone call or a Facebook message, answered by hand, during business hours — and the people asking were usually deciding between two venues on a phone in a car park.

The venue is also four businesses in one place: day desks, seven meeting rooms, a restaurant and overnight rooms. A visitor who only finds the coworking half books somewhere else for the other half.

What we built

One page, in the order people ask. Rooms first, then price, then the reviews and the FAQ that close the decision, then how to get there. No navigation to learn and nothing behind a click — the whole answer is one scroll, which is how a page gets read on a phone.

Every room shown, not described. All seven rooms carry their own photography and capacity, so “the big one” stops being a phone call. Prices are on the page rather than “contact for quote”, with the entry figure stated up front.

The FAQ is the call log. The questions the venue already answers most often, written down once. A question that reaches the page stops reaching a person.

How it is built

Astro, so the page is HTML. The whole site ships as static markup with no client framework and no hydrated island on it — a venue page has nothing to hydrate, and the visitor is on mobile data outside the city. Images go through Astro’s own pipeline to WebP at several widths, which is where nearly all the weight of a photography-led page would otherwise sit.

Structured data, because this is a local search. LocalBusiness, opening hours and geo coordinates are published as JSON-LD, so the venue’s hours and location come back in the search result itself rather than depending on a click. For a business people find by searching a district name, that markup is not decoration — it is the listing.

Static on Vercel, behind Cloudflare. Nothing to run, nothing to patch. The site is files at an edge, which is the correct amount of infrastructure for a page that changes when the prices do.