Page
What this is used for
One page of the site, built from an ordered list of sections. Set Kind first: it decides which of the fields below apply and which route renders the page. Adding a page is an entry here — it does not need a code change.
How you use it
Create one entry per page. Set its Kind, then add the sections you want in the order they should appear. A new page needs no developer work.
17
Fields you can fill in
2
Fields kept in step automatically
0
Used by
content typesFields you can fill in
| Field | What goes in it | Notes |
|---|---|---|
Title title | Short text | — |
Slug slug | Short text | REQUIRED for Generic pages — it is the URL. Leave blank for every other kind; those routes come from the application, and a slug here would be ignored while looking authoritative. |
SEO seo | One linked entry | Links to: |
Internal name internalNamerequired | Short text | — |
Kind kindrequired | Short text | Set this FIRST. Generic is a CMS-routed page and needs a Slug · Homepage, Search results and the four My Kuoni kinds are routed by the application · Hotel detail needs a Hotel · Trip idea needs a Trip idea and a Trip type. Choose one of: generic homepage hotelDetail tripIdea searchResults quoteList quoteDetail bookingList bookingDetail |
Sections sections | Several linked entries | The page, top to bottom. Drag to reorder — the order here is the order on the page. Most pages are a hero, then content rails, then a CTA band. |
Hotels hotels | Several linked entries | The accommodation this page is about. A hotel detail page uses the FIRST one and ignores the rest — link several only where the page genuinely references more than one property. For a row of related hotels use a Content rail with source “hotels” instead. Links to: |
Trip idea tripIdea | One linked entry | Trip idea only. The itinerary this page is about. Links to: |
Trip type tripType | Short text | Choose one of: single-centre multi-centre-stopover multi-centre-complex |
Travel areas travelAreas | Several linked entries | Trip idea only. Every travel area this page relates to. Unordered, and with no single owner — for the one that owns the breadcrumb and the URL, use Primary travel area below. The same field the hotel record carries, except that a hotel's is synced from ePIM and a page's is authored here. Links to: |
Primary travel area primaryTravelArea | One linked entry | Trip idea only. The ONE travel area that owns this page in the hierarchy — the parent used for the breadcrumb and the URL. Different from 'Travel areas', which lists every area the page relates to and has no single owner. Set the most specific area that applies (a city rather than its country); the hierarchy rolls up from there on its own. Links to: |
Search bar configuration searchBar | One linked entry | Links to: |
Result tabs tabs | Structured data | Search results only. |
Filters filters | Structured data | Search results only. |
Sort options sort | Structured data | Search results only. |
No-results heading noResultsHeading | Short text | — |
No-results body noResultsBody | Long text | — |
Fields kept in step automatically
These appear greyed out, or not at all. They are filled in from another system, so anything typed here would be overwritten.
| Field | What goes in it | Notes |
|---|---|---|
Component key (sitemap catalogue ID) componentKeyrequired | Short text | — |
Hotel hotel | One linked entry | SUPERSEDED by Hotels above, which takes more than one. Read-only: its value is still used as a fallback while every environment catches up, and it will be deleted in a later migration. Do not rely on it. Links to: |