> For the complete documentation index, see [llms.txt](https://docs.guibo.travel/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.guibo.travel/content-management.md).

# Content Management

- [Overview](https://docs.guibo.travel/content-management/overview.md): With GUIBO's centralized content management tour operators maintain product updates only once but publish across multiple channels: Tour Guide App, Roadbook PDF, TourMaps for Webshop, API, B2B Network
- [Language & Translation](https://docs.guibo.travel/content-management/language-and-translation.md): Managing Guidebooks in Multiple Languages in GUIBO
- [Integrate External Content](https://docs.guibo.travel/content-management/integrate-external-content.md): Already managing content in another system? Decide which integration approach fits your setup so you only have one single point of truth for your data.
- [When using template based releases](https://docs.guibo.travel/content-management/integrate-external-content/when-using-template-based-releases.md): How to integrate external content when your itinerary is defined in GUIBO — so your external system stays the single source of truth.
- [When using on-demand releases](https://docs.guibo.travel/content-management/integrate-external-content/when-using-on-demand-releases.md): How to integrate external content when the itinerary is managed in your external system — so your external system stays the single source of truth.
- [Set up library sync](https://docs.guibo.travel/content-management/integrate-external-content/set-up-library-sync.md): How to sync routes, POIs, and text pages from a third-party system into GUIBO libraries — so your external system stays the single source of truth.


---

# 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.guibo.travel/content-management.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.