Componentes
Cards
Present a compact group of related documentation destinations.
Cards make a small set of important next destinations easier to scan. Keep normal text links in surrounding prose so the page remains useful outside the visual UI.
Example
Properties
Card accepts title, description, href, and an optional Lucide icon.
Applications can replace an icon name through site.icons with a project-owned
SVG.
Usage
Use two to four cards for meaningful choices. A long API list should remain a normal list or table rather than becoming a grid of oversized controls.
Last updated 2 ago 2026