> 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

Reference for Plenit's Documentation center: available categories, material types, and behavior of each card.

This page collects the categories and behavior of the Documentation center, as shown in the panel.

To understand what it is and what it is for, see [Documentation.](https://docs.plenit.com/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       | Sales presentations for each service.                                 |
| Sales documentation | Sales support material.                                               |
| Sustainability      | Material related to sustainability.                                   |
| Security            | Certificates and security documentation (ENS, HDS, etc.).             |
| Courses             | Training content.                                                     |
| Contracts           | Contract templates, including the generation of customized contracts. |
| Email Marketing     | Newsletter templates for campaigns.                                   |

### Card structure

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

### Behavior according to the type of material

| Type         | Behavior when clicked                               |
| ------------ | --------------------------------------------------- |
| PDF or ZIP   | Downloads the document.                             |
| HTML         | Opens the content online (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 sales documentation and presentations are downloaded in white-label format, with your logo in the PDF, so you can present material with your identity to your client.

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

### Next steps

* Generate a contract by following[ How to generate a contract.](https://docs.plenit.com/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.](https://docs.plenit.com/docs-en/go-to-market/how-to/how-to-create-an-email-campaign-with-mailchimp.md)
* Understand the concept in [Documentation.](https://docs.plenit.com/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 by asking a question.

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

```
GET https://docs.plenit.com/docs-en/go-to-market/details/documentation-catalog.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.
