> 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/designer-onboarding.md).

# Designer Onboarding

Turn PSD designs into reusable banner packages for host-platform jobs.

Designers use BannersUI to turn PSD files into controlled, reusable banner packages. They preserve design intent while defining exactly what users can edit.

***

## Designer flow

| Workflow step | Main outcome                                           |
| ------------- | ------------------------------------------------------ |
| Prepare       | PSD layers are named, merged, and ready to import.     |
| Import        | BannersUI creates package artboards and shared layers. |
| Refine        | The package matches the intended design across sizes.  |
| Configure     | Brandkits, locks, visibility, and animation are set.   |
| Publish       | The host platform can expose the package for jobs.     |

### Prepare PSD files

Before import, organize PSD layers so they can become editable package layers.

* Name layers clearly and consistently.
* Keep text, image, shape, video, and background intent clear.
* Merge unsupported Photoshop effects when needed.
* Use one intended background layer when the template requires a background.
* Prepare separate PSD files for artboards or sizes that should become separate package artboards.

Layer names matter because BannersUI uses them to identify matching layers. When you add an artboard, matching layers are copied and shared across both artboards.

### Import and validate

1. **Start the import**
   * Upload PSD files through the host platform.
   * Open the BannersUI PSD import workflow.
   * Enter or confirm the package name.
2. **Validate imported layers**
   * Review the imported layer list.
   * Rename, type, merge, or set a background layer as needed.
   * Resolve import warnings before continuing.
3. **Create the package**
   * Choose a design preset or size setup.
   * Continue to create the package.

### Refine the package

After import, review the package in the package editor.

1. **Review the design**
   * Confirm that every artboard matches the source design.
   * Edit text styles, colors, image placement, shape styling, and layer order.
2. **Add package options**
   * Add missing artboard sizes with presets, custom sizes, or assisted layouts when enabled.
   * Create or attach a brandkit with approved colors and fonts.
   * Configure alternate media when users need selectable image choices.
   * Add animation to supported layers when animated output is required.
3. **Preview and resolve issues**
   * Resolve missing fonts, overset text, invalid names, or media warnings.

### Configure for users

Before publishing, decide what users may change.

* Lock **content** to prevent text or media replacement.
* Lock **position** to prevent moving or resizing layers.
* Lock **properties** to prevent style changes such as color, font, stroke, opacity, or rotation.
* Hide layers that should not appear or should only be controlled by designers.
* Keep important shared layers consistently named across artboards.

Users customizing jobs only see and edit the controls allowed by these locks.

### Publish and hand off

When the package is ready, save it through the connected workflow and publish or expose it to the host platform. The exact publishing step depends on the DAM or platform that launched BannersUI.


---

# 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/designer-onboarding.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.