A restaurant website in Rome: menu, languages and groups

A restaurant site in Rome has to carry three audiences on the same page: residents looking for today's hours, visitors who want the menu in English, and someone booking for a group. If the form only takes tables of two or four, the third audience calls instead, and often does not call at all.

The local fact is population: 2,748,109 residents in 2023, read from Wikidata on 1 November 2026, in Roma Capitale, Lazio. It is the largest municipal figure in Italy: it sizes the resident catchment, not the visitor flow and not a quote.

Three audiences, three answers on one page

The resident wants three things: whether you are open, where you are and whether there is room tonight. The visitor also wants to know what they are ordering, so an English menu and honest dish photos. The group wants a quote with terms. A site that answers only the first audience loses two bookings in three, because groups and visitors decide before they call.

The pages you need

Menu and allergens: the page read at the table

Regulation EU 1169/2011 requires allergen information to be available before the order is placed, including for someone reading on a phone. Write the menu in HTML, one line per dish, price alongside, and the fourteen entries of Annex II on a per-dish card or in a table. A PDF gets no indexing, does not fit the screen and stays frozen at the last upload.

Booking: three fields, plus the form for groups

The menu has an English version with the same dishes and the same prices, not a summary. If enquiries come from one extra market, that is the second language to add: choose it on real requests, not on prestige. The rules for separate URLs and hreflang are in a multilingual website.

Costs are national, not Roman

A six or seven page site for a single venue sits in the low thousands of euro when copy, photos and menu arrive ready. With a photo shoot, translation and copy written from scratch the bill rises. Those are national ranges, published as such: our dataset holds no per-city prices, and a «Rome» figure would be an estimate with no source. The gap between the two ends is almost always what is included, not the code.

Three catalogue records

Table 01 from ephraimduncan is the table to fill with dishes, prices and allergens in both languages. Gallery 01 from Shadcn Space covers the photo grid of the dining room. The contact category is the widest choice for the booking form and for the group one. The licence is declared by the publisher and needs checking on each block; previews are free, the full code sits in the Pro plan.

The limitation to state up front

The catalogue holds React and Tailwind components: no booking engine, no table management, no integration with Google Reserve or with booking platforms. The site covers the interface, availability arrives from an external service. On WordPress these blocks do not install as they are: they work as a structural reference.

# la versione inglese esiste e dichiara hreflang corretto?
curl -s https://www.esempio.it | grep -o 'hreflang="[^"]*"' | sort -u

# il modulo gruppi risponde?
curl -s -o /dev/null -w "%{http_code} %{time_total}s\n" https://www.esempio.it/gruppi

# il menu è in HTML e non in PDF?
curl -s https://www.esempio.it/menu | grep -c "<li"

The full guide is a restaurant website, costs item by item in what a website costs, the venue's structured data in adding schema markup. The menu blocks already counted are in the best menu blocks.