Skip to Content

Hospitality Components

Choose and compose Puzzle Pieces for accommodation discovery, booking presentation, restaurant menus and reservations, reviews, local guides, hosts, services, and gift vouchers.

The hospitality surface composes existing Pieces and generic UI. It is a presentation layer: applications supply all content, data, validation, availability, prices, and actions. Start with a fit-for-purpose component below, and reuse existing Hero, Gallery, Location, Testimonials, Resource, Team, Services, and Product Grid components instead of building parallel systems.

Beta API maturity varies by component; check each reference.

Component map

AreaComponentsUse
Accommodation presentationAccommodation Overview, Accommodation Details, Amenity ListCompare stays, explain one property, and group facilities.
Stay planningAvailability Search, Rate Plans, Stay Summary, House RulesPresent caller-provided search values, rate offers, price lines, and policies.
Restaurant menuRestaurant Menu, Dish Card, Dietary InformationRender supplied menus, dishes, dietary tags, and allergen information.
Restaurant operationsOpening Hours, Table ReservationPresent supplied schedules and reservation forms or external provider links.
Shared guest experienceGuest Reviews, Local Guide, Host Profile, Service Options, Gift VoucherShow review evidence, local recommendations, a host, optional services, and externally purchased vouchers.
Existing general sectionsAccommodation Hero, Restaurant Hero, Gallery, Testimonials, Location, Resource, Team, Services, Product Grid, CTAReuse the general component when hospitality-specific content is not needed.

Responsibility boundaries

  • Reviews: the application supplies review text, dates, source, score, and any aggregate distribution. Pieces does not verify reviews or calculate averages.
  • Local guide: distances and travel times are displayed as supplied. Pieces does not geocode, create maps, or calculate routes.
  • Services and vouchers: prices and purchase destinations are supplied. Pieces does not provide checkout, voucher administration, or payment.
  • Availability and reservations: Pieces can present forms and callbacks. The application or provider owns availability, confirmation, and persistence.
  • Menus: allergen and dietary information must be explicitly supplied. Filtering is presentation behavior; it does not infer ingredients or determine suitability.
  • Frameworks: components stay router-independent and work in Next.js and TanStack Start using their normal React client boundaries for interactions.

Complete reference compositions

Boutique B&B

The Boutique B&B page composes the existing accommodation Hero, details, Gallery, and Amenity List with shared reviews, host, services, local guide, gift voucher, and CTA sections.

Restaurant

The Restaurant Experience page combines an existing RestaurantHero, menu, opening hours, location, and reservation presentation with the five shared hospitality components.

Composition guidance

Use one component for each distinct responsibility. LocationSection describes the venue; LocalGuideSection describes nearby places. TestimonialsSection handles generic quotes; GuestReviewsSection adds dated review metadata and a supplied score summary. TeamSection is for multiple people; HostProfileSection is a single host. ServicesSection handles general services; ServiceOptionsSection adds included/optional labels.