> 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/introduccion.md).

# How the website editor works

The public website's text and photos are changed in the **Studio**, the content editor (built with Sanity). You don't need to code or ask anyone.

## Signing in

1. Open `https://<club-domain>/studio`.
2. Choose how to sign in (Google, GitHub or email and password) with the Sanity account you were given. It's a different account from your CRM one.

![The Studio's sign-in screen](https://310662894-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUtfEXMFEU0mFg84Ri6hx%2Fuploads%2Fgit-blob-2a3568b4231f7722e37c1e9ef83a1e2d514f7da6%2Fstudio-login.png?alt=media)

## What's edited here and what isn't

| Edited in the Studio             | Edited in the CRM                         |
| -------------------------------- | ----------------------------------------- |
| Page text, headlines and buttons | Camp prices, weeks, days and places       |
| Photos                           | Publishing or unpublishing a camp         |
| Venues (address, map, photo)     | Forms: what people send goes to **Leads** |
| Reviews                          | Automatic emails                          |
| FAQs                             |                                           |
| The camps' welcome guide (PDF)   |                                           |

## The Studio's menu

The Studio's labels are in Spanish:

* **Páginas** (pages): one entry per website page: **Portada** (home), **Tenis**, **Pádel**, **Eventos**, **Campamentos** and **Contacto**. Each page exists only once: you don't create or delete them, only edit them.
* **Sedes** (venues): the facilities (Marbella, Mijas…).
* **Reseñas** (reviews): what families and members say.
* **Preguntas frecuentes** (FAQs): the club questions shown on the home page.

## English and Spanish

Almost every field has two boxes, **Inglés** (English) and **Español** (Spanish).

* **English is required.** You can't publish without it.
* **Spanish is optional**, but always fill it in. If it's empty, the Spanish website shows the English text.

## Editing and publishing

1. Open the page or item and change what you need. Changes save on their own as a **draft**: they're not on the website yet.
2. When it's ready, click **Publish**.
3. The website updates on its own within seconds. If you don't see the change after a couple of minutes, tell whoever maintains the website.

{% hint style="info" %}
Made a mistake? **Discard changes** drops the draft and goes back to what's published. The document's history lets you bring back an earlier version (**Restore**).
{% endhint %}

{% hint style="warning" %}
If a required field is empty, the Studio won't let you publish and marks it in red. Don't try to get round it: the website page would break without that content.
{% endhint %}


---

# 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/introduccion.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.