Label
Every control has a visible label or fieldset legend before the control surface.
--primitive-text-2xs / --primitive-font-monolabel text, legend, group labelCanonical board-first form patterns for contact, booking, quotes, search, uploads, auth, billing, compliance, supplier operations, roster workflows, support, and checkout. Interactive demos only; no production submissions are wired.
Forms system atlas is a reusable Oak Flats Muffler Men UI primitive with documented states, accessibility expectations, theme behavior, and implementation evidence.
Forms system atlas: Canonical board-first form patterns for contact, booking, quotes, search, uploads, auth, billing, compliance, supplier operations, roster workflows, support, and checkout. Interactive demos only; no production submissions are wired.
This atlas promotes the existing gallery forms into the canonical board, fills the missing operational families, and gives every consuming route a stable pattern anchor.
Forms now expose the atomic grammar downstream pages must consume: labels, hints, fields, selects, errors, submit rails, validation states, and the exact Shared DNA routes they depend on.
Every control has a visible label or fieldset legend before the control surface.
--primitive-text-2xs / --primitive-font-monolabel text, legend, group labelHelper text is connected with aria-describedby and never replaces an error.
--primitive-body / --primitive-mutedhint text, format note, privacy noteText, email, password, textarea, date, and search controls inherit field height, radius, focus, and recessed surface.
--primitive-size-field-mdinput, textarea, field wrapperMenus, radio groups, chips, toggles, and native selects use one choice-state grammar.
--primitive-size-field-mdselect, radio cards, chips, togglesInvalid states reserve message space, expose role or aria-invalid semantics, and keep focus visible.
--primitive-red / --primitive-focus-ringerror row, invalid border, status copySubmit and reset actions use Actions DNA for sizing, disabled state, destructive state, and success transition.
--primitive-size-command-smsubmit rail, reset command, local success statusLabel, control, hint, error, and command slots stay present across every form family.
Validation message occupies a reserved slot.
Validation and submission states use Feedback, Surfaces, Actions, and Selection tokens.
Every live demo is mapped to a domain, intent, field list, consumer routes, and state list.
Domains match the UI primitives board: public website, workshop, parts, commerce, CMS, operations, governance, agent surfaces, and marketing.
All demos stay local to the board. They submit to component state only, so they can be exercised without touching production APIs or CMS data.
Name, email, phone, subject, message, attachment slot, and consent.
Open full routeCompact email capture with success state and unsubscribe promise.
Open full routeRego, date picker, slot selection, drop-off mode, callback, and confirmation.
Open full routeRego lookup, make/model/year, engine, body, fuel, photo tray, and notes.
Open full routeThree-step vehicle, service multi-select, contact, and audience flow.
Open full routeCountry, street autocomplete, suburb, state, postcode, and delivery override.
Open full routeKeyword, price range, category, vehicle, supplier toggle, and sort menu.
Open full routeDrop zone, file list, progress, type/size validation, remove, and submit.
Open full routeStar rating, category, title, message, photo attachment, and anonymity toggle.
Open full routeRecommendation scale, multi-select improvements, ranked list, notes, and slider.
Open full routeLogin, password, OTP, recovery, session trust, and security consent.
Profile, team invite, role, bay assignment, notification preference, and save state.
Card details, billing address, ABN, invoice contact, tax toggle, and receipt email.
Line item editing, discount, terms, signer, signature method, and acceptance.
Date range, time, recurrence, bay, technician, and conflict check.
Identity evidence, declaration, consent, data request, policy version, and signoff.
Catalog upload, SKU creation, order acknowledgement, invoice, and compliance cert.
Time off, shift swap, technician profile, bay assignment, and training signoff.
Field builder, validation rules, conditional logic, workflow variables, and admin query filters.
Reply body, internal note, macro picker, mention picker, priority, and resolve toggle.
Customer, shipping, delivery, payment method, order notes, and terms acceptance.
Notification channel rules, quiet hours, role scope, access request, and approval reason.
Subject, preheader, audience, personalization token, test recipient, and send check.