> For the complete documentation index, see [llms.txt](https://cardstock-studio.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cardstock-studio.gitbook.io/docs/design/templates-design-your-cards/components/fill-components.md). # Fill Components There are three "Fill" type components: **Fill**, **Gradient Fill**, and **Image Fill**. Each of these will work with each other, and their effects are calculated in the Component Stack order, with the first Component (higher in the stack) computed first. *** ## Common Properties All three Components have a *Blend* value, which determines how the visuals blend with the underlying layers. They each also have an *Opacity* value which handles their own opacity. The **Gradient Fill** has a gradient for the opacity. *** ## Fill

**Fill** has a *Color* value that will fill the shape with the chosen color. Like all properties, you can link this to a [Variables](/docs/design/templates-design-your-cards/variables.md) to drive the color dynamically, so each Card in your Deck can have its own color.

You can also set this to be a [Global Values](/docs/design/global-values.md), which is useful for when you want to tweak a specific color — any Templates using the **Global Value** will be updated. *** ## Gradient Fill

**Gradient Fill** lets you create a gradient, including opacity. You can set the *Type* to be "Linear" or "Radial". ### Scope for Text The **Scope** determines how the bounds of the gradient are calculated. "Per Letter", "Per Word", "Per Line", or "Per Block" which is the entire text block. *** ## Image Fill **Image Fill** accepts an image, and works great with tileable images.

Try playing with the *Blend Mode* and matching with **Fill** or **Gradient Fill**.

### Scope for Text The **Scope** determines how the bounds of the image are calculated. "Per Letter", "Per Word", "Per Line", or "Per Block" which is the entire text block. --- # 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://cardstock-studio.gitbook.io/docs/design/templates-design-your-cards/components/fill-components.md?ask=&goal= ``` `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.