> For the complete documentation index, see [llms.txt](https://docs.plenit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.plenit.com/docs-en/go-to-market/details/documentation-catalog.md).

# Documentation catalog

This page lists the categories and behavior of the Documentation center, as it appears in the panel.

To understand what it is and what it is used for, see [Documentation.](/docs-en/go-to-market/concepts/documentation.md)

### Categories

Materials are filtered from the tabs at the top:

| Category                 | Content                                                           |
| ------------------------ | ----------------------------------------------------------------- |
| All                      | All materials, unfiltered.                                        |
| Presentations            | Commercial presentations for each service.                        |
| Commercial documentation | Sales support material.                                           |
| Sustainability           | Sustainability-related material.                                  |
| Security                 | Security certificates and documentation (ENS, HDS, etc.).         |
| Courses                  | Training content.                                                 |
| Contracts                | Contract templates, including the generation of custom contracts. |
| Email Marketing          | Newsletter templates for campaigns.                               |

### Structure of each card

Each item is presented as a card with its **image** header, **title**, **description** and **category label**.

### Behavior according to the type of material

| Type         | Behavior on click                                   |
| ------------ | --------------------------------------------------- |
| PDF or ZIP   | Downloads the document.                             |
| HTML         | Opens the online content (common in courses).       |
| External URL | Redirects to the resource (for example, tutorials). |

Some cards have their own actions, such as **Generate contract**, **Go to Tutorials** or **Go to Email Marketing**.

> #### 📘 Materials with your brand
>
> Much of the commercial documentation and presentations are downloaded white-labeled, with your logo in the PDF, so you can present your client with material in your own identity.

> #### 📘 Availability by language
>
> The catalog adapts to the language of the panel.&#x20;
>
> In languages other than Spanish, some categories such as Courses may not be shown, and in commercial documentation only the most recent material may appear.

### Next steps

* Generate a contract following[ How to generate a contract.](/docs-en/go-to-market/how-to/how-to-generate-a-contract.md)
* Set up a campaign with [How to create an email marketing campaign.](/docs-en/go-to-market/how-to/how-to-create-an-email-campaign-with-mailchimp.md)
* Understand the concept in [Documentation.](/docs-en/go-to-market/concepts/documentation.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 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.plenit.com/docs-en/go-to-market/details/documentation-catalog.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.
