Restaurant / Menu / Multi-location

Crawfish House

WEB-06

A four-page sample rebuild for a Cajun seafood boil with Renton and White Center locations. It replaces a broken HTTPS site and a template placeholder menu with real prices and a shorter mobile path to order.

Focus: Two locations, real menu prices, mobile ordering
Contribution: Web design and development
Status: Sample redesign / draft preview

Crawfish House draft preview homepage with a seafood-boil hero and Renton and White Center location cards.

The experience at a glance

Give two locations one clear way to order.

Home, Menu, Locations, and Order each have one job. The homepage names both kitchens, and the menu shows the restaurant’s prices instead of template placeholders.

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.

01 / Problem

The product challenge

The previous site failed over HTTPS, and the menu still showed template placeholders instead of the restaurant’s prices. Visitors choosing between Renton and White Center needed hours, a real menu, and a way to order on a phone.

02 / Design intent

The experience goal

Make the boil, the two addresses, the priced menu, and the order step easy to reach without a single overloaded page.

03 / Key decisions

How the interface supports the goal

Home leads with boils by the pound and names both Renton and White Center.
Location cards show address and hours side by side: 247 Park Ave N in Renton, and 9826 16th Ave SW in White Center.
The menu uses the restaurant’s prices in place of template placeholder items.
Order stays available from the header on each page.
Hours that still need confirmation are marked for the owner to verify, rather than presented as final.
The preview is labeled as a draft and not the official site.

04 / Interaction & usability

Helping users move through the product

Four pages keep a phone user from scrolling one long homepage. Location, menu, and order are separate destinations that share the same header.

05 / Tools & skills

What this work demonstrates

Multi-page information architecture, menu content, location patterns, responsive layout, and front-end implementation.

06 / What I’d improve next

Next iteration

Resolve the hours still marked for owner verification.
Check price formatting on the narrowest phones.
Give each location its own order or call action if the kitchens differ.
Note items that belong to only one location, if the menus are not the same.

Thinking beyond this preview

The same four-page structure can hold confirmed hours and a per-location order link once the details still marked for verification are settled.

Open the preview ↗