> 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/reference/publication.md).

# Publication

Struct PIM Publications bridges the gap between your data and your audience. Effortlessly generate dynamic catalogs, spreadsheets, and PowerPoints directly from your PIM.

If you're managing a massive catalog of products and feeling the "copy-paste fatigue" of trying to get that data into catalogs, price lists, or spec sheets, Struct PIM **Publications** is essentially your digital escape hatch.

In a nutshell, it’s a specialized module within the Struct PIM (Product Information Management) ecosystem designed to bridge the gap between your raw product data and ready-to-print (or digital) marketing materials.

### What you can do with Publications

* **Organize and automate your product data** for high-quality print and digital documents.
* **Build a structured Publication Tree** to arrange products into chapters, sections, and pages, ensuring a logical flow for catalogs or price lists.
* **Sync data directly to Adobe InDesign** via specialized connectors to eliminate manual copy-pasting and layout errors.
* **Generate on-demand PDFs** or data sheets that stay updated with the latest PIM attributes, images, and pricing.
* **Create targeted versions of your publications** for different languages, regions, or customer segments using the same master product data.
* **Generate editable PowerPoint presentations instantly**, allowing sales teams to create custom pitch decks with live product data, specs, and imagery.
* **Build format-specific commerce feeds** (JSON, XML, CSV and XLSX) that serve snapshots of your data, perfectly tailored to feed your commerce website.

### Publication walkthrough

#### Publication layout

The main publication page consists of links to specific functionality within Publications. From here, you can go to templates, prints, fonts and translations.

#### Print publications

1. Click 'Show print publications' to go to [Print publications](/reference/publication/print-publications.md).

#### Publication template

1. Click 'Show publication templates' to go to [Publication templates](/reference/publication/publication-template.md).

#### Publication translation

1. Click 'Show publication translations' to go to [Publication translation](/reference/publication/publication-translation.md). 

#### Publication font

1. Click 'Show publication fonts' to go to [Publication font](/reference/publication/publication-font.md).

{% hint style="info" %}
You can also use the navigation menu to the left to go to these pages.
{% endhint %}

### Related tutorials

* [How to create a publication template](/tutorials/guides/how-to-use-publications/how-to-create-a-publication-template.md)
* [How to set up EasyCatalog with publications](/tutorials/guides/how-to-use-publications/how-to-set-up-easycatalog-with-publications.md)
* [How to create a PowerPoint presentation with publications](/tutorials/guides/how-to-use-publications/how-to-create-a-powerpoint-presentation-with-publications.md)


---

# 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/reference/publication.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.