PRODUCT WORKFLOW EXAMPLE · KYOTO

One itinerary.
Three journal states.

See exactly what happens to a planned day when it is visited, kept private or shared.
3 days12 planned places1 shared example
Transparent demonstration

The itinerary below is an existing GetTrippage editorial route. The journal text is fictional demonstration copy—not a traveller review, a claim of a completed visit or a third-party endorsement. It exists only to explain the product states.

Open the source itinerary ↗

INTERACTIVE EXAMPLE

Follow one day from plan to memory.

1 · ORIGINAL PLAN2026-10-12 · Nishiki + Gion

Market flavours and lantern-lit lanes

Nishiki MarketNishiki TenmanguKennin-jiGion Shirakawa

This route comes directly from the existing GetTrippage Kyoto editorial itinerary.

2 · OWNER'S JOURNALVISITED · Joy

One memory, attached to the day

Demonstration entry: rain slowed the market morning, so the quiet walk beside Gion Shirakawa became the moment worth remembering.

Shared by owner
3 · PUBLIC RESULTVISIBLE ON THE TRIP PAGE

Nishiki + Gion · Joy

Demonstration entry: rain slowed the market morning, so the quiet walk beside Gion Shirakawa became the moment worth remembering.

What changes?The route remains the same. Only the owner-controlled memory and its visibility change.

WHAT THE EXAMPLE PROVES

The plan does not have to become the public story.

01

Visited + shared

Day 1 shows how a planned route can gain one owner-written memory that appears publicly.

02

Visited + private

Day 2 shows that recording a memory does not automatically publish it.

03

Still planned

Day 3 stays part of the itinerary but is never presented as an experience that happened.

USE THE SAME WORKFLOW

Plan first. Remember what actually happened.

Build your itinerary →Read the five-step guide