Form
A form allows people to input information.
When to use
- Collecting several values that belong together and are saved in one act.
- Any task with a submit, where the reader should be able to review before committing.
- Work grouped into sections, where a header explains each group.
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 long enough to lose people. Split it across steps and show a progress tracker.
Guidance
Do
Create a queue
Conversations matching its rules will arrive here.
Say what the form achieves, 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.
- The submit button repeats the title, so the reader ends where they started.
- Mark required fields when most are optional, and optional fields when most are required. Marking everything is noise.
- Group fields into sections only when the groups have names worth reading.