Use a card when one item has a coherent title, supporting content and actions. A compact list or table is often easier for comparison and scanning. Avoid nested cards and decorative surfaces around every paragraph.
This package supports filled, outlined and elevated surfaces corresponding to the Material card family, plus a default that retains the previous border/small-shadow appearance. These are visual grouping choices, not automatic button, selection or review semantics.
The reference’s elevated, filled and outlined variants have the same task capabilities with different emphasis: a subtle filled grouping, elevated separation, or an explicit outline. The container is the only required element; title, subhead, supporting text, media, dividers and actions follow the item’s hierarchy. Do not force a card around content that spacing and headings would organize more clearly.
Native reference measurements include 12dp corners, 16dp inline padding and up to 8dp between cards. This library instead uses its actual radius, 24px part padding and caller-owned layout gap. Those native measurements are not CSS conversions or imported component presets.
Reference subject
Web composition and boundary
Content and media
Keep coherent blocks in reading order. Inset dividers separate related blocks; full-width divisions can clarify expanded content. Prefer text separate from imagery; any overlay needs contrast across the real image, an appropriate scrim/bounding shape and meaningful alternative text. No image or permission service is installed by Card.
Actions and semantics
Choose a non-actionable container with independently named controls, or one native whole-card link/button with no nested actions. The specimen demonstrates both separately. Native link Enter activation and Space scrolling remain different from a button’s Enter/Space activation. The root div supplies no selection, hover action or automatic tab stop.
Collections and adaptation
Keep resting cards coplanar, with filter/sort controls outside the collection applying to every record. The actual collection filters titles/bookmarks, sorts titles and retains bookmarks across presentation changes. Grid columns reflow from available space; long content grows instead of clipping to a forced equal height. Related Lists/carousel guidance covers alternate presentations.
Expansion and scrolling
The actual native details disclosure grows its card in document flow. Reference mobile cards avoid nested scrolling and can expand into a screen; desktop guidance permits internal expansion/scroll. This specimen keeps one document scroll and does not install a native hero container transform or full-screen navigation transition.
Drag, swipe and state
Reference picked-up cards rise above peers without pushing them aside, and allow one swipe action without nested swipe carousels. Card itself installs no drag/swipe/disabled/loading behavior. If composed, provide explicit pointer/keyboard commands, actual target/recovery state and clear focus; see Input and gestures rather than implying a styled surface implements those operations.
These compositions use 16 CSS px part insets and 12 CSS px action padding, retaining room for full words when root text doubles. The package defaults remain those specified above. The whole-card destination is deliberately brief; its separate surrounding explanation remains readable in document flow.
Local reading collection
An English-only example with explicit actions.
The container itself is not clickable. Open the related guidance or change this local bookmark.
A collection with independent actions
Filters and sorting apply to every local card. Surface changes preserve bookmarks. The cards grow with their contents and do not scroll internally.
Shown 3 of 3 local cards. 0 bookmarked. No remote or durable write occurred.
Reading notes
Local reading settings and a retained English-only draft.
Read Reading notes details
This is retained local content for Reading notes. Expanding grows the card in normal document flow. It does not validate a source, authorize access or create a remote result.
Comparison notes
Local examples arranged for comparison, without review claims.
Read Comparison notes details
This is retained local content for Comparison notes. Expanding grows the card in normal document flow. It does not validate a source, authorize access or create a remote result.
Recovery notes
Local cancellation, retry and retained recovery examples.
Read Recovery notes details
This is retained local content for Recovery notes. Expanding grows the card in normal document flow. It does not validate a source, authorize access or create a remote result.
A separate, single-action card
This whole-card link has one destination and no nested controls. The collection above keeps its independent controls inside non-actionable containers.
The root is read-only by default and must not become an unexplained Tab stop. Use a real link for navigation and a button for actions.
Keep separate actions separate. Do not put buttons inside a whole-card link or nest interactive controls.
If an application needs a single linked card, make its one link understandable from the title and avoid duplicate destinations. If selection is needed, compose a named checkbox or radio with actual selected state.
For media, provide a useful alternative or mark decorative imagery appropriately. Confirm rights, identification and locality before using real cultural/resource imagery.
Retain long titles, empty/error/loading messages and action visibility at narrow widths. Clipped overflow must not crop essential focus indicators.
No unconditional elevation-on-hover is applied: a static container should not suggest a click that has no outcome.
Verify the actual title, description relationships, focus destination, keyboard operation and task result in the consuming application.
Exercise narrow and short viewports, both themes, long labels, text spacing, reduced motion and forced colors. Reach the last action by scrolling and keyboard.
For overlays, check background interaction, scroll locking and each permitted dismissal path. A role or aria-modal attribute alone does not prove modal behavior.
Use a named screen reader and browser for spoken output. Local examples and automated DOM checks do not prove announcements or a persisted backend result.
Retain source/review/permission evidence. A container or confirmation cannot grant authority or establish that a request succeeded.