> 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/roadbook-pdf.md).

# Roadbook PDF

The roadbook is a **print-ready PDF travel document**: routes with auto-generated mapsheets, turn-by-turn directions, POIs, and text pages from your guidebook. Travelers download it via the Trip Link — viewable on any device, printable at home, and a reliable fallback when no smartphone is available.

App and roadbook are powered by the same guidebook content — maintain your data once, publish to both.

## Generation & updates

GUIBO generates the PDF automatically **24 hours before the download period** of the release. From that point, it is available via the Trip Link.

{% hint style="info" icon="triangle-exclamation" %}
**The PDF does not update automatically.** Changes to the release or guidebook after generation are not reflected in the existing PDF.
{% endhint %}

To apply changes, re-create the PDF manually: **Release Dashboard** → select the release → `Actions` → `Re-create PDF`.

Note: PDF Roadbooks are based on the **Master** Guidebook and are not updated for customized releases. If you personalize a Guidebook for a specific release, these changes will only appear in the App, not in the PDF. PDFs are intended as a fallback option. GUIBO's preferred channel for personalized traveler information is the App.

## Customization

Every roadbook consists of a **front cover**, **content pages**, and a **back cover**.&#x20;

<table><thead><tr><th width="163">Element</th><th>Standard (default)</th></tr></thead><tbody><tr><td><strong>Front cover</strong></td><td>Your logo, brand color, guidebook title &#x26; cover image</td></tr><tr><td><strong>Styling</strong></td><td>Custom colors</td></tr><tr><td><strong>Back cover</strong></td><td>Your own full-page image</td></tr></tbody></table>

Logo and brand color are taken from your **Account Settings**. Content pages are always generated automatically from your guidebook.

## Roadbook in B2B reselling

When you share a release with a reseller, the roadbook covers are automatically rebranded — the content pages always remain from the tour operator's guidebook.

| Release shared with reseller...     | Front cover                                    | Back cover                                     |
| ----------------------------------- | ---------------------------------------------- | ---------------------------------------------- |
| **Via GUIBO B2B Network**           | Seller's front cover                           | Seller's back cover                            |
| **Via self-managed reseller brand** | GUIBO default with seller's logo & brand color | GUIBO default with seller's logo & brand color |

#### Learn more

* [Trip Link](/publishing/trip-link.md)
* [How to publish](/publishing/how-to-publish.md)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.guibo.travel/publishing/roadbook-pdf.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
