Click on boxes below for more information on each page/section
NB Standard pages such as Tell a Friend, Accessibility, Terms of Use, Privacy, Contact Details will appear as footer links on all pages
The homepage will present random customer reviews and slideshow images (both selected from the back-end).
Depending on layout, and content supplied, the About Arran On A Plate information may also site on the homepage.
Information about Richard (his Master-Chef status) and any other staff that add to the 'quality' of the establishment.
This page will display the opening times of the restaurant, as defined in the back-end administration.
Any exciting news about the restaurant would be displayed here, including new menu items, reviews etc. This page would show only the last item added to the back-end system.
There would also be a link to older latest news on this page as well as a link to join the mailing list.
The latest five articles of news would be shown here with links to read more.
A link to archived news would be shown at the end of the page.
A simple form requesting some information about the user will be presented here, to allow them to join the mailing list and receive information about any news sent from the back-end system.
The archived news section will present a list of older news items, with links to reach article in full.
If any job vacancies have been added to the back-end system, and the closing date has not been reached, they should be listed here. Otherwise a standard 'no jobs at this time' message would be displayed.
This section will display links to each of the restaurant menus.
This will display a web-friendly version of the Summer Menu created in the back-end with a link to the automatically created print-friendly PDF version.
This will display a web-friendly version of the Winter Menu created in the back-end with a link to the automatically created print-friendly PDF version.
This will display a web-friendly version of the Wine List created in the back-end with a link to the automatically created print-friendly PDF version.
The restaurant address, telephone number and e-mail address will be pulled through from the site settings defined in the back-end system and shown here. A link to the Google Map will also be provided.
This page should also detail any wheelchair access etc.
This will display a Google Map pin-pointing the location of the Restuarant.
This section of the site will display the latest Award/Press Reviews and Customer Reviews, with links to more in each.
This page will list all awards and press reviews.
This section will display all approved customer reviews.
This simple form will allow customers to add reviews which are then queued in the back-end for approval.
The front-end bookings section will tie into the back-end database. This means that as bookings are confirmed in-house, either by approving an online booking, or adding details from a phoned-in reservation, the website will always show up-to-date information.
This section of the site should list positive feedback from customers/suppliers. This page will be generated from a list stored in the database, which can also be used to populate the randomised content that appears on the homepage.
This section of the site should list positive feedback from customers/suppliers. This page will be generated from a list stored in the database, which can also be used to populate the randomised content that appears on the homepage.
This section of the website will show a customer-friendly graphic representation of the restaurant floor plan, with a date/time selector to navigate to when they wish to book a table.
Each group of tables will be clickable, unless already booked (in which case they'll appear as 'locked').
Customers can choose groups of table to ensure that they book enough tables for their party.
Once they are happy with their selection, they would complete the reservation form, which would submit details to be confirmed to the database. These table selections would then be marked as semi-locked (pencilled in) while a final confirmation is still to be made.
Reservations could require a non-refundable deposit, based on number in party. But perhaps this is best left off just now.
Using a Secure Socket Layer (SSL), credit card details can be securely gathered from the website, and used to take the deposit from the customer.
The details provided by the customer would be used to populate the booking database. Once payment of the deposit has been confirmed, all credit card details would be removed from the database (where they are stored in hashed key format).
This section of the site would allow visitors to purchase gift vouchers for the restaurant on behalf of another. Once they have made their purchase, the physical, signed vouchers would be sent to the address indicated.
Alternatively, the Vouchers could be generated in PDF format from a link sent to the customer confirming their purchase, which would generate a unique code for the customer that would match up with the database details held.