# Custom Cards
## Overview
## Usage
### When to use this component?
Custom cards are perfect when you need flexibility in both design and content. Use them when standard card layouts don't meet your requirements, and you want to tailor the structure, style, and interaction to suit specific data types, user needs, or branding guidelines. Ideal for dashboards, content feeds, or modular UI sections, custom cards empower designers and developers to create rich, personalized components.
### How it works
Custom cards act as a configurable container that supports dynamic content and layout customization. Users can define their own combinations of elements—such as headings, icons, buttons, media, and metadata—and control styling aspects like spacing, colors, and typography. This modular approach enables the creation of reusable components while allowing full creative freedom to adapt to various use cases. Optional slots or configuration props can be used to inject custom content or interactivity, making the cards highly versatile across projects.
### Code
{% tabs %}
{% tab title="Vanilla Js" %}
```jsx
Card main title
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
```
{% endtab %}
{% tab title="React" %}
```jsx
Card main title
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
```
{% endtab %}
{% tab title="Vue" %}
```jsx
Card main title
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
```
{% endtab %}
{% tab title="Angular" %}
```jsx
Card main title
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
```
{% endtab %}
{% endtabs %}
### Properties
| Property | Description | Type |
| ---------------------- | ---------------------------------------------------------------------------------------------------------------------------------- | -------- |
| card\_header\_text | The label displayed at the top of the banner card, typically indicating the card’s category or context (e.g., "Event"). | `string` |
| card\_header\_icon | Name of the Icon to be shown alongside the header text. | `string` |
| card\_header\_icon\_id | Unique identifier for the header icon element. Useful for targeting the icon programmatically (e.g., for click events or testing). | `string` |
## Anatomy
### Anatomy Options
**Card Title:** Indicates the type of content (e.g., “Event”), helping users immediately recognize the card’s purpose.
**Icon:** **con:** A contextual icon that can represent various functions such as settings, alerts, status indicators, or additional options—serving as a quick access point for supporting actions or information relevant to the event card.
**Image:** A banner image representing the event, used for visual context and thematic consistency.
**Event Title:** The primary title of the event, clearly stating its name or subject.
**Description:** A short text summary providing users with a quick overview of the event’s focus or content.
**Button:** A clear call-to-action that guides users to view more detailed event information.
***
## Dos and Don'ts
| Dos | Don'ts |
| -------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- |
| **Use clear, legible icons** that immediately convey the card's purpose or action. | **Don’t use low-quality or blurry images** for the `image_src`—it reduces visual appeal. |
| **Write concise, meaningful titles** to ensure quick understanding. | **Avoid long or vague titles** that don’t communicate the card’s content. |
| **Keep descriptions short and relevant** to avoid overwhelming users. | **Don’t overload the description** with too much text—keep it scannable. |
| **Use consistent styling and spacing** if multiple cards are displayed together. | **Avoid placing multiple cards without spacing**, which can cause visual clutter. |
| Maintain a consistent design language across all cards to ensure a cohesive user experience. | **Don’t leave the `onclick` empty or use console logs in production.** |
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://designsystem.dubai.ae/components/cards/custom-cards.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.