## XCard Usage Rules XCard is individual link display card, suitable for displaying individual links with a richer and more visually appealing presentation format. ### Attributes - `data-title` (required): Card title. - `data-icon` (optional): Icon identifier (e.g., lucide:icon-name or material-symbols:rocket-outline). - Icons should prioritize Lucide (lucide:icon-name). If not available in Lucide, use Iconify (collection:icon-name, e.g., material-symbols:rocket-outline). - `data-image` (optional): Image URL, can coexist with icon. - Prefer to use image url from ``. - **Requirement**: At least one of `data-icon` or `data-image` must be provided. - It's recommended to always provide data-icon. - `data-href` (optional): Navigation link for clicking the card or button. - `data-horizontal` (optional): Whether to use horizontal layout. - `data-cta` (optional): Button text (call to action). ### Children - Must be written within `...` children. - Plain Text Only: Do not use any Markdown syntax (see `` for the full list). ### Good Examples - Example 1: Basic card with icon and description ```md SIGALRM: Sent when a real-time timer has expired. ``` - Example 2: Horizontal card layout ```md This is an example of a horizontal card. ``` ### Bad Examples - Example 1: Inline Markdown formatting in card content ```md `SIGALRM`: Sent when a real-time timer has expired. ``` - Example 2: Code block inside card content ````md Creates a listener for "ctrl-break" events. ```rust use tokio::signal::windows::ctrl_break; #[tokio::main] async fn main() -> std::io::Result<()> { let mut stream = ctrl_break()?; stream.recv().await; println!("got ctrl-break"); Ok(()) } ``` ````