> For the complete documentation index, see [llms.txt](https://smedai.aivd.ch/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://smedai.aivd.ch/applications/gitbook/creer/structure-du-contenu.md).

# Structure du contenu

Dans notre contexte, vous contribuez à **un espace** GitBook via une invitation. Vous y éditez des **pages**, organisées dans une **table des matières**.

{% hint style="info" %}
Les éléments « organisation », « collections », « site publié » et « domaine » sont gérés par les responsables de l’espace ou l’équipe SIC.
{% endhint %}

{% hint style="info" %}
La **création d’un espace** n’est pas en libre-service. Demandez-la à la **SIC (Stratégie de l’information et de la connaissance)** ou au **service tech**.
{% endhint %}

### Les 2 notions à connaître

* **Espace** : le conteneur d’un sujet (un projet de doc).\
  Il contient des pages, des groupes et des liens.
* **Page** : l’unité de contenu.\
  Elle peut avoir des sous-pages.

{% hint style="info" %}
GitBook peut aussi regrouper des espaces dans des **collections**. Dans la plupart des cas, vous n’avez pas à les gérer.
{% endhint %}

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-type="image">Image de couverture (sombre)</th><th data-hidden data-card-target data-type="content-ref"></th><th data-hidden data-card-cover data-type="image">Image de couverture</th><th data-hidden data-card-cover-dark data-type="image">Image de couverture (sombre)</th></tr></thead><tbody><tr><td><strong>Espaces</strong></td><td>Un espace regroupe les pages d’un même sujet. Vous êtes invité sur un ou plusieurs espaces.</td><td><a href="https://601792523-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQdlZrbfmgS8KBIQC0kYO%2Fuploads%2Fgit-blob-66188efd3a77fe8f700a0304e2d38f60ba707b2a%2FSpaces.svg?alt=media">Spaces.svg</a></td><td><a href="/applications/gitbook/creer/structure-du-contenu/espaces.md">Espaces</a></td><td><a href="https://601792523-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQdlZrbfmgS8KBIQC0kYO%2Fuploads%2Fgit-blob-5771526e13ae1cb08d2e164ed5d9b35ae8499584%2FSpaces.png?alt=media">Spaces.png</a></td><td><a href="https://601792523-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQdlZrbfmgS8KBIQC0kYO%2Fuploads%2Fgit-blob-2b52f523dab6c370cc10560e0cce8b92d0c82a35%2FSpaces%20(1).png?alt=media">Spaces (1).png</a></td></tr><tr><td><strong>Pages</strong></td><td>Une page est une unité de contenu. Vous pouvez créer des sous-pages et structurer la navigation.</td><td><a href="https://601792523-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQdlZrbfmgS8KBIQC0kYO%2Fuploads%2Fgit-blob-209dcca239298dfaf8b6c9738984190d896c292e%2FPages.svg?alt=media">Pages.svg</a></td><td><a href="/applications/gitbook/creer/structure-du-contenu/pages.md">Pages</a></td><td><a href="https://601792523-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQdlZrbfmgS8KBIQC0kYO%2Fuploads%2Fgit-blob-b052682aa4dc35ec42df196e6dbc5d8e4d554c8a%2FPages.png?alt=media">Pages.png</a></td><td><a href="https://601792523-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQdlZrbfmgS8KBIQC0kYO%2Fuploads%2Fgit-blob-666ef0c784c0ca62a319e8590ba44c282a004145%2FPages%20(1).png?alt=media">Pages (1).png</a></td></tr></tbody></table>


---

# 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://smedai.aivd.ch/applications/gitbook/creer/structure-du-contenu.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.