\n The object card is now the account card patterns. To use an actions\n variant of the account card, visit the{' '}\n
\n Object cards are used to list repeatable, related content, such as\n user accounts or addresses, where each card represents a discrete\n object. They are intended to create discernable visual patterns that\n are quickly recognized, so they should only represent one type of\n information within an experience. Object cards often appear in\n collections and should follow the same internal structure so they\n are easily scanned.\n
\nThe select variant has both an empty state and an active state.
\n\n Object cards are designed to stack vertically. To reflect their visual\n pattern and enhance scannability, always place them on a fixed grid.\n
\n\n At smaller breakpoints, the action variant will responsively list the\n available actions at the bottom of the card. To optimize touch\n interactions likely at these breakpoints, the select variant will\n trigger a full-screen modal that lists each available option as a\n populated object card instead of triggering a dropdown. Selecting an\n object within the list will exit the modal and bring the user back to\n the initial screen.\n
\n\n Action labels should use strong verbs and specific language, similar\n to{' '}\n \n buttons\n {' '}\n . The empty state title and subtitle for the select variation should\n be simple CTAs, such as \"Select a(n) [object]\" and \"Expand to see a\n list of available [objects]\". Otherwise, follow the microcopy\n guidelines for the{' '}\n \n icon links\n {' '}\n and{' '}\n \n label\n {' '}\n components.\n
*/}\n \n \n )\n}\n"],"sourceRoot":""}