Hero
The full-width photo at the top with the hotel's name, its destination, its rating and its badges over it.
The hotel's own Accommodation entry
Where the content really comes from
ePIM, synced into the Accommodation entry
What makes it this section
The hero is the only part of the page that is per-hotel by nature. It is drawn from the Accommodation entry the URL resolved to — not from the shared template, which may link whichever hotel an editor happened to attach.
What a visitor sees
- 1
Hotel name (WEB)
- 2
Destination line — the travel areas
- 3
Main image
- 4
Internal rating — “our rating”
- 5
TripAdvisor ID — the live review feed
- 6
Badge label and tooltip — authored
What each field controls
The Field column is the label as it appears in Contentful; under it, the field's id, for talking to a developer. The number matches the marker on the screenshots above.
| # | Field | What it controls | Notes |
|---|---|---|---|
1 | Hotel name (WEB) hotelNameWeb | The name in the hero, and in the page title. | Synced from ePIM. This is the name customers see, as opposed to the internal one. |
2 | Travel areas / Primary travel area travelAreas / primaryTravelArea | The destination line, the breadcrumb and the page's URL. | Synced from ePIM. The URL is built from the deepest area — a city beats the country above it. Primary travel area is the one that owns the breadcrumb. |
Slug slug | The hotel page's URL. | Generated from the name on first import and yours to edit afterwards — import will not overwrite your edit. Changing a live slug needs a redirect, so it goes through the editorial workflow. | |
3 | Main image / Images mainImage / images | The hero photo and the gallery behind it. | Celum URLs, not uploads. Pictures are not stored in Contentful. |
4 | Internal rating internalRating | The "our rating" figure. | Kuoni's own rating out of 5, from ePIM. It is deliberately not published to search engines as a review score, because it is neither an official classification nor an independently collected score. |
5 | TripAdvisor ID tripAdvisorId | The review score and count beside the rating. | Synced from ePIM. It is the id the live feed is fetched with, so a wrong one shows another property's reviews — and an empty one shows none. |
YouTube video id youtubeVideoId | The property tour behind the hero. | — | |
Engage / hotel tags engage / hotelTags | Which badges appear. | Whether a badge SHOWS is decided here and cannot be changed by wording: Kuoni exclusive needs the "exclusive" tag in the PIM, Engage collection needs a non-empty Engage value, and Book online waits on the reservation system reporting the hotel bookable online. |
Fields on each badge (Icon Item)
Three badges, authored once and shared by every hotel page — so keep the wording hotel-independent.
| # | Field | What it controls | Notes |
|---|---|---|---|
Kind kindrequired | What kind of icon item this is. | Must be heroBadge. This is what stops these three being picked up by the home page's trust band, which looks for trustMark. | |
Hero badge badgeKey | Which badge this item supplies the wording for. | Matched by this key, not by order, so dragging two badges cannot swap their tooltips. Choose one of: bookOnline kuoniExclusive engageCollection | |
6 | Label labelrequired | The badge text. | — |
Supporting text description | The tooltip behind the badge's info icon. | Write one for every badge — it is the only explanation a customer gets, and a badge with no tooltip shows no info icon at all. |
Other entries this section needs
| Content type | Why you need it |
|---|---|
| Content rail (card row) | The badge WORDING. A rail with Card source = iconItems, holding Icon items of Kind "heroBadge" — entry "Hotel template — hero badge wording (not a band)". It renders no band of its own; the hero reads it. |
| Icon Item | One per badge, carrying the badge label and the tooltip behind its info icon. |
How to change it, step by step
Decide whether the field is actually yours
Most of the hero is synced from ePIM. Editing it in Contentful can be overwritten by the next sync. The slug is the exception, and the badge wording lives in the CMS on purpose.
For wording: open the badge rail
Search for "Hotel template — hero badge wording (not a band)" and edit the Icon item for the badge you mean. Publish the Icon item and the rail.
For the hotel's own details: open its Accommodation entry
Search for the hotel by name. Change what is genuinely editorial, publish, and check the page.