Make the current menu easier to read and maintain.

01 / The customer decision

Start with the information the visitor needs.

A large image or PDF can make a simple price check awkward on a phone. Organised text can help customers browse categories and understand dishes, but the editing structure needs to match how the restaurant maintains its menu.

Agree which information is displayed. Prices, availability and dietary statements must come from the restaurant and stay accurate. A menu website does not automatically manage orders, tables or kitchen operations.

02 / A practical content plan

A restaurant menu your team can maintain: a useful starting structure.

This is an example content plan for discussion. It describes information to organise, rather than an automatic promise that every feature or section is included.

1. 01

   Menu categories

   Group dishes in the way customers choose a meal.

2. 02

   Dish details

   Agree fields for names, descriptions, prices and any client-confirmed dietary information.

3. 03

   Visit information

   Show current hours, location details and the contact or reservation destination supplied by the business.

4. 04

   Editing tasks

   Decide how the team changes prices or menu descriptions within the supported CMS setup.

03 / Choose by the work required

Check the fit before choosing a package.

Use CMS

Your team expects to update menu information regularly.

Review content size

A large menu or several outlets may need a scope beyond five pages.

Discuss separately

Ordering, delivery, table management, payments and POS integrations are additional systems.

04 / Promotional packages

A clear scope at each price.

These are promotional website packages. They are separate from the standard website packages. The ten- and twenty-page limits include the shared website pages; they are not extra pages added on top.

I agree page types, source content and functionality before work starts. Payment, delivery, domain, hosting, revisions and support arrangements should be confirmed with your project scope. No recurring service, advanced integration or unlimited future work is implied by the page count.

05 / Prepare a useful brief

What to send with your enquiry.

• A current menu in an editable format.
• Confirmed categories, prices and dish descriptions.
• Approved images, hours and location information.
• The menu updates your team needs to make.

Public website links and a description of your needs are enough to start the discussion. Share account access through an appropriate invitation when needed; do not put passwords in an enquiry message.

06 / Before you decide

Questions about this website scope.