# Siblings collection

> Feature introduced in Pipeline 6.2

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 collection**. Then change the Namespace from `custom` to `theme` and the key to simply `siblings`.&#x20;

{% hint style="info" %}
Important steps (**two** changes):

* Rename <mark style="color:red;">**`custom`**</mark> to <mark style="color:green;">**`theme`**</mark>
* Rename the key to <mark style="color:green;">**`siblings`**</mark>(Be sure to change from siblings\_collection to simply siblings)
  {% endhint %}

<figure><img src="/files/kPdfH69Oefd9mjTXsN6M" alt=""><figcaption><p><strong>Two Changes required in the Namespace and key</strong></p></figcaption></figure>

Next, add a description. You can name this one *Collection handle for siblings*.&#x20;

Then click on **Select content type** and choose **Single line text** as the type and **One value**:

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

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

### Important - Check the saved metafield

Your second metafield should look like this:

<figure><img src="/files/gH6xq7iNzK2X500xrEBS" 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<mark style="color:red;">**`custom`**</mark>. This will need to be changed to<mark style="color:green;">**`theme`**</mark> and also **trim** the **key** to just<mark style="color:green;">**`siblings`**</mark>.&#x20;

&#x20;
{% endhint %}

The content type is **Single line text** and **One value**.

### Product setup

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

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


---

# Agent Instructions: 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://pipeline.groupthought.com/siblings/product-siblings/siblings-collection.md?ask=<question>
```

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.
