Boise, Cooper Street
Mountain West, no folklore.
At lunch, a table that holds for ninety minutes. In the evening, a menu that follows the market and wines we fetched ourselves.
The kitchen
We cook what grows, swims or ripens within forty minutes' drive. That isn't a philosophy, it's the shortest supply chain we can get.
Lunch moves fast: three mains, one recommendation on the board, soup or salad alongside if you want it. Arrive at twelve, be back at your desk by half one.
Evenings take their time. The menu is short because every dish is started the same day. When something is gone it's gone — it says so on the board before you sit down.
The house
Outlines instead of photographs: this demo shows a made-up business, so there are no real pictures of it. Your own website would show your own shots here.
Guests
We come for the menu and stay for whatever Isla pours next.
Three courses at lunch and we still got the conversation done. That's exactly what client meetings need.
I had my nut allergy speech ready. The waiter knew before I opened my mouth.
A table tonight?
Book online until 5 pm; after that, call — by then someone is already standing at the pass.
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.
Something like this for your business?
This demo took a few days. Your real site gets your content, your brand and your inquiry flow.
See a different handwriting:Ashworth ElectricalWhitfield & PartnersPalmer Motor RepairsWheeler Kesteven ArchitectsThe Millpond PracticeWetherall Tool & SafetyUnit Nine TrainingRookhurst Fine FoodsRenshaw Machine PartsGreywick AtelierFoxbridge Farm MarketTradeCallIronvale Machinery ExchangeLinden House Yoga