The guest is looking for the menu, the prices and the opening hours. Usually on a phone and usually on the move.
On most restaurant websites each of them ends with a new PDF file.
The artwork has to be reworked, exported to PDF and uploaded. It usually ends with the old menu staying on the site.
In LessCMS: you change the price in the field on the dish. The menu on the site updates in the same second.
Summer soups hang on the menu until November, because removing them from the file is another job for a designer.
In LessCMS: you switch the dish off with a toggle. It stays in the database and you switch it back on next year in one click.
They get a PDF they have to pinch-zoom. Half of them close the page and keep looking.
In LessCMS: the menu is an ordinary page — it reads on a phone just as it does on a computer.
The menu is a list of dishes with a category. Order, grouping and dietary tags are set in a form.
The menu splits into categories automatically, based on a field on the dish.
Once, dish by dish. After that you only change what changes.
They go on the site and into the data Google reads.
The old site can redirect to the new one without losing rankings.
Create an account and type up the first ten dishes. You will see how long it takes.