> For the complete documentation index, see [llms.txt](https://docs.maker.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.maker.co/maker-pages/get-started/using-collections.md).

# Using collections

<figure><img src="/files/rQm9w1xeldC6q649Ecmo" alt=""><figcaption></figcaption></figure>

Creating collections

Adding to a collection

Embedding collections

<figure><img src="/files/nPtgqn1Bo5AYNxlMws2j" alt=""><figcaption></figcaption></figure>

With the Stories Manager open, you'll see the Collections panel on the left.

Here you'll find the default collections and any custom collections your team has created. Click on a specific collection name to see its respective stories.

You can use collections to address two main objectives:

1. Internal organization
2. Live embedding

To use collections for internal organization, create as many collections as needed to which you and your team can gradually add relevant stories.

To use collections to embed on your site as part of a UGC or related story grid , create and curate collections as before before following the embed instructions below.


---

# 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.maker.co/maker-pages/get-started/using-collections.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.
