|
|
| (2 intermediate revisions by 2 users not shown) |
| Line 1: |
Line 1: |
| − | ==Restaurant Guide==
| + | #redirect [[Restaurant guide]] |
| − | | + | |
| − | A list of places to eat (pretty obvious really!)
| + | |
| − | | + | |
| − | There have been many good restaurant guides produced over the years, and here is some of the information that they have included:
| + | |
| − | | + | |
| − | *Name of restaurant
| + | |
| − | *Cuisine type (pizza, Indian, French etc.)
| + | |
| − | *Address
| + | |
| − | *Zip/postal code, especially useful if people will be using SatNav or MapQuest/Multimap etc.
| + | |
| − | *phone number for booking or to order delivery
| + | |
| − | *website (for menus, online booking etc.)
| + | |
| − | *price guide (either a typical meal price range, or sometimes encoded, e.g. "$"=cheap to "$$$$$"=very expensive)
| + | |
| − | *any other factual notes (dress code, closed on Labor Day, booking required on Saturday evenings, Kareoke Elvis on Sunday)
| + | |
| − | *if possible, a quick review ("great pizza, avoid the garlic bread, service very slow on Saturdays")
| + | |
| − | | + | |
| − | Unless it is a really short list, it is suggested that restaurants should be listed grouped by cuisine/culture (e.g. Japanese, Italian etc.)
| + | |
| − | | + | |
| − | It is also possible to divide restaurants into "delivery/takeaway" and "eat in".
| + | |
| − | | + | |
| − | And it is possible to divide restaurants by distance/time (e.g. short walking distance, long walk, taxi/car/bus distance)
| + | |
| − | | + | |
| − | Cross reference with local area map (e.g. put in reference numbers on the map and match them up on the restaurant list)
| + | |
