Last updated April 22, 2026
When a client opens their itinerary link, the first thing they see on the At a glance page is a Highlights section. This is where the big, magazine-style hero cards for their cruise ships and theme parks live.
These cards are richer than the per-day blocks — they pull from the full JourneyFuse ship catalog, the park schedule cache, and cruise sailing data to give clients a trip-level briefing before they drill into specific days.
Two flavors today:
Both use the same magazine layout: hero image → sticky tab bar → deep-dive content per tab. Clients can tap any tab for more detail, and the whole thing collapses to the Overview tab only when they print or download the PDF.
A Ship Overview card appears automatically whenever a cruise booking is attached to a trip. Behind the scenes, a cruise_overview block gets inserted on day 1 of the trip when you fill out the booking — you don't need to add it manually.
| Tab | Source | What's in it |
|---|---|---|
| Overview | Ship catalog | Ship description, launch year, passenger capacity, gross tonnage |
| Itinerary | Booking + Sailings DB | Port-by-port rail: arrival/departure times, sea-day badges, embarkation & disembarkation markers |
| Your cabin | Booking's stateroom selection | Booked cabin image, sq ft, occupancy, amenities, plus other cabin categories on the ship |
| Dining | Ship catalog | Venues grouped into Complimentary vs. Specialty; adults-only tag; descriptions |
| Activities | Ship catalog | Featured entertainment, shows, experiences |
| Tips | Per-cruise-line curated list | "Know before you go" tips tailored to Royal Caribbean, Disney Cruise Line, Carnival, NCL, etc. |
There are two ways the port-by-port itinerary gets populated:
(cruise line, ship, sailing date) against our scraped sailings database (50k+ sailings from CruiseMapper) and pulls the itinerary from there. Clients see a full port-by-port plan with no work on your part.Agent-entered data always wins. The fallback kicks in only when no manual cruise days exist.
The hero image at the top of the card comes from the ship catalog. Every ship in the catalog (623 as of April 2026) has a hero image — major ocean liners use their Wikipedia photo; smaller river/expedition ships use a stock cruise photo.
If a ship is missing or has the wrong image, head to Settings → Ship Catalog, find the ship, and use the image refresh button.
Whenever a park_day block exists on the itinerary for a recognized park, a Park Overview hero card appears at the top. It auto-inserts on the earliest day the park is referenced.
Currently recognized parks: Magic Kingdom, EPCOT, Disney's Hollywood Studios, Disney's Animal Kingdom, Disneyland Park, Disney California Adventure, Universal Studios Florida, Islands of Adventure, Epic Universe.
Any park outside this list will still render a generic card if a park_overview block is added manually, but the tab pattern works best with the curated parks.
| Tab | Source | What's in it |
|---|---|---|
| Overview | Park profile | Hero image, tagline, description, quick stats (park days, hours coverage, tips count) |
| Schedule | ThemeParks.wiki | Open / close times for every trip date the park is visited |
| Tips | Per-park curated list | Walk-through tips: rope drop strategy, Lightning Lane timing, park-break suggestions, Express Pass advice for Universal |
Multiple parks on the same trip each get their own card (e.g., a 7-day Disney World trip would show cards for Magic Kingdom, EPCOT, Hollywood Studios, and Animal Kingdom if all four are on the itinerary).
When you add a park_day block with a recognized park, a matching park_overview hero card is created automatically. If one already exists for that park on that trip, nothing happens (it's idempotent — you won't get duplicates).
When a client prints their itinerary or downloads the PDF:
This keeps printed itineraries looking tight while the web version remains rich and explorable.
park_day blocks.park_profiles / cruise_line_tips table is on the roadmap.Build a single proposal where the client picks one hotel AND one set of tickets AND one excursion — instead of forcing them to choose just one option.
When clients forward their Disney confirmation emails, JourneyFuse parses them and puts them in one queue. Review, attach to a trip, and create a booking in a few clicks.
Swap a client's booking for a new one, or cancel a booking outright — without losing history, payments, or commission records.
Ready To Launch
JourneyFuse is ready to sell, service, and scale with you now. No waitlist. No stitched-together stack. Just one sharp platform your team can actually run on.

Bold branding outside. Serious operating system inside.