> For the complete documentation index, see [llms.txt](https://docs.echevarrisports.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.echevarrisports.com/guia/en/website-sanity/imagenes.md).

# Photos and PDFs

## Uploading a photo

1. Click the photo field and drag the image in, or pick it from your computer.
2. If the photo was uploaded before, find it in the gallery instead of uploading it again.

## Choosing what shows (the hotspot)

The same photo is cropped differently on a phone and on a computer. So that a face or the important part isn't cut off:

1. Click the pencil or crop icon on the photo.
2. Move the **hotspot** to what must always be visible.
3. If needed, adjust the crop box.

## Tips

* **Format**: JPG for photos, and PNG only if there's transparency.
* **Size**: about 2000 px wide is plenty. A 10 MB photo slows the website down without looking any better.
* **Photos of children**: only use photos of children whose families gave photo consent. You can check it in the CRM, in the child's camp panel.
* **Activity photos**: if you don't have a real photo of that activity, it's better to use none.

## The welcome guide PDF

In **Campamentos › Guía de bienvenida (PDF)** upload one PDF under **Español** and another under **English**. To change it, upload the new one in the same field and click **Publish**: the emails start sending the new one straight away.


---

# 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.echevarrisports.com/guia/en/website-sanity/imagenes.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.