Skip to content

Item

Copy editable source into an initialized application:

Terminal window
pnpm dlx @simurgh-ui/cli add item

For package consumption, import from the component subpath and load its optional recipe CSS:

import {
ItemGroup,
Item,
ItemMedia,
ItemContent,
ItemTitle,
ItemDescription,
ItemActions,
} from '@simurgh-ui/react/item';
import '@simurgh-ui/styles/item.css';
import {
ItemGroup,
Item,
ItemMedia,
ItemContent,
ItemTitle,
ItemDescription,
ItemActions,
} from '@simurgh-ui/vue/item';
import '@simurgh-ui/styles/item.css';
import {
ItemGroupComponent,
ItemComponent,
ItemMediaComponent,
ItemContentComponent,
ItemTitleComponent,
ItemDescriptionComponent,
ItemActionsComponent,
} from '@simurgh-ui/angular/item';
import '@simurgh-ui/styles/item.css';

Omit the component stylesheet for fully headless styling. CLI-copied components use the local path written to simurgh.json and the copied application styles instead of these package imports.

Item structures repeated rows such as files, settings, notifications, and search results. Item Group and Item provide native list/listitem roles while the remaining parts keep media, text, and actions consistently aligned.

The optional recipe supplies layout and stable structure without a strong visual treatment. Product typography, color, and emphasis remain consumer-owned.

Live component Item

Design system

Updated two minutes ago

The public component parts are listed in API surface below. Use only the parts needed by the example; compound components depend on their documented parent/child nesting.

This component exposes no public controlled/uncontrolled state pair. Configure it through the props, events, native attributes, or parent-owned state documented in the API tables.

Give the group an accessible name when multiple lists occur on the same page. Media is decorative by default; set decorative to false when its accessible content adds information not repeated by the title or description.

<ItemGroup aria-label="Projects">
<Item>
<ItemMedia>D</ItemMedia>
<ItemContent>
<ItemTitle>Design system</ItemTitle>
<ItemDescription>Updated two minutes ago</ItemDescription>
</ItemContent>
<ItemActions>
<Button>Open</Button>
</ItemActions>
</Item>
</ItemGroup>

Preserve the documented composition and accessible names when wrapping or restyling this component. See accessibility and RTL guidance for keyboard, focus, labeling, and directionality requirements.

  • React exports: ItemGroup, Item, ItemMedia, ItemContent, ItemTitle, ItemDescription, ItemActions
  • Vue exports: ItemGroup, Item, ItemMedia, ItemContent, ItemTitle, ItemDescription, ItemActions
  • Angular exports: ItemGroupComponent, ItemComponent, ItemMediaComponent, ItemContentComponent, ItemTitleComponent, ItemDescriptionComponent, ItemActionsComponent

Import these public symbols from the component subpath shown in Installation. Framework-specific props, events, slots, directives, methods, defaults, and native-attribute behavior belong in the API tables on this page; use the linked source only to verify the current implementation.

React API reference

An inherited-attributes entry means the component accepts the complete named React native interface, including its event handlers and ARIA and data attributes. Remaining attributes are forwarded to the rendered element unless the component behavior described on this page overrides them.

Inherited attributes: HTMLAttributes<HTMLDivElement> & RefAttributes<HTMLDivElement>.

PropTypeDefault / requirement
childrenReactNodeundefined
refRef<HTMLDivElement> | undefinedundefined

Inherited attributes: HTMLAttributes<HTMLDivElement> & RefAttributes<HTMLDivElement>.

PropTypeDefault / requirement
childrenReactNodeundefined
refRef<HTMLDivElement> | undefinedundefined

Inherited attributes: HTMLAttributes<HTMLDivElement> & RefAttributes<HTMLDivElement>.

PropTypeDefault / requirement
childrenReactNodeundefined
decorativebooleantrue
refRef<HTMLDivElement> | undefinedundefined

Inherited attributes: HTMLAttributes<HTMLDivElement> & RefAttributes<HTMLDivElement>.

PropTypeDefault / requirement
childrenReactNodeundefined
refRef<HTMLDivElement> | undefinedundefined

Inherited attributes: HTMLAttributes<HTMLHeadingElement> & RefAttributes<HTMLHeadingElement>.

