Build a Restaurant Website Customers Can Use
Build a mobile restaurant homepage with accessible menu, accurate hours and locations, and trustworthy booking or takeaway actions. Use when launching or repairing a local restaurant site.
Start with the customer tasks the owner supports: check today's hours, read the menu, find the correct address, book a table or order. Confirm the location, timezone, contact number and action destinations with the operator. For multiple locations, use a location-specific page or clearly scoped selector. Never send an order or reserve a table merely to prove a link works. ## Key Points - [Google restaurant and LocalBusiness structured data](https://developers.google.com/search/docs/appearance/structured-data/local-business?error=error_code) - [W3C WCAG 2.2](https://www.w3.org/TR/WCAG22/?KBOpenTab=undefined) - [HTML grouping and lists](https://html.spec.whatwg.org/multipage/grouping-content.html)
skilldb get web-polish-skills/restaurant-website-essentialsFull skill: 29 linesBuild a Restaurant Website Customers Can Use
Start with the customer tasks the owner supports: check today's hours, read the menu, find the correct address, book a table or order. Confirm the location, timezone, contact number and action destinations with the operator. For multiple locations, use a location-specific page or clearly scoped selector. Never send an order or reserve a table merely to prove a link works.
Publish one maintainable version of the menu and hours
Use a semantic HTML menu with readable categories, dish names, prices and owner-supplied dietary or allergen information. A photo, QR code or PDF may complement that menu, but make the essentials usable without zooming a picture or downloading a file. Do not infer dietary or allergen status. Give the owner one reviewed source for normal hours, holiday exceptions and menu changes. Present temporary closures and separate service hours explicitly, including which location is affected. Update any structured data from the same published facts; Google LocalBusiness fields do not guarantee search placement.
Keep hours, address, menu and one primary action easy to reach on a phone. Use concise labels such as “Book a table” or “Order pickup” and name the destination or service where useful. Keep a telephone and address available in text even if a map embed or external booking script fails. If the venue does not offer online bookings, show its real contact process instead of a mock flow. Use only brand assets and photos the user has authorized.
Test the decisions customers make
At a narrow viewport and enlarged text, open the menu with keyboard and touch, find the current location and verify that its published hours and address agree with owner-provided evidence. Open the booking or order link through its supported test boundary and confirm the provider shows the exact location and intended action before any submission. Check mobile interaction without the map, with reduced connectivity and with a temporarily unavailable external destination. Test a holiday closure or out-of-stock menu state against normal information.
Give the owner the menu and hours editing entry points, plus a list of links or facts awaiting confirmation. If no real restaurant data is available, label demo content and keep deployment or transaction submission pending.
References and rights
Original SkillDB instructions under LicenseRef-SkillDB-Content. References were checked 2026-11-13 and used for technical verification.
Install this skill directly: skilldb add web-polish-skills
Related Skills
Typography Cleanup
Fix font chaos in a vibecoded website — too many font sizes, inconsistent weights, broken heading hierarchy, mismatched line heights, and mixed font families. Establish a clean type scale and apply it everywhere. Trigger when fonts "look off," headings are inconsistent, or there are too many text sizes.
UI Audit
Audit a vibecoded or inconsistent website for visual and structural problems — mismatched components, font chaos, color drift, spacing irregularities, broken states, and missing interactions. Produces a prioritized fix list. Trigger when users say "this looks off," "make it consistent," "audit the UI," "fix the design," or "polish this site."
Vibecode Upgrade
The comprehensive playbook for upgrading a vibecoded website from "it works" to "it feels premium." Combines all other web-polish skills into a prioritized workflow — audit, extract tokens, unify components, fix responsiveness, add polish. Trigger when users want to "upgrade the whole site," "make it look professional," "polish everything," or "it was vibecoded and needs to be cleaned up."
Visual Polish
Apply the final layer of visual polish to a website — hover states, transitions, micro- interactions, loading states, empty states, scroll behavior, and the small details that make a site feel premium. Trigger when a site "works but feels cheap," needs "polish," or the user says "make it feel premium/professional/finished."
Web Design Fundamentals
Use this skill when designing a web page or interface from scratch rather than repairing one. Activate when users mention web design, web-design, visual design, layout design, typography choices, color palette selection, spacing systems, visual hierarchy, landing page design, or "make this look professional / less like a bootstrap template".
Color System Repair
Fix color chaos in a vibecoded website — too many near-duplicate colors, inconsistent semantic usage, broken dark mode, contrast failures, and colors without purpose. Establish a minimal palette with clear roles. Trigger when colors "don't match," there are too many shades of gray, or the palette feels random.