Before / After · Case Study
EFES is a Turkish restaurant that has fed Warsaw since 1994 across three locations — and its WordPress site showed its age everywhere a customer touched it. The rebuild is a Polish-first Next.js 15 storefront with the complete 74-item menu at real PLN prices (scraped and verified from the restaurant's own published pricing), a cart with pickup checkout (pay at pickup — no card rail forced onto a cash-friendly business), and a token-gated admin for orders. Live at restauracjaefes.oglife.app; cutover to restauracjaefes.pl is pending the client's sign-off on the 12,900 PLN quote.
“Thirty years of kebab earned better than a 2012 WordPress theme — and the menu is the site, so the menu is data.”
Receipts — measured
The pixel diff
Left: everything the legacy site shipped — frozen in place. Right: an auto-scrolling tour of the rebuild, from hero to booking. No slider to fight with.
This is everything the legacy site had to offer above the fold. No pricing, no calendar, no booking — the funnel ended at a mailto.
Auto-scrolls through the modern site so you can see the booking surface, the package grid, the pricing table, and the calendar inline — without leaving this page.
The four beats
Scroll past the legacy frame. The four beats land in order. At the end, the modern site fades into the same window.
Three Warsaw locations, loyal customers since 1994 — and a WordPress site that buried the menu, took no orders, and looked like the era it was built in. The restaurant's oldest asset (trust) was undermined by its newest one (the site).
Nobody visits a kebab site to read about values — they want the menu, the price, and how to get it. Structuring all 74 items as data with real prices makes the whole surface useful, and pickup-pay-at-counter keeps the business model exactly as it works today.
Menu and pricing scraped from the restaurant's own published materials and verified. Next.js 15 + Railway Postgres, cart + pickup checkout, token-gated admin, Vercel CLI deploys. Polish-first throughout.
restauracjaefes.oglife.app is live and complete. The 12,900 PLN quote (plus monthly care) is with the client; on sign-off, restauracjaefes.pl points at the new stack and the WordPress era ends.
Three Warsaw locations, loyal customers since 1994 — and a WordPress site that buried the menu, took no orders, and looked like the era it was built in. The restaurant's oldest asset (trust) was undermined by its newest one (the site).
Nobody visits a kebab site to read about values — they want the menu, the price, and how to get it. Structuring all 74 items as data with real prices makes the whole surface useful, and pickup-pay-at-counter keeps the business model exactly as it works today.
Menu and pricing scraped from the restaurant's own published materials and verified. Next.js 15 + Railway Postgres, cart + pickup checkout, token-gated admin, Vercel CLI deploys. Polish-first throughout.
restauracjaefes.oglife.app is live and complete. The 12,900 PLN quote (plus monthly care) is with the client; on sign-off, restauracjaefes.pl points at the new stack and the WordPress era ends.
Architecture
What changed
Each claim ships with concrete evidence — env vars, table names, cadence chips. No marketing fluff.
All 74 items live as structured records with real PLN prices scraped and verified from the restaurant's own published pricing — browsable, cartable, and updatable without touching a page layout. The legacy site's menu was the usual restaurant-web failure: static pages that drifted from reality.
The cart checks out to a pickup order paid at the counter — no forced card processing, no delivery-platform commission. Orders land in a token-gated admin the staff can work from a phone behind the counter.
The UI is written in Polish as the primary language — the customer base's language — rather than an English site with a translation toggle bolted on. Copy, ordering flow, and admin all read natively.
