> 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/paginas.md). # The pages, one by one Every page shares some blocks. Those come first, then what's specific to each page, with a screenshot of how it looks on the website. Field names are given as the Studio shows them (in Spanish), with the English in brackets. ## Blocks that repeat **SEO** * **Título** (title): shown in the browser tab and on Google. Best under 60 characters. * **Descripción** (description): the paragraph Google shows under the title. Best under 160 characters. **Cabecera** (header): the top of the page. * **Antetítulo** (eyebrow): the small line above the headline. * **Titular** (headline). On the home and camps pages it's two lines: **Titular (primera línea)** and **Titular (segunda línea)**. * **Texto** (text). * **Foto de fondo** (background photo). **Bloque de cierre** (closing block): the block at the end with **Titular**, **Texto** and **Botón** (button). Tennis, padel, events and camps have it. **Tarjetas** (cards): each card has **Título**, **Texto** and, optionally, an **Etiqueta** (tag): the lime pill, for example "Ages 4 to 16" or "One to one". ## Portada (home) ![The home page](https://310662894-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUtfEXMFEU0mFg84Ri6hx%2Fuploads%2Fgit-blob-0efa7c53edaeaa95b27ff9fa8ad9482e87ab7df8%2Fsite-home.png?alt=media) | Field | What it is | | --------------------------------------------------- | ---------------------------------------------------------------------------------- | | **Cifras** (figures) | The highlighted numbers ("3", "10+", "600+"…) with their text. | | **Sección de sedes** (venues section) | The headline and text above the venue cards. Venues are edited under **Sedes**. | | **Qué hacemos todo el año** (what we do all year) | Four cards **in this order**: tennis, padel, events and camps. | | **Banda del Summer Camp** (Summer Camp band) | Eyebrow, headline, text, the Marbella button and a photo. | | **Hazte socio** (become a member) | Eyebrow, headline, text, bullet points and a photo. | | **Reseñas** (reviews) | Only the headline and the note on the right. Reviews are edited under **Reseñas**. | | **Preguntas frecuentes** (FAQs) | The headline and text. The questions are edited under **Preguntas frecuentes**. | | **Clientes y colaboradores** (clients and partners) | The title and the list of names. | ## Tenis (tennis) ![The tennis page](https://310662894-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUtfEXMFEU0mFg84Ri6hx%2Fuploads%2Fgit-blob-09aba47c114befb66ac99dc8671f05d768a55c59%2Fsite-tennis.png?alt=media) * **Titular de los programas** and **Programas** (programmes): four cards. The last one is drawn on green. * **Botón de los tres primeros** (button on the first three) and **Botón del cuarto** (button on the fourth). * **Superficies** (surfaces): eyebrow, two-line headline, text and photo. ## Pádel (padel) ![The padel page](https://310662894-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUtfEXMFEU0mFg84Ri6hx%2Fuploads%2Fgit-blob-6f6a7731b92c2cc790f8ef41b68bc34090a07099%2Fsite-padel.png?alt=media) * **Bloque de clases** (classes block): headline, text, two cards (private and group), a button and **Foto central** (centre photo), which sits between the two cards. ## Eventos (events) ![The events page](https://310662894-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUtfEXMFEU0mFg84Ri6hx%2Fuploads%2Fgit-blob-10e0e9c457d494339b51b3894cb33d0b09bd8c7c%2Fsite-events.png?alt=media) * **Titular de qué organizamos** and **Qué organizamos** (what we organise): cards with what we organise. * **Lo que viene** (what's coming): headline, note and cards for upcoming events. Each has a tag, title, text, photo and **Enlace** (link): a path on the website, for example `/camps`. ## Campamentos (camps) ![The camps page](https://310662894-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUtfEXMFEU0mFg84Ri6hx%2Fuploads%2Fgit-blob-283ce53bdc51f4e0e3168089224528f7a98c9145%2Fsite-camps.png?alt=media) {% hint style="warning" %} Only text and photos are edited here. **Prices, weeks and places come from the CRM** (see [Camps](/guia/en/crm-erp/campamentos.md)). {% endhint %} | Field | What it is | | ---------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Botón principal de la cabecera** (main header button) | Scrolls down to "Choose your camp". | | **Botón secundario de la cabecera** (second header button) | Scrolls down to the facility visit form. | | **Cifras** (figures) | The white band under the header ("11", "3–16", "600+"…). | | **La experiencia** (the experience) | Eyebrow, headline, two paragraphs, ✓ points and a photo. | | **Actividades** (activities) | Headline, text and the list of activities. They're drawn in a grid of three, so nine activities make a neat square. The photo is optional: without one the card is green with the number, which is better than a photo of a different activity. | | **Un día en el camp** (a day at camp) | Text and **Horario** (schedule: time and what happens). | | **Elige tu camp** (choose your camp) | Only the headline and text. Each camp's card comes from the CRM. | | **Banda lima** (lime band) | For siblings and several weeks: headline, text and button. | | **Equipo y seguridad** (team and safety) | Text, photo and the blocks below. | | **Galería** (gallery) | Five photos. The first is shown double size. | | **Qué traer** (what to bring) | The list and the footnote. | | **Entrada y recogida** (drop-off and pickup) | Rows with a label and a value, for example "Drop-off · 9:00". | | **Reseñas** (reviews) | Only the headline. | | **Preguntas frecuentes** (FAQs) | The **camp's** questions. They're kept separate from the club questions on the home page. | | **Bloque de cierre** (closing block) | Headline, text, main button, WhatsApp button and photo. | | **Guía de bienvenida (PDF)** (welcome guide) | One PDF in Spanish and one in English. | {% hint style="info" %} The **welcome guide** is added as a button to the registration emails and to the day-before email. If one of the two languages is missing, the email in that language goes without the button. {% endhint %} ## Contacto (contact) ![The contact page](https://310662894-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUtfEXMFEU0mFg84Ri6hx%2Fuploads%2Fgit-blob-da7037dcd828aef6c109549930394562fa7c2488%2Fsite-contact.png?alt=media) Eyebrow, headline, text, **Título del formulario** (form title) and the message people see after sending the form (headline and text). --- # 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/paginas.md?ask=&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.