> 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.md).

# ε Graphic

Element: Overlays, corner radius and any overlays or effects to the image happen at this level.

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

* Parent: [ListItem](https://able.bucca.com/core/components/list-item.md), [CardItem](https://able.bucca.com/core/ks-modules/card-view/card-item.md), GridItem, Multiple
* Sister: [Illustration](https://able.bucca.com/core/overview/graphic/illustration.md)
* Child: [Overlay - Top, Center, Bottom](https://able.bucca.com/core/overview/graphic/overlay.md)

## Properties

**Radius** (Corner) - Gives the Graphic a corner radius treatment. The radius that we use are standardized to the following for all Graphics.

* None (0dp)
* Tiny (2dp)
* XSmall (4dp)
* Small (8dp)
* Medium (12dp)
* Large (16dp)
* XLarge (20dp)

**Aspect Ratio** - The design system has standardized the display of graphics to follow a set of consistent aspect ratios. The following ratios are the only ones used throughout the system. Each of these are listed in their Landscape orientation, but can also exist in Portrait format.

<figure><img src="https://217329376-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MXJWCEk7b7vvAFeWpr2%2Fuploads%2FjoC3OwUGanyWKevR9igU%2FAspect%20Ratio.png?alt=media&amp;token=4a748b6b-fa16-4158-b38b-6790be07c7f6" alt=""><figcaption></figcaption></figure>

* 1:1 (Square)
* 5:4
* 4:3
* 3:2
* 16:10
* 1.618:1 (The Golden Ratio)
* 16:9 (Video Size)
* 2:1
* 21:9 (Movie Theater Screen Size)

Note: Each of the placeholder images for these aspect ratios have a different appearance and have the ratio number in the lower right corner of the image to help in understanding the ratios at a glance.

**Overlay** - Provides the ability to include a layer of content over top of the graphic. This lets us add icons, text, banners, buttons on top of the graphic. There are three areas for overlays...

* **Top** - Docked to the top of the graphic.
* **Center** - Floating at the vertical center of the graphic
* **Bottom** - Docked to the bottom of the graphic

These overlays can be On/Off independent of one another.

**Treatment** - The ability to add different filters and fades to a graphic to alter the appearance of the underlying graphic. Note, all fades and shading for overlays are contained within the Overlay itself and not at this treatment layer. Think of it as three layers (from bottom to top) Graphic > Treatment > Overlay where each sits on top of the previous.


---

# 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.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.
