> For the complete documentation index, see [llms.txt](https://help.craftsmanplus.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.craftsmanplus.com/play/catalogue/catalogue-editor/understanding-the-catalogue-editor.md).

# Understanding the Catalogue Editor

<figure><img src="https://3019081569-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZBycFFNxrdS0X9OsGtmT%2Fuploads%2Fgit-blob-4b74a7f6eeb03d8ec4b34c8f1fa226d60cdd9b83%2Fimage-20251112-184613.png?alt=media" alt=""><figcaption></figcaption></figure>

The **Catalogue Editor** is the primary interface for creating, editing, and managing catalogue data inside CRAFTSMAN STUDIO.

\
It’s designed to feel familiar, functioning like a lightweight spreadsheet, while still enforcing structure through validation, content types, and publishing controls.

* **Columns (Across the Top)**
  * Each column represents a header, either a **content column** (like text, image, or URL) or a **condition column** (like language, device, or region).
  * Columns define the type of data stored and control how values are validated and used in your project.
* **Rows (Down the Page)**
  * Each row represents a single **variant** of your creative.
  * Rows store what content is associated with what conditions
* **Toolbar (Above the Table)**\
  The toolbar provides quick access to all core catalogue actions:
  * **Edit Controls** (copy/cut/paste, undo/redo)
  * **AI Auto-Translate** for generating multi-language text variants
  * **Publishing Controls** for launching Draft and Live versions


---

# 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://help.craftsmanplus.com/play/catalogue/catalogue-editor/understanding-the-catalogue-editor.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.
