> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/platform/guides/developer-guide/ui-developer-guide/digit-ui-components0.2.0/molecule/panel-card.md).

# Panel Card

The Panel Card component is a composite component designed to communicate clear, high-visibility feedback messages, typically success or error outcomes. It brings together an icon, message, optional description, interactive actions, and optional widgets into one cohesive layout.

<figure><img src="/files/o4HgV1VRS0tfkfBqhXY8" alt=""><figcaption></figcaption></figure>

{% tabs %}
{% tab title="Component React" %}

```
// Sample code

<PanelCard
  animationProps={{
    loop: false,
    noAutoplay: false
  }}
  cardClassName=""
  cardStyles={{}}
  className=""
  customIcon=""
  description="Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat."
  footerChildren={[
    <Button label="Button" onClick={()=>{}} type="button" variation="secondary"/>,
    <Button label="Button" onClick={()=>{}}  type="button"/>
  ]}
  footerStyles={{}}
  iconFill=""
  info="Ref ID "
  maxFooterButtonsAllowed={5}
  message="Success Message!"
  multipleResponses={[]}
  props={{}}
  response="949749795479"
  sortFooterButtons
  style={{}}
  type="success"
>
  <AlertCard
    className="panelcard-alert-card"
    text="This is success"
    variant="success"
  />
</PanelCard>
```

{% endtab %}

{% tab title="Component Flutter" %}

```
// Sample code

PanelCard(
            type: PanelType.success,
            title: 'Success Message',
            actions:[
              DigitButton(
                label: 'Cancel',
                onPressed: () {},
                type: DigitButtonType.secondary,
                size: DigitButtonSize.large,
              ),
              DigitButton(
                label: 'Submit',
                onPressed: () {},
                type: DigitButtonType.primary,
                size: DigitButtonSize.large,
              ),
            ],
            additionWidgets: const [
              InfoCard(
                title: 'Additional Info',
                type: InfoType.success,
                description: 'This is an example of additional widget content that can be toggled.',
              ),
            ],
          ),
```

{% endtab %}

{% tab title="Component Design" %}

{% endtab %}
{% endtabs %}

## Anatomy

<figure><img src="/files/NPTjwJGMLxa78mvodHCC" alt=""><figcaption></figcaption></figure>

## Variants

***

<table data-header-hidden><thead><tr><th width="321"></th><th></th></tr></thead><tbody><tr><td><div><figure><img src="/files/Uq5jKm172cjDJgDzQM2I" alt=""><figcaption></figcaption></figure></div></td><td><p><strong>Success Panel</strong></p><p>Displays a confirmation message indicating successful operations and uses a green colour scheme with success iconography and optional ID or confirmation number.</p></td></tr><tr><td><div><figure><img src="/files/K0Xl7ZTT5OzDpXRsXkFV" alt=""><figcaption></figcaption></figure></div></td><td><strong>Error Panel</strong><br>Indicates failure or issues in the process, and this feature has a red colour scheme with an error icon, and optionally includes details on what failed and how to resolve it.</td></tr></tbody></table>

## Properties

<table data-header-hidden data-full-width="false"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td><br><img src="/files/RWX2yPzbTND7QNY1ZGw7" alt=""></td><td><p><strong>Description</strong></p><p>Toggle the presence of additional descriptive text below the main message.</p></td></tr><tr><td><strong>Edit Description</strong><br>Enables inline editing of the description field when required, allowing admins or users to update metadata or identifiers dynamically..</td><td><div><figure><img src="/files/VuZXuVlUb08nrQN6in1I" alt=""><figcaption></figcaption></figure></div></td></tr><tr><td><strong>Actions</strong><br>Supports one or more action buttons such as “Go Back,” “Continue,” “Retry,” or custom CTAs.</td><td><div><figure><img src="/files/iWx0yr4dwIQtLeRgE2GE" alt=""><figcaption></figcaption></figure></div></td></tr><tr><td><strong>Additional Widgets</strong><br>Includes optional elements like info cards, links, or nested content to provide supplementary guidance or system feedback.</td><td><div><figure><img src="/files/U5tPTeNw3wgi3SWMaoKi" alt=""><figcaption></figcaption></figure></div></td></tr></tbody></table>

## Property Configuration Table

Each design component offers a range of configurable options. These options are intentionally platform-agnostic, allowing implementations to adapt and tailor them to align with the specific requirements of the chosen framework.

{% tabs %}
{% tab title="React" %}

<table><thead><tr><th width="257">Property</th><th>Value</th><th>Default</th></tr></thead><tbody><tr><td>className</td><td>text</td><td>-</td></tr><tr><td>style</td><td>text</td><td>-</td></tr><tr><td>children</td><td>yes/no</td><td>-</td></tr><tr><td>footerChildren</td><td>yes/no</td><td>-</td></tr><tr><td>message</td><td>number</td><td>-</td></tr><tr><td>type</td><td>yes/no</td><td>false</td></tr><tr><td>info</td><td>yes/no</td><td>-</td></tr><tr><td>response</td><td>yes/no</td><td>-</td></tr><tr><td>customIcon</td><td>yes/no</td><td>0</td></tr><tr><td>iconFill</td><td>number</td><td>false</td></tr><tr><td>multipleResponses</td><td>yes/no</td><td>-</td></tr><tr><td>footerclassName</td><td>yes/no</td><td>false</td></tr><tr><td>footerStyles</td><td>yes/no</td><td>-</td></tr><tr><td>cardClassName</td><td>yes/no</td><td>-</td></tr><tr><td>cardStyles</td><td>yes/no</td><td>-</td></tr><tr><td>maxFooterButtonsAllowed</td><td>yes/no</td><td>-</td></tr><tr><td>sortFooterButtons</td><td>yes/no</td><td>-</td></tr><tr><td>showChildrenInline</td><td>yes/no</td><td>-</td></tr><tr><td>description</td><td>yes/no</td><td>-</td></tr></tbody></table>
{% endtab %}

{% tab title="Flutter" %}

<table><thead><tr><th>Property</th><th width="209">Value</th><th>Default</th></tr></thead><tbody><tr><td>type</td><td>PanelType</td><td>required</td></tr><tr><td>title</td><td>String</td><td>required</td></tr><tr><td>description</td><td>String</td><td>-</td></tr><tr><td>additionalDetails</td><td>List&#x3C;String></td><td>-</td></tr><tr><td>additionWidgets</td><td>List&#x3C;Widget></td><td>-</td></tr><tr><td>actions</td><td>List&#x3C;DigitButton></td><td>-</td></tr><tr><td>actionSpacing</td><td>double</td><td>-</td></tr><tr><td>inlineActions</td><td>bool</td><td>false</td></tr><tr><td>animate</td><td>bool</td><td>true</td></tr><tr><td>repeat</td><td>bool</td><td>false</td></tr><tr><td>sortButtons</td><td>bool</td><td>true</td></tr></tbody></table>
{% endtab %}
{% endtabs %}

## Usage Guide

***

| <div><figure><img src="/files/GvLEuADBzxLdbmrCbo7R" alt=""><figcaption></figcaption></figure></div> | <p><strong>Provide specific feedback</strong></p><p>Display a unique reference ID, transaction number, or message that helps users verify or follow up.

Leave users guessing with vague messages like “Request submitted” without additional traceable context.</p> |
| --------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| <div><figure><img src="/files/sOKzVZ9kucsXHFZODGRk" alt=""><figcaption></figcaption></figure></div> |                                                                                                                                                                                                                                                                      |
|                                                                                                     |                                                                                                                                                                                                                                                                      |

## Change log

***

| Date         | Number  | Notes                                                                                           |
| ------------ | ------- | ----------------------------------------------------------------------------------------------- |
| Dec 15, 2024 | v-0.0.2 | <p>This component is added to the website.<br>This component is now individually versioned.</p> |

## Design Checklist

***

<table data-header-hidden><thead><tr><th width="129" data-type="checkbox"></th><th></th></tr></thead><tbody><tr><td>true</td><td><strong>All interactive states</strong> - Includes all interactive states that are applicable (hover, down, focus, keyboard focus, disabled).</td></tr><tr><td>true</td><td><strong>Accessible use of colours</strong> - Colour is not used as the only visual means of conveying information (WCAG 2.1 1.4.1)</td></tr><tr><td>true</td><td><strong>Accessible contrast for text</strong> - Text has a contrast ratio of at least 4.5:1 for small text and at least 3:1 for large text (WCAG 2.0 1.4.3).</td></tr><tr><td>true</td><td><strong>Accessible contrast for UI components</strong> - Visual information required to identify components and states (except inactive components) has a contrast ratio of at least 3:1 (WCAG 2.1 1.4.11).</td></tr><tr><td>true</td><td><strong>Keyboard interactions</strong> - Includes all interactive states that are applicable (hover, down, focus, keyboard focus, disabled).</td></tr><tr><td>false</td><td><strong>Screen reader accessible</strong> - All content, including headings, labels, and descriptions, is meaningful, concise, contextual and accessible by screen readers.</td></tr><tr><td>true</td><td><strong>Responsive for all breakpoints</strong> - Responsiveness for 3 breakpoints - Mobile, Tablet and Desktop</td></tr><tr><td>true</td><td><strong>Usage guidelines</strong> - Includes a list of dos and don'ts that highlight best practices and common mistakes.</td></tr><tr><td>false</td><td><strong>Content guidelines</strong> - Content standards and usage guidelines for writing and formatting in-product content for the component.</td></tr><tr><td>true</td><td><strong>Defined variants and properties</strong> - Includes relevant variants and properties (style, size, orientation, optional iconography, decorative elements, selection states, error states, etc.)</td></tr><tr><td>true</td><td><strong>Defined behaviours</strong> - Guidelines for keyboard navigation and focus, layout management (including wrapping, truncation, and overflow), animations, and user interactions.</td></tr><tr><td>true</td><td><strong>Design Kit</strong> - Access to the design file for the component in Figma, multiple options, states, colour themes, and platform scales.</td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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://docs.digit.org/platform/guides/developer-guide/ui-developer-guide/digit-ui-components0.2.0/molecule/panel-card.md?ask=<question>
```

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.