> 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/en/getting-started/word-best-practices/headers-and-footers.md).

# Organize information in Word (headers, footers)

It is recommended to avoid using text boxes

## Display information

* It is recommended to avoid using text boxes
* You can create tables with invisible borders to structure your data

## Multi-column display

* Select the text in question, then, from the "Layout" tab, click "Columns"
* Choose how many columns to display

## Keep paragraphs together

* To prevent the rows of a table or the lines of a paragraph from being split across two pages, select the block concerned and right-click to open "Paragraph"
* In the "Line and Page Breaks" tab, check the "Keep with next" and "Keep lines together" boxes. Save.

![Example of paragraphs kept together](https://content.gitbook.com/content/U1Chwyf7Cc7FN9BiEh0V/blobs/fYWGyx6OT1NGhHrDLVag/bonnes-pratiques-word-3.png)

## Use page and section breaks

* Insert a page break to move cleanly to a new page
* Insert a section break to change the formatting from one section to another without affecting the entire 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/en/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.