With a form you let visitors get in touch or sign up. You choose the fields yourself, and the input is validated automatically.
Example: a contact form
Create a contact form with name, email and message and put it on the contact page.Why forms are more than a contact box
A form is often the first real interaction a visitor has with your business, so the fields you ask for matter. Keep it short — every extra field is a reason for someone to abandon it halfway.
A common use case: a signup form that feeds straight into your subscribers list, so new leads are ready for your next newsletter without any manual copying.
Pair a form with automated email to send an instant confirmation the moment someone submits — it reassures visitors their message actually arrived.
Practical tip: for anything beyond a simple text input — checkboxes, dropdowns, file uploads — check the form field block reference to see which field types are available.
Designing a form people actually finish
Every additional field measurably lowers completion rates, so the real design work in a form is deciding what you can leave out, not what to add. A contact form asking for a name, email and message converts better than one that also demands a phone number, a company name and a preferred contact time "just in case" — ask for the extra details later, once someone has already reached out.
Field order matters too. Put the easiest, lowest-commitment field first — a name or an email — rather than opening with something that requires thought, like a detailed message. Visitors who complete the first field are far more likely to finish the whole form.
Forms across different kinds of sites
A recruitment page needs a form that accepts a file upload for a CV alongside the usual text fields. An events page needs a registration form that might collect a number of attendees or dietary preferences. A support page often needs a form with a dropdown to route the message to the right department. Each of these is the same underlying mechanism — fields, validation, storage — configured differently for what the page actually needs to collect.
Whatever the form, matching its fields to what happens next avoids collecting data nobody uses: a CV upload is only useful if someone actually reviews it, so route submissions to wherever that review happens.
Common mistakes with validation
Overly strict validation is a frequent source of frustration — a phone number field that rejects perfectly valid international formats, or an address field that assumes a structure that doesn't match every country, sends genuine visitors away confused. Validate for genuinely required fields and obviously malformed input, not for a narrow assumption about what "correct" looks like.
The opposite mistake is no validation at all, which leads to a subscriber list or submissions table full of typos and unusable email addresses. A required-field check and a basic email format check cover most of the real-world value validation provides, without adding friction.
For the technical detail of how field types and validation rules work together, see forms and validation; if a form should feed directly into your own list layout rather than a fixed table, the radio field block and the data types article cover how submitted answers can become structured content.