> 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/content-management/overview.md). # Overview ## **Overview** GUIBO is built on one idea: **create your content once as reusable building blocks, then assemble it into travel itineraries.** Update a building block in one place, and every itinerary using it updates automatically — ready to publish across the Tour Guide App, Roadbook PDF, TourMaps, API, and B2B Network. Five terms describe everything in GUIBO content management:
TermWhat it is
Building blockA reusable piece of content: a route, POI, text page, or destination
LibraryA collection that stores building blocks for reuse across itineraries
Guidebook TemplateA complete, reusable travel itinerary — building blocks arranged in sequence by stages
StageA step in the itinerary (e.g. one day) that puts building blocks in order
ReleaseOne booking — a guidebook generated from the template with booking-specific details added
{% hint style="info" %} **Building blocks are the pieces. Libraries and guidebooks are the containers that hold them.** Keep that one distinction in mind and the rest of GUIBO falls into place. {% endhint %} ### Building blocks Building blocks are the reusable pieces of content you assemble into guidebook templates. They come in two families: **geo assets** (anything on the map) and **text pages**. #### Geo assets | Geo asset | Description | Used for | | --------------------- | ---------------------------------------------------------------------------------------------- | ------------------------------------------------- | | **Route** | A path from A to B with turn-by-turn navigation for biking and hiking. | App navigation, roadbook mapsheets, overview maps | | **Point of Interest** | Anything travelers care about along the way — hotel, sight, restaurant, monument. | Tour Guide App, roadbook | | **Transfer route** | An orientation-only path, not meant for turn-by-turn navigation (bus, train, boat, ferry). | Overview maps | | **Destination point** | Marks where a stage ends and anchors booking-specific accommodations. Managed as a map marker. | Stage destinations, accommodation assignment | #### Text pages Text pages hold structured information — descriptions, tips, arrival instructions, FAQs — with headings, images, and links. Use them for anything that isn't tied to a specific point on the map. ### Libraries A **library** is where you store building blocks so you can reuse them across many guidebook templates. Instead of rebuilding the same route or hotel in every itinerary, you maintain it once in a library and reference it wherever it's needed. {% hint style="info" %} **Maintain once, update everywhere.** Change a building block in its library and every guidebook template that references it updates automatically — no manual rework. {% endhint %} Two library types match the two building-block families:
Library typeStores
Geo libraryRoutes, POIs, transfer routes, destination points
Text libraryText pages and their images
Create as many libraries as you need to stay organized — for example, one for hiking routes, one for cycling routes, and one for hotels. #### Bringing library content into a guidebook template Guidebook templates pull building blocks from libraries in two ways: | Method | Used for | How it works | | ----------------------- | -------- | ------------------------------------------------------------------------------- | | **Manual referencing** | Routes | Pick specific building blocks from a library and import them into a stage | | **Dynamic referencing** | POIs | Connect a POI library — GUIBO automatically pulls in every POI near your routes | Both methods create **references, not copies**. The guidebook template always reads the current version from the library. ### Guidebook templates A **guidebook template** is one complete travel itinerary. It holds your building blocks — stored directly in the template or referenced from libraries — and arranges them in sequence using **stages** (for example, one stage per day). The stage order is what turns a set of routes and POIs into a day-by-day trip. A guidebook template on its own isn't tied to any booking. That happens at release. See [Create your first guidebook](https://docs.guibo.travel/get-started/getting-started/create-your-first-guidebook) for a step-by-step walkthrough. ### From template to traveler To deliver an itinerary for a specific booking, you publish a **release**. The release generates a guidebook from the template and adds the booking-specific details on top — accommodations, travel dates, and documents. One booking always results in one release. Where your building blocks live — in GUIBO, in another system, or a mix — is your choice. See [Integrate External Content](/content-management/integrate-external-content.md) to find the right setup, and How to publish to turn templates into releases. --- # 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: ``` GET https://docs.guibo.travel/content-management/overview.md?ask= ``` 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.