> For the complete documentation index, see [llms.txt](https://docs.struct.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.struct.com/developer/publications/publication-template.md).

# Publication template

### What is a publication template?

A publication template defines how your product data is structured and presented in a print. It controls which data appears, where it appears, and how it is formatted when you generate a publication.

Use a template to turn the same PIM data into different outputs. For example, you can create:

* A product catalogue with category pages, images, descriptions, and specifications.
* A price list that shows product names, SKUs, and prices.
* A data sheet that highlights selected technical attributes for each product.

Build templates from content, category, and table of contents pages. Add shared headers and footers for a consistent layout. The selected render engine processes the template and produces the final output.

### The template designer

You can design and edit your template with the template designer which can be accessed from the publication template overview. Depending on your template data type, the designer is used to structure how you want your data to appear in external integrations or design PDF's — just the way you want it.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.struct.com/developer/publications/publication-template.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
