Home & living · A4 portrait · v0.1.0
Travel Itinerary
Day-by-day trip itinerary on a vertical timeline: bold trip masthead, sand-tinted essentials card for flights and stay, numbered day cards with timed plans, and a good-to-know tips block. Pick it for city breaks, holidays and any multi-day trip.
Paste the prompt into Claude (or any agent that can fetch URLs) with your content — you get back a finished, self-contained HTML file. Manifest ↗
Live preview — the example content ships with the template and is replaced by your content.
What an agent may change — and what content you should have ready. Everything outside these slots is fixed by design.
Slots
| Slot | Type | Req. | Example |
|---|---|---|---|
doc-title |
text | yes | Travel Itinerary — Lisbon in five days |
trip-title |
text | yes | Lisbon in five days |
trip-dates |
text | yes | 14 – 18 Sep 2026 |
travellers |
text | yes | Bram & Sanne · 2 travellers |
essentials-content |
html | no | <dl><dt>Outbound</dt><dd>TAP TP 665 · AMS → LIS · Mon 09:40 – 11:35</dd><dt>Return</dt><dd>TAP TP 674 · LIS → AMS · Fri 18:20 – 22:05</dd><dt>Stay</dt><dd>Casa do Limoeiro · Rua do Limoeiro 12, Alfama</dd></dl> |
tips-content |
html | no | <ul><li><strong>Tipping</strong> — round up or leave 5–10% at dinner.</li><li><strong>Getting around</strong> — buy a Navegante card and load Zapping credit.</li></ul> |
footer-line |
text | no | Prepared 13 Aug 2026 · Lisbon city break for two |
Repeat: day (1–14×)
One timeline card per travel day, in chronological order. The numbered dot on the spine renders automatically for each card.
| Slot | Type | Req. | Example |
|---|---|---|---|
day-label |
text | yes | Day 1 · Mon 14 Sep |
day-title |
text | yes | Alfama & the miradouros |
day-plan |
html | yes | <ul><li><strong>09:00</strong> Pastéis de Belém — arrive before the queue</li><li><strong>10:00</strong> Jerónimos Monastery — cloisters first, then the church</li><li><strong>19:00</strong> Time Out Market — dinner from the stalls</li></ul> |
Optional blocks
essentials— Sand-tinted card under the masthead with flights, stay and emergency numbers; remove when these are unknown or not wanted.tips— Good-to-know block after the timeline: transport, tipping, one lesser-known spot.
The authoritative fill instructions from manifest.json — the only place a template may instruct an agent (why).
Duplicate the 'day' block once per travel day, in chronological order, and delete the two data-example day cards (preview content only). The numbered dot on each card renders automatically — you never edit dot numbers, only the text slots. Mirror the placeholder formats exactly: day-label like 'Day 1 · Mon 14 Sep', trip-dates like '14 – 18 Sep 2026', times 24-hour HH:MM. Write each day-plan as one <ul> with 3–6 <li> items shaped '<strong>09:00</strong> Activity — short practical note'. Keep activities realistic, in sensible time order, and geographically sane: cluster each day around one neighbourhood or area the way the Lisbon sample does, and give each day-title the day's area or theme. Set doc-title to 'Travel Itinerary — ' + trip-title. If flights, stay or emergency numbers are unknown, either remove the essentials optional or keep it with recognizable placeholders like [FLIGHT NUMBER] and [HOTEL ADDRESS] and tell the user to fill them via the built-in Edit button. Remove the tips optional unless you have genuinely useful local advice (transport card, tipping, one lesser-known spot). Two pages are fine for longer trips — day cards never break across pages — but avoid a nearly empty final page: trim plan items rather than strand one small card.
Published versions are immutable: /t/travel-itinerary@{version}/ never changes once live. /t/travel-itinerary/ always points at the latest.