# When using guidebook-based releases

## When to use this

You manage routes, POIs, or text content in a third-party system and want to use that data as building blocks in GUIBO to manage your guidebooks.

Continue reading [here](https://docs.guibo.travel/content-management/integrate-external-content/broken-reference), when you are not only managing assets in a third party system but also managing the trip structure on a booking level in another system (so you do not need to manage guidebooks in GUIBO). 

<table><thead><tr><th width="248.01953125">Your situation</th><th>What to do</th></tr></thead><tbody><tr><td><strong>Routes managed in another geo system</strong></td><td>Sync routes into a GUIBO library via API</td></tr><tr><td><strong>Hotels/POIs managed in a booking system</strong></td><td>Sync POIs into a GUIBO library via API</td></tr><tr><td><strong>Text content managed in a CMS</strong></td><td>Sync text pages into a GUIBO library via API</td></tr><tr><td><strong>Some content external, some in GUIBO</strong></td><td>Libraries managed in GUIBO and synced libraries work side by side — libraries behave identically regardless of how they were filled</td></tr><tr><td><strong>All content managed in GUIBO</strong></td><td>No integration needed</td></tr></tbody></table>

## How it works

Your external content is synced into GUIBO libraries. These libraries feed into your guidebooks — just like manually managed content.

```
External system → Sync → GUIBO libraries → Guidebooks → Personlaized Releases (per booking)
```

## Step 1: Sync your content into libraries

Set up a nightly sync that pushes routes, POIs, and text pages from your external system into GUIBO libraries.&#x20;

See [Set up library sync](https://claude.ai/chat/set-up-library-sync.md) for the complete setup.

## Step 2: Build guidebooks from synced libraries

Guidebooks pull content from libraries through two methods:

<table><thead><tr><th width="213.27734375">Method</th><th width="131.85546875">Used for</th><th>How it works</th></tr></thead><tbody><tr><td><strong>Manual referencing</strong></td><td>Routes</td><td>Import specific routes from a library into each day/stage category</td></tr><tr><td><strong>Dynamic referencing</strong></td><td>POIs</td><td>Connect a POI library to a guidebook — GUIBO automatically imports all POIs near the routes</td></tr></tbody></table>

Both methods create **references, not copies**. The guidebook always reads the current version from the library.

Typical setup per guidebook:

1. Create day/stage categories (Day 1, Day 2, …)
2. Import routes per category via **manual referencing** from your routes library
3. Connect your POI libraries — GUIBO pulls relevant POIs via **dynamic referencing**

See [Create your first guidebook](https://claude.ai/get-started/getting-started/create-your-first-guidebook.md) for the step-by-step walkthrough.

### What happens when content changes in an external system

Because guidebooks reference library content, every change in a library is automatically reflected in all connected guidebooks:

<table><thead><tr><th width="252.69140625">What changes in the library</th><th>What happens in guidebooks</th></tr></thead><tbody><tr><td>Route updated</td><td>All guidebooks referencing that route show the updated version</td></tr><tr><td>POI added</td><td>Dynamically referenced guidebooks pick up the new POI if it is near a route</td></tr><tr><td>POI removed</td><td>Dynamically referenced guidebooks no longer show the removed POI</td></tr><tr><td>POI updated</td><td>All guidebooks referencing that POI show the updated version</td></tr><tr><td>Text page updated</td><td>All guidebooks referencing that text page show the updated version</td></tr></tbody></table>

No manual updates to individual guidebooks required.

## Step 3: Create releases per booking

Once your guidebooks are set up, create releases per booking — via the web portal or automated via API.

See [How to publish](https://docs.guibo.travel/publishing/how-to-publish) for the API documentation.