Form
A form lets people enter information.
When to use
- Collecting several related values that are saved together.
- Any task with a submit step, where people should be able to check their answers first.
- Fields split into sections, each with a header that explains it.
When not to use
- A single value changed in place. That is an inline edit or a toggle.
- A setting that takes effect at once, which needs no submit.
- A form so long that people give up. Split it into steps and show a progress tracker.
Guidance
Do
Create a queue
Conversations matching its rules will arrive here.
Say what the form does, mark what is required, and label the submit with the same words as the title.
Don't
Form
Do not title a form Form and end it with Submit. Neither says what will happen, and Name does not say whose.
Content
What to write, and what to leave out.
- Title the form with the outcome. Create a queue, not New queue form.
- Use the words of the title on the submit button, so people know it does what the title said.
- Mark required fields when most are optional, and optional fields when most are required. Marking every field adds clutter.
- Only group fields into sections when each group has a useful name.