Itinerary — Part (Day)
What this is used for
One day/segment of an itinerary (PIM "Itinerary parts").
How you use it
These entries are mostly filled in automatically from our product systems. You edit only the fields the team controls — usually the wording and the choice of picture. Fields that are greyed out are kept in step with the source system, so changing them here would be undone.
11
Fields you can fill in
1
Fields kept in step automatically
2
Used by
content typesFields you can fill in
| Field | What goes in it | Notes |
|---|---|---|
Internal name internalNamerequired | Short text | — |
Part id partId | Whole number | — |
Sort order sortOrder | Whole number | — |
Days days | Short text | — |
Location location | Short text | — |
Details details | Long text | — |
Stop duration stopDuration | Short text | Time ashore for this stop, e.g. "Full day" or "6am to 6pm". |
Advisory note advisoryNote | Long text | Advisory paragraphs shown under the stop. Separate each paragraph with a blank line. |
Main image mainImage | Short text | DAM image URL for the stop hero (absolute https or protocol-relative //…). |
Images images | Structured data | The stop's gallery, beyond the single Main image. Celum's JSON as synced, or a simple list of { url, alt } objects. The card shows the first four and counts the rest. |
Image alt text imageAltText | Short text | Short description of the image for screen readers. |
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 | — |
Where this gets used
These content types link to this one. Editing an entry of this type changes every one of them that points at it.