> 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/tutorials/guides/how-to-use-publications/how-to-create-a-print-publication.md).
# How to create a print publication
This guide will teach you how to create a publication prints.
### What is a print publication?
You can think of the print publication as the rules for what data gets put into and structured by the template. This is where you define where the data should come from, and whether a filter should be applied to the results within that catalogue or category.
### Creating a print publication
To create a publication print, head over to 'Publications', and click 'Publication prints' either on the page or in the menu to the left of the screen.
This will take you to the publication print page.
On this page, click the button in the top right corner that says '+ Create print publication'.
Give it a name and fill out the [required details](/reference/publication/print-publications/print-publications-details.md). If you want, you can set up filters for the print. This is just like designing a search query in general inside the PIM.
Click 'Save'.
---
# 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/tutorials/guides/how-to-use-publications/how-to-create-a-print-publication.md?ask=&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.
