When to use it

Use Input for search, form fields, and inline edits where the SDK should keep spacing, focus treatment, and invalid states consistent.

Choose outlined when the field needs a clear boundary inside a longer form. Choose plain when the field sits inside a denser toolbar, filter row, or lightweight editorial surface.

Composition notes

• Use startSlot and endSlot for icons, shortcuts, or compact status markers.
• Keep decorators presentational. Screen reader labels and helper copy should stay outside the slot content.
• Pair the field with Label, helper text, and error text in the surrounding layout instead of trying to bake those concerns into the input itself.

State and theming guidance

Input already includes focus, disabled, and invalid states. Prefer semantic tokens like --radius, --enad-input-height, and --enad-input-px over one-off utility overrides so the field stays aligned with the rest of the control system.

If a surface needs a lower-emphasis treatment, switch to variant="plain" before replacing borders or padding by hand. That keeps the behavior consistent while letting the page feel lighter.