Restaurant Sites
- Started
- Last post
- 5 Responses
- Chazolta
One of the latest projects on my plate is for a local restaurant. I've never done a restaurant site and kinda need a little inspiration. Got any ideas? ( No Chains Please. )
- gadg3tg1rl0
Here are Iron Chef Rob Feenie's restaurant sites (Vancouver, BC)
http://www.feenies.com/main.html…
http://www.lumiere.ca/
- kreydle0
http://www.porterstavern.com/ is nice
- harlequino0
Morimoto's NYC restaurant site is wacky 3D flash:
http://www.morimotonyc.com/*warning: browser resizing is involved.
- mg330
1. NO FLASH. EVER.
2. Make it responsive. Do not use some third party company that offers mobile restaurant this or that. Those sites are horrible, they use different urls than the main restaurant site, an inconsistent design, and require the restaurant owner to manage more than one set of content.
3. Also, make sure that the mobile versions are perfect. I have a theory that far more people view restaurant sites on a mobile device because they are looking for a place to eat NOW, and aren't at home on their computers. The site that is posted directly above, http://www.aquavit.org/dinner/, is awful on a mobile device when it comes to the menu. Too much pinching and zooming to see the menu.
4. NO PDF menus. Make the menu easily editable by whoever runs the website. PDF menus suck when you have to zoom in and out constantly to view it, because they're using a PDF of the actual menu that they print out.
The porterstavern.com link above lets me go to http://coquetteraleigh.com/eat-d…, which uses likely the same menu as their physical menus. It's horrible on a mobile device, and just as bad on a desktop.
5. Make sure that the SEO helps the website be found above quickly, and that there aren't other menu sites or listing sites for it appearing first.
6. Incorporate reviews.Wow... I only just realized this is an old post from 2008. Further proves my point though: for the most part restaurant sites are just as bad now as they were 6 years ago. True story.