> For the complete documentation index, see [llms.txt](https://university.gonexa.fr/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://university.gonexa.fr/doc/getting-started/word-best-practices/headers-and-footers.md).

# Organiser l'information dans Word (en-têtes, pieds de page)

Il est recommandé d'éviter d'utiliser des zones de textes

## Afficher de l'information

* Il est recommandé d'éviter d'utiliser des zones de textes
* Vous pouvez créer des tableaux à bordures invisibles pour structurer la donnée

## Affichage multi colonnes

* Sélectionnez le texte concerné, puis, depuis l'onglet "Mise en page", cliquez sur "colonnes"
* Choisissez le nombre de colonnes à afficher

## Créer des paragraphes solidaires

* Pour éviter que les lignes d'un tableau ou d'un paragraphes ne se coupent entre deux pages, sélectionnez le bloc à scinder, et via le clic droit accédez à "paragraphes"
* Dans l'onglet enchainement, cochez la case "paragraphes solidaires et lignes solidaires". Enregistrez.

![Exemple de paragraphes solidaires](https://4198981723-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTYUzkIngX1MnHE8kOJDR%2Fuploads%2FEIl2gS2OKGsjvKtbzGSV%2Fbonnes-pratiques-word-3.png?alt=media)

## Utiliser des sauts de page et de section

* Insérez un saut de page pour passer à une nouvelle page proprement
* Insérez un saut de section pour modifier la mise en forme d'une section à une autre sans affecter tout le document


---

# 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://university.gonexa.fr/doc/getting-started/word-best-practices/headers-and-footers.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.