> For the complete documentation index, see [llms.txt](https://decky.gitbook.io/decky-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://decky.gitbook.io/decky-docs/brand-and-themes/backgrounds.md).

# Backgrounds

Define the types of slide backgrounds Decky can use.

Define the types of slide backgrounds Decky can use.

### Support different slide needs

Backgrounds gives Decky approved visual foundations for different slide layouts and content needs.

A good Theme can use multiple background approaches. This keeps every slide from looking identical.

Backgrounds should support different content amounts and placements. They should remain consistent with your brand.

Update Backgrounds when:

* Slides consistently feel too busy.
* Content lacks usable space.
* The presentation needs more layout variety.
* Decky uses a treatment your company no longer wants.

You can also ask the Theme agent: “Make customer-facing slides more minimal and remove gradients.”

### Related articles

* [Make changes to your theme](/decky-docs/brand-and-themes/make-changes-to-your-theme.md)
* [Colors](/decky-docs/brand-and-themes/colors.md)
* [Imagery](/decky-docs/brand-and-themes/imagery.md)


---

# 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, and the optional `goal` query parameter:

```
GET https://decky.gitbook.io/decky-docs/brand-and-themes/backgrounds.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.