Turn the visitor's questions into the homepage's sections

A one-page site has to answer questions in the order people ask them. In Plan, you wrote down the attendee's questions, in order. Now each one becomes a section of the homepage.

Give each question a section: what it must answer, the slots it holds, and what it asks next. What it is, when and where go first, with the ticket button, because that's what someone arriving cold needs. Is it credible comes next. A stranger won't care who's speaking until they believe the event is real. The proof is AllWeb's own published history, and the figures come from their site.

Then who will I hear from, what the day is like, whether it's worth it, and what happened before. Each section answers one question, and none tries to answer two. The last section asks how do I go, and repeats the date, the place and the ticket button. By the bottom of the page, a convinced visitor is ready to act.

Then check the build kept the order. On the built page, each section starts with a note naming its question. One search lists them, top to bottom. Those notes are for whoever edits the page next. Move a section, and the note says which question you just moved.

Last, map the calls to action. For each section, write the one action it offers and where it sits. One search finds every action button on the page: five for tickets, one for partners. Write each one down with its place. The header button is hidden on phones, so phones get one pinned to the bottom after the hero. Now nobody has to guess where the next step is.

Take the visitor's questions in the order they ask them, give each one a section with its slots, map where each action sits, and keep that order all the way into the code.