> For the complete documentation index, see [llms.txt](https://overleaf-pro.ayaka.space/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://overleaf-pro.ayaka.space/latex/es/preguntas-y-respuestas/53-how-to-organise-and-reference-sections-in-latex-documents.md).

# Cómo organizar y referenciar secciones en documentos LaTeX

Este es el octavo video de una serie de 21 de [Dr Vincent Knight](http://bit.ly/186ai3Z) la Universidad de Cardiff. Aquí vemos cómo añadir secciones y subsecciones a tus documentos de LaTeX, y cómo referirse a ellas usando los comandos \ref y \label. Al usar `\label` y `\ref` comandos, las referencias siempre apuntan a la sección correcta, incluso si cambias el orden de las secciones más adelante.

{% embed url="<https://www.youtube.com/embed/E2xT0xNk8EU>" %}

Este tutorial se basa en el [video anterior](/latex/es/preguntas-y-respuestas/74-including-titles-in-your-latex-document.md) que mostró cómo añadir los campos de título, autor y fecha al inicio de tu documento de LaTeX.

Para crear tu propia versión del archivo del video para usarla como plantilla, haz clic aquí para [abrir el ejemplo 'Sections and Referencing'](https://www.overleaf.com/latex/examples/hello-world-example/vvqkyrsyryyq).


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://overleaf-pro.ayaka.space/latex/es/preguntas-y-respuestas/53-how-to-organise-and-reference-sections-in-latex-documents.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.