> 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/get-started/getting-started/guidebook-structures.md).

# Guidebook structures

Every guidebook follows one of two structures. Your choice determines **how you build content** — and how accommodations and content appear in the Tour Guide App.

## How is your trip structured?

<table data-header-hidden><thead><tr><th width="185.015625"></th><th></th><th></th></tr></thead><tbody><tr><td></td><td><strong>Itinerary-based</strong></td><td><strong>Collection-based</strong></td></tr><tr><td><strong>Structure</strong></td><td>Stages = day programs</td><td>Categories = curated collections</td></tr><tr><td><strong>Best for</strong></td><td>Multi-day tours with a set program; star trips</td><td>Location stays with recommendations for the area</td></tr><tr><td><strong>Example</strong></td><td>Point-to-point cycling tour; hub-and-spoke hiking week</td><td>Outdoor stay with restaurant, route &#x26; activity tips</td></tr><tr><td><strong>Accommodations in the app</strong></td><td><p>Accommodation list <strong>+</strong></p><p>Per day as check-in / check-out</p></td><td>Accommodation list only</td></tr></tbody></table>

### Itinerary-based guidebooks

The guidebook is divided into **stages** — one stage is typically one day's program. This is the standard for multi-day trips with a set program.

It covers two variants:

* **Point-to-point** — a different destination, and usually a different hotel, each day.
* **Star trips** — day-trip suggestions from a single base; the same hotel every night.

Days can also exist **without a program** — for example, extra nights booked at a destination.

### Collection-based guidebooks

The guidebook holds **categories of curated assets** — e.g. restaurant tips, hiking routes, or other activities. This is the standard for **location stays** with no daily itinerary, just recommendations for the surrounding area.

Travelers browse by category instead of following a day-by-day plan.

### What this means for accommodations

The structure decides how hotels reach the traveler:

* **Itinerary-based** — GUIBO places the right hotel on each day automatically, using destination points. Travelers see a **check-in and check-out** hotel per day, plus the full list.
* **Collection-based** — there are no travel days, so the per-day display is switched off. Every hotel still appears in the accommodation list.

[Click here](broken://pages/dCpXCx6xVKUTP5vue8ZG) for more information on personalized accommodations.


---

# 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/get-started/getting-started/guidebook-structures.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.