Skip to content
Nitro Kitv2.0.0.alpha.4

Search gallery…

IntroductionGalleryAgent guideGalleryHuman guideGalleryColorsFoundations · ThemeTypographyFoundations · ThemeSpacing & sizingFoundations · ThemeEffectsFoundations · ThemeButtonComponents · ActionsButton groupComponents · ActionsButton toComponents · ActionsAppearance pickerComponents · FormsCheckboxComponents · FormsCheckbox groupComponents · FormsComboboxComponents · FormsControl groupComponents · FormsDropzoneComponents · FormsFieldComponents · FormsField groupComponents · FormsFieldsetComponents · FormsInputComponents · FormsLabelComponents · FormsRadio buttonComponents · FormsRadio button groupComponents · FormsRich text areaComponents · FormsSelectComponents · FormsSwitchComponents · FormsTextareaComponents · FormsCommand paletteComponents · OverlaysDialogComponents · OverlaysDropdownComponents · OverlaysSheetComponents · OverlaysTooltipComponents · OverlaysAlertComponents · FeedbackEmpty stateComponents · FeedbackToastComponents · FeedbackAccordionComponents · Data displayAvatarComponents · Data displayAvatar stackComponents · Data displayBadgeComponents · Data displayDetails tableComponents · Data displayIconComponents · Data displayProgressive imageComponents · Data displayStat gridComponents · Data displayTableComponents · Data displayTypesetComponents · Data displayPaginationComponents · NavigationPagination barComponents · NavigationTabsComponents · NavigationToolbarComponents · NavigationCardComponents · LayoutContainerComponents · LayoutFlexComponents · LayoutGridComponents · LayoutApplication navigationComponents · ApplicationApplication shellComponents · ApplicationAuthentication shellComponents · ApplicationDanger zoneComponents · ApplicationData sectionComponents · ApplicationForm sectionComponents · ApplicationPage headerComponents · ApplicationSettings layoutComponents · ApplicationSign inCompositions · Access & onboardingPassword resetCompositions · Access & onboardingEmail verificationCompositions · Access & onboardingInvitation acceptanceCompositions · Access & onboardingAccount creationCompositions · Access & onboardingAccount securityCompositions · Access & onboardingWorkspace onboardingCompositions · Access & onboardingBranched onboardingCompositions · Access & onboardingWorkspace dashboardCompositions · Workspace & organizationWorkspace settingsCompositions · Workspace & organizationWorkspace usersCompositions · Workspace & organizationTeam managementCompositions · Workspace & organizationAPI credentialsCompositions · Workspace & organizationOrganization overviewCompositions · Workspace & organizationOrganization settingsCompositions · Workspace & organizationTeam activityCompositions · Workspace & organizationTeam memberCompositions · Workspace & organizationSubscription billingCompositions · Billing & commerceCheckout and paymentCompositions · Billing & commerceCheckout resultsCompositions · Billing & commerceData resource overviewCompositions · Data & operationsData resource activityCompositions · Data & operationsData resource settingsCompositions · Data & operationsProduct resource lifecycleCompositions · Data & operationsAPI webhooksCompositions · Data & operationsIntegration managementCompositions · Data & operationsFile uploadsCompositions · Data & operationsActivity and audit logCompositions · Data & operationsChangelogCompositions · Product & supportHelp centerCompositions · Product & supportSystem status and errorsCompositions · Product & supportProduct landingCompositions · MarketingPublic pricingCompositions · MarketingProduct featuresCompositions · MarketingPublic contactCompositions · MarketingSidebar operations applicationCompositions · Complete applicationsTopbar media applicationCompositions · Complete applicationsHybrid account applicationCompositions · Complete applications

