gotcb.comBash · Build · Go
Customer · Oxford · Honduran kitchen

La Cocinita de Jackie

A family of four is driving back from a soccer tournament in Oxford. They are hungry. The driver pulls out her phone and types "Honduran restaurant Oxford MS." La Cocinita is the first result.

Client
Jackie — La Cocinita de Jackie
Industry
Honduran restaurant · single location
Stack
Lovable · static single-page · Restaurant JSON-LD · embedded map · tap-to-call
Live at
jackieskitchenoxford.com
Hero screenshot or photo · 16:8

The problem

Before the build, La Cocinita ran on word of mouth, paper menus, and a Facebook page. No website. No searchable menu. No way for a new customer to discover Jackie's food, check prices, or call ahead. Every new customer arrived through personal referral or drive-by.

Jackie cooks. Her existing customers love her. But the family in the car, fifteen minutes from a decision about where to eat, has no way to find her. The Google Maps pin shows the restaurant exists. The Facebook page has a half-stale phone number. The menu is on paper, inside the restaurant, which is the one place the customer is not yet standing.

The harness

A single-page site. Full-bleed food photo at the top. The menu visible without a click, dish names in Spanish, English where useful, a price next to each one. A sticky tap-to-call bar on mobile so the phone number is one tap from anywhere on the page. An embedded map with a directions button. Hours posted plainly. A WhatsApp link for catering inquiries — Ole Miss family weekends, church gatherings, small office lunches, named by name. The Restaurant JSON-LD schema wired to signal entity match with the Google Business Profile, so the site and the GMB pin are the same thing to Google. Static. Edge-rendered. Zero backend. No admin. No online ordering. No database.

The smallest harness in the family. By design.

The result

The family in the car taps the phone number. Jackie picks up. ¿Tienen baleadas? Sí, todos los días. They pull in fifteen minutes later. They sit. They eat. They love it. They leave a five-star Google review on the way out.

The next ship is the Quarterly Refresh — once every three months, a WhatsApp message from Taylor to Jackie. Anything new on the menu? New photos? Did the hours change? No invoice attached. The Refresh is the act of being the person who remembers to ask. Memory like a witness, applied to a paper-based restaurant where there is no automated drift detection.

The phases
01 · Audit
Did not build what Jackie did not need.
No dashboard. No ordering. No reservations. The site does one job.
02 · Wire
Schema before chrome.
Restaurant JSON-LD before the design system. Google has to see the entity first.
03 · Hand off
Editing the menu is one file.
One file edit, one click to publish. No tech support calls.