Matador
Burger and Steak House, Hove
Website design, Menu system, Booking, Copywriting
Hospitality
Five
Next.js
Live menu and booking
What was wrong
A restaurant doing genuinely good food on Church Road, represented online by a PDF menu and a third party booking widget on a page nobody wanted to look at.
How we read the brand
Food photography carries a restaurant site or nothing does, so the whole first screen is one long table shot at low light with the name set in a warm Didone over it. The menu became a real page rather than a download, which matters because a menu is the single most visited thing on any restaurant site, and the booking form was brought inside so the last step feels like the same restaurant as the first.
What it does now
A menu people can read on a phone in a queue, and a booking that happens on the restaurant's own site instead of somebody else's.
Every screen, as it really renders.
Captured from the live site at full width. Nothing here is a mockup or a flattering crop.
Home
The table shot, the name, and two buttons. Nothing else competes on the first screen.
Menu
The real menu, sectioned and priced, built to be read on a phone rather than pinched and zoomed.
Booking
Covers, date, time, and a note, kept to one screen because a table booking should take twenty seconds.
Our story
A decade of burgers told briefly, because the food photography has already made the argument.
On a phone
Most of the traffic to a site like this arrives on a phone, so the mobile layout is designed first and the desktop version follows it.
The same site at 430 pixels wide. Type resizes rather than shrinks, the navigation collapses into something you can reach with a thumb, and every image is served at a size that will actually load on mobile data.