Project description
We run a restaurant with two halls — a quiet one for family dinners and a larger one we let out for celebrations — and the site we have is years behind the kitchen. The menu lives there as one photographed sheet: unreadable on a phone, impossible to search, and out of date the week after the chef changes a sauce. Guests write to ask whether a dish is hot, or whether there is anything without meat, and every one of those questions is an answer the site should already have given.
We want the new site built phone first, because that is where people read us: on the way over, at the tram stop, at the table. The menu should be split into sections, and every dish should carry a photograph, its composition, the weight of the portion and the price, with clear marks for dishes without meat and for dishes the kitchen considers hot. Booking should let a guest choose the hall, the date, the time and the number of seats and send the request to us. We also need a banquets and events page, a gallery of both halls, and an electronic menu a guest opens from the table by a short code — and our administrator has to be able to edit all of it without calling a developer for a price change.
Three things we ask you to build honestly, because they are the ones that burn us in practice. The composition of dishes and the allergen warnings are written by our chef and updated whenever a recipe changes — the site must never invent or guess them, and it must be visible when a card was last edited. A booking is confirmed by our administrator: automatic confirmation without a check against the seating plan produces double bookings, and we would rather a guest wait ten minutes for a real answer than arrive to a taken table. And the photographs must be our own dishes, not stock pictures — a guest who comes for the image and is served something else does not come back, and tells others.
What we expect in the work:
— menu by sections: photo, composition, portion weight, price, marks for meatless and for hot dishes;
— booking with a choice of hall, date, time and number of guests, confirmed by a person;
— a banquets and events page with a request form and a description of both halls;
— a gallery of the halls and of the kitchen's work;
— an electronic menu opened at the table by a short code, with nothing to install;
— an admin area where our own staff edit the chef's texts, prices and photographs;
— a phone-first layout, checked on a real phone and not on a narrowed browser window.
We want the new site built phone first, because that is where people read us: on the way over, at the tram stop, at the table. The menu should be split into sections, and every dish should carry a photograph, its composition, the weight of the portion and the price, with clear marks for dishes without meat and for dishes the kitchen considers hot. Booking should let a guest choose the hall, the date, the time and the number of seats and send the request to us. We also need a banquets and events page, a gallery of both halls, and an electronic menu a guest opens from the table by a short code — and our administrator has to be able to edit all of it without calling a developer for a price change.
Three things we ask you to build honestly, because they are the ones that burn us in practice. The composition of dishes and the allergen warnings are written by our chef and updated whenever a recipe changes — the site must never invent or guess them, and it must be visible when a card was last edited. A booking is confirmed by our administrator: automatic confirmation without a check against the seating plan produces double bookings, and we would rather a guest wait ten minutes for a real answer than arrive to a taken table. And the photographs must be our own dishes, not stock pictures — a guest who comes for the image and is served something else does not come back, and tells others.
What we expect in the work:
— menu by sections: photo, composition, portion weight, price, marks for meatless and for hot dishes;
— booking with a choice of hall, date, time and number of guests, confirmed by a person;
— a banquets and events page with a request form and a description of both halls;
— a gallery of the halls and of the kitchen's work;
— an electronic menu opened at the table by a short code, with nothing to install;
— an admin area where our own staff edit the chef's texts, prices and photographs;
— a phone-first layout, checked on a real phone and not on a narrowed browser window.
Web development Cash, Bank transfer
