# Tag

### **Use Cases:**&#x20;

✅ Categorizing or labeling items: Use "Tag" to provide visual labels that help users quickly identify the attributes or categories of items, such as articles, products, or photos.

✅ Filtering or sorting: "Tag" components can be used to enable users to filter or sort content based on specific attributes. Clicking on a tag could trigger a filtering action.

✅ Highlighting important information: Tags can be used to highlight key information, such as "New," "Featured," or "Sale," to draw attention to specific items.

✅ Associating keywords: Tags can represent keywords or topics associated with content, making it easier for users to find related items.

### **Not to Use Cases:**

&#x20;❌ Using "Tag" for non-categorization purposes: "Tag" components should not be used purely for decorative purposes without conveying meaningful information.

❌ Overloading with too many tags: Avoid overwhelming users by using an excessive number of tags, as it can lead to visual clutter and confusion.

❌ Using "Tag" for interactive actions: "Tag" components are primarily for visual representation and categorization, not for triggering interactive actions. Individual tags should not have independent interactive behaviors.

❌ Using "Tag" without clear context: Each "Tag" should have a clear and meaningful purpose, providing valuable information or categorization. Avoid using tags arbitrarily or without a specific purpose.

<br>


---

# 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://2600hz.gitbook.io/sds/sds-3.0/sds-components/components/tag.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.
