Item

Presentation row with native content and action slots.

All components · Theme builder · Implementation source

Live preview

Install

Shell

netscript ui:add item

Usage and examples

The preview runs this JSX with the installed components. Import any composed primitives from your UI directory.

TypeScript

import { useState } from 'preact/hooks';
import { Item } from '@app/components/ui/item.tsx';

export function Example() {
  const [value, setValue] = useState('standard');
  const [open, setOpen] = useState(false);
  const [notice, report] = useState('');
  return (<><div><Item title="Order SO–10480">Ready for fulfillment</Item></div><p role="status">{notice}</p></>);
}

Props

Generated from native deno doc --json --private over the shipped implementation. Compound component props retain their owning interface; native attributes pass through where declared.

Owner	Prop	Type	Optional
`ItemProps`	`title`	`ComponentChildren`	No
`ItemProps`	`description`	`ComponentChildren`	Yes
`ItemProps`	`media`	`ComponentChildren`	Yes
`ItemProps`	`actions`	`ComponentChildren`	Yes
`ItemProps`	`header`	`ComponentChildren`	Yes
`ItemProps`	`footer`	`ComponentChildren`	Yes
`ItemProps`	`chevron`	`boolean`	Yes
`ItemProps`	`variant`	`"default" \| "outline" \| "muted"`	Yes
`ItemProps`	`size`	`"default" \| "sm" \| "xs"`	Yes
`ItemProps`	`class`	`string`	Yes

TypeScript

ItemProps extends Omit<JSX.HTMLAttributes<HTMLDivElement>, "title" | "size" | "class">

Keyboard

Key	Action
`Tab/Shift+Tab`	Move between native child controls
`Enter/Space`	Activate native child buttons; links use Enter

Tokens

Semantic contract roles: border/default, radius/badge, radius/input, space/card/padding, space/stack/gap, surface/muted, text/muted.

CSS custom properties referenced directly: --ns-border, --ns-border-width, --ns-card-padding, --ns-control-gap, --ns-fg, --ns-muted, --ns-muted-fg, --ns-radius-badge, --ns-radius-input, --ns-ring, --ns-space-1, --ns-space-2, --ns-stack-gap, --ns-text-caption, --ns-text-small, --ns-text-strong, --ns-weight-strong.

Contract and compatibility

Accessibility pattern: noninteractive presentation

Native child controls retain their own semantics and keyboard behavior; no wrapper key manager.

Design contract values marked planned are not implementation props. The props above describe what ships today.