One-Day Seminar

One-Day Seminar is a landing page for an event people have to physically travel to — which changes what the page must answer. A webinar sells a topic; a seminar sells a Saturday, a train fare and a room full of specific people, so travel, catering, seating and refunds are treated as first-class content rather than small print.
Sections, in order

Sticky navbar with anchors and a booking button.
Split hero — a deep navy panel carrying the edition badge, the promise, three meta lines (date and running order, venue and capacity, what is included), two calls to action and the seats-remaining line, beside a full-height photograph with a floating seats-taken badge.
Gold ticker strip repeating the three commercial facts: early price, what is included, free transfers.
Why the day is built this way — three numbered rules, each written as a lesson from a previous edition.
Programme — a working morning/afternoon switcher over two full agendas, every slot with time, title, description and speaker, breaks included rather than hidden.
Speakers — an eight-card grid with portrait, role and the specific talk each one gives.
What the ticket buys — five itemised inclusions beside a photograph, written to stop the "is lunch extra?" email.
Tickets — three tiers on the navy band with a highlighted middle card, plus transfer and refund terms in plain words.
Venue and travel — the building, train, parking, doors time and accessibility, beside a map block.
Last year's gallery — a six-image mosaic.
Partners — five logos and an explicit statement of what sponsorship does not buy.
FAQ — six practical questions: transfers, refunds, recordings, remote attendance, invoicing, what to bring.
Booking section — a form with ticket type, lunch-table topic and dietary field, beside the three commercial promises repeated.

Design and style. Editorial rather than techy: DM Serif Display headlines over Inter, ivory and sand surfaces, navy blocks and a gold accent, square-cornered eyebrow labels and a rule under every section heading. Programme switcher, FAQ accordion, scroll reveal and mobile menu are vanilla JavaScript.
Before you publish. The date appears in the hero, the ticker, the tickets, the FAQ and the footer — change it in all five. Keep the price ladder consistent between the ticker, the ticket cards, the booking column and the form dropdown, and keep the seats-taken figure the same in the hero badge, the hero note and the booking heading. Forms use named inputs with no action attribute, so PageHub attaches the handler on publish and each booking lands in Form Submissions with its dietary requirement and table choice attached.
Best suited to one-day conferences, professional training days, industry meet-ups, association gatherings, launch days and any ticketed in-person event where the programme and the practical details decide whether someone books.