Getting StartedInstall and bootstrap headless foundations 4
LayoutHeadless structural primitives for expandable and container patterns 6
OverlayHeadless modal and floating layer behavior 3
FeedbackHeadless notification and status communication patterns 5
FormHeadless input and selection contracts 17
UtilityReusable action, identity, and clipboard behavior 6
NavigationHeadless trails, trees, menus, and command surfaces 7

API reference

Headless card is a slot-only primitive surface. It adds stable data-slot hooks and otherwise leaves semantics, content, and interaction flow to your markup.

Root and slots

Attach the directives to the elements that already make sense for your content model rather than wrapping everything in non-semantic containers.

Headless card attachment

html
<article tngCard>
  <div tngCardMedia>...</div>
  <header tngCardHeader>
    <h3 tngCardTitle>Roadmap update</h3>
    <p tngCardDescription>Plan next-quarter work and owners.</p>
  </header>
  <section tngCardContent>...</section>
  <hr tngCardDivider />
  <footer tngCardFooter>
    <a tngCardLink href="/roadmap">Open board</a>
    <div tngCardActions>...</div>
  </footer>
</article>
DirectiveSelectorSlotPurpose
TngCard[tngCard]cardRoot container for the grouped content surface.
TngCardHeader[tngCardHeader]card-headerHeading wrapper for title and description content.
TngCardTitle[tngCardTitle]card-titlePrimary heading hook.
TngCardDescription[tngCardDescription]card-descriptionSupporting summary or metadata text.
TngCardMedia[tngCardMedia]card-mediaMedia wrapper for imagery, charts, or preview surfaces.
TngCardContent[tngCardContent]card-contentMain body copy or owner-authored custom layout.
TngCardDivider[tngCardDivider]card-dividerVisual separation between regions.
TngCardFooter[tngCardFooter]card-footerFooter row for links, meta, and actions.
TngCardLink[tngCardLink]card-linkInline focusable link hook within the footer area.
TngCardActions[tngCardActions]card-actionsAction grouping hook for aligned button rows.

Owner responsibilities

  • Choose semantic host elements such as article, header, and footer.
  • Author all visual state, including emphasis, density, hover treatment, and elevation.
  • Manage any interaction model yourself when the full card or inner regions are clickable.
  • Provide meaningful accessible names for linked cards, inline actions, and media alternatives.