Split Contact Form
A contact form beside the channels that bypass it — a real address, a support link and a response-time promise, which is what makes a form people cannot see into feel worth filling.
Support requests, sales enquiries, split map-and-form layouts.
A contact form is a promise about a reply, so the useful ones say when to expect it and offer an alternative for people who would rather not fill anything in. These carry the full state machine — idle, submitting, success, and an error that keeps what the user typed — which is the part most hand-built forms are missing when the network drops.
A contact form beside the channels that bypass it — a real address, a support link and a response-time promise, which is what makes a form people cannot see into feel worth filling.
The state every form reaches and none of them illustrate: a focused summary at the top linking to each bad field, validation that waits for submit, and somewhere for the failure that belongs to no field.
A three-step form where each step validates only its own fields, errors are wired to inputs with aria-describedby, and advancing moves focus to the new heading.
One click to rate, everything after it optional — the shape that collects a complaint from someone mid-task who would never open a contact page.
A qualifying contact form that asks the three things a first reply needs, and says what happens next before you send it.
A support form that asks for the one thing that halves resolution time — what you already tried — and says when a human will read it.
Error, success and required styling driven by CSS selectors.
Closing bands, inline prompts, newsletter and waitlist captures.
Floating labels, filled and outlined fields, focus rings.
Stat rows, chart cards, activity feeds and admin shells.
Sortable grids, bulk selection, filters, pagination and row actions.
Dropzones, progress lists, image pickers and paste-to-upload.