> For the complete documentation index, see [llms.txt](https://docs.amondo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.amondo.com/getting-started/core-platform-concepts/collections.md).

# Collections

A **Collection** is where content in Amondo's back-end is organised and managed. Every piece of content, whether created or sourced, is stored inside a Collection before it can be displayed in an Imprint. Collections act as the central workspace where teams can review, manage and prepare content for publishing.

### Purpose of Collections

Collections serve three main purposes:

1. **Storage** – they hold all content items that a team has created or imported.
2. **Organisation** – they provide a structured way to manage content, making it easier to curate and prepare for publishing.
3. **Connection** – they can be linked to one or more Imprints, allowing the same content to be reused across multiple experiences.

### Working with Collections

* Each Collection has its own name and appears in the Collections list for users with access.
* Collections can be connected to one or more Imprints, meaning content can be published in different formats without duplication.
* Collections can be created for different campaigns, projects or teams to keep content separate and manageable.

### Collections and Imprints

Imprints are the layouts or formats used to display content. Collections provide the source content that Imprints draw from. By connecting a Collection to an Imprint, you make its content available for use in galleries, carousels, stories or displays.

### Related

* [Imprints](/getting-started/core-platform-concepts/imprints-and-formats.md)
* [Tiles](/getting-started/core-platform-concepts/tiles.md)