Components · Forms
Forms
Default: a labelled native control. Add one field only when the decision needs the answer.
Start with one native field
Install @subconscious/subconscious-base. Use .field, .input and .help; no field dependency. The label, bounds and browser validation stay native.
<div class="field">
<label for="target">Service target</label>
<input id="target" name="service-target" autocomplete="off" class="input" type="number"
min="90" max="99" required aria-describedby="target-help">
<p id="target-help" class="help">90–99%.</p>
</div>
Inspect the same field in the product register. Form composition owns the rules.
Distinct input jobs
Text, selection, notes and range retain browser semantics. These are sample values.
Product fields
Use these specialist controls when a native field cannot complete the job. Pro source stays in the licensed consumer.
Workspace address
Password
Verification
Keyboard shortcut
Date range
Natural date
Invitations
Invite teammates by email or link, then finish sign-up from the invite. Names and addresses are samples.
Sign up from an invite
Invite teammates
When the input is an open question
ai-input-search owns prompt entry, attachment and search mode. Install that public item only for a question workflow.