Eight templates cover
every experience.
From a single boxing match to the World Cup, from the Ed Sheeran tour to a multi-city heritage package — every page on Lumera renders through one of eight templates plus a generic listing view. Pick a template to see how it looks and which schema fields drive each section. Append ?demo=true to any template URL to see the schema-binding pill banner.
Tournaments with stages — group → R32 → R16 → QF → SF → Final. Stats strip, four-tier entry points, featured matches, multi-match passes. Examples: World Cup, Wimbledon, NBA Playoffs.
Linear tour with chronological dates, residency clusters (Toronto 3-night), VIP packages, signals strip. Examples: Ed Sheeran LOOP, Taylor Swift Eras, Coldplay tours.
The fallback. Used for any event without a parent series. Hero, stats, fighters/participants strip, ticket tiers, undercard, seat map preview, venue card. Most events on the site render this template.
Continuous, no elimination. Standings table is the central artifact, with matchday-paginated fixtures, recent results, and per-club follow filter. Examples: Premier League, NFL, NBA, La Liga, F1 season.
2-D grid of day × stage (because parallel performers across stages can't be a linear list). Pass tiers, headliner cards, A–Z lineup, festival map. Examples: Coachella, Glastonbury, Tomorrowland.
A production runs at one venue across many dates. The seat map is shared across every date — so it's prominent. Date calendar is the central UX element. Cast, reviews. Examples: Hamilton on Broadway, Adele in Vegas.
No specific show time, no real-time inventory — voucher validity, lead-capture CTA, agent calls back to confirm itinerary and price. For cruises, multi-city sightseeing, cultural and heritage packages from a second provider.
Faceted listing across an entire category. Subcategory pills, featured series carousel, filter rail, mixed event-type results. Drives /sports, /concerts, /theatre, /search.
v1 build advice: ship the single_event + category_browse templates first — together they handle 100% of the catalogue.
All eight templates pull from the same canonical schema. The right hub template is determined by walking event_group → series → primary_performer → fallback.