No destinations found.

  • Introduction
  • Agent guide
  • Human guide
  • Foundations
    • Colors
    • Typography
    • Spacing & sizing
    • Effects
  • Actions
    • Button
    • Button group
    • Button to
  • Forms
    • Appearance picker
    • Checkbox
    • Checkbox group
    • Combobox
    • Control group
    • Dropzone
    • Field
    • Field group
    • Fieldset
    • Input
    • Label
    • Radio button
    • Radio button group
    • Rich text area
    • Select
    • Switch
    • Textarea
  • Overlays
    • Command palette
    • Dialog
    • Dropdown
    • Sheet
    • Tooltip
  • Feedback
    • Alert
    • Empty state
    • Toast
  • Data display
    • Accordion
    • Avatar
    • Avatar stack
    • Badge
    • Details table
    • Icon
    • Progressive image
    • Stat grid
    • Table
    • Typeset
  • Navigation
    • Pagination
    • Pagination bar
    • Tabs
    • Toolbar
  • Layout
    • Card
    • Container
    • Flex
    • Grid
  • Application
    • Application navigation
    • Application shell
    • Authentication shell
    • Danger zone
    • Data section
    • Form section
    • Page header
    • Settings layout
  • Access & onboarding
    • Sign in
    • Password reset
    • Email verification
    • Invitation acceptance
    • Account creation
    • Account security
    • Workspace onboarding
    • Branched onboarding
  • Workspace & organization
    • Workspace dashboard
    • Workspace settings
    • Workspace users
    • Team management
    • API credentials
    • Organization overview
    • Organization settings
    • Team activity
    • Team member
  • Billing & commerce
    • Subscription billing
    • Checkout and payment
    • Checkout results
  • Data & operations
    • Data resource overview
    • Data resource activity
    • Data resource settings
    • Product resource lifecycle
    • API webhooks
    • Integration management
    • File uploads
    • Activity and audit log
  • Product & support
    • Changelog
    • Help center
    • System status and errors
  • Marketing
    • Product landing
    • Public pricing
    • Product features
    • Public contact
  • Complete applications
    • Sidebar operations application
    • Topbar media application
    • Hybrid account application

Input

Native input controls with explicit HTML semantics.

Source
app/components/nitro_kit/input.rb
API
NitroKit::Input.new(type:, id:, name:, value:)

Native types

Representative browser types keep native value, completion, placeholder, and requirement semantics.

Type matrix

Workspace name
Account email
Password
Search members
Seat limit
Renewal date
Webhook URL
Legacy account ID
ViewportFull width
Rubytest/dummy/app/components/gallery/components/input_page.rb
Gallery::Data.input_examples.each do |input|
  sample(input.label, slug: input.slug) do
    render_input(input)
  end
end

Specialized controls

Boolean, file, and range controls retain their browser-specific attributes.

Specialized types

Checked checkbox
File upload
Range
Viewport640 px · sm
Rubytest/dummy/app/components/gallery/components/input_page.rb
sample("Checked checkbox", slug: "checkbox") do
  render NitroKit::Input.new(
    type: :checkbox,
    id: "gallery-input-checkbox",
    name: "preferences[weekly_digest]",
    value: "1",
    checked: true,
    aria: { label: "Send weekly digest" }
  )
end
sample("File upload", slug: "file") do
  render NitroKit::Input.new(
    type: :file,
    id: "gallery-input-file",
    name: "profile[avatar]",
    accept: "image/png,image/jpeg",
    aria: { label: "Profile image" }
  )
end
sample("Range", slug: "range") do
  render NitroKit::Input.new(
    type: :range,
    id: "gallery-input-range",
    name: "notifications[volume]",
    value: 60,
    min: 0,
    max: 100,
    step: 10,
    aria: { label: "Notification volume" }
  )
end

Date controls

Date selection is an ordinary native input with server-verifiable constraints and normalized cross-browser alignment.

Date matrix

Empty
Selected
Required range
Read only
Disabled
Viewport640 px · sm
Rubytest/dummy/app/components/gallery/components/input_page.rb
sample("Empty", slug: "empty") do
  render_date("gallery-input-date-empty", aria: { label: "Start date" })
end
sample("Selected", slug: "selected") do
  render_date(
    "gallery-input-date-selected",
    value: Date.new(2026, 7, 13),
    aria: { label: "Start date" }
  )
