> For the complete documentation index, see [llms.txt](https://docs.feathery.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.feathery.io/platform/build-forms/design/reuse-styles-and-elements/assets.md).
# Assets
**Assets** are form elements configured with certain sets of styles and properties. These custom-configured elements can then be reused throughout your form.
For example, you may configure different `Next` and `Back` button styles and want to use them interchangeably in your form. You would then create two assets in your theme, one for each style.
#### How to Create Assets
You can save assets to your form's associated theme for quick access.
1. Start with an element and make desired changes to its styles and properties.
2. Click the `+ Save as Asset` button that appears in the left panel.
3. View your saved asset by selecting the red number badge in grid view or switching to list view.
4. Publish your form to save the new asset to your theme.
#### How to Update Assets
You can update assets in a form or theme. Updates will apply to all assets in all forms using the same theme.
To update in a form:
1. Make desired changes to the asset's styles and properties.
2. Select the ↻`Update Asset` button in the left panel OR the individual style Override Menu in the right panel.
3. Publish the form to finalize your asset update.
#### How to Manage Assets
You can manage assets by using the `Overflow Menu` found in the left panel (open via `Right Click`) or in their associated theme. The theme will give you an overview of all your assets.
---
# 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://docs.feathery.io/platform/build-forms/design/reuse-styles-and-elements/assets.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.