Back to the websites

Example site for an entirely fictional business — not a real company.

Contact

Tell us.

Parties, vouchers, questions about the menu. For an ordinary table the booking form is faster.

Write to us

The more the form says, the shorter the call back. For parties, the occasion, the number of people and the timing help most.

This is a demo — the form does not send anything.

Opening hours

Tuesday to Friday
11:45 AM – 2:00 PM and 6:00 PM – 11:00 PM
Saturday
6:00 PM – 11:30 PM
Sunday and Monday
closed
Kitchen in the evening
until 9:30 PM
Phone
from 10:00 AM

The courtyard opens from April, weather permitting. We close on 24 and 31 December; dates for the holiday menus go on the card from November.

Sample hours

Whether the doors are open right now is something this demo deliberately does not claim — only the finished website can, with the real hours of The Tinderbox.

Getting here

SchematicNot a real map extract — a sketch of the location.

Address

The Tinderbox9 Cooper StreetBoise, ID 83702, United States

Buses 1, 3 and 5 to the Capitol, then two minutes on foot. Parking garage opposite on Main Street, cheaper evening rate from 6 pm. The dining room is step-free; two steps lead down to the courtyard — say the word and we'll move the table.

On the finished website, tapping the map opens the visitor's own maps app. This demo deliberately loads nothing from third parties.

Rather book straight away?

Live availability, confirmation the same moment.

The Tinderbox

Mountain West cooking in Boise. A short card at lunch, and an evening menu that follows the market.

© 2026 The Tinderbox · tinderbox-boise.com

Demo site — restaurant and content are fictional

The project frame

How Awelior would approach this project

The Tinderbox is invented — the way it is built is not. None of this is work delivered for a client. It is the shape we would give such a project — with the same depth, but without a client who would have to answer for it.

Where it starts

The Tinderbox cooks Mountain West food, a short card at lunch and an evening menu that follows the market. That is exactly where restaurant websites fail: the menu hangs there as a PDF from last autumn, the opening hours are wrong, and the booking leads to a phone number nobody answers during service. Three problems with one cause — the site was not built to be changed often.

Decisions

  • The menu is content, not a document

    Dishes appear as entries with description, price and labeling inside categories — not as a PDF. Only that way can the kitchen change it on a Tuesday, read it on a phone, and have it show up in a search.

  • Booking on its own page, with the honest note

    The booking flow stands alone and states at the end what the confirmation would look like in real operation. A booking button with no reply is worse than a phone number.

  • Large type, few elements

    A high-contrast archetype, plenty of space, short text. A restaurant sells an expectation, not a feature list — and anyone searching on a phone in the evening reads three sentences at most.

Deliberately left outNo delivery ordering and no third-party review stars. An embedded review widget pulls in foreign scripts and makes the site dependent on a platform free to change its rules whenever it likes.

What is in it

Pages
5
Content blocks
24
Languages
4

Five pages, in all four languages. Navigation, the menu categories, the gallery and the booking flow all respond. Indicated only: all food imagery, directions and the form target; the opening hours are sample values.

How it would go on

  • A table plan, not time slots

    A real booking needs tables, turn times, combinability and a place where somebody can say no. That is the difference between a calendar and a reservation system.

  • Keeping the menu current

    A login the kitchen uses to change the evening card without phoning us — including the allergen labeling that has to travel with every dish.

  • Pictures of the actual place

    Hospitality lives on imagery. Every guest recognizes stock photography, and it is the fastest way to lose trust before anyone has arrived.

Talk through your project