> 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/about-these-docs/mantener-la-documentacion.md). # Keeping them up to date These docs live in the CRM repository, in the `docs/` folder, and GitBook publishes them on its own through **Git Sync**. There's one folder per language: `docs/es/` (Spanish, the default) and `docs/en/` (English). Both have the same files with the same names, so the language selector takes you to the same page in the other language. ## Two ways to edit * **From GitBook** (no coding needed): open the page, click **Edit**, change what you need and publish. GitBook saves the change to the repository. * **From the code**: edit the `.md` files. When it's merged to `main`, GitBook updates on its own. Always change **both languages** together. To add a page, create the file in `docs/es/` and `docs/en/` with the same name and add it to both `SUMMARY.md` files (the menu's table of contents). ## Screenshots Each language has its screenshots in `.gitbook/assets/`, with the CRM in that language. A script takes them: it signs in to the CRM with the demo data, opens each screen and outlines in red the button to click. See `scripts/docs-screenshots/README.md`. * Always use the **demo data**, never real families: screenshots show names, phone numbers and medical details. * If a screen changes, retake the screenshots in both languages. * To add a screenshot by hand, save it in both languages' `.gitbook/assets/` with the same name and link it like this: `![Description](../.gitbook/assets/name.png)`. ## When to update Whenever something on screen changes (a button, a tab, a flow), update the matching page in the same code change. The pages follow the CRM's menu order: `erp/
.md`. --- # 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/about-these-docs/mantener-la-documentacion.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.