Sweet Basil

A Vail landmark since 1977. My redesign went live in January 2022, and I rebuilt it in 2026, from the menus out.

Ten things the site does for the restaurant.

  1. A table from any page, with the hours always thereFrom any page a guest picks party, date and time, and the booking page opens with them. Eleven or more becomes a private event request. Hours, address and phone are one tap away.
  2. The menu the kitchen is serving now, on a phoneTwo in three visits come from a phone. A guest goes straight to lunch, après, dinner or dessert, sees the hours, and sees which menu the kitchen is serving now. The drinks follow the same rail.
  3. The wine list, on Sweet Basil’s own siteThe bottle list sits on Sweet Basil’s own page, readable on a phone. The wine director keeps one list in the wine software; every morning the site copies it, so nobody retypes it.
  4. Private events, with the room named in the requestEvery room with its seats, set out like a menu. Ask about one, and the request form opens with that room named. Ten or fewer are sent to book a table instead.
  5. The people who grew with the restaurantThe history runs decade by decade as you scroll. The team page shows people who grew with the restaurant. Alumni who opened their own restaurants have a page. Every visit opens on its 1988 crest.
  6. Events that come off the calendar on their ownThe tasting evenings, upcoming events and the press sit in one place. Past events move themselves off the calendar on Vail’s own date.
  7. A donation request without a phone callA nonprofit asks in four short steps. The form checks it qualifies, keeps the answers on the device, reads it all back, and sends a complete request.
  8. Written so search engines and assistants get the hours rightThe hours, menus, prices and events are written so search engines and AI assistants read them right, and old links still lead somewhere.
  9. The staff change dishes and events themselvesThe team edits dishes, people, events and press in lists they own. Anything else they need goes through the restaurant’s own form, and each request gets a reference number.
  10. A manual that says who changes whatThe staff run the content themselves, and a written manual says who changes what. The report the restaurant approved shows every page before and after.

After the list:The project

The panel has three steps: the house rules, the table, and a thank-you that never claims a booking was made. The header, the footer and the home page show the same hours, checked on every page.

One page for each menu, with a rail to jump between them. On a phone every photograph leads its own course. The staff edit the dishes as a list.

It replaced a page on the wine software’s site that nearly every page sent guests out to. If the list ever shrinks wrongly, the copy stops and writes nothing.

A guide suggests a room from the guest count, and every room has its own Ask about this room.

A bio opens over the team page, with its own link. The history carries the restaurant’s own photographs and each era’s logo.

The tasting evening sells on one page. Each event has a page of its own, and the press sits in one archive.

It asks nonprofits to apply 45 to 60 days before the event, and takes a tax number written with a dash.

Every page has its own title and description, the two addresses became one, and the old addresses forward to the new pages.

The form takes four short steps: what kind of change, where, when, then a review. Anything the lists do not cover starts there.

The manual covers every page, what to do when something breaks, and how a change reaches the site.

A manual that says who changes what.

The staff run the content themselves, and a written manual says who changes what. The report the restaurant approved shows every page before and after.

The project.

Started
2021. The new site went live in January 2022.
Status
Ongoing.
Relationship
Looked after since 2021.

The restaurant, in the press.

See sweetbasilvail.com

Live since October 2026.

Tell me what you’re working onNext: Izzy Neutron