PropTypeDefault / requirement
childrenReactNodeundefined
refRef<HTMLHeadingElement> | undefinedundefined

Inherited attributes: HTMLAttributes<HTMLParagraphElement> & RefAttributes<HTMLParagraphElement>.

PropTypeDefault / requirement
childrenReactNodeundefined
refRef<HTMLParagraphElement> | undefinedundefined

Inherited attributes: HTMLAttributes<HTMLDivElement> & RefAttributes<HTMLDivElement>.

PropTypeDefault / requirement
childrenReactNodeundefined
refRef<HTMLDivElement> | undefinedundefined
Vue API reference

Boolean props without explicit defaults use Vue’s false default. Undeclared attributes follow the fallthrough behavior stated for each component.

Vue attribute fallthrough is enabled for the rendered root.

No declared props.

No emitted events.

Slots: default.

Exposed methods: none.

Vue attribute fallthrough is enabled for the rendered root.

No declared props.

No emitted events.

Slots: default.

Exposed methods: none.

Vue attribute fallthrough is enabled for the rendered root.

PropTypeDefault / requirement
decorativebooleantrue

No emitted events.

Slots: default.

Exposed methods: none.

Vue attribute fallthrough is enabled for the rendered root.

No declared props.

No emitted events.

Slots: default.

Exposed methods: none.

Vue attribute fallthrough is enabled for the rendered root.

No declared props.

No emitted events.

Slots: default.

Exposed methods: none.

Vue attribute fallthrough is enabled for the rendered root.

No declared props.

No emitted events.

Slots: default.

Exposed methods: none.

Vue attribute fallthrough is enabled for the rendered root.

No declared props.

No emitted events.

Slots: default.

Exposed methods: none.

Angular API reference

Inputs and outputs use their public template names. Public methods are callable through a template reference or ViewChild. Native attributes apply to the documented template root or directive host; they are not automatically forwarded through component hosts.

Component selector: simurgh-item-group. The template’s first native element is ng-content. Angular host bindings: { role: 'list', '[attr.data-slot]': "'item-group'" }.

No inputs.

No outputs.

Content projection: default.

No public methods.

Component selector: simurgh-item. The template’s first native element is ng-content. Angular host bindings: { role: 'listitem', '[attr.data-slot]': "'item'" }.

No inputs.

No outputs.

Content projection: default.

No public methods.

Component selector: simurgh-item-media. The template’s first native element is ng-content. Angular host bindings: { '[attr.aria-hidden]': 'decorative \|\| null', '[attr.data-slot]': "'item-media'", }.

InputTypeDefault / requirement
decorativebooleantrue

No outputs.

Content projection: default.

No public methods.

Component selector: simurgh-item-content. The template’s first native element is ng-content. Angular host bindings: { '[attr.data-slot]': "'item-content'" }.

No inputs.

No outputs.

Content projection: default.

No public methods.

Component selector: simurgh-item-title. The template’s first native element is h3.

No inputs.

No outputs.

Content projection: default.

No public methods.

Component selector: simurgh-item-description. The template’s first native element is p.

No inputs.

No outputs.

Content projection: default.

No public methods.

Component selector: simurgh-item-actions. The template’s first native element is ng-content. Angular host bindings: { '[attr.data-slot]': "'item-actions'" }.

No inputs.

No outputs.

Content projection: default.

No public methods.

Follow the framework example as a structural contract. Root components own shared state; parts that consume that state must stay under the root (or be attached to projected descendants in Angular). Parts described as conditional are optional until their corresponding interaction or semantic region is used. Do not render a state-consuming part by itself.

FrameworkRequired parent/child relationshipConditional partsSupporting types
ReactRender ItemGroup as the ancestor. Nest the listed parts inside that root so they can read its shared state/context.Item, ItemMedia, ItemContent, ItemTitle, ItemDescription, ItemActions are conditional parts: include only those needed by the documented anatomy. A trigger/control and its matching content/item are required when that interaction is used.None.
VueRender ItemGroup as the ancestor. Nest the listed parts inside that root so they can read its shared state/context.Item, ItemMedia, ItemContent, ItemTitle, ItemDescription, ItemActions are conditional parts: include only those needed by the documented anatomy. A trigger/control and its matching content/item are required when that interaction is used.None.
AngularCreate ItemGroupComponent first. Attach listed directives to elements inside its projected content; nested component parts must remain inside it.ItemComponent, ItemMediaComponent, ItemContentComponent, ItemTitleComponent, ItemDescriptionComponent, ItemActionsComponent are conditional parts: include only those needed by the documented anatomy. A trigger/control and its matching content/item are required when that interaction is used.None.

Accessible names, descriptions, and form labels remain required whenever the component’s purpose cannot otherwise be determined, even when the corresponding visual part is optional.

The adapters target the same user-visible behavior and accessibility contract. Their public shapes follow each framework’s conventions and are not expected to be symbol-for-symbol identical.

ConcernContract
Public compositionAll adapters export 7 public symbols, with framework-idiomatic names.
State and change eventsNo controlled state contract; use native attributes, inputs, or events documented above.
Children and contentReact uses children; Vue uses the slots listed above; Angular uses the documented content projection selectors.
Native attributesReact forwards the named native interface; Vue follows the stated fallthrough rule; Angular attributes apply to the component host unless an input, directive, or documented native root consumes them.
Imperative accessReact forwards native refs; Vue exposes no methods; Angular exposes no public methods.

These differences are intentional adapter design. Behavioral or accessibility differences not stated on this page are parity defects rather than supported variations.

This component is not a form control and does not contribute a named value to FormData. Use it to structure or describe a form only when its purpose and accessibility guidance apply.

The table distinguishes component behavior from application-owned presentation. “Not supported” means there is no public state contract for that adapter; do not invent one with an undocumented attribute. Keep status and error messages accessible when they are rendered outside the component.

StateReactVueAngular
LoadingNot supported by this component API; handle this state in surrounding application UI.Not supported by this component API; handle this state in surrounding application UI.Not supported by this component API; handle this state in surrounding application UI.
EmptyNot supported by this component API; handle this state in surrounding application UI.Not supported by this component API; handle this state in surrounding application UI.Not supported by this component API; handle this state in surrounding application UI.
InvalidNot supported by this component API; handle this state in surrounding application UI.Not supported by this component API; handle this state in surrounding application UI.Not supported by this component API; handle this state in surrounding application UI.
Read-onlyNot supported by this component API; handle this state in surrounding application UI.Not supported by this component API; handle this state in surrounding application UI.Not supported by this component API; handle this state in surrounding application UI.
DisabledNot supported by this component API; handle this state in surrounding application UI.Not supported by this component API; handle this state in surrounding application UI.Not supported by this component API; handle this state in surrounding application UI.
ErrorNot supported by this component API; handle this state in surrounding application UI.Not supported by this component API; handle this state in surrounding application UI.Not supported by this component API; handle this state in surrounding application UI.
Styling contract

The selectors below are used by the published component recipe or emitted consistently by an adapter. Treat these as the supported styling surface. Element order, anonymous wrappers, and undocumented descendants are implementation details and should not be targeted.

SurfaceStable hooks
Recipe classes.simurgh-item, .simurgh-trigger
Stable DOM parts[data-slot="item"], [data-slot="item-actions"], [data-slot="item-content"], [data-slot="item-description"], [data-slot="item-group"], [data-slot="item-media"], [data-slot="item-title"], [data-slot="menubar-item"], [data-slot="select-option"]
Stable data attributes[data-density], [data-highlighted], [data-slot]
ARIA/state selectors used by the recipe[aria-disabled]
CSS custom properties consumed--simurgh-border, --simurgh-item-height, --simurgh-muted, --simurgh-muted-foreground, --simurgh-radius, --simurgh-ring, --simurgh-surface

Prefer a semantic token override for theme-wide changes. Use the listed class or part selectors for a component-scoped override. When omitting recipe CSS, preserve state attributes and ARIA semantics even if your replacement styles use different selectors.

Load the optional component stylesheet for the default recipe, override semantic tokens for broad theme changes, or omit the recipe CSS for headless styling. See theming and styling hooks for import order, selectors, dark mode, RTL, and reduced-motion guidance.

Last verified on 2026-08-13 against Simurgh registry 0.1.1.