Skip to content

Overview

Events is a presentation theme for conferences, summits, meetups, and other time-bound programmes. It provides event-focused sections for agendas, speakers, ticket comparisons, countdowns, venues, sponsors, live/replay messaging, and past editions.

  1. Open the theme-management extension entry for Theme Events and activate the Events theme for the intended site.
  2. In Theme Studio, choose Events for the poster-style preset or Green Room for the denser backstage-style preset, then adjust the standard theme controls.
  3. Build the page in Layout Builder and enter the current programme, speaker, venue, ticket, sponsor, and status content in the relevant Events sections.
  4. Preview the site at desktop and mobile sizes before making the changes live.
  • Sections for multi-track agendas, speaker profiles, ticket tiers, countdowns, venue and travel details, sponsor tiers, live/replay states, and past editions.
  • Events-owned navigation and footer presentation, with Foundation Theme providing the shared runtime.
  • An optional demo command for installing a complete seven-page Events example.
  • Install Foundation Theme and Layout Builder first.
  • This theme is separate from the Events package. Its agenda, ticket, countdown, and live/replay sections render the content entered in Layout Builder; they do not create event records, sell tickets, accept registrations, or synchronise a live schedule.
  • The theme adds no package-specific settings, permissions, public routes, external service connection, or database tables. Publishing and access continue to follow the normal Capell workflow.
  • Keep time-sensitive sections current yourself. In particular, review countdown targets, ticket availability, agenda changes, and live/replay wording before and during the event.
  • capell:theme-events-demo can install sample pages for selected sites and languages. Existing populated layouts are preserved unless you deliberately pass --force; replace all fictional event, contact, ticket, and venue details before publishing.

For developers: see the README.