3 min read
Restaurant website design that doesn't become your second job
You already run staff, suppliers, food costs, wine, payroll, and accounts payable. A website shouldn't add a design project to that list. What done-for-you actually means.
Restaurant websites, ADA compliance, menu design, and how to stop paying $399/mo for a homepage.
3 min read
You already run staff, suppliers, food costs, wine, payroll, and accounts payable. A website shouldn't add a design project to that list. What done-for-you actually means.
2 min read
Overlay widgets promise one-line-of-code accessibility. They don't deliver it — and they can make things worse. Why the fix has to happen at the source, not on top.
3 min read
What good alt text for a dish photo actually looks like — with before-and-after examples, when to mark an image decorative, and the difference between menu photos and gallery shots.
2 min read
A PDF menu can't be read by screen readers, barely indexed by Google, and miserable on a phone. Why your menu should be real HTML — for SEO and for every guest.
2 min read
Marketplaces and ordering platforms take 15–30% of every order. Ordering on your own domain keeps the margin — here's the math, and how Square-synced ordering makes it work.
2 min read
Per-cover reservation fees look small until you multiply them by a month of diners. Flat-rate vs per-cover math, with real numbers, so you can read a pricing page in one minute.
2 min read
Restaurant website pricing comes in three models: flat-rate, revenue-share, and DIY with hidden costs. What each one really costs per month, and how to spot the traps.
3 min read
WCAG 2.2 Level AA, translated into restaurant terms: your menu, your reservation form, your photos, your hours. What the standard actually demands, in plain English.
1 min read
Restaurants deserve a website that's actually theirs. Accessible by default. Free if you take online orders, or $99 a month dine-in. No data hostage situations. Why we built Remi.