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

# Designer Onboarding

Use this workflow when preparing an InDesign document for PrintUI.

## Before you initialize

Confirm that the document is suitable for browser editing and server output.

* Save all links locally. (InDesign's packaging feature can be used to find and save the links locally.)
* Use licensed fonts that can be uploaded to a server and embedded in PDFs.
* Prefer TrueType or OpenType fonts with `.ttf` or `.otf` file extensions.
* Remove facing-page spreads.
* Keep images sized appropriately for their final printed size.
* Convert overly complex vector artwork to JPEG or PNG when it may slow output.
* Decide which content users may edit and which content should remain fixed.

## Log in to PrintUI

Before upload, log in from the PrintUI Management panel flyout. The panel saves an encrypted token for later automatic login; it does not save your password. Log out before closing the panel if you do not want automatic login on that machine.

## Initialize the template

1. Open the InDesign document.
2. Open the PrintUI Management panel.
3. Log in if prompted.
4. Choose **Initialize Template**.
5. Select any optional layers the template requires, such as Foreground, non-printing layers, or Imposition.
6. Save the document.

Initialization creates the layer structure PrintUI needs. The only required layer added is **Background**, used for fixed content that users should not edit.

## Prepare editable and fixed content

Move fixed artwork to the Background layer. Use a Foreground layer when fixed artwork must appear above editable content.

Keep user-editable frames on editable layers. Lock frames that should be editable but not moveable. Mark frames as non-selectable (in the PrintUI Frame Options panel) when user should see but not move or edit them.

Use non-printing layers for visual guides or instructions that should appear in the editor but not in final output.

## Configure options

Use **Template Options** for template-level behavior such as multi-size setup, content type, transparent background, and color conversion.

Use **PrintUI Frame Options** for frame-level behavior such as keywords, non-selectable frames, no-preflight exceptions, fill-text-frame behavior, minimum and maximum font size, and content validation.

The frame options panel is especially useful for templates where users need guided image galleries, fixed-but-visible frames, automatic text fitting, or strict formatting rules for phone numbers and other structured text.

## Preflight and upload

Run preflight from the PrintUI panel's Package and Upload section. Resolve all errors before uploading. Uploading will also preflight and package automatically, but running preflight first makes issues easier to fix.

After the template passes, upload it and any missing fonts. Test the template in a browser, edit sample content, and generate final output before releasing it to users.

## Manage existing templates

Use the Templates area in the PrintUI panel to download an existing template, open a browser test page, or remove a template. Remove templates carefully: deleting a template from the server will also remove customized jobs based on that template.


---

# 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/printui/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.