DocsUser guidePublish your program

Publish your program

One button turns the private board into a public schedule. You never have to publish twice.

  1. On Agenda, press “Publish agenda” and confirm. The dialog tells you exactly how many sessions go live and where.

    The Publish the agenda dialog naming the public address and the session count
    Until you do, the public page says “Schedule coming soon” — no times leak.
  2. That is it. Your public event page is live, with Schedule, Speakers, Sessions and My schedule.

    The live public page for Devcon Berlin 2026 showing the published schedule, track filters and add-to-calendar buttons
    The same talk the speaker submitted, now on a public programme. Every later edit goes out live — no re-publishing.
  3. Attendees can take it with them. Every level has an add-to-calendar button next to it.

    Add to calendar at the top of the page takes the whole event; Add the whole program and Add this day do what they say; and each session card has its own. Google, Outlook, Apple or a plain .ics download — and My schedule lets someone bookmark just the sessions they picked and subscribe to those.

  4. Publishing is one reversible flag.

    An Unpublish button appears next to a “Published · date” pill, and unpublishing deletes nothing.

  5. Need it on your own website? Open Embeds — options on the left, a live preview of the real thing on the right.

    The Embeds page: saved embeds, widget, format and display options on the left, and a live preview of the agenda grid on the right
    Pick a widget (agenda grid, sessions, speakers…), a format (embedded widget, link, static HTML, JSON, XML, calendar feed), then what shows — down to which tracks. The preview updates as you pick, and the Code tab is the snippet to paste.
  6. Give the configuration a name so you can come back to it — “Agenda for the homepage”.

    Saved embeds sit at the top of the left column, each with an off switch: turn one off and every page you pasted it into says “This embed is turned off” instead of showing the programme — no need to edit your website.

    The calendar and XML feeds need no key at all: attendees subscribe once and their calendar keeps itself right, and a CMS that imports an XML feed re-reads yours whenever the programme changes.

The JSON feed is the same data as the HTTP API — it needs an API key, which lives with you rather than with the event: avatar menu → Account settingsAPI & MCP.