> For the complete documentation index, see [llms.txt](https://broadcast.presidiocreative.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://broadcast.presidiocreative.com/broadcast-v3/siblings/siblings-metafields/siblings-collection.md).

# Siblings collection

> Feature introduced in Broadcast 3.5

The second required metafield is **`theme.siblings`**&#x20;

```
theme.siblings
```

The **content type** is: Single line text and One value.&#x20;

This metafield maps each product to the correct collection handle for the siblings.&#x20;

Start by defining a **Products** metafield and name it **Siblings**. Then change the Namespace from `custom` to `theme` and the key to simply `siblings`.&#x20;

{% hint style="info" %}
Important steps:

* Rename **`custom`** to **`theme`**
* The key should be **`siblings`**
  {% endhint %}

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

Next, add a description. You can name this one *Collection handle for siblings*. Then click on **Select content type** and choose **Single line text** and **One value**:

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

**Save** the definition.&#x20;

### Check the saved metafield

Your second metafield should look like this:

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

{% hint style="success" %}
Please ensure you change the Namespace and key to this custom version for Pipeline:\
\
\&#xNAN;**`theme.siblings`**\
\
By default, the namespace begins with **`custom`**. This will need to be changed to **`theme`**&#x20;
{% endhint %}

### Product setup

Next, we will use these newly defined metafields in the Product Setup for each product:

{% content-ref url="/pages/3AzWzLNIuo8fNMSH5s0P" %}
[Siblings product setup](/broadcast-v3/siblings/siblings-product-setup.md)
{% endcontent-ref %}


---

# 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://broadcast.presidiocreative.com/broadcast-v3/siblings/siblings-metafields/siblings-collection.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.