end
sample("Required range", slug: "required-range") do
  render_date(
    "gallery-input-date-required",
    min: Date.new(2026, 7, 13),
    max: Date.new(2026, 8, 13),
    required: true,
    aria: { label: "Deployment date" }
  )
end
sample("Read only", slug: "readonly") do
  render_date(
    "gallery-input-date-readonly",
    value: Date.new(2026, 7, 13),
    readonly: true,
    aria: { label: "Invoice date" }
  )
end
sample("Disabled", slug: "disabled") do
  render_date(
    "gallery-input-date-disabled",
    value: Date.new(2026, 7, 13),
    disabled: true,
    aria: { label: "Archived date" }
  )
end

Schedule a release

Schedule production release

Choose a weekday within the next thirty days.
Viewport640 px · sm
Rubytest/dummy/app/components/gallery/components/input_page.rb
render NitroKit::Card.new(id: "gallery-input-date-release-card") do |card|
  card.title("Schedule production release", level: 3)
  card.body do
    form(id: "gallery-input-date-release-form", action: "/gallery/releases", method: "post") do
      render NitroKit::FieldGroup.new do
        render NitroKit::Field.new(
          nil,
          :release_date,
          as: :date,
          id: "gallery-input-date-release-date",
          name: "release[date]",
          label: "Release date",
          description: "Choose a weekday within the next thirty days.",
          value: Date.new(2026, 7, 20),
          min: Date.new(2026, 7, 13),
          max: Date.new(2026, 8, 12),
          required: true
        )
        render NitroKit::Button.new(
          "Schedule release",
          id: "gallery-input-date-schedule",
          type: :submit,
          variant: :primary
        )
      end
    end
  end
end

Month and ISO week

Native month and week types are progressive enhancement. The server must validate YYYY-MM or YYYY-Www and all range rules.

Native month
Enter YYYY-MM if your browser does not provide a picker.
Native ISO week
Enter YYYY-Www if your browser does not provide a picker.
Exact month choice
Use explicit application-owned options when only these periods are valid.
Viewport640 px · sm
Rubytest/dummy/app/components/gallery/components/input_page.rb
sample("Native month", slug: "month") do
  render NitroKit::Field.new(
    nil,
    :billing_month,
    as: :month,
    id: "gallery-input-month",
    name: "billing[month]",
    value: "2026-08",
    label: "Billing month",
    description: "Enter YYYY-MM if your browser does not provide a picker.",
    min: "2026-01",
    max: "2026-12",
    required: true
  )
end
sample("Native ISO week", slug: "week") do
  render NitroKit::Field.new(
    nil,
    :delivery_week,
    as: :week,
    id: "gallery-input-week",
    name: "delivery[week]",
    value: "2026-W32",
    label: "Delivery week",
    description: "Enter YYYY-Www if your browser does not provide a picker.",
    required: true
  )
end
sample("Exact month choice", slug: "month-select") do
  render NitroKit::Field.new(
    nil,
    :reporting_month,
    as: :select,
    id: "gallery-input-month-select",
    name: "report[month]",
    value: "2026-08",
    label: "Reporting month",
    description: "Use explicit application-owned options when only these periods are valid.",
    options: [ [ "July 2026", "2026-07" ], [ "August 2026", "2026-08" ] ]
  )
end

Validation and availability

Required, invalid, read-only, and disabled state remains inspectable in native attributes.

Control states

Invalid

Enter a valid email address

Length limited
Read only
Disabled
Viewport640 px · sm
Rubytest/dummy/app/components/gallery/components/input_page.rb
sample("Invalid", slug: "invalid") do
  render NitroKit::Input.new(
    type: :email,
    id: "gallery-input-invalid",
    name: "billing[email]",
    value: "not-an-email",
    required: true,
    aria: { label: "Billing email", invalid: true, describedby: "gallery-input-invalid-error" }
  )
  p(id: "gallery-input-invalid-error") { "Enter a valid email address" }
end
sample("Length limited", slug: "length") do
  render NitroKit::Input.new(
    id: "gallery-input-length",
    name: "workspace[slug]",
    value: "mothership",
    minlength: 3,
    maxlength: 24,
    aria: { label: "Workspace slug" }
  )
end
sample("Read only", slug: "readonly") do
  render NitroKit::Input.new(
    id: "gallery-input-readonly",
    value: "acct_42NK",
    readonly: true,
    aria: { label: "Account identifier" }
  )
end
sample("Disabled", slug: "disabled") do
  render NitroKit::Input.new(
    id: "gallery-input-disabled-state",
    value: "Unavailable",
    disabled: true,
    aria: { label: "Legacy setting" }
  )
end

Component contract

Constructor options, rendered root, closed vocabularies, and compound boundary for this component, exactly as shipped.

docs/component_contracts.md · NitroKit::Input

Constructor-specific options
  • type: :text, id: nil, name: nil, value: nil, placeholder: nil, disabled: false, readonly: false, required: false, autocomplete: nil, min: nil, max: nil, step: nil, minlength: nil, maxlength: nil, multiple: false, accept: nil, pattern: nil, inputmode: nil, checked: nil
Root and closed vocabulary
native input[data-nk=input]; types button checkbox color date datetime-local email file hidden month number password radio range search tel text time url week
Contract
Every owned attribute is a keyword; passing one through html: raises and names the keyword. type: :file with a value: raises. Boolean attributes and length constraints are validated; minimum length cannot exceed maximum. Read-only controls have their own muted treatment. date receives the Safari editor-alignment fix. month and week retain their native types only as progressive enhancement: browsers may expose text entry without picker, normalization, or min/max/step enforcement. Applications must server-validate YYYY-MM or YYYY-Www plus range and step rules, and should compose an application-owned Select for exact bounded choices.

Relevant patterns

Application conventions this component belongs to. Each summary is the leading section of its pattern document.

docs/patterns/resource_form.md

Resource form

  • One model-backed Phlex component renders initial and invalid states.
  • Rails owns names, values, and errors; Nitro owns presentation.
  • Invalid mutations render the same model with 422; success redirects with 303.
  • Use one primary submit: the shell toolbar owns it, or a standalone form keeps it inside form.group.
  • Wrap the form in a Turbo Frame only when it needs an independent lifecycle.

System rules for coding agents

Instructions for coding agents, repeated on every component page so one fetched page has enough context. Humans can usually skip this section.

test/dummy/app/components/gallery/agent_rules.rb

View agent instructions
  • Nitro Kit 2.0 is a gem-owned, Phlex-only UI system for Rails. Render components directly: render NitroKit::Button.new("Save", variant: :primary).
  • Compose Nitro components inside application-owned Phlex classes. Public initializers and declared slots are the component API; private methods are not.
  • Public options are explicit keywords, and enumerated options are closed vocabularies. Invalid names or values raise ArgumentError; this component's accepted options are in the contract above.
  • Pass native attributes through their typed boundary: html: for HTML, aria: for ARIA, and data: for application data. class and style are forbidden, including inside html:.
  • Nitro owns NitroKit::Component::RESERVED_DATA_ATTRIBUTES: data-nk, data-slot, data-variant, data-size, data-nk-escape, data-enhanced, data-state, data-disabled, data-required, data-orientation, data-presentation, data-placement, data-layout, data-side, data-field-type, data-dir, data-gap, data-align, data-justify, data-wrap, data-cols, data-mode, data-key. Do not pass them through data:. data-action, data-controller are additive and compose with Nitro behavior.
  • If an integration truly requires a class, use desperately_need_a_class:. It requires a non-blank String and marks the exception with data-nk-escape="class".
  • Every root emits data-nk; owned parts emit component-qualified data-slot values such as field-control or card-title. Select on those attributes, never on classes.
  • Customize components with documented --nk-* custom properties in an application stylesheet. Variables beginning with --_nk-* are private component mechanics.
  • Use NitroKit::Flex and NitroKit::Grid for layout. Parents own external placement and available width; components own their intrinsic geometry.
  • Preserve native elements and accessibility semantics. State is exposed through native semantics and ARIA first, and through data-state when styling or behavior also needs it.