Cards

Pipeline A does not support any of these — ::link-card{...} inside an AUP format: "markdown" text field renders as literal text (marked has no concept of remark directives). All four card types below are pipeline-B only.

link-card (768 files) and card-group (741 files) are the two most-used extensions in a real production content corpus, so they lead this page.

link-card

A card that navigates somewhere when clicked — the whole card becomes a link.

Source:

::link-card{title="Console" description="Open the operator console" href="/console" icon="rocket"}

Rendered:

Without an href, a link-card degrades to a non-interactive info block instead of a broken link — it never renders a dead <a>.

Source:

::link-card{title="No target set" description="This card has no href attribute"}

Rendered:

action-card

A card whose body holds one or more explicit ::action{...} buttons, rather than making the whole card clickable.

Source:

:::action-card{title="Deploy" description="Ship the current build" icon="rocket"}
::action{label="Deploy now" href="/deploy" variant="primary"}
::action{label="View logs" href="/logs" variant="secondary"}
:::

Rendered:

info-card

A genuinely non-interactive content card — unlike link-card, an href attribute on info-card is silently ignored; it can never become a link. This is the first real-world usage of info-card in this repository (the production corpus scan found zero usages before this reference).

Source:

:::info-card{title="Before you start" description="Prerequisites for this guide"}
You'll need:

- Node 20+
- A DID Space

Run `arc --version` to check your install.

```bash
arc --version
```

> [!NOTE]
> Keep your DID Space credentials backed up.
:::

Rendered:

arc --version

info-card accepts any block content in its body — paragraph, list, inline code, fenced code, and even a nested admonition, all recursed through the same converter that handles top-level document content.

card-group

Wraps consecutive card directives into a responsive multi-column grid instead of each card stacking full-width down the page.

The colon-fence nesting rule matters here: card-group needs more colons than the deepest directive nested inside it. action-card already needs 3 colons for its own body, so card-group needs 4:

Source:

::::card-group
::link-card{title="Console" href="/console" icon="rocket"}
::link-card{title="API reference" href="/api" icon="book"}
:::action-card{title="Deploy" description="Ship it"}
::action{label="Go" href="/deploy" variant="primary"}
:::
::::

Rendered:

See Steps for the general statement of this colon-nesting rule — it applies to every nesting directive in this pipeline (steps/step, card-group/card directives, view{mode="tabs"}/panels), not just this one.