> 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/graphic/graphic-status.md).

# Θ Graphic - Status

Collection: A convenience container for the Status of a Graphic. These are used within the different Views to easily change the status of Cell, Card, Grid Items.

### Status

* **View** - The default normal state of an image/graphic
* **Select** - When in an action of selecting the image/graphic from a listing of graphics. With each tap the icon toggles the selection on/off.
* **Reorder** - When in an action of reordering in a collection of images in a grid, or cards/cells when in a collection of cards/cells.
* **More** - The ability to reveal additional actions that can be taken on the object.
* **Favorite** - The ability to Toggle the Favoriting of the object On/Off with each tap of the Action Icon.
* **Share** - The ability to bring up the share abilities for the object.


---

# 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/graphic/graphic-status.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.
