EMBER TABLE
FOOD & DRINKPAID
Restaurant website
A restaurant site has three jobs: show the food, show the room, and get the booking started. Everything else is decoration.
Most restaurant sites fail in the same place: a beautiful film on the home page, the menu three clicks down, and a phone number baked into an image that will not dial on a phone. Decide one thing before you start — what is the visitor most likely to want? Someone scrolling at seven in the evening wants to know whether there is a table tonight, not the brand story.
The Skills below build finished sites, not mockups: the menu is a real section, the photographs have places to sit, and the booking button is where a thumb can reach it. The photographs in the asset pack are stand-ins — swap in your own under the same file names and the layout stays put.
The AI cannot know your closing days, your minimum spend or which dish sold out, so every Skill here is told not to invent reviews, awards, addresses or phone numbers. Give it those yourself, and leave a gap rather than letting it guess.
FAQ
Enough for someone to decide whether to come, not the whole book. Three to six dishes per section with a line pointing to the full menu in-house is usual, and it is far easier to keep accurate when prices move.
The booking button can point at a phone number, a messaging app, a form or any booking service you already use. The site itself never takes the reservation and never collects the data.
Yes, but order them. Lead with your best shot of the room, then three to five dishes. Do not upload twenty photographs of uneven quality: one blurred image drags the whole page down with it.