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

Fieldset

A semantic form section with legend, guidance, grouped fields, and disabled state.

Source
app/components/nitro_kit/fieldset.rb
API
NitroKit::Fieldset.new(legend:, description:, disabled:) { fields }

Semantic boundaries

A native fieldset owns one legend, optional guidance, and an explicit fields region.

Boundary states

Empty
Optional advanced settings

No advanced settings are available for this plan.

Disabled
Legacy synchronization

Locked while migration is in progress.

Viewport640 px · sm
Rubytest/dummy/app/components/gallery/components/fieldset_page.rb
sample("Empty", slug: "empty") do
  render NitroKit::Fieldset.new(
    legend: "Optional advanced settings",
    description: "No advanced settings are available for this plan.",
    html: { id: "gallery-fieldset-empty" }
  ) { nil }
end
sample("Disabled", slug: "disabled") do
  render NitroKit::Fieldset.new(
    legend: "Legacy synchronization",
    description: "Locked while migration is in progress.",
    disabled: true,
    name: "legacy-sync",
    html: { id: "gallery-fieldset-disabled" }
  ) do
    render NitroKit::Field.new(
      nil,
      :destination,
      id: "gallery-fieldset-disabled-destination",
      name: "legacy[destination]",
      value: "Compliance archive",
      label: "Destination"
    )
  end
end

Compound legend and description

Deployment targets

Production changes require two approvals.

Viewport640 px · sm
Rubytest/dummy/app/components/gallery/components/fieldset_page.rb
render NitroKit::Fieldset.new(html: { id: "gallery-fieldset-compound" }) do |fieldset|
  fieldset.legend("Deployment targets")
  fieldset.description do
    plain "Production changes require "
    strong { "two" }
    plain " approvals."
  end
  render NitroKit::Field.new(
    nil,
    :approvers,
    as: :number,
    id: "gallery-fieldset-compound-approvers",
    name: "deployment[approvers]",
    value: 2,
    label: "Required approvers",
    min: 1,
    max: 5
  )
end

Long policy section

Production credential rotation and revocation policy for deployment targets

Replacement credentials are distributed before the current credential expires. Revocation begins only after every target confirms receipt.

Viewport640 px · sm
Rubytest/dummy/app/components/gallery/components/fieldset_page.rb
render NitroKit::Fieldset.new(
  legend: "Production credential rotation and revocation policy for deployment targets",
  description: "Replacement credentials are distributed before the current credential expires. Revocation begins only after every target confirms receipt.",
  html: { id: "gallery-fieldset-long" }
) do
  render NitroKit::FieldGroup.new(html: { id: "gallery-fieldset-long-fields" }) do
    render NitroKit::Field.new(
      nil,
      :rotation_window,
      as: :number,
      id: "gallery-fieldset-rotation-window",
      name: "credential_policy[rotation_window]",
      value: 14,
      label: "Rotation window in days",
      min: 1,
      max: 90,
      required: true
    )
    render NitroKit::Field.new(
      nil,
      :automatic_rotation,
      as: :switch,
      id: "gallery-fieldset-automatic-rotation",
      name: "credential_policy[automatic_rotation]",
      label: "Generate replacement credentials automatically",
      checked: true
    )
  end
end

Rails form builder

A real model-backed multipart form composes builder fieldsets, groups, errors, choices, and actions.

Registration details

Registration details

Required fields preserve Rails validation and submission behavior.

Used only for the registration receipt.
  • Email is invalid
  • Role is not included in the list
  • Terms must be accepted
Viewport640 px · sm
Rubytest/dummy/app/components/gallery/components/fieldset_page.rb
registration = Registration.new(email: "not-an-email", role: "", terms: false, source: "gallery")
registration.validate

form_with(
  model: registration,
  scope: :registration,
  url: "#registration-details",
  builder: NitroKit::FormBuilder,
  id: "gallery-fieldset-registration-form"
) do |form|
  form.hidden_field(:source, id: "gallery-fieldset-registration-source")
  form.fieldset(
    legend: "Registration details",
    description: "Required fields preserve Rails validation and submission behavior.",
    html: { id: "gallery-fieldset-registration" }
  ) do
    form.group(html: { id: "gallery-fieldset-registration-fields" }) do
      form.field(
        :email,
        as: :email,
        id: "gallery-fieldset-registration-email",
        description: "Used only for the registration receipt.",
        required: true
      )
      form.field(
        :role,
        as: :select,
        id: "gallery-fieldset-registration-role",
        label: "Role",
        prompt: "Choose a role",
        options: [ [ "Developer", "developer" ], [ "Designer", "designer" ] ],
        required: true
      )
      form.field(
        :terms,
        as: :checkbox,
        id: "gallery-fieldset-registration-terms",
        label: "I accept the workspace terms",
        required: true
      )
      form.field(
        :attachment,
        as: :file,
        id: "gallery-fieldset-registration-attachment",
        label: "Supporting note",
        accept: "text/plain"
      )
    end
    form.submit("Register", id: "gallery-fieldset-registration-save")
  end
end

Component contract

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

docs/component_contracts.md · NitroKit::Fieldset

Constructor-specific options
  • legend: nil, description: nil, disabled: false, name: nil
Root and closed vocabulary
native fieldset[data-nk=fieldset]
Contract
Requires a content block and a legend through the constructor or the matching legend compound method; description accepts either form too. Declarations may appear anywhere in the block and always render legend → description → fields.

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.