> For the complete documentation index, see [llms.txt](https://able.bucca.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://able.bucca.com/core/overview/badge.md).

# Φ Badge

Primitive: The possible styles and sizes of a badge are set here. A badge can be attached to many objects, icons, adaptIcons, Avatars, Labels (like within a button, app bar, tabs etc.)

[Styleguide Link](https://zpl.io/bzxkPPA)

* Parent: Multiple... [Badge - Usecase](/core/overview/badge/badge-use.md), [Icon](/core/overview/icon.md), [Label](/core/overview/label.md), [AdaptIcon](/core/overview/adapticon.md), [Avatar](/core/overview/avatar.md), [Button](/core/overview/button.md), [Tab](/core/overview/tab.md) etc.

## Properties

### Type

* **Value** - The use of a number to indicate the amount of actionable activities attached to the object. Note, the font used here is an exception in the design system and is set to a font-size of 8.
* **Color** - The association of a color to a status. IE. Red=Away, Green=Available

<figure><img src="https://217329376-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MXJWCEk7b7vvAFeWpr2%2Fuploads%2FRVhRUEwbgJUfHupxiRjL%2FType.png?alt=media&amp;token=796db9a0-ee40-4aa3-ac36-e06160e946f1" alt=""><figcaption></figcaption></figure>

### Size

* Medium (12dp)
* Small (6dp)

### State

* Enabled
* Disabled

## Usage

A badge is an onscreen object linked to a notification/alert. A badge consists of a small circle, typically containing a number or other characters, that appears in proximity to another element or component. A badge is both a notifier that there are items associated with an object and an indicator of how many items there are.

A badge is used to draw the user's attention to an object, or to emphasize that something may need their attention. For example:

* A "New messages" notification might be followed by a badge containing the number of unread messages.
* A "Shopping cart" badge showing the number of items in the cart.
* A "Status" badge on an Avatar might have an accompanying badge to indicate the users activity status at that moment.

<figure><img src="https://217329376-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MXJWCEk7b7vvAFeWpr2%2Fuploads%2FDB4a2LE4Ay78ZI9We08v%2FUsecase.png?alt=media&amp;token=72174125-cffa-48bb-ac70-3a028f72702a" alt=""><figcaption></figcaption></figure>

A badge signifies that with a tap of the object tied to the badge, additional information indicated by the badge is accessible. Badges are a common feature in user interfaces, and provide users with a visual clue to help them discover additional relevant content. Their design and use is therefore an important factor in the overall user experience.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://able.bucca.com/core/overview/badge.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.