> 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/sedes-resenas-faq.md).

# Venues, reviews and FAQs

These three work as lists: you can create, edit and delete items. The **Orden** (order) field decides the order they appear in on the website: the lowest number comes first.

## Sedes (venues)

Each venue has:

* **Nombre** (name).
* **Identificador** (identifier): `marbella` or `mijas`.
* **Dirección** (address) and **Enlace de Google Maps** (Google Maps link).
* **Superficies de pista** (court surfaces), for example "Clay and hard court".
* **Descripción** (description): the text on its card on the home page.
* **Foto** (photo).
* **Deportes** (sports): tennis, padel or both.
* **Orden** (order).

Venues show on the home page, in the venues section.

{% hint style="danger" %}
**Don't change a venue's Identificador**: the website uses it internally, and if it changes the venue can no longer be found.
{% endhint %}

## Reseñas (reviews)

* **Texto** (text): what the person says, in English and Spanish.
* **Quién lo dice** (who says it): their name.
* **Rol** (role), for example "Family, Marbella" or "Member".
* **Orden** (order).

They show on the home page and the camps page.

## Preguntas frecuentes (FAQs)

* **Pregunta** (question) and **Respuesta** (answer), in English and Spanish.
* **Orden** (order).

These are the **club's** questions and show on the home page. The camp's questions are edited inside the **Campamentos** page.

## Creating a new item

1. In the menu, go to **Sedes**, **Reseñas** or **Preguntas frecuentes**.
2. Click the create button (✏️ / **+**).
3. Fill in the fields, at least the English ones.
4. Click **Publish**.


---

# 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/sedes-resenas-faq.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.