> For the complete documentation index, see [llms.txt](https://xoops.gitbook.io/publisher-tutorial/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://xoops.gitbook.io/publisher-tutorial/4.0-operating-instructions/4.3-articles/4.3.1-images.md).

# 4.3.1 Images

Publisher is using the XOOPS ImageManager to manage its images.

When you open the "Images" Tab, you'll be able to select the Image Category from the XOOPS ImageManager, and either use one of the already available images or upload a new one.

![](/files/-LD6N-81VGlmWyaqkBdB)

If you didn't do it yet, you can go to the ImageManager and create a special category for your Publisher Images. The best way is to go to the Modules Admin by clicking on the Modules menu:

![](/files/-LD6N-83TX2f1LDDac3T)

and then click on the "ImageManager" icon:

![](/files/-LD6N-856dJqOrbOF-t-)

Once there, you can see what categories you already have, if any, and how many images each of them has.

Let's create a new Category for Publisher:

![](/files/-LD6N-87qE6d0UzhVoG5)

Here you can set the Category name, select groups that will have access to that category, and the maximum image sizes:

![](/files/-LD6N-89RS9NdV-hh3K8)

Once this is done, let's save it:

![](/files/-LD6N-8BBNqf8qskybX4)

Now we can add the images here, or we can go back to the Publisher and upload the images there. First, we need to select the category to which will upload the pictures to, so let's select the "Publisher":

![](/files/-LD6N-8DH2klnDTVd9U5)

then click on the "Upload new image" button, and select an image from your local drive. Once this is done, you new image will be visible in Publisher, and it will be automatically added to the "article images", and it will be selected as the "featured image":

![](/files/-LD6N-8F93aiTpBskUf_)

We can upload few more images, and then select which will be included in the article, and which will be the featured one:

![](/files/-LD6N-8HYgduhjr7iPZo)

We can also check out the images in the XOOPS ImageManager:

![](/files/-LD6N-8J24srcj7acWtZ)

> ![](/files/-LD6N-8LnP1T9IhDYNLj)**NOTE:** Please note that if you don't specify a name of the image before the upload in Publisher, Publisher will just use the name of the file.

We can also make changes, so if we decided that we want to change the "visible" name of the image, we can do it right there by clicking on the "Edit" icon:

![](/files/-LD6N-8NH5eSYkzgNuSS)

and changing the name in the provided form:

![](/files/-LD6N-8PeQsy_W0PsDf_)

and the changes will be visible back in the Publisher:

![](/files/-LD6N-8R7rOQS6rqMowy)

Once we're done we can click on the "Submit" button to save the changes to the Article. Make sure that you have fill out all the other information in the "Main" tab.


---

# 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://xoops.gitbook.io/publisher-tutorial/4.0-operating-instructions/4.3-articles/4.3.1-images.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.