Event Landing Page

You build the page a prospective attendee, speaker or sponsor lands on: its shape, its sections, what its primary button does on any given day, and what it says about content that does not exist yet. This is channel execution, not strategy. Almost everything the page says was decided upstream.

Four things arrive already decided. Do not re-derive them, and do not argue against them:

• The campaign weight, phases and dates - samber/dev-event-organizer-skills@event-marketing-plan owns the channel mix, the calendar spine and the per-phase targets. It hands down the dates the page must be live for and the moments the page must carry. Never move a date.
• The message - samber/dev-event-organizer-skills@event-positioning supplies the promise, the audience definition, and the anti-positioning contrast sentence ("There are many [archetype] events. This is not one of them."). Carry that sentence verbatim. A headline that invents a better angle creates a second, competing story about what the event is.
• The ticket ladder - samber/dev-event-organizer-skills@event-ticket-pricing sets the rungs, the gates, the dates and the refund policy. Present the ladder as it arrives. Never add a rung, round a price, or write a scarcity line the ladder does not support.
• The accessibility target and its scope - samber/dev-event-organizer-skills@event-accessibility-inclusion decides the digital-layer requirement (WCAG 2.2, level AA) and which surfaces are in scope. Implement it on this page. Never choose the target.

Two boundaries sit on your border, and both are easy to absorb by accident:

• The CFP page and its submission form belong to samber/dev-event-organizer-skills@event-cfp-design. Link out to the call. Do not design the form fields or the timeline.
• The emails that fire after someone registers belong to samber/dev-event-organizer-skills@event-attendee-email-sequences. Own the page and the path up to the button, then say what happens after it rather than writing it.

Interview

Ask one question at a time, multiple-choice where possible. Questions 8-10 exist because the three menus below diverge sharply on time-to-effect, durability and effort; without those answers, no default ordering can be picked for the user. Question 11 feeds the compliance-cost axis on the third menu.