Eater reservations

Centralizing Eater venue data to allow for on-site reservations

This project centralized Eater's venue data into a unified component, giving users access to reservations from multiple locations across the site.

I started by creating a restaurant data component that worked in multiple locations on the site. It has options for borders or no borders which can be displayed based on the component location.

data component data component, option for borders or no borders

That component appears in 3 main locations on the site: venue component in articles, venue landing page and venue component on maps page.

enue card component in articles venue card component in articles
venue landing page venue landing page
venue in maps page experience venue in maps page experience

This made it so we could add a "book a table" link to the centralized data component and readers would be able to access this experience easily across the site. The "book a table" modal has many different states, depending on venue data available.

only capital one booking available only capital one booking available
only seven rooms booking available only seven rooms booking available
both capital one and seven rooms booking available both capital one and seven rooms booking available
both bookings available, no capital one availability both bookings available, no capital one availability
both bookings available, no seven rooms availability both bookings available, no seven rooms availability
both bookings available, no availability both bookings available, no availability

Once a user selects a table, they are taken through confirmation screens.

time selected time selected
confirmation confirmation

More info coming soon!