01 / Problem
The product challenge
The owner’s homepage had been hijacked and was showing gambling links, so a search for the restaurant no longer showed the menu, the hours, or a way to order.
Restaurant / Rescue rebuild
La Fogata
A sample rebuild for a Maple Valley family Mexican restaurant. It restores a normal restaurant page after the owner’s homepage was hijacked with gambling links, and it points ordering to the restaurant’s existing Menufy site.
- Focus
- Restaurant information, menu, Menufy handoff
- Contribution
- Web design and development
- Status
- Sample redesign / draft preview
The experience at a glance
Put the restaurant back on the page.
The preview leads with the food, the Maple Valley address, and a way to order. Online ordering points to the Menufy site the restaurant already uses.
Visit the preview ↗This case study describes a draft pitch preview and the design decisions visible in that preview. It is not the business’s official site, and it does not claim the business hired this work or published it on their domain.
02 / Design intent
The experience goal
Put the restaurant back in front—what it serves, where it is, when it is open—and send online orders to Menufy.
03 / Key decisions
How the interface supports the goal
- The page leads with the restaurant, the Maple Valley address, and hours.
- Menu and Location & Hours are separate from Order.
- Pickup and delivery are named, and ordering points to the existing Menufy site.
- The address is 23745 225th Way SE, facing Maple Valley Hwy at Witte Rd, with the phone in the hero.
- Hours that still need confirmation are marked for the owner to verify.
- The preview is labeled as a draft and not the official site.
04 / Interaction & usability
Helping users move through the product
Order, menu, and phone are in the hero, so a visitor can act without reading about the old homepage. That homepage is context for the rebuild, not the content of the new page.
05 / Tools & skills
What this work demonstrates
Information architecture, rebuilding a usable restaurant page, menu hierarchy, ordering handoff, responsive layout, and front-end implementation.
06 / What I’d improve next
Next iteration
- Keep the public page free of leftover references to the compromised homepage.
- Confirm the hours marked for owner verification.
- Make the Menufy handoff explicit before the visitor leaves the preview.
- Check pickup versus delivery labels on a phone.
Thinking beyond this preview
The preview can stay a pitch until the restaurant chooses what to do with the old domain. Nothing here assumes that switch has happened.
Open the preview ↗