# Overview

## **Guidebooks**

Each Guidebook in GUIBO represents one travel product and contains all content relevant to that tour. Guidebooks serve as containers that either store content assets directly (e.g. POIs, routes, text pages)  or reference content assets from libraries for optimal content reuse.

## Libraries

In libraries you can store content that's used across multiple travel products (e.g. generic operator or agency text pages, POIs relevant for products). Storing content in libraries instead of guidebooks centralizes updates, reducing the need to modify multiple guidebooks. Create as many libraries as you want to structure your data (e.g. one for hiking routes, one for cycling routes, one for hotels) .

* **Text Libraries**\
  Text Libraries contain reusable text and image content. 
* **Geo Libraries**\
  Geo Libraries store geo assets (e.g. routes, POIs) that appear in multiple travel products. 

### Importing library assets into guidebooks

1. **Manual referencing**\
   Choose specific assets from a library and import them into the guidebook
2. **Dynamic referencing**\
   All POIs in the library that are located near one of the routes in the guidebook are then automatically imported into the guidebook.

## Content Asset Types

Content types are the building blocks for your guidebooks. GUIBO distinguishes between geo assets and text pages.

### Geo Assets

<table><thead><tr><th width="187">Geo Asset Type</th><th>Description</th></tr></thead><tbody><tr><td><strong>Point of Interest (POI)</strong></td><td><p>Any point of interest for travelers (e.g. hotel, sightseeing spot, restaurant, cultural monument). Typically relevant for</p><ul><li>tour guide app</li><li>roadbook</li></ul></td></tr><tr><td><strong>Routes</strong></td><td><p>Predefined routes from A to B with turn-by-turn navigation for biking and cycling. Typically relevant for</p><ul><li>tour guide app navigation</li><li>mapsheets within the roadbook</li><li>overview maps for roadbook and webshop</li></ul></td></tr><tr><td><strong>Transfer Routes</strong></td><td><p>Transfer routes that provide orientation for the traveler but are not intended for turn-by-turn navigation (e.g. bus, train, boat, ferry, etc.). Typically relevant for</p><ul><li>overview maps for roadbook and webshop</li></ul></td></tr><tr><td><strong>Markers</strong></td><td><p>GEO markers are for internal purposes and are not visible to travelers. Typically relevant for </p><ul><li>assigning booking specific hotels</li></ul></td></tr></tbody></table>

### **Text Pages**

Text Data in GUIBO consists of structured content with hierarchical organization, embedded images, and links. This content provides travelers with essential information about their journey beyond geographical data.


---

# Agent Instructions: 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:

```
GET https://docs.guibo.travel/content-management/overview.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.