Appearance
FAQ
Where:
Content → FAQQuestions and answers, organised into groups, shown on your FAQ page and — in a shorter form — on the landing page.
Write it from your inbox
The best FAQ is written after your first week of registrations, from the questions people actually asked.
The questions you predict are rarely the ones that arrive. Predicted FAQs cover what you think is unclear; real ones cover what genuinely is.
Start with a short set before launch, then rewrite it properly once you have evidence.
Groups
Questions are organised into groups, and both groups and questions can be dragged into order.
Order by frequency, not by tidiness. The most-asked question goes first, even if that makes the taxonomy untidy. Nobody navigating an FAQ is admiring its structure.
Writing answers
Answer the question directly, first. Context afterwards, if at all.
Be specific about dates, prices and deadlines. "Shortly before the event" generates a follow-up email; a date does not.
Link to the thing. If the answer is "on your profile page", link the profile page.
The short FAQ on the landing page
A selection of questions can be shown on the landing page, separately from the full FAQ page.
Choose the ones that block a decision to register: what it costs, what you get, whether you can do it, what happens if you cannot finish. Everything operational belongs on the full page — it matters to people who have already signed up, not to people deciding whether to.
Keep it current
An FAQ answering last year's questions with last year's dates is worse than no FAQ, because participants believe it.
Reread it when your dates change. It is the page most likely to contain a date you forgot you had written down.