> 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/publishing/how-to-publish.md).

# How to publish?

Publishing in GUIBO means delivering content — maintained once — to travelers across every channel, from a single point of truth.

GUIBO's leading principle is **single point of truth**: content is maintained **once** and published everywhere. This strictly avoids manual content duplication — the main driver of channel-by-channel and season-by-season maintenance work.

Publishing therefore means **how to deliver that content across all required channels** — without ever maintaining it twice.

GUIBO can even publish content that is maintained in an **external system**, so your existing tools stay the single point of truth. See [Integrate External Content](/content-management/integrate-external-content.md).

#### Publishing channel overview

<table><thead><tr><th width="219.9140625">Channel</th><th>What the traveler gets</th></tr></thead><tbody><tr><td><a href="/publishing/trip-link.md"><strong>Trip Link</strong></a></td><td>One personalized weblink to access all booking data and travel documents.</td></tr><tr><td><a href="/publishing/tour-guide-app.md"><strong>Tour Guide App</strong></a></td><td>Personalized, customized itinerary with accommodations, offline maps, navigation, and real-time updates.</td></tr><tr><td><a href="/publishing/roadbook-pdf.md"><strong>Roadbook PDF</strong></a></td><td>Printable PDF with the detailed itinerary — text content and detailed map sheets.</td></tr><tr><td><a href="/publishing/b2b-network.md"><strong>B2B Network</strong></a></td><td>Share releases with resellers so they can forward a re-branded Trip Link to the traveler.</td></tr><tr><td><a href="/publishing/tourmaps-for-webshop.md"><strong>TourMaps</strong></a></td><td>Interactive overview maps for website embedding — guidebook-level, not booking-specific.</td></tr></tbody></table>

## **What's next?**

Travel documents are delivered to travelers through **Releases** — one is created in GUIBO for each booking. See [Releases](/publishing/how-to-publish/how-to-publish.md).&#x20;


---

# 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/publishing/how-to-publish.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.