A real HTML menu instead of a PDF, reservations, live open/closed status, and Restaurant + Menu schema built in.
Most restaurant websites fail at one specific thing: the menu is a PDF. Google cannot read it properly, phones render it as a pinch-zoom scan, and updating it means re-exporting from a design file. Table & Fork is built around fixing exactly that — the menu is structured HTML with real Menu schema, so every dish is legible to a customer on a phone and to the search engine deciding whether to show you.
Around that menu are the parts a restaurant page is actually for: a live open-or-closed indicator computed from your hours, a reservations section that points wherever you take bookings, and Restaurant structured data so your name, cuisine and hours are machine-readable.
It is MIT licensed and static — a restaurant site has no reason to cost monthly hosting. Put it on Cloudflare Pages free, update the menu by editing one config file, and let the food photography you add do the selling.
The menu is structured HTML, not an embedded PDF — so Google can read every dish, and a phone renders it without pinch-zooming a scan.
Structured data for the restaurant and the menu itself is built in — the markup search engines use to show hours, cuisine and menu details.
The site shows whether you are open right now, computed from your stated hours — the first thing a hungry visitor checks.
A reservation flow ready to point at your booking system or phone — the page’s one job, given a clear path.
The three answers restaurant visitors come for, structured and impossible to miss.
Menu items, hours and details live in config/site.ts — update the menu like editing a list, no CMS required.
Four commands from clone to a production build. The build outputs static files — host them anywhere, free.
git clone https://github.com/haider484991/tablefork-nextjs-restaurant-template.git
cd tablefork-nextjs-restaurant-template
npm install
npm run dev # develop at localhost:3000
npm run build # static site in out/ — deploy to any static hostRather have it done for you? See how we design restaurant sites that turn searches into bookings — with a teardown of what converts.
Because the menu is the highest-intent content a restaurant has. As a PDF it is invisible to search and painful on phones — the device nearly every diner uses. As structured HTML with Menu schema, every dish becomes searchable text and renders natively.
Menu items live in the config file as a simple list — edit prices or dishes, rebuild, deploy. No CMS subscription; if you later want one, the structure maps cleanly onto any git-based CMS.
It gives reservations a proper section and call to action, pointed at whatever you use — OpenTable, Resy, a booking form or your phone number. It deliberately does not lock you into one system.
Yes — we design restaurant websites as a specialty, from adapting Table & Fork through fully custom builds. See our restaurant web design page for how we approach it, then get in touch.
Write posts in Markdown, get a fast static site with RSS and dark mode. MIT licensed — use it for anything.
View Nova →Auth shell, sortable tables and hand-drawn SVG charts in a colour-blind-safe palette — with zero chart-library lock-in.
View Pulse →Pricing tables, feature grid, FAQ schema and email capture — the sections every SaaS page needs, already assembled.
View LaunchPad →White label web development for agencies and studios. Your brand on everything, fixed quotes…
Read more →Free website cost calculator. Answer six questions and get a realistic price range instantly …
Read more →Custom web development from $3,500. Hand-built on Next.js and React — no page builders, no…
Read more →Tell us about your business and we'll design a custom homepage concept within 48 hours — free, no strings attached.