Events & invitations · A4 portrait · v0.1.0
Event Programme
Elegant one-page order-of-day programme: centred serif header, gold ornament divider, a timed running order on hairline rules, optional practical notes and a word of thanks. Fits weddings, anniversaries, ceremonies, conferences and concert evenings.
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 | Programme — Willem & Margriet de Vries · 25 Years |
kicker |
text | yes | Programme |
event-title |
text | yes | Willem & Margriet de Vries |
event-date |
date | yes | Saturday 26 September 2026 |
venue-name |
text | yes | Landgoed Duin & Kruidberg, Santpoort |
welcome-line |
html | yes | <p>Twenty-five years ago we said yes to each other; tonight we raise a glass to everything that followed. We are so glad you are here — welcome, and make yourselves at home.</p> |
practical-content |
html | no | <p><strong>Parking</strong> — free on the estate; follow the signs from the main gate.</p><p><strong>Taxis</strong> — Taxi Santpoort, +31 23 538 22 11.</p> |
thanks-line |
html | no | <p>With thanks to our children, Floor & Daan, who planned this evening down to the smallest detail.</p> |
footer-line |
text | no | Willem & Margriet · 26 September 2026 · Landgoed Duin & Kruidberg |
Repeat: entry (2–20×)
One row of the running order: time, title and an optional short detail line.
| Slot | Type | Req. | Example |
|---|---|---|---|
entry-time |
text | yes | 17:00 |
entry-title |
text | yes | Reception on the south lawn |
entry-detail |
html | no | <p>Champagne & canapés · Weather permitting</p> |
Optional blocks
practical— Hairline-ruled band with practical notes in two columns: parking, taxis, wi-fi, accommodation, contact number.thanks— Single centred italic line of thanks above the footer.
The authoritative fill instructions from manifest.json — the only place a template may instruct an agent (why).
Keep entries in strict chronological order with plausible, consistent times formatted like the placeholders: 24-hour, zero-padded ('09:30', '17:00' — never am/pm). Remove the data-example rows and create one 'entry' per programme item. entry-title stays short (≤60 characters, no trailing period); entry-detail is at most two short lines (who/where/note, parts separated by ' · ') and may be left empty — never a paragraph. Adapt the register to the event while keeping the same structure: warm and gracious for weddings, anniversaries and ceremonies; crisp and neutral for conferences and concerts (set kicker to 'Agenda' or 'Order of Service' when that fits better). Write event-date out in full with the weekday ('Saturday 26 September 2026'). The document must stay ONE A4 page: beyond ~14 entries, tighten or drop entry-detail lines first, then remove the practical block. Remove the practical and/or thanks optional blocks when there is nothing real to say. If details are unknown (venue, contact number, menu), leave clearly recognizable placeholders like [VENUE NAME] or [CONTACT NUMBER] and tell the user to fill them in via the built-in Edit button.
Published versions are immutable: /t/event-programme@{version}/ never changes once live. /t/event-programme/ always points at the latest.