Skip to Content

Accommodation Discovery Composition

Compose an accommodation hero, overview, detailed profile, gallery, amenities, guest reviews, and CTA.

This example combines the existing AccommodationHero with the new accommodation overview, details, and amenity sections. It reuses GallerySection, TestimonialsSection, and CTASection; it does not add a booking engine or a second hero/gallery implementation.

Beta API maturity: Beta.

Complete example

The example uses three fictional stays with intentionally different shapes:

  1. Pinecone Cabin: small capacity, a studio-style sleeping arrangement, one image, and a short list of facilities.
  2. Willow House: family capacity, several bedrooms and beds, and a mid-sized facility list.
  3. Shoreline Lodge: the largest capacity, multiple bedrooms, six gallery images, and extensive facilities and highlights.
390 × 844

Composition map

Page areaComponentResponsibility
IntroductionExisting AccommodationHeroEstablish the accommodation story and primary action.
DiscoveryAccommodationOverviewSectionCompare names, images, capacity, sleeping counts, price, badges, and highlights.
ProfileAccommodationDetailsSectionPresent a selected stay's description, sleeping layout, and highlights.
PhotosExisting GallerySectionDisplay photos and provide its optional keyboard-operable lightbox.
FacilitiesAmenityListSectionGroup amenities with optional collapsible categories.
Social proofExisting TestimonialsSectionDisplay guest feedback supplied by the application.
Next stepExisting CTASectionPresent a caller-owned contact action.

Responsive and accessibility notes

The example relies on fluid component layouts and responsive image ratios. Test 320, 375, 430, 768, 1024, 1280, 1440, and 1920px widths, plus intermediate sizes. Keep content slots shrinkable, use meaningful image alternatives, keep headings in a logical order, and provide labels for custom icon-only actions. Native details summaries and the existing carousel/gallery controls retain keyboard support.

Ownership and limitations

All stays, reviews, prices, and facilities are fictional presentation data. Availability, booking, payments, routing, translated labels, and data fetching remain application responsibilities. See the individual references for full types, defaults, accessibility, theming, and customization: