docmd uses a depth-tracking recursive container parser. You can nest components within each other to build complex, interactive UI structures purely in Markdown without custom HTML.
Starting in v0.9.1, docmd introduces explicit opening and closing container tags (e.g., ::: card … ::: /card, ::: tab … ::: /tab), explicit key-value properties (title:"...", url:"..."), and trailing # comments. This modernised syntax is recommended for all new documentation. Full backward compatibility for legacy sub-block markers (== tab, 1.) and positional argument fallbacks is strictly preserved.
The ::: button component is self-closing (single-line). Never add a terminal ::: immediately after a button—doing so terminates the parent container, resulting in broken page layouts.
Composition Examples
Interactive Resource Block
Combine a Card for structural framing, Tabs for environment-specific commands, and a Callout for alerts:
::: card title:"Monorepo Quickstart"
Choose your preferred initialisation path:
::: tabs
== tab "Automated"
```bash
pnpm onboard
```
::: callout success
This script handles package installation and workspace linking automatically.
::: /callout
== tab "Manual"
Manually fetch and link the core engine packages.
::: button title:"Go to Developer Guide" url:"./#developer-guide"
::: /tabs
::: /card
Platform-Specific Tutorial Steps
Nesting Tabs inside Steps is a standard pattern for providing OS-specific commands within a sequential tutorial:
::: steps
1. **Environment Setup**
Configure your local operating system.
::: tabs
== tab "macOS"
Ensure Homebrew is installed and up to date.
== tab "Linux"
Verify the presence of `curl` and `bash`.
::: /tabs
2. **Core Verification**
Execute the version check to confirm connectivity.
::: /steps
Design Rules & Limits
| Rule | Technical Note |
|---|---|
| Recursive Tabs | Nesting tabs within other tabs is discouraged as it creates complex UX on mobile viewports. |
| Sequential Conflicts | If you need numbered steps within a tab pane, use a standard ordered list rather than ::: steps. |
| Source Indentation | Indentation is optional, but 2 or 4-space indentation improves Markdown readability. |
Container nesting provides clear Semantic Boundaries. A callout nested within a card explicitly scopes that tip to the card’s topic in the llms.txt stream, preventing context leakage across unrelated sections.
