Content library

Your content library is the catalog of things you sell. When you build an itinerary, you drag items out of the library into the day plan. The library exists so you only have to describe a lodge or an activity once, then reuse it forever.

What goes in the library

• Accommodations. Lodges, camps, hotels, mobile camps, anything you book clients into.
• Activities. Game drives, walking safaris, balloon flights, cultural visits, snorkeling.
• Images. A shared image bucket used by accommodations, activities, and proposals.

Rate-related data (per-night prices, seasonal pricing, vehicle costs) lives separately in Rate cards. That separation lets the same accommodation reuse multiple seasonal rates and lets you update prices without touching descriptions.

Curation, not bulk import

We deliberately don't ship a pre-populated database of every lodge in Africa. Two reasons:

1. Lodges change names, owners, room counts, and meal plans constantly. A static database goes stale.
2. Operators sell a small, curated set of lodges they have relationships with. A bloated dropdown of 2,000 options is worse than a clean list of 30.

So you'll add the lodges you actually sell. Most operators end up with 20 to 100 accommodations in their library.

Tips for a healthy library

• Write descriptions in your brand voice. They appear verbatim on every proposal.
• Upload at least two images per accommodation. Proposals look thin with one.
• Tag accommodations with style (luxury, mid, budget) and location (park, region). Tags speed up filtering in the itinerary builder.
• Archive, don't delete. If a lodge closes or you stop selling it, archive it. Past itineraries that reference it still need to render.

Sharing across workspaces

Library content is workspace-scoped. If you have multiple brands and want to share a master content library, contact support — we can set up a shared parent workspace for you.