Mount in MDX as <LeafCard/> + <LeafGrid/>
Metadata header for an Open Register leaf integration. Mirrors the registry descriptor so every per-leaf docs page leads with the same compact summary, one card, six fields, no prose to skim. <LeafGrid/> renders a responsive grid of cards for the overview page; each card links to its dedicated docs route when href is set.
Import & example
import {LeafCard, LeafGrid} from '@conduction/docusaurus-preset/components';
<LeafCard
id="calendar"
label="Meetings"
icon="Calendar"
group="comms"
requiredApp="calendar"
storage="link-table"
status="backend-ready"
description="Link a register record to one or more Nextcloud Calendar events..."
/>
<LeafGrid columns={3}>
<LeafCard id="calendar" status="backend-ready" href="/docs/integrations/calendar" ... />
<LeafCard id="contacts" status="backend-ready" href="/docs/integrations/contacts" ... />
<LeafCard id="mail" status="stub" href="/docs/integrations/mail" ... />
</LeafGrid>Props (LeafCard)
id machine slug used as the link-table keylabel human-readable name shown as the card headingicon MDI icon name (e.g. Calendar); falls back to the first letter of idgroup one of core / comms / docs / workflow / externalrequiredApp Nextcloud app id this leaf depends on; "" or omit when always availablestorage one of magic-column / link-table / external / query-timestatus one of backend-ready / stub / external / built-in — tints the status pillhref when set, the whole card is clickabledescription optional one-paragraph body
LeafGrid takes columns (1–4, default 3) and children.