Talk about your next project
Fireworks landing page

The lesson

Turn an event page into a schedule and meeting planner, not just a badge that says you will be there.

The move

The page opens with “Join us at Microsoft Ignite 2026” and explains that Fireworks is showing teams how to run open models at scale on Microsoft Foundry. It then moves into “Where to meet us,” separating the booth, Ember Lounge, and After Dark Reception by setting and purpose. The middle of the page lists “Fireworks on stage” sessions with durations, times, locations, descriptions, and speakers. Near the close, “Fireworks x Microsoft Foundry” connects the event presence back to the product, followed by a final “Join Fireworks at Microsoft Ignite” meeting prompt.

Why it works

  • Our readThe page answers the practical event question first, showing where to find Fireworks before asking the reader to care about the product story.
  • Our readEach session card includes the topic, time, location, and speaker, so a visitor can decide whether to attend without leaving the page.
  • Our readThe Microsoft Foundry section gives the event page a product anchor, so the meeting request is tied to a specific launch and platform story rather than a generic sales conversation.

What not to copy

Don't copy the event-specific lounge, reception, and session stack unless you have enough real programming to support it. Keep the structure of hero, meet-us options, agenda cards, product tie-in, and meeting CTA.

More from Fireworks

More landing pages

Steal it for your brand.

Tell us what you want to make. We’ll talk through how to put these ideas to work for your brand.