> For the complete documentation index, see [llms.txt](https://docs.santacruzsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.santacruzsoftware.com/bannersui/getting-started/quickstart.md).

# Quickstart for Users

Use this guide when you are customizing an existing BannersUI job.

Customize an existing BannersUI job by editing approved content, reviewing artboards, and completing the connected workflow.

***

## Workflow overview

| When                   | What to do                                                                      | What happens                                      |
| ---------------------- | ------------------------------------------------------------------------------- | ------------------------------------------------- |
| You are ready to begin | Launch the job from the host platform.                                          | BannersUI opens the job in the editor.            |
| The job is open        | Change the text, images, videos, and layout settings you are allowed to change. | Your changes appear on the artboards as you work. |
| You are done working   | Preview every artboard and resolve warnings.                                    | The job is ready to save.                         |
| You are finished       | Save your changes and return to the host app for output.                        | The host app creates or publishes the final file. |

## Open a job

1. Start from the DAM, BrandingUI, Sagittarius, or other host platform.
2. Choose the package or job you need to customize.
3. Open the editor. BannersUI loads the job and its artboards.

If the job cannot be found, the editor shows an error. Return to the host platform and confirm that the selected job still exists and that you have access.

## Edit approved text

1. Select a text layer on the artboard or in the layers panel.
2. Use <kbd>Edit Text</kbd> in the Right Palette to change the text content.
3. Use available text controls for font, size, style, color, alignment, spacing, padding, or fitting.
4. Watch for overset warnings. Overset text means some text is not visible and may be missing from final output.

{% hint style="info" %}
If text controls are disabled, the designer locked the text content or attributes.
{% endhint %}

## Replace approved media

1. Select an image or video layer.
2. Choose <kbd>Edit Content</kbd> in the Right Palette to change the image, upload media, or for the gallery option provided by your environment.
3. Select a replacement file.
4. If prompted, decide whether to replace only the current artboard or all artboards that use the same media.
5. Adjust crop, fitting, scale, or position when those controls are available.

BannersUI may prevent scaling an image below the required resolution. Use a higher-resolution file if you see a preflight or minimum-resolution warning.

## Check every artboard

1. Move through each artboard in the package.
2. Confirm that text, media, links, and layout still look correct.
3. Use preview to inspect the output appearance.

If you finish before reviewing every page, BannersUI may warn that not all pages were checked.

## Finish

1. Resolve all visible warnings.
2. Save your changes if the host workflow provides a **save** action.
3. Choose <kbd>Finished</kbd> or return to the host platform to generate or publish output.

Final output is usually generated by the connected DAM or production system after BannersUI saves the customized job.


---

# 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.santacruzsoftware.com/bannersui/getting-started/quickstart.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.