> For the complete documentation index, see [llms.txt](https://pipeline.groupthought.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://pipeline.groupthought.com/siblings/product-siblings/siblings-collection.md).
# Siblings collection
Metafield editor
> Feature introduced in Pipeline 6.2
The second required metafield is **`theme.siblings`**
```
theme.siblings
```
The content type is **Single line text** and **One value**.
This metafield maps each product to the correct collection handle for the siblings.
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`.
{% hint style="info" %}
Important steps (**two** changes):
* Rename **`custom`** to **`theme`**
* Rename the key to **`siblings`**(Be sure to change from siblings\_collection to simply siblings)
{% endhint %}
Two Changes required in the Namespace and key
Next, add a description. You can name this one *Collection handle for siblings*.
Then click on **Select content type** and choose **Single line text** as the type and **One value**:
**Save** the definition.
### Important - Check the saved metafield
Your second metafield should look like this:
{% hint style="success" %}
Please ensure you change the Namespace and key to this custom version for Pipeline:\
\
**`theme.siblings`**\
\
By default, the namespace begins with**`custom`**. This will need to be changed to**`theme`** and also **trim** the **key** to just**`siblings`**.
{% 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
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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://pipeline.groupthought.com/siblings/product-siblings/siblings-collection.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
