Your program as data

A program is data: one record per item — a talk, a workshop, the lunch break — in a collection. Once it is in, templates, agenda boards and “Up next” screens all read from it, and a change to one record shows everywhere it plays. Entering it puts nothing on a screen: a collection plays only where a story uses it.

This page walks through a conference day: three rooms, a keynote block, sessions on the hour, speakers with their photos.

Speakers are presenters, the same people who can later go live on a screen. Open Run → Presenters and use Add presenter for each: name, job title, organization, and a photo. Adding them first means a session can link to the person instead of repeating their name — change a title or a photo once, and every session that names them shows it.

• Text — anything: a title, a room, a level. Rooms are best short keys such as A, B, C, and all for items everyone attends — screens per room pick their items by it.
• Date — the day, 2026-09-25.
• Time — 13:00. An item without an end ends when the next one in its room starts.
• Image — a picture from your media library (choose or upload it on the record), or the web address of one. On screens it is downloaded with everything else, so it plays offline.
• Presenters — one or more speakers, in order. A field named speaker also gives templates {speaker} (all names), {speaker_title}, {speaker_organization} and {speaker_photo} from the first speaker — kept up to date when you edit the presenter.
• Link to a record — one or more records of another collection, in order: the sponsor of a talk, the room it is in. Choose the collection under Links to. A field named sponsor gives templates {sponsor} (the linked titles) and one blank per field of that collection from the first one — {sponsor_logo}, {sponsor_url} — kept up to date when you edit the sponsor. A picture there stays a picture, so a Still or an agenda row can show {sponsor_logo}. The field owns every sponsor_… name, so no other field may start with sponsor_.

On the Records tab, type a short key after the prefix — conference-2026/program/keynote-1 — and choose Record. Fill in its values and Save; “Saved” confirms it. For the speaker, pick one or more presenters from the list; change the order with the arrows. For a linked record, type in its search box and pick from the collection it links to. For the picture, Choose from media, Upload, or paste a web address.

Items with no time of their own yet — two keynotes inside an opening block, say — can leave the time empty until it is known, instead of two items claiming the same minute.

A talk that a person gives live on a screen also becomes a session — the live part: which screen, when it may go live, the speaker’s private link. Link the two on the session page: under Program item, search the program, pick the item and Save. From then on the session’s slides are filled from the item — title, time, room, speakers — and the item’s page shows Live session: … with a link. The program stays in one place; nothing is typed twice. (Behind the scenes the session takes the item’s ref, which is how an AI agent or the API links them too.)

Nothing in steps 1–3 needs a screen. Put the program on screens when you are ready: an agenda board, a room’s “Up next”, or a rolling list — and let visitors touch a session to see the speaker. How all of that works, for this program or any other collection: From data to screen.

Paste the program into your connected agent and ask, in your own words: “Put this program into Wunderframe as data, with the speakers as presenters — don’t put it on any screen.” The agent adds the missing presenters, makes the collection with typed fields, and writes one record per item with the speakers linked. It shows you its plan first and leaves times empty rather than guessing